On 2021-01-25, Chaoren Lin wrote: > if you did that, you'd break all the plugins that rely on the current > behavior > > Do you mean because they use \r? I don't mind having both \r and \n mean the > same thing in the replacement string.
That would be another way to implement the requested behavior, but it still changes the existing behavior. > Do plugins actually use \n in the replacement string with its current > behavior? > I don't mind not using those plugins. I don't know. You may not mind not using those plugins, but other people might. > People who have problems with it could choose either to not use the option or > not use the plugins. Or plugins could get updated to detect this option. We > already have many options that change behavior (e.g., magic) and plugins just > deal with them by checking or by being careful with their regexes (e.g., \v, \ > m, \V, \M). When a plugin starts behaving oddly, it doesn't announce, "My behavior has changed because you changed this to that". The user just notices that something's not right. They may not notice the problem for a while and may not associate the change in behavior to their setting of the option. The problem then has to be troubleshot. The use of \r instead of \n in the replacement string is enough of an annoyance to new users that nearly every new user, upon hearing about an option to change the behavior, would set that option. They would be unaware of the possible consequences and would be the least capable of troubleshooting their configurations if a problem arose. Plugins often don't get updated. They are written, then maintained for a while, then the author disappears or loses interest. There is not a central repository of plugins, so it would not be possible for one person to just update them all. One of the great features of Vim is that Bram is fastidious about maintaining backward compatibility. Vim hardly ever breaks because of some new feature. Consequently, little annoyances like this persist and have to adjusted to or worked around. I still think that your best bet is to write your own command that would do what you want. It solves your problem and doesn't interfere with anything or anyone else. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210125210317.GB5133%40phoenix.
