On Tue, Dec 13, 2011 at 7:55 PM, HansBKK <[email protected]> wrote:
> These would be IMO most ideal - allow the user to choose delimiter
> characters either in mySettings or within the outlines
>
> Given widespread support for extended character sets and unicode, it then
> becomes trivial (for the user) to select characters guaranteed not to
> conflict with the source content.
>
> However if this will be a difficult to implement, and the issue hasn't been
> a significant problem for decades, then a quicker fix that handles most use
> cases would be worth further complicating the differences between the
> different @ <file> directives.
When I awoke this morning I had ideas similar to yours.
A new directive, similar to @delims, and handled in about the same
way, will be easier to code and better for the user. There should be
no need for user settings: indeed: such settings could cause problems.
There *is* a place in the external file for the information, namely in
the sentinel line that represents the new directive, say::
@section-delims <<< >>>
The sentinel would be (for Python)::
#@@section-delims <<< >>>
To repeat, this will work like @delims, so that one could change
section delims many times in an external file. It's much safer than
@delims because the *comment* delims don't change, so no matter what
happens the result will always be a valid source file, in our example,
a valid Python file.
I plan to do this today. First, though, I'll disable section handling
entirely for @auto imports. It makes no sense to support section
references in @auto!
Edward
P.S. Leo used to support @noref, but here a new directive is better
than yet another @<file> type. So this is progress...
EKR
--
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.
