On 29 Nov, 17:11, Terry Brown <[email protected]> wrote: > I didn't entirely understand the OP's need, which seemed to be resolved > by discovering clone-find-all.
I'm in the need to study a c++ library and I'm started to add a @path node pointing to the tests and one to the examples. By active_path plugin I load all the examples in the dir as @shadow node, and the files are over 750. I would use Leo to explore and experience this library, starting from the examples, one file at a time, noting what is unclear to me, the documentation collected, the techniques used, etc.. and organizing them in the files. Soon I needed to classify the examples to distinguish better between them... and this isn't the first time. I'm lazy and started to ctrl+drag the nodes... but the files are too many. Then I tried to select multiple nodes and copy and paste as a clone... but don't worked. When I wrote the request I imagined being able to work side by side on two trees, with one hoisted on the argument-focus. I'm a newbee and underestimated the power of Leo, so lauched ipython and marked nodes by using regexp and cloned them from script. After two successful clone I created a button, and I started to think that Leo is not a tool for lazy people, even for lazy programmer , but a great tool for programmer. Laziness is a virtue for me. Then when I found the clone-find-all I realized that it is the Swiss boxcutter that every geek must have. I'm beginning to think that this boxcutter has so many blades that I will never see.. and I think being so young. Every time I think back to my problem I can think of different solutions ... and then I discover that they are or might be possible in Leo. I like python, but I'm not a huge fan. I like the python zen but I'm a c++ dev too, so I know that with the power everything can be done in several ways and the burden and pleasure of control are in this. I use Leo because I see it as part of the solution of my problems. I want to focus on the initial needs, not on the needs born by the tools for finding solutions. I want to be lazy. I think Leo is so rich from having so many use paradigms that seem to have none. Leo seems to suffer the same problem of linux window managers: there are so many and each has its unique characteristics that make it ideal for some users. I'm a wmii user. But history tells us that if it were not kde and gnome, linux would not be used as it is today. The user want to be lazy. Only when he knows the instrument may decide to venture into trying different ways of use. Thinking about it has been for a while 'I started to copy settings at the start of the file depending on the use of leo, and this is good. But I'm a newbee... and each time this settings change, maybe I'm using the wrong paradigm or the wrong personal-standard. It would be nice to have some standard configuration or standard interface. Would be nice to choose which configuration to use to create a new project. It 'late and I doubt that my thoughts are very clear, and certainly my pseudo English does not help you. Anyway, thanks for making this instrument: it has changed my way of managing, Costantino Giuliodori -- 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.
