On Thu, Mar 26, 2009 at 4:04 PM, VR <[email protected]> wrote:
> > the situation is slightly more complicated. - I create two minimal > test-outlines (TOL) > > * TOL-#1 - which contains an @enabled-plugins node containing rst3.py > + mime.py > * TOL-#2 - which contains an @enabled-plugins node containing only > mime.py > (expecting to pick up rst3.py from either LeoSettings.leo or > myLeoSettings.leo) > > TOL-#1 works as aspected, however the log does not showing the trace > line you > mentioned. > > TOL-#2 behaves exactly as I described in my initial email, i.e. it > does not even > offer the menu-cmd "Edit -> Write-Restructured-Text - and - also the > log does > not offer the trace line you mentioned. I think the essence of the problem is that when opening a .leo file, only the plugins mentioned in the @enabled-plugins node *for that file* are loaded. In other words, @enabled-plugins nodes are not cumulative for the initial open. However, when you *later* open a .leo file, any plugins mentioned in the @enabled-plugins node for the *newly opened* file are also enabled. In other words, the present operation of @enabled-plugins nodes can be highly confusing. This scheme does have some advantages. For example, when directly opening test.leo or unitTest.leo, the @enabled-plugins nodes in other files have no effect, so I can run tests cleanly. In general, though, I agree that the present way is not great. I'll think about this some more. 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 -~----------~----~----~----~------~----~------~--~---
