Oh my, thanks a lot for such an immediate reaction. I didnt expect it and pleased a lot. Thanks.
I understand ... and I would add something. To develop making good use of > some of Leo's strengths, I have found myself breaking up files into > subtrees, and nodes. Each node usually only has a page's worth of code, > sometimes much less. Their arrangement and names in the outline convey > quite a bit of information about the code flow. Comparing this with > ordinary editors and IDEs, it seems to me that being able to highlight each > use of a word in a single node tends to be less useful in Leo, because so > much of the rest of the code will be in other nodes - and you won't be able > to see them at a glance anyway. > First of all, I am using breaking code into small pieces where just small part of code resides. That is the feature that prevents me from returning to vim in my everyday development - files seem too huge and clumsy for me now. Even if I ever return to vim of vscode or something - I would first find and install some outliner plugin. Second, I am familiar with leo's cff patterns. I don't see it's power and use it rarely. I use clones in another way: I am cloning nodes which are required for my current task, reducing their amount to 10-12 nodes. So I dont need to jump over the code and can remember what's going on in every part and can concentrate on the algorithm, not on the locations. Third, Leo's refactoring tools are POOR. For now if I need to perform a refactoring - I am loading code to somewhere else (vscode, visual studion, vim - depends). Because leo's plain find'n'replace is a pain. Ok, the preamble is done. Let's go further. > This is where the clone-find-xxx commands can be useful. All nodes with > the target word get cloned and placed in a new (usually temporary) subtree > outside of your working tree. What is missing is a highlight of the target > word in each of these cloned nodes. But I have found that you can jump to > and highlight each instance of the target word in a cloned node by pressing > <F3> (since that word is already in the *find *buffer). > Cursor is jumping. You need to press keys. This breaks concentration. Most of time I just want to overview the field and decide - should I do anything with this particular variable. Or make another decision. When I just highlight occurrences - I am doing this faster. And better. Cause when you're F3 from one match to anohter - I are already dont remember what was 2 steps before. And you're pressing F2. And doing pressings not thinking. > Before diving in to trying to implement highlighting a target word > everywhere in a node, a little more about the requirements would be > helpful. For example, if you press any key, or click anywhere in the body, > should the highlighting go away? > New word - new match. In the current body only. Highlighting is activated only by user action - shortcut or mouse click. When you're typing - nothing is going on. If not, how should the highlighting be removed? > Highlighting does not disappear if user does nothing. Th criteria for removing hl - user enters text or mouse position changed. HL activates only by trigger. Should Leo treat the original highlighted word differently from all the > other instances (e.g., having <CTRL-X> delete only it)? > yes, sure. HL is not a clone of the word in the body :-) Some more thought now will pay off later, if someone undertakes to > implement this behavior. > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ca5ded18-fe92-4f21-a051-837aca8f7db5n%40googlegroups.com.
