On Wed, Jun 25, 2014 at 2:48 PM, 'Terry Brown' via leo-editor <[email protected]> wrote: > On Wed, 25 Jun 2014 12:17:40 -0700 (PDT) > Fidel N <[email protected]> wrote:
>> And the main thing is its the other way around. AHK sniffs around my >> actions, then points to Leo commands to complete them. >> So if I want to add my selected text (outside Leo) as a child of >> currently Leo selected node, AHK helps me call a command in Leo. > > Hmm, I'd probably use a Leo button, Yes, that's natural. As Fidel probably knows, @button and @command nodes create commands that can be executed from the minibuffer (and bound to keys) But I'd like to step back a bit and make a more general point, one that relates to Offray's post re the discussion of Leo and Light Table. (I'll say more on that thread later today.) The point is this: Leo allows any node to contain a (simple!) python script, so even though a user doesn't think of themselves as a programmer, any conceivable set of mundane actions can be automated. This includes creating @button nodes, or other commands, or data or whatever. Without knowing in detail exactly what you want to do, the general approach of writing one or more helper scripts is right on target. HTH. 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.
