Cannot type numbers in Kakoune when using programmer's Dvorak layout #3837
Comments
|
Also, |
|
If it helps, here's me trying to type 1: And here's me typing "a": And typing "1" outside of Kakoune: |
|
I have the same problem, so I looked into it, and it seems that kak is enabling CsiU mode. I think that corresponds to the docs as https://wezfurlong.org/wezterm/config/key-encoding.html#xterm-modifyotherkeys I'm going to see if changing the config in that section: affect this behavior in any way. Sadly, neither worked. |
|
The reason they all show up as <a-]> is probably because of the fallback here: |
|
looks like the case for 27 is missing from the switch here: |
|
Looking through the kak debug log, it seems that the kitty keycodes are handled corrrectly: |
|
Sadly, it seems that those keys confuse kakoune and any key using shift stops working. |
|
Please try the latest release; I think this was essentially a duplicate of:
|
wez
added
the
waiting-on-op
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Mutter 43.3
WezTerm version
20230530-062729-95e44f21
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
When I try to type numbers into Kakoune, instead of receiving number keys, it receives something else entirely.
If I run Kakoune like
kak -debug keysand then open the*debug*buffer, when I try to type 1 (QWERTY equivalent: Shift+5),Client 'client0' got key '<a-[>'is output to the debug buffer, instead of the expectedClient 'client0' got key '1'. The same thing happens with most of the numbers. Changing layouts to QWERTY-US works as expected, andkgxdoes handle this just fine.Given that it's always
<a-[>, my best guess would be some sort of escape sequence thing not working quite right. Although given that it works fine with QWERTY-US, not sure if that's it.Also, as an aside (not sure whether there's already a report for this), re-showing the mouse cursor on Wayland seems to fail.
To Reproduce
No response
Configuration
Expected Behavior
No response
Logs
Apart from a whole ton of messages like
00:32:26.565 ERROR window::os::wayland::pointer > set_cursor: Unable to set cursor to arrow: cursor not found, Unable to set cursor to 'default': cursor not found, none related to this.Anything else?
The system is Void Linux, booted from ZFS with ZFSBootMenu, running on a Framework Laptop with an Intel i5-1240P.
List of installed packages (
xbps-query -l)The text was updated successfully, but these errors were encountered: