[vim/vim] GVim 9.0 on Windows does not recognize the right Alt key (Issue #10826)

77 views
Skip to first unread message

k-euser

unread,
Jul 31, 2022, 3:22:47 PM7/31/22
to vim/vim, Subscribed

Steps to reproduce

  1. Start GVim on Windows.
  2. Type any Alt-key combination (other than a menu bar accelerator) using the right Alt key. For example, RightAlt-i works to demonstrate the problem.

Expected behaviour

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

Version of Vim

9.0 and 9.0.0117

Environment

Microsoft Windows 8.1 (64-bit) and Microsoft Windows 10 (64-bit)

Logs and stack traces

No response


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10826@github.com>

Bram Moolenaar

unread,
Aug 1, 2022, 6:03:25 AM8/1/22
to vim/vim, Subscribed

@LemonBoy @ant0sha


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10826/1200987365@github.com>

Benoit Mortgat

unread,
Aug 1, 2022, 8:35:26 AM8/1/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1201143556@github.com>

N V

unread,
Aug 1, 2022, 9:15:14 AM8/1/22
to vim_dev
I confirm that on windows vim9 x64 patch 0128, the command Ctrl+$ in a help file as vim9.txt help does not recognize goto command and don't bring me to definition of |vim9script|.
Nicolas.

Christian Brabandt

unread,
Aug 1, 2022, 11:27:57 AM8/1/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1201352528@github.com>

Christian Brabandt

unread,
Aug 1, 2022, 11:27:57 AM8/1/22
to vim/vim, Subscribed

Closed #10826 as completed.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/10826/issue_event/7102626720@github.com>

k-euser

unread,
Aug 1, 2022, 12:33:31 PM8/1/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1201440001@github.com>

Christian Brabandt

unread,
Aug 1, 2022, 12:35:07 PM8/1/22
to vim/vim, Subscribed

Reopened #10826.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/10826/issue_event/7103154097@github.com>

Anton Sharonov (ant0sha)

unread,
Aug 3, 2022, 3:37:54 PM8/3/22
to vim/vim, Subscribed

@LemonBoy @ant0sha

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.Message ID: <vim/vim/issues/10826/1204393466@github.com>

Georg Mayr-Duffner

unread,
Aug 19, 2022, 8:46:14 AM8/19/22
to vim/vim, Subscribed

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.

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.Message ID: <vim/vim/issues/10826/1220634589@github.com>

zoumi

unread,
Oct 4, 2022, 8:36:40 PM10/4/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1267767277@github.com>

Bram Moolenaar

unread,
Oct 5, 2022, 7:58:41 AM10/5/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1268340296@github.com>

k-euser

unread,
Oct 5, 2022, 2:23:09 PM10/5/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1268786400@github.com>

zoumi

unread,
Oct 5, 2022, 8:37:46 PM10/5/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1269150626@github.com>

Bram Moolenaar

unread,
Oct 6, 2022, 7:41:09 AM10/6/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1269874641@github.com>

Anton Sharonov (ant0sha)

unread,
Oct 6, 2022, 3:30:39 PM10/6/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1270582697@github.com>

Anton Sharonov (ant0sha)

unread,
Oct 10, 2022, 3:33:55 AM10/10/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1272893772@github.com>

Christian Brabandt

unread,
Oct 10, 2022, 7:43:56 AM10/10/22
to vim/vim, Subscribed

closing then again :)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10826/1273190804@github.com>

Christian Brabandt

unread,
Oct 10, 2022, 7:44:01 AM10/10/22
to vim/vim, Subscribed

Closed #10826 as completed.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/10826/issue_event/7553326313@github.com>

zoumi

unread,
Oct 10, 2022, 7:46:05 AM10/10/22
to vim/vim, Subscribed

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.Message ID: <vim/vim/issues/10826/1273193050@github.com>

Reply all
Reply to author
Forward
0 new messages