Christian Brabandt wrote:
> Bram,
> one of my annoyances with vim currently is, that when using n/N for
> searching the direction depends on the previous search command. But I
> usually forget if I initially used / or ? and then my brain gets stuck
> whether I need to press n to search backwards or N. (e.g. I start a
> search backwards using '?' and want to go further upwards and press
> routinely 'N', but this moves back downwards again).
>
> I find it easier to know that n searches downwards while N searches
> upwards, since I usually only know whether I want to go further down or
> up, so I can reliably hit n to go further down and N to go further up to
> the next match.
>
> This is what the attached patch enables, by adding the new flag 'N' to
> the 'cpo' setting.
Well, instead of adding an option, what about:
:noremap n /<CR>
:noremap N ?<CR>
--
ARTHUR: Old woman!
DENNIS: Man!
ARTHUR: Man. I'm sorry. Old man, What knight live in that castle over there?
DENNIS: I'm thirty-seven.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
