On Sat, Oct 15, 2011 at 3:12 PM, Christian J. Robinson <[email protected]> wrote: > On Sat, 15 Oct 2011, Donald Allen wrote: > >> Try it with .vimrc like so: >> >> set incsearch >> set nocp >> >> I think the cause is the 'set incsearch'. > > This still gives me the expected error: > > vim -u NONE -U NONE -i NONE -N -c 'set incsearch' > > However, if I do create a temporary vimrc as you suggested and invoke vim > like this: > > vim -u vimrc_tmp -U NONE > > Then press "n" I get a different message. What's happening is that you're > still getting a viminfo file read when you invoke it your way, which can set > a previous search pattern. Try adding "-i NONE" to your command line and > see if you still get this behavior.
Yes, disabling the viminfo stuff, which I was not aware of, eliminates this behavior. I find it very odd that this is enabled by default. I think most people think of different editing sessions as different editing sessions, not a continuation of a previous session. But thank you for getting me straightened out about why this is occurring. /Don > >> I'm running 7.3.337 on a 64-bit Slackware 13.37 system. > > 7.3.338 on Cygwin, and the same version on Windows. > > - Christian > > -- > As I learn, I know about more things I don't yet know. > Christian J. Robinson <[email protected]> > http://christianrobinson.name/ > > -- > 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 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
