On Fri, Jan 16, 2009 at 5:34 AM, Kent Tenney <[email protected]> wrote:
> > Maybe some simplification is possible. Some people may indeed be able to simplify how they use settings files. However, changing the present scheme would not be a good idea--it would likely force people to change their settings files. This I really don't want to do unless there is an extremely good reason, which imo there is not. > > What is the rationale for 'leoSettings.leo' in home or local? > I would consider config in those locations to be, by definition, mine. I don't remember, except that somebody, maybe even you, wanted the flexibility. > > Come to think of it, what is the need for both names, leoSettings.leo > and myLeoSettings.leo? It's not fruitful to focus on the itty-bitty details. The big picture is that we want at least the following kinds of settings: - Per-installation or per-machine settings. - Per-user settings. - Per-folder settings. - Per-file settings. myLeoSettings.leo exists primarily to support per-user settings, but the search order allows either leoSettings.leo or myLeoSettings.leo to be pressed into service. 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 -~----------~----~----~----~------~----~------~--~---
