On Sun, Jul 2, 2017 at 2:42 PM, Terry Brown <terrynbr...@gmail.com> wrote:
On Sun, 2 Jul 2017 09:00:22 -0700 (PDT) > vitalije <vitali...@gmail.com> wrote: > > > A problem can arise when user changes any of relevant settings files: > > some .leo.db files can have outdated settings embedded. > > The arrangement that springs to mind for me is: > > The default settings, currently distributed in leoSettings.leo, would be > in leoSettings.sqlite. They wouldn't need to be in a (sqlite) Leo > outline, just a sqlite settings representation. > > The user's general settings, currently in myLeoSettings.leo, would be > in myLeoSettings.sqlite, same storage approach as leoSettings.sqlite > above. > I think we have to do this so that the db's change when changing branches. > The .leo file specific settings would be in the sqlite file storing the > Leo outline. > Reasonable. The `config` for c.config could be created without any Leo outline > loading (and therefore be available very early in Leo's init.) or very > easily in a settings editor. An important advantage. It may also simplify the init code. > It would just be sqlite connections to > three files, somefile.sqlite, myLeoSettings.sqlite, and > leoSettings.sqlite, searched in that order. > > I don't see a clear reason for all settings to be in each Leo outline, > I think users are used to personal and default settings that are > separate from file specific settings. > It would be bad style to put all settings anywhere except leoSettings.leo or leoSettings.db. However, the settings code must handle any eventuality. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
