On Mon, Dec 12, 2011 at 11:39 PM, Terry Brown <[email protected]> wrote:
> If there isn't already a way to disable any special treatment of << and
>>> there should be,
Use @asis or @nosent instead of @auto or @file.
> I wonder if Edward has this thread parked in his to-read pile.
Full bug-fixing mode means I save most discussions for later.
> Anyway, if it turns out there isn't, file a bug report to make sure it gets
> added.
I made a conscious decision, which I never regretted, not to support
any escape mechanism for << and >>. The problem is that escapes do
*not* appear explicitly in the external file. That's the whole
purpose of escapes! Thus, the read code must (somehow!) recreate
escapes in the *outline*.
But how to do this? We don't want to do AI in the read code.
Experience with earlier versions of Leo (15+ years ago) shows that
this greatly complicates the read code and makes it much more fragile.
So we want to represents escapes *explicitly* in the external file. Alas,
the only place for their representation would be in sentinels, but we
don't want to break lines for sentinels because that would cause other
problems.
In short, there is no good way to fix the problem directly.
It would be possible to use other delimiters for section references,
say <<< and >>>. This could be done by adding another argument field
to @+leo sentinel lines. A new directive would be required::
@ref-delims <<< >>>
This probably could work relatively cleanly, but it would be a
significant change to Leo.
Finally, a new setting would specify default section reference delims.
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.
