On Wed, May 24, 2017 at 2:53 PM, Eric S. Johansson <[email protected]> wrote:
> There are two types of structure. One is the structure of code in hierarchy and organization of entities, another is the hierarchy expressed in Leo. But in writing there is the structure of the narrative, the plot line of characters. There have been lengthy, ongoing discussions about the difficulties of using, say, the rst3 command, to document code. N either clones nor bookmarks suffice to "access" code, comments or any other "narrative item" embedded a Leo outline. The general solution is a custom script that "pick s out" the desired data, creating either an @rst tree or, say, an @auto-md tree. What gets "pick ed out" from an outline requires some kind of additional markup that you (your script) supplies. > What I'm looking for is [links to definitions]. Yes, that would be useful, in specific places. > For me the the way I would want information about Leo plug-ins is this: > How do I access the contents of the node? > How do I change the contents of a node? > How do I store context dependent information for later use? These are all basic operations on p. p.h is the headline, p.b is the body text. p.u is the user attributes (uA). > How do I invoke my code on an event such as doing something before or after saving? Define event handlers, as described <http://leoeditor.com/writingPlugins.html#handling-events> here <http://leoeditor.com/writingPlugins.html#handling-events>, in the <http://leoeditor.com/writingPlugins.html> writing plugins chapter <http://leoeditor.com/writingPlugins.html>. > How do I tell Leo to save the results of my code interpreting the contents of the node rather than the contents of a node I don't understand this question. >> Select the lines, then do Tab or Shift-Tab. > I hope you understand why that's not really a good solution for speech recognition. :-) ... Actually, I don't understand. > Leave Mark > jump to end of block > indent region > Or, a better form would be: > Indent block > I'll explain what I mean by block in a different note. Leo already can do almost all of this. For specific tweaks you could define @commands. > But with speech, I can say "leave Mark" and then move the mouse to someplace else and speak a command that operates on a region. You can probably do this in Leo. > I also added a second enhancement request for having a series of commands "<jump|push> to <beginning | start | finish | end> of line". How do you think Leo implements Ctrl-Home and Ctrl-End? These bindings aren't built into Leo! Instead, there are commands that are bound to Ctrl-Home, Ctrl-End and many other sequences. Here's how to find them. Do a regex search for ctrl.home in leoSettings.leo You will find: beginning-of-buffer = Ctrl-Home This is in a node called (not very helpfully) Changes. The parent is @keys EKR bindings. Look in these nodes: @shortcuts Arrow keys and the <return> key @shortcuts Changes @shortcuts Cursor Moves You will see that Leo already has ** *all *the standard Emacs commands related to cursor movement, with the possible exception of the Emacs mark command. But don't be so sure about that. Leo knows the about selections, and the direction of selections (point and mark). > If the guideline is a page or two long, it helps a lot. Voluminous documentation just doesn't work. Leo has several summaries. Start with the cheat sheet. > Are you familiar with the learning technique of explaining what you learned to a novice? I explain things to Rebecca :-) > I apologize for it being so long because I really didn't have time to write a short one. Lack of time is a feeble excuse. Edward ------------------------------------------------------------------------------------------ Edward K. Ream: [email protected] Leo: http://leoeditor.com/ ------------------------------------------------------------------------------------------ -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
