A reminder, the opposite of "light" is "heavy", not "dark" :-)
Leo's print-settings, print-commands and print-bindings commands
create too much text.
Suppose they created outline nodes instead, replacing existing nodes
if they exist. Something like this:
- Reference (Anywhere you like)
- @print-settings
etc.
- @print-bindings
etc
- @print commands
etc
Doh! This uses Leo's power. The subnodes can be as voluminous as
desired, and there can be organizer nodes in each case. The actual
tree could be specified as in @menus.
Etc., etc. This could moot the need for separate apropos commands.
Conversely, apropos commands could create their own trees, or
subtrees.
This could be the tip of an iceberg.
The more I think about the light/heavy distinction, the more I think
it is getting close to what makes Leo special. For example, clones
(and nodes, for that matter) drastically lighten the apparent
complexity of programs or data.
Edward
--
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.
