fredizzimo

Since there are no new reports after the 0.11.0 release, I will clsoe this

This was fixed in the 0.12.0 release by * https://github.com/neovide/neovide/pull/2070

This should be fixed by #1899, it would be great if you can test that.

I don't think that the issue that @mgax reported be fixed, unless we get a list of mapped keys from Neovim itself and choose which one of the mappings should...

> Would this work for vs Yes, it should, but we probably need https://github.com/rust-windowing/winit/pull/2887. On other plarforms we are able to do similar mappings.

It seems like winit might not be reporting the shifted character at all in combination with `CMD`. If that's the case we should report it to the Winit team, since...

@technicalpickles, `` and `` are the correct mappings, that's how it works on both Linux and Windows. I suspect that the problem is that `keyevent.text` is `p` instead of `P`...

It looks like it's more complex than I thought, the other platforms are actually not working correctly either in all cases. Nvim itself treats `` and `` the same, but...

Could someone do some testing in combination with https://github.com/neovide/neovide/pull/1962, and attach the log here? That should give us more information to report the bug to Winit, and possibly about a...

I also got another log ``` TRACE [neovide::window::keyboard_manager] KeyEvent { physical_key: SuperLeft, logical_key: Super, text: None, location: Left, state: Pressed, repeat: false, platform_specific: KeyEventExtra { text_with_all_modifiers: None, key_without_modifiers: Super, },...