On 08/04/09 13:10, 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.
>
> 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?
>
> Thanks,
> John
Well, not sure if it's a bug, a feature, an undocumented feature, or
whatever, but here are my comments:
- mswin.vim plays havoc with the Vim control-key bindings. Use it at
your own risk. I don't.
- keymodel=stopsel means that an unshifted cursor-movement key will stop
selection.
- I use neither ":behave xterm" nor ":behave mswin" but the following
compromise. I believe it is superior, but YMMV. At leat it suits me
better than either. Nickname it "behave Tony" if you want to. ;-)
set selectmode=key,mouse " same as mswin
set mousemodel=popup " same as mswin and dos/win default
set keymodel=startsel " halfway compromise
set selection=inclusive " same as xterm and default
With these settings, a shifted cursor movement will start select mode,
but no cursor movement will stop it once started.
Best regards,
Tony.
--
ADA, n.:
Something you need only know the name of to be an Expert in
Computing. Useful in sentences like, "We had better develop an ADA
awareness."
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
