When I was trying to figure this out I remember reading something in the documentation that recommended putting only the individual nodes you wished to change into the myleoSettings.leo file, as it is read after the defaults and will take precedence.
It makes for a much smaller item to troubleshoot. I am still working on breaking myself of the habit of looking for the "Preferences" in the menus. Chris On Sat, Oct 26, 2013 at 12:10 PM, wgw <[email protected]> wrote: > Yep; that was the problem with my "broken" myLeoSettings.leo file. > > I had simply pasted the node "Candidates for settings in > myLeoSettings.leo" into a blank leo file. As you say, the @enabled-plugins > node was not under an @settings node. > > My old myLeoSettings.leo file was a complete copy of leoSettings.leo, so > the cloned links were intact. > > There is a lot of work to make myLeoSettings both friendly, flexible and > idiot proof (I am the perfect tester! I will blunder into any and all idiot > traps). > > Another crucial feature is knowing how the myLeoSettings differs from an > updated leoSettings.leo file. For the moment, the best idea is to use Meld > to compare the two files. If a new commented plugin appears in the > leoSettings.leo file, Meld will spot it, hopefully. Then I can update my > myLeoSetttings.leo file. > > The only problem is of course that the leo then has to deal with two > nearly identical settings files on startup. Still, it starts up fast enough > for me. > > Thanks for the bug fix! (... or more like a bugged user fix) > > Bill > > > Le samedi 26 octobre 2013 05:43:00 UTC-7, Terry a écrit : >> >> On Sat, 26 Oct 2013 00:48:59 -0700 >> Matt Wilkie <[email protected]> wrote: >> >> > I too am having trouble with settings and getting the bookmark plugin >> to >> > work; filed as a bug report, >> > https://bugs.launchpad.net/**leo-editor/+bug/1244887<https://bugs.launchpad.net/leo-editor/+bug/1244887> >> >> https://bugs.launchpad.net/**leo-editor/+bug/555014<https://bugs.launchpad.net/leo-editor/+bug/555014>is >> what really needs fixing. >> >> I just added >> >> # This node *MUST* be a child of the @settings node to take effect. >> >> to the @enabled-plugins node in leoSettings.leo, it appears not to be >> because it's cloned in to a top level position as well, but that's what >> you were missing. >> >> But in general it's clear Help -> myLeoSettings.leo needs to create a >> sensible skeleton automatically when the file doesn't exist, copying >> @enabled-plugins from leoSettings.leo etc. >> >> Cheers -Terry >> > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
