On Mar 17, 9:06 am, Tony Mechelynck <[email protected]> wrote: > 'iminsert', keymaps, and language-mappings affect: > - everything in Insert mode > - search strings entered in ? or / command-line mode > - replace letters, argument of r in Normal mode > - search letters, argument of f F t T in Normal mode > etc., in short anything which can be expected to be in the language of > your editfile and not in the language of "commands to Vim". > > And in addition, they can be toggled on and off, e.g. after > > :%s/ > > you will probably toggle them in, and toggle them out before typing the > flags (if any) at the end of that substitute command; similarly when > typing a single- or double-quoted string in "edittext language" in an > expression.
This doesn't answer the part about why incremental search ever falls back to command key mapping. I've looked through the documentation for a bit and can't find any explanation for why this is happening. I feel like there's a documentation page on key mapping that I'm not reading. Everytime I think I understand how it should work I find some new option or differing behavior which changes the way I need to think about key mapping. Is there a good page which overviews the modes, special cases and the many different options which control key mapping? -- 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
