fredizzimo

> The problem is, I think, just the logic in KeyboardManager.format_modifier_string which clearly doesn't add the S- in some cases where it should. No that's not the problem, but it's...

Another reason why the patch is problematic is that with the fix you have to map like this ``, but if the issue is fixed upstream, then Neovide starts to...

MacVim is correct and that’s what Neovide should send too unless it’s impossible. Neovim-qt also sends an acceptable code, and for ascii characters, I’m pretty sure both of those mappings...

> Is it reasonable to ask, though, that unless this is fixed in winit for the next Neovide release, we get the very wrong solution instead of the no solution?...

I reported the issue here now https://github.com/rust-windowing/winit/issues/3078 with incomplete information, please fill in any details there if needed.

If someone is able to help the Winit team debug and perhaps even fix the code, we can probably get this moving forward faster. I guess you could start by...

I just reported a Neovim issue that is related https://github.com/neovim/neovim/issues/25068 (but not the cause of this). It just makes it different to map things with `CMD` accross different GUIs. It...

Since there was another keyboard issue, which will require extensive testing, I combined it with a partial fix for this issue in this PR https://github.com/neovide/neovide/pull/2018. The advantage of the solution...

* #2018 is merged to main, but it only fixes the problems for alpha keys, the numbers and other special characters will need a winit fix.

The winit fix is now merged * https://github.com/rust-windowing/winit/issues/3078 So, once a new release is made and we update, we should finally be able to completely close this issue.