I am using an alternative keyboard layout called "neo2". [http://www.neo-layout.org/] This layout focuses on minimal finger movements and instead works with several layers activated by pressing and holding a modifier key (e.g. caps-lock). In this layout modifier 4 + space bar is equivalent to "0" on the numerical key pad.
Not so in gvim: here the modifier key is ignored and all I get is a space character. That is quite annoying, because it doesn't work in normal mode, too. So I always get strange results for things like "10k". All other keys in neo2 layer 4 work perfectly normal (i.e. mod4+m for "1"), only the space bar is not recognized correctly.
As for gvim is the ONLY application I encountered having any problem with the layout, so I think it is causing the problem by some kind of input processing.
"gvim -N -u NONE" does not make any difference, so this is not plugin related. Commandline vim works fine, but I'd prefer using gvim due to better color support :-)
I am running Windows 8.1 64bit and can reproduce this using the official 7.4 build as well using the single drop distribution v7.4.657. I even tried older versions (e.g. v7.1.42 portable)
—
Reply to this email directly or view it on GitHub.![]()
Hi
In the absence of other potential fixes, may I suggest dowloading the (rather fabulous) Autohotkey utility: http://www.autohotkey.com/ This is a windows utility that allows mapping keystrokes and key-chords to other keystrokes and/or custom system actions. It allows filtering so as to intercept and modify only the keystrokes for gVim, thus leaving other apps unaffected. It is free and open source. Almost assuredly, it will be able to fix your problems.
Thanks
--David
--
--
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 because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Closed #423.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, .![]()
This issue seems to conflict with #250
If I REMOVE the line {VK_SPACE, ' ', NUL}, from gui_w32.c, then the issue with the neo2 layout is gone.
I don't have any smart idea though, how I could provide a fix suitable for all users. So I'll just compile gvim from the sources from now on :-)