Thanks for getting me on track: I realize now that I copied over to myLeoSettings much more than is necessary (though I'm not really sure how it got there -- it's been a long time!) Once I trim things down, it will be easy to manage. (I did know that myLeoSettings could be empty, but forgot it when I started tinkering with my configuration.)
For a Leo code/idea registry: looks like there should be a clearinghouse with volunteer housekeepers. Git/bzr is supposed to manage a lot of that, I believe, and maybe it can, but many potential housekeepers, incapable of core development, are equally bamboozled by git/bzr. On the other hand, if the Gui's to Git/bzr get a bit more user friendly, then maybe there would be more volunteer support. (for Git: http://www.maketecheasier.com/6-useful-graphical-git-client-for-linux/2012/01/18 ) I agree that it is tough to get any kind of systematic documentation from anyone who is not working full time on the project, but if the text search function is good enough (like sublime's fuzzy search or google's search), and if searchers could document their searches as well (ie add comments that would make searching easier), perhaps the snippets and insights could organize themselves through use. Google groups is perhaps sufficient I suppose ... but it is hard to add a layer of comments designed to organize the ideas expressed in the exchanges. I do find bazaar disappointing, even using the ubuntu bzr explorer: There should be a thorough search system. And google group members should be able to add comments to an idea branch that can be searched. For example, I looked for Terry's overview code on bazaar but found nothing (the code is working fine for me as copied from google groups). I'm sure it is up there somewhere on bazaar (Terry said he pushed it), but no sign of it, not even with google search: site:http://bazaar.launchpad.net/~leo-editor-team overview This is probably just me -- a potential part-time housekeeper but too klutzy to operate a broom. Thanks! Bill Le mercredi 1 mai 2013 14:42:43 UTC-7, Edward K. Ream a écrit : > > On Wed, May 1, 2013 at 3:26 PM, wgw <[email protected] <javascript:>>wrote: > >> For the moment, I use Meld to compare/update myLeoSettings.leo file. That >> seems a bit error-prone. Is there a better way? By update, I mean that, for >> example, in the bzr copy of LeoSettings.leo, the code_wise node says : >> >> True: use codewise completions. >> False: use leo-specific completions. >> >> This setting is no longer used! >> >> >> But in my (now old) myLeoSettings.leo file it says: >> >> True: use codewise completions. >> False: use leo-specific completions >> >> >> I want to transfer that updated setting comment to myLeoSettings so that >> I don't have to refer to LeoSetttings.leo when I tweak my installation. >> >> Another example: the plugins list will change with new plugins or >> eliminated plugins, but those changes won't be noted in the myLeoSettings >> file. So you have to check both settings files to find/enable plugins. >> >> In general, it would seem useful to be able to merge the two leo files >> (like bzr merge?) or somehow make note of differences in the myLeoSettings >> file. >> >> This is starting to sound complicated.... :) Sorry! >> > > It is complicated. One tiny workaround is to delete nodes from > myLeoSettings.leo if and when they become unused. More generally, you only > have to put nodes in myLeoSettings.leo if they are different from the > defaults. But you probably already know that :-) > > Really, this is a special case of the fundamental problem the Leo > developers have been struggling with: Leo is great for storing gobs of > data, but not so great at sharing. As a result, everyone, including Leo's > developers, struggles to remember, access or browse all the great stuff > that is already present. > > Requiring tags is no solution: it's hopeless to require volunteers to do > anything :-) I'm not just making a joke. Someone who contributes a script > to this Google Group is under no further obligation to somehow be > compatible with *any* other submission rules. Somehow, it's up to me, or > the other core developers, to find a simple, reliable way of "indexing" the > submissions. Right now I have no solutions. > > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
