Re: Proposal: @button x should create the x-@button command
On Wed, Mar 25, 2015 at 7:04 AM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com 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. How difficult would it be to change your config? In my experience, it's fairly easy to get an unbounded recursion due to the collision of names. If you think it unwise to change @command as I suggest, perhaps a headline option, similar to @key, could be added for you. In other words, I really want x-@command :-) It would have helped considerably while I was reviewing commands for the commands reference. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
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 leo-editor@googlegroups.com 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 edream...@gmail.com 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
On Thu, Mar 26, 2015 at 6:59 AM, Kent Tenney kten...@gmail.com wrote: 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 At last I see. You and Terry are correct. Hmm. I am going to leave things as they are. @button and @command already create @button-x and @command-x (for use by the tab completer). If these are not enough to indicate how x was created, more new commands won't help. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
Never mind - didn't see your response Edward. Cheers -Terry On Thu, 26 Mar 2015 10:53:04 -0500 'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote: On Thu, 26 Mar 2015 05:20:40 -0500 Edward K. Ream edream...@gmail.com wrote: On Wed, Mar 25, 2015 at 7:04 AM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com 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. How difficult would it be to change your config? In my experience, it's fairly easy to get an unbounded recursion due to the collision of names. Well, they're not all in a single config, some of them are file specific. It wouldn't be the end of the world, but... If you think it unwise to change @command as I suggest, perhaps a headline option, similar to @key, could be added for you. In other words, I really want x-@command :-) It would have helped considerably while I was reviewing commands for the commands reference. ... I agree with Kent in another post, you expect @command foo to create command `foo`. When you say x-@command would have helped when reviewing the docs., how so? Commands can be tagged in the docs. with an rst class, :cmd:`foo`, but I'm not sure if that's what you mean. Cheers -Terry 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
On Thu, 26 Mar 2015 05:20:40 -0500 Edward K. Ream edream...@gmail.com wrote: On Wed, Mar 25, 2015 at 7:04 AM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com 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. How difficult would it be to change your config? In my experience, it's fairly easy to get an unbounded recursion due to the collision of names. Well, they're not all in a single config, some of them are file specific. It wouldn't be the end of the world, but... If you think it unwise to change @command as I suggest, perhaps a headline option, similar to @key, could be added for you. In other words, I really want x-@command :-) It would have helped considerably while I was reviewing commands for the commands reference. ... I agree with Kent in another post, you expect @command foo to create command `foo`. When you say x-@command would have helped when reviewing the docs., how so? Commands can be tagged in the docs. with an rst class, :cmd:`foo`, but I'm not sure if that's what you mean. Cheers -Terry 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
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 edream...@gmail.com 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: @button x should create the x-@button command
On Wed, Mar 25, 2015 at 5:48 AM, Edward K. Ream edream...@gmail.com wrote: At present, each @button x node creates two commands: x and @button-x. Whoa, cool, never knew. There is no indication that @button created the x command. This can cause confusion. Indeed, seems like a great way to introduce confusion by silently tromping on commands. Imo, the @button x node should create the x-@button command instead of the plain x command. sounds right: thanks to tab completion, the verbosity isn't a problem. retain the @button-x name ... ? 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
