An addendum to the clone-find-all-flattened post.
clone-find-all-flattened often includes clones of nodes whose location is
unclear. No problem! Just select the mysterious node and do Alt-N
(goto-next-clone). Leo will select the next clone of that node, wrapping
the search as necessary. One or two Alt-N takes me to the "real" node, the
node having an ancestor @<file> node.
Ideally, the meaning of all nodes would be clear from their headlines. I
typically use the following conventions. For section definitions, the
headline should contain file or class name. Examples::
<< imports >> (leoCommands.py)
<< docstring >> (LeoApp)
For functions and methods, the headline should start with an id. Examples:
c.whatever
g.whatever
p.whatever
v.whatever
The general rule is:
The more important the class, the shorter its id.
leoPy.leo#Code--> About this file-->Terminology gives the following id's::
btw: leoFrame.BaseTextWrapper
stw: leoFrame.StringTextWrapper
bqtw: qt_text.BaseQTextWrapper
lqtb: qt_text.LeoQTextBrowser
qhlw: qt_text.QHeadlineWrapper
qmbw: qt_text.QMinibufferWrapper
qlew: qt_text.QLineEditWrapper
qsciw: qt_text.QScintiallaWrapper
qtew: qt_text.QTextEditWrapper
Not all these classes have id's in their nodes (yet). And no, I don't try
to remember these less important (thus *longer) id's. They exist just to
disambiguate methods with common names.
I add more id's as I find ambiguous nodes. It's easy to add an id to all
methods of a class. Just use the following regex search, limited to
headlines::
Replace ^(.) with <the id>.\1
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.
For more options, visit https://groups.google.com/d/optout.
