On Fri, May 31, 2013 at 9:52 AM, Edward K. Ream <[email protected]> wrote:
> On Fri, May 31, 2013 at 6:53 AM, Fidel Pérez <[email protected]> wrote: > >> Hi, Im guessing you are really used to search and replace by using the >> command "change all" but from the noobs standpoint, I would sincerelly >> switch the name of that command into: >> replace all >> Since thats what every other editor uses, I just spent 10 minutes trying >> to figure out which was the command, and I was checking the "edit" menu, >> but since Change all is not usually what I use for replacing, coudnt "find" >> it. >> > > Good idea. I'll do it today. > Done at rev 5801. All unit tests pass. The name change could have a slight effect on existing scripts. The following would no longer work:: k.simulateCommand('change') k.simulateCommand('change-then-find') k.simulateCommand('change-all') Imo, this small incompatibility acceptable. The alternative would be to retain the existing change* commands, but that would be confusing. I've also changed the docs for the commands. ****Oops****. I've forgot to update the shortcuts in leoSettings.leo. 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?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
