My complaint has some tangencies with this one: http://groups.google.com/group/leo-editor/browse_thread/thread/f181c57a96eafd81 I'm posting it in this thread for a couple of reasons: - that thread is reasonably old and I can't post there anymore - the problem is somehow related to the plugins, as this thread is - it'll be a reminder for me, because I had a deja vu feeling when bumping into the problem. Searching the list for it just confirmed that the deja vu feeling was right
So, short story: I was in the process of merging an @enabled-plugins node from an older myLeoSettings with an @enabled-plugins node from a recent leoSettings. I have found that: 1. there is no reference to todo.py in @enabled-plugins. 2. there are two(!) references to cleo.py, which is its tk counterpart (but hey, qt is the default GUI nowadays!) in @enabled-plugins I don't know why it happened, perhaps because the default @enabled- plugins node is modified manually [or is not :-)] by the authors of plugins. I recall adding todo.py to myLeoSettings after finding out about it on this list, but what about leo newcomers? leo itself is good at managing TODO lists, but cleo/todo are great experience improvers. Terry, now that you are at it, what do you think about delegating one more task to your code which scans for plugin docstrings: to generate the default @enabled-plugins? It could also optionally include short descriptions of each plugin (at the risk of bloating the @enabled plugins node), so somebody who is deciding which plugins to enable would not switch attention between the @enabled-plugins node and the more detailed documentation. -- 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.
