-
-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are key combinations that don't work with Helix, such as "Ctrl + º" #4933
Comments
You can try debug use following process:
|
Please upgrade to at least the current version of wezterm, If you are still experiencing problems, see https://wezfurlong.org/wezterm/troubleshooting.html#debugging-keyboard-related-issues and share the debugging information here. It would also be helpful to know what keyboard layout is configured for your system. |
I've installed the latest version of flatpak but the error keeps happening. Running Wezterm from konsole and pressing
If I press
Pressing
I'm from Spain and I use a standard Spanish keyboard with my KDE Manjaro (X11). These last days I've been testing several terminals (for Helix) and the truth is that these key combinations don't work with Wezterm or Kitty but they do work with Alacritty. I like Wezterm a lot and I would prefer to use it since it has a built-in multiplexer. |
Please try the nightly appimage download; the nightly is not available in flatpak due to flatpak release policies. |
I also have the same problem with When I run it from konsole to debug, and press
Pressing
And pressing Ctrl + backspace:
Using this appimage, I'm also running Helix and it happens the same, the key combination doesn't work either (it's as if other keys were being pressed). |
Thanks; with that appimage, please run it like this to capture a little bit more debug info:
|
hmm, that appimage version is older than I was expecting. b8d93ed is the commit I'd like you to be on or beyond. Please download the nightly appimage: https://github.com/wez/wezterm/releases/download/nightly/WezTerm-nightly-Ubuntu20.04.AppImage |
No problem, I've downloaded this nightly and the bug persists using Helix as well.
|
The workaround was to allow ctrl-c to behave as expected for users of cyrillic layouts, but it was scoped too broadly, as it impacted eg: pressing ctrl-grave; in a spanish layout that is expected to expand to º This commit adjusts the scope of the workaround to only activate when the original expansion is itself cyrillic. I doubt this is the last we'll hear of this, but let's see how it goes! refs: #4933
I've pushed a commit to eg: running The commit should show up in a nightly build within about 20 minutes or so. |
I just tried the new nightly and now it's different, it seems that the combination now writes the character that is pressed
Before it was just executing other keys and another key combinations However, when executing The command
|
Log of the nightly with the last commit:
|
For the https://gitlab.com/craigbarnes/dte/-/issues/207 Thanks for wezterm behavior respect the most popular terminals instead of xterm. |
What Operating System(s) are you seeing this problem on?
Linux X11
Which Wayland compositor or X11 Window manager(s) are you using?
Kwin
WezTerm version
wezterm 20230712-072601-f4abf8fd
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
There's key combinations I can't use with Helix Editor, even with
disable_default_key_bindings
enabled , for exampleCtrl + º
,Ctrl + .
,Ctrl + backspace
, and so on.Do you know if it's really a bug or just that Wezterm doesn't allow them?
To Reproduce
Open Wezterm and run Helix, which has the following configuration in the
config.toml
fileInside Helix, when pressing this key combination, it doesn't perform the indicated action (reload the configuration file). Instead, it seems to execute the key combination
Ctrl + Space
(since I've configured those keys to open a popup).Configuration
local wezterm = require 'wezterm'
return {
disable_default_key_bindings = true
}
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: