On Feb 10, 9:13 am, "Edward K. Ream" <[email protected]> wrote:
> > The limitations of previous statement would be mitigated if Leo
> > implemented native 'sessions' or 'projects' wherein I could call
> > Leo with a session name, the session consisting of the names
> > and current nodes of a set of Leo files.
>
> An interesting idea. However, I think that scanning the command line
> for paths ending in leoSettings.leo and myLeoSettings.leo gives
> complete flexibility.
Drat. This isn't strictly true. To get this "ultimate" flexibility
one needs to avoid loading the setting file.
Suppose Leo supports two new command-line options, say::
--leo-settings=<path to any leo file>
--my-leo-settings=<path to any leo file>
These arguments would have "supreme" priority: they would supersede
even myLeoSettings.leo and leoSettings.leo files that appear in the
command line. Leo would use these settings files but would *not* load
them, unless they *also* appeared in the list of .leo files on the
command line.
In the new scheme, including myLeoSettings.leo and/or leoSettings.leo
in the list of loaded simply loads these files as usual. Such files
would have no effect on settings: they would be treated just as
ordinary loaded files, and they would use the settings in whatever
myLeoSettings.leo or leoSettings.leo files are in effect for all other
loaded files. This is actually a nice simplification.
This hardly seems like the simplest thing that could possibly work,
but it look likes a reasonable and least surprising scheme, and it
looks like the most flexible scheme. I'll do this unless someone
proposes a better way, or tells me why it's a bad idea.
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.
