Thanks Tony and Matt for your thoughts. I agree that using mswin.vim is kind of flirting with danger - the main reason I used it was for the ctrl-x/c/v mappings which can be a simple way to access the clipboard - but I created my own version yesterday, to remove some fat I didn't want.
"undocumented side effect" seems rather accurate to me - but I'm most surprised it's been this way since 6.4.10. Thanks very much for checking that one - I can only presume that my memory sucks, perhaps since I've only started working everyday under windows in the last year (and since linux/unix don't have the same clipboard, I never missed mswin.vim). Anyway - this behaviour from Ctrl-F is not unreasonable I guess - though it would be more reasonable if <c-s-f> did extend the selection, which of course it doesn't since it's the same as <c-f> - but thank you, I guess I'm satisfied with the response. No more stopsel for me... and I might well adopt "behave Tony" - seems like a wise compromise. Thanks so much, John On Wed, 08 Apr 2009 22:54:05 +0200, Matt Wozniski <[email protected]> wrote: > > 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 -~----------~----~----~----~------~----~------~--~---
