Neovim-qt: Dead keys are broken in Windows for some keyboard layouts

[equalsraf]

• Pressing a dead key followed by space, produces a space instead of the expected key
• Pressing the dead key twice produces the expected key.

References

• https://github.com/equalsraf/neovim-qt/issues/179#issuecomment-244522196
• https://github.com/neovim/neovim/issues/6642
• http://stackoverflow.com/questions/28793356/qt-and-dead-keys-in-a-custom-widget
• https://groups.google.com/forum/#!topic/leo-editor/re5fieBHRgw

[equalsraf]

Builds with some extra logged info for this at https://ci.appveyor.com/project/equalsraf/neovim-qt/build/1102/job/sso8sx24gk5ghq9w/artifacts but so far a dead key produces two keypress events with ~

[yuntan]

I cannot input "*" on jp106 keyboard ("*" is input by "shift :"). My problem may be related to this issue.

[yuntan]

I just confirmed that I can't reproduce the problem that I commented above on master (https://ci.appveyor.com/project/equalsraf/neovim-qt/build/job/3dpsatte6lr94fmv/artifacts). Above comment is on the version that is bundled in neovim v0.2.0.

[w1mb0r]

tested this again on nvim-qt dating 06/09/2017 17:58 with nvim v0.2.3-234-gb0e9132cf and using an azerty keyboard
issue still exists

[w1mb0r]

I tested this again on nvim-qt dating 2018-08-26 with nvim v0.3.2-402-ge30ccd56d and using an azerty keyboard.
This issue still occurs.
The affected keys are:

• ¨
• ^
• ´
• `
• ~

If i type such such dead key followed by the space bar, I should get the character but nothing appears.
I need to type the dead key twice, then I get the character twice and delete the redundant character.
It does work correctly on nvim on the text console / without nvim-qt.

[ghost]

My fix (https://github.com/AssertFailure/neovim-qt/tree/fix-270) to the missing dead keys is to not ignore Event's text when the actual key is a special key. It seems to work fine, but it needs a suboptimal special handling for special keys which would produce unintended text as well. I noticed that only Delete key did that on my setup, but I'm not certain if that depends on the key layout or something.

[TheSandvichMaker]

This is still an issue for me on on the latest build at this time (23/06/2019), nvim v0.3.5-11-g1060bfd03, using the US International layout. So long as there isn't a fix, using nvim-qt would be very cumbersome for me (which is a shame, since I want to use it!)

[kayzzen01]

Neovim Qt is much nicer than nvim on CMD, at least on Windows it is. I will use gvim for now on Windows and I am monitoring this its solution.

NVIM v0.4.3
NVIM-Qt 0.2.14.0

[markstos]

In my case I found that the issue was that I was using a QMK-powered keyboard and my asterisk key was sending a "Numpad Asterisk". I updated the firmware to send a "Shifted Punctuation Asterisk" instead and that resolved the issue with Neovim 0.3.8.

[lucasteles]

Same problem here ☹