Michael Henry wrote: > I've always been confused by the behavior of "n" and "N" > after backward searches. The only work-around my brain can > handle is to simply avoid backward searches entirely; > instead, I search forward and press "N".
Agreed. That's usually how I resolve the problem as well. However, sometimes I take the trouble to scroll everything to just how it is needed (so some critical portion of code is visible). Pressing * to search forwards, and then N followed by another N to go backwards might scroll the window, and that would be a great distraction. Worse is when I stop to think "if I press * will the window scroll?", because by the time I've pondered that, and whether some tweaks to my setup might overcome my difficulty, I have forgotten what I needed to do in the code I was looking at. John -- -- 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/groups/opt_out.
