> Um, this has been vi behavior since the beginning, AFAICT...I've
> got an older version of nvi as well as vim6.2 (yes, I can hear
> Tony complaining already ;-) and they both behave the same way:
> search for X, do a :%s/Y/Z/ and then use n/N to search for the
> next instance and it will attempt to search for Y (which may or
> may not return results depending on whether you include the "g"
> flag or if you include the search in the replacement) instead of
> X.
I don't have any older versions available to test right now, I just
don't recall ever running into this problem before, and I have used
vim hours a day for years.
However it used to work at some point in the past, I believe the
behavior that I suggest would be much more sensible. If you want to
do what vim does by default now, search for Y, :%s/Y/Z and then n/N to
get to the next Y. But that won't keep you from searching for X, :s/Y/
Z/ and then n/N to get to the next X. As it is now, you have to keep
typing X in over and over again, which is not very friendly.
Does that sound reasonable?
--
You received this message from the "vim_use" 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
No comments:
Post a Comment