On Sun, Jan 4, 2009 at 9:49 AM, Lorenz Köhl <[email protected]> wrote: > > Kent Tenney wrote the following: >> double clicking the node icon opens it in vim, edit and exit >> vim, the node is not changed in Leo. > > I had the same trouble when I put the @enabled-plugins node > in myLeoConfig. Worked after removing this and enabled it in > the main config.
I was having problems when more than one config file contained @enabled-plugins nodes I copied the @enabled-plugins node from <config>/leoSettings.leo to <cwd>/myLeoSettings.leo, and put additional <cwd>/myLeoSettings.leo This solved some problems, but evidently created another. I'd prefer not to be changing the <config> copy, but evidently that's what works. ... Yep, I removed @enabled-plugins from <cwd>/myLeoSettings.leo and put my non-default plugin declarations in <config>/leoSettings.leo, and the vim plugin is working again. So I'll stick with using only <config>/leoSettings.leo In playing with this I've found that <alt-x>print-plugins-info doesn't seem to report accurately (probably related to bug?) <alt-x>print-plugins-info would be more useful if it reported fully qualified path of the file, since myLeoSettings.leo could be in more than one location. Thanks, Kent > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
