This sounds right, defining a command is intentional, a @button creates a command as a stealth side effect.
It would be surprising if node @command write-to-file didn't result in the command write-to-file Is there a problem if there is also now a command write-to-file-@command (if I understand Edward's proposal) On Wed, Mar 25, 2015 at 7:04 AM, 'Terry Brown' via leo-editor <[email protected]> wrote: > Hmm, @command is a way of creating commands. Creating commands can shadow > other commands, that's a given. I wouldn't change what @command does. I'm > sure it would break a lot of personal config. > > @buttons I have no strong opinion about. > Cheers -Terry > > > On March 25, 2015 5:48:03 AM CDT, "Edward K. Ream" <[email protected]> > wrote: >> >> At present, each @button x node creates two commands: x and @button-x. >> >> There is no indication that @button created the x command. This can cause >> confusion. >> >> Imo, the @button x node should create the x-@button command instead of the >> "plain" x command. >> >> Similar remarks apply to @command. >> >> Your comments, please. >> >> 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. -- 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.
