RightAlt-i
works to demonstrate the problem.If you hit RightAlt-i, Vim should invoke any mapping that exists for <m-i>
or beep if no such mapping exists. Instead, it acts as if you simply typed i
.
More detailed description of the problem:
GVim 9.0 on Windows does not recognize the right Alt key; if you hit RightAlt-Somekey
, it acts as if you just hit Somekey
alone.
The one exception to this is that the menu bar accelerators work: if you hit RightAlt-f
, for example, it does invoke the File menu.
I'm using a US keyboard, so the right Alt key is not an AltGr key, in case that matters.
The left Alt key works fine.
Both Alt keys work in the text-mode version of Vim; only GVim is affected.
Both Alt keys work in GVim 8.2.
I've confirmed that the problem exists when starting GVim via gvim --clean
so it's not a settings issue.
I've confirmed that the problem exists on two different computers, one running Windows 8.1 and one running Windows 10.
I've confirmed that the problem exists in the most recent stable version listed for download on vim.org (https://github.com/vim/vim-win32-installer/releases/download/v9.0.0000/gvim_9.0.0000_x86_signed.exe) and in a recent nightly (https://github.com/vim/vim-win32-installer/releases/download/v9.0.0117/gvim_9.0.0117_x64.exe).
9.0 and 9.0.0117
Microsoft Windows 8.1 (64-bit) and Microsoft Windows 10 (64-bit)
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Hello, this seems to be a duplicate of issue #10753.
@k-euser Could you try this build: https://github.com/vim/vim-win32-installer/releases/tag/v9.0.0124
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
closing as dupe of #10753
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Closed #10826 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
That's not precisely a duplicate, although it might be related; #10753 is about AltGr-Space
not working whereas this is about RightAlt-anything
not working, on a keyboard layout where RightAlt is not AltGr.
In any case, I've just tried v9.0.0124 and the problem is still there.
Please reopen.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Reopened #10826.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Recently tried to create test case for this bug using new test_gui_w32_sendevent
low level key press simulation mechanism, but it fails: internally whatever key code i simulate gui_w32.c logic judges it as "left alt", thus performing all tests without revealing bug reported here. Only manually operating the keyboard i can reproduce the problem. Still have some hope, will try to extend logic in test_gui_w32_sendevent
to use scan_code instead of wVk. Seems will not come to it very soon, have some busy weeks now.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
That's not precisely a duplicate, although it might be related; #10753 is about
AltGr-Space
not working whereas this is aboutRightAlt-anything
not working, on a keyboard layout where RightAlt is not AltGr.In any case, I've just tried v9.0.0124 and the problem is still there.
I can confirm the issue for this keyboard layout: https://www.europatastatur.de/e1
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Is there any plan to fix this?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
It requires someone with this keyboard to figure out what happens and come up with a solution (that doesn't break things for other keyboards).
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
You don't need a physical keyboard with one of the affected layouts to reproduce the problem. You can reproduce it just fine using the "On-Screen Keyboard" included with Windows after setting the keyboard layout in Windows' Language settings.
(Actually, I suspect simply changing the keyboard layout would be sufficient to reproduce it on essentially any physical keyboard as well, but I don't have any way of checking that as I don't have a non-US keyboard available.)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
RAlt
VK SC Type Up/Dn Elapsed Key
-------------------------------------------------------------------------------------------------------------
A5 138 d 12.45 RAlt
A5 138 u 0.17 RAlt
LAlt
VK SC Type Up/Dn Elapsed Key
-------------------------------------------------------------------------------------------------------------
A4 038 d 24.81 LAlt
A4 038 u 0.09 LAlt
RAlt +p
VK SC Type Up/Dn Elapsed Key
-------------------------------------------------------------------------------------------------------------
A5 138 d 8.06 RAlt
50 019 d 0.20 p
50 019 u 0.19 p
A5 138 u 0.06 RAlt
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Can you try out #11294 ?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Can you try out #11294 ?
No need any more ((( , just checked myself - it breaks AltGr handling completely (but US RightAlt starts to work though).
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
should it be not closed since 8d8b975 ?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
closing then again :)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Closed #10826 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Yes,it works now.Thank you!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.