On Wed, Apr 8, 2009 at 7:10 AM, John Orr wrote: > > Hi all, > > Just curious if anyone else has seen this. > > I'm using Vim 7.2 with patches up to 148 on Windows - the latest installer > from the Cream project. > > For at least a month now, I think I've noticed different behaviour to what > I'm used to. > If I edit a file with > gvim -u NONE -U NONE > then use Shift-V to go to line-wise visual mode, if I then press Ctrl-F I > expect to move forward a page, extending the visual selection. > > This seems to work - unless I first run > :behave mswin > in which case it exits visual mode.
It's behaved like that since vim 6.4.10, at least. That's the oldest vim I have to test with. Though it seems to be an undocumented side effect of <C-F> being treated like <PageDown> - keymodel has been changed to include 'stopsel', which means that <PageDown> ends a visual selection and <S-PageDown> continues it... and I *think* that vim is deciding that <C-f> is the same as an unshifted pagedown, so it ends the visual selection. > I've used gvim on Windows - sourcing mswin.vim which I assume has always > run behave mswin - and I don't remember this behaviour. > > Do others see this, and is it intentional do you think? Well, wanting <PageDown> to not extend a visual selection is strange, and not useful, and only ruins vim's modality to make life easier for those used to how notepad works. I'm not sure if it's intentional that <C-f> behaves like an unshifted <PageDown> in this context, and not as <S-PageDown>, but that's what you get for letting mswin.vim get loaded. :-p ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
