On Thu, Jan 15, 2009 at 6:52 AM, zpcspm <[email protected]> wrote: > > > So, I will rely on 2 facts about app settings that work very well in > the UNIX world: > 1. global and user-specific app settings > 2. the power of the command line
Leo already has these. I'll consider only small mods to how these work. > > This is the scenario I can imagine: > > 1. leo starts > 2. If a file was passed via -c command line option, leo treats it as > its settings file and loads the settings into a SETTINGS structure in > memory. goto 5. Leo already has a settings structure. It's complicated. This structure comprises both lists and dictionaries. Leo adds entries when opening .leo files, and removes entries when closing .leo files. Some kinds of settings are handled with global variables: @enabled-plugins is one of those. It's difficult to describe *exactly* how Leo works in words. I don't think this is a problem with Leo's code, and I don't want to change the underlying code in any significant way. That would create chaos. The specific proposal you make would change the order of entries in the table in leoConfig.py:readSettingsFiles. That's not a good idea, imo. Having said that, I do want to support more flexible settings, possibly by adding entries to the table or by making other tweaks to readSettingsFiles. I'll say more about this in a new thread. 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 -~----------~----~----~----~------~----~------~--~---
