On Fri, Feb 10, 2012 at 4:38 PM, Terry Brown <[email protected]> wrote: > is there some way to make the list of places to look a @setting?
Only on the command line. When I awoke this morning I saw the way forward. 1. The -c option must go. It's a bad idea and nobody uses it. Similarly, the --leo-settings and --my-leo-settings options are bad ideas. None of these options are worth the time to document, much less implement. 2. Leo *will* look in the local directory for myLeoSettings.leo, but not leoSettings.leo. This will give almost all the advantages of the -c option, with the added advantage that somebody, somewhere, might actually use this feature. **Footnote**: Leo will (as at present), load at most one myLeoSettings.leo file per session: Leo will determine the local directory using the path to the first loaded .leo file on the command line. This works well in practice because the startup messages always make clear where settings are coming from. The take away message is that simplicity matters. Specifying the location of settings files on the command line is featuritis. I welcome comments, but I don't think anyone is going to change my mind. Our lengthy conversation has been rewarded with a cleaner design. 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.
