On 2016-07-09, Manuel Ortega wrote: > call and call() are also. But I don't think it makes confusing. > > > But it does, for new users and people learning VimScript. I'm not confused > *anymore* about :substitute/substitute(), because I've now done a ton of > vimscripting. But when I was new, I can't tell you how many times that messed > me up when looking for documentation, and when trying to remember which one > can > take which flags. > > It's so easy to avoid doing things that confuse people for no good reason.
If a command and a function do the same thing, or essentially the same thing, I would much rather they be given the same name, one that actually describes what they do, than be given different names that mean almost the same thing. Using the same name shouldn't be a source of confusion--it should make it easier to find a command or a function. If I know of a command that does something and I want a function that does the same thing, it is fairly easy to just look to see if there is a function by the same name. Further, it is not always easy to find good English names for functions and commands. Regards Gary -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
