Quantcast

Shift + Insert (behave mswin not working) in latest version.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Shift + Insert (behave mswin not working) in latest version.

ggjsoft
Sorry if I posted this twice.
So using this installer: ftp://ftp.vim.org/pub/vim/pc/gvim80-069.exe
When installing, I mark the checkbox "create bat files" for console use.
However in the console version ctrl ins + shift ins does not work, I think the entire "behave mswin" does not work at all.
I know for a fact, that in gvim74 it worked. Something was screwed in the installer?

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shift + Insert (behave mswin not working) in latest version.

Tony Mechelynck
 On Sun, Apr 9, 2017 at 10:01 PM,  <[hidden email]> wrote:
> Sorry if I posted this twice.
> So using this installer: ftp://ftp.vim.org/pub/vim/pc/gvim80-069.exe
> When installing, I mark the checkbox "create bat files" for console use.
> However in the console version ctrl ins + shift ins does not work, I think the entire "behave mswin" does not work at all.
> I know for a fact, that in gvim74 it worked. Something was screwed in the installer?

I think you are confusing the ":behave mswin" command and the
mswin.vim script. They are not the same.
• ":behave mswin" is a shorthand for ":set selectmode=mouse,key
mousemodel=popup keymodel=startsel,stopsel selection=exclusive".
Nothing more, nothing less.
• The mswin.vim script sets a number of mappings which override
standard Vim key bindings, some of which are quite useful. IMHO this
script is un-Vim-like in the extreme, but, well, if you insist on
using it — on your head be it.

To see if mswin.vim has been sourced, look at the output of the
:scriptnames command: it lists all sourced scripts in the order they
were first sourced. If it was invoked it would normally appear near
the top of the list.

Another possibility is that on some systems, some key combinations
don't make it to Vim, especially when running in a console terminal.
If the same key combinations work as desired in gvim with the same
startup files, then maybe your console terminal is stealing those
particular key combinations, or else disguising them as something
else. I cannot test it since I'm on Linux and there is no necessary
correspondence between which keys your console intercepts and what
mine does. To see what Vim "sees" for a given key combination, go to
Insert mode then use Ctrl-V (or Ctrl-Q if your Ctrl-V is Paste)
followed by the problematic key combo. If nothing appears (and, if you
have 'showmode' on, ^V remains near the bottom right corner) then Vim
hasn't got the key combo at all. Otherwise you can see which keycodes
it has got, and compare them with those for a slightly different key
(for instance, <Insert> without Shift or Ctrl) by using the same
procedure with that other key: if the keycodes are the same, Vim
cannot tell these keys apart from each other.

Best regards,
Tony.

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...