On Friday 16 January 2009 06:34 am, Kent Tenney wrote: > Maybe some simplification is possible.
Minor point/question: Maybe, but maybe I missed the point about why all this dicussion is coming about. Is it because once a plugin is specified in one of the earlier read files is loaded, that loading can't be overridden (the plugin can't be unloaded) by a configuration file that is read later? If so, I guess that is different than what I'm becoming used to in the Linux world--an alternative would be to read all the configuration files before installing any plugins, applying the appropriate precedence rules (which I think are just: * last file read "wins" * configuration files are read in order from least specific to most specific (thus global, personal, local) ) > What is the rationale for 'leoSettings.leo' in home or local? > I would consider config in those locations to be, by definition, mine. I can easily envisage running more than one instance of Leo for slightly different purposes. Maybe for that reason they need slightly different configurations. The file in home would set my configurations generally, the file(s) in the local directories would fine tune the configuration on a per instance basis. Randy Kramer -- I didn't have time to write a short letter, so I created a video instead.--with apologies to Cicero, et.al. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
