The prefix "DingDing" signifies that this post is an answer to the
lament:
"Wouldn't it be great if we all could remember what we,
and others, have already done :-)"
Last night I had a forehead-slapping moment: the place to put @button
nodes is in myLeoSettings.leo.
This morning, I realized that using @command rather than @button
completes the Aha.
This organization has all benefits, and no drawbacks:
- I always know here scripts are.
- No need for duplicates.
- I can organize the scripts within myLeoSettings.leo as usual using
organizer nodes. This organization can change as needed.
- Using @command rather than @button means that I never have to
disable scripts. No more @@button.
- Using @command saves screen real estate. In my experience, having
buttons be visible doesn't prevent them from being hidden in full
view.
- If I use common prefixes, like c_ (for command) or edit_ (for edit-
related scripts) or ekr_ (for personal scripts), the *typing
completion* will let me zero in on the script I want to use:
<alt-x> c_<tab>
<alt-x> c_import<tab>
etc. Furthermore, Ctrl-P (repeat-complex-command) will allow me to
rerun the last script run. This is a quite common case.
Summary
=======
This Aha substitutes an *already-existing* usage (typing completion)
for a whole set of memory-intensive retrieval problems. I'm not
likely ever to forget typing completion, although I might forget the
specif prefixes used in @command nodes. If that happens, I'll know
where to look.
This Aha takes full advantage of Leo's organization strengths and
*concentrates* those strengths by putting all the to-be-organized
material in one place. This allows for easy reorganization: changing
command-name prefixes, for instance, would be straightforward.
This is another example of the assertion that Leo already has most of
what is required to handle any task.
Edward
P.S. The mod_scripting plugin could automatically add a c_ prefix to
all commands created by either @button or @command. It would allow
<alt-x>c_<tab> to zero in on my "user-defined" commands.
The drawback is that the "c_" prefix is kinda like an Easter Egg, and
if you don't know about it it might be hard to discover the command.
I suppose the mod_scripting plugin could create both the prefixed and
unprefixed command name, but that clutters up the list of commands.
No, the more I think about it, the more I think the user should create
whatever prefixes she likes.
EKR
--
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.
