On Tue, May 11, 2010 at 1:23 PM, Gour <[email protected]> wrote: > Some applications (e.g. LyX) which has their own file-format, hide > the 'sentinels' and display only clear content - that's similar to > Leo.
Yes. This is similar to the idea I floated earlier. We want an algorithm that allows the user to edit text without seeing the sentinels, but preserving the sentinels in the end. To repeat the general idea: the algorithm would never insert sentinels, and would delete sentinels only in begin/end pairs. Clearly, such an algorithm is possible. I might even do a prototype. The problem, alas, is building such an algorithm into vim, emacs, eclipse, etc. For that, I think we need "native" users of those tools. > However, if one wants to have docs under VCS, it is not so pretty to > look at in a 'ascii' editor. > > This, of course, means to have front-end which is same for everybody > which is not possible with the source code files. Exactly. > Are you aware of Haskell language? Yes. > It requires that some 'intelligence' in embedded in the Haskell > compiler in order to do that which compilers for other languages > cannot do due to various reasons. > > Maybe here lies the secret how to do it...Don't ask me more. I do not > know the answer now... The title of another thread is "the right kind of magic". I am completely sure that there is no magic that will recreate sentinels in all situations. Indeed, the proof is trivial: in Leo the user has the option of inserting sentinels in arbitrary places. Thus, there is *no way* that any algorithm can recreate those sentinels, because the algorithm would have to recreate arbitrary user choices. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
