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
x11/wayland: CTRL-+ key assignments no longer recognized #3610
Comments
Please run through: https://wezfurlong.org/wezterm/troubleshooting.html#debugging-keyboard-related-issues Note that the default key assignments for $ wezterm -n show-keys --lua | grep FontSize
{ key = ')', mods = 'CTRL', action = act.ResetFontSize },
{ key = ')', mods = 'SHIFT|CTRL', action = act.ResetFontSize },
{ key = '+', mods = 'CTRL', action = act.IncreaseFontSize },
{ key = '+', mods = 'SHIFT|CTRL', action = act.IncreaseFontSize },
{ key = '-', mods = 'CTRL', action = act.DecreaseFontSize },
{ key = '-', mods = 'SHIFT|CTRL', action = act.DecreaseFontSize },
{ key = '-', mods = 'SUPER', action = act.DecreaseFontSize },
{ key = '0', mods = 'CTRL', action = act.ResetFontSize },
{ key = '0', mods = 'SHIFT|CTRL', action = act.ResetFontSize },
{ key = '0', mods = 'SUPER', action = act.ResetFontSize },
{ key = '=', mods = 'CTRL', action = act.IncreaseFontSize },
{ key = '=', mods = 'SHIFT|CTRL', action = act.IncreaseFontSize },
{ key = '=', mods = 'SUPER', action = act.IncreaseFontSize },
{ key = '_', mods = 'CTRL', action = act.DecreaseFontSize },
{ key = '_', mods = 'SHIFT|CTRL', action = act.DecreaseFontSize }, |
debug_key_events = true :
Here is my minimal config:
|
FWIW,
Interesting. I think this is related to the changes in 21e19ca What is your keyboard layout? DE? |
Ah, sorry. removing the
|
I just build wezterm with the commit |
I would add here that |
As a workaround suggestion, could you try setting the XKB_DEFAULT_LAYOUT environment variable (to "de" for your case I guess). |
This workaround did not work unfortunately. |
This is fixing a regression introduced by the fix for #2845. The resolution for this is relatively straightforward, but took a bit of effort to plumb. Previously: * CTRL/ALT/SUPER-modified keys with no explicit expansion would end up just taking the US layout version of the key. That worked well for the intended problem with non-latin layouts, but for eg: German layouts it caused expansion to totally the wrong thing Now: * CTRL/ALT/SUPER-modified keys which effectively expand to non-ascii text (eg: cyrillic "Es") now take the equivalent key press from the US layout (which would be "c" in the "Es" case). For European layouts this heuristic seems to avoid unexpected effects, but could do with some validation from native users. To support this, the xkb code splits the `Keyboard` struct out from some of the higher level logic and introduces a `KeyboardWithFallback` struct that is built out of the user-selected keyboard layout, and the fallback keyboard. Now the fallback keyboard is fed the same key inputs as the selected keyboard to correctly model the key combinations. refs: #3610 refs: #3933
This should be resolved now in It typically takes about an hour before commits are available as nightly builds for all platforms. Linux builds are the fastest to build and are often available within about 20 minutes. Windows and macOS builds take a bit longer. Please take a few moments to try out the fix and let me know how that works out. You can find the nightly downloads for your system in the wezterm installation docs. In particular: please confirm that any/all ctrl/alt modified keys now work as you expect in the DE layout: I think I resolved this, but I'm not sure if there are some edge cases for keys that produce latin-but-not-ascii output. If you prefer to use packages provided by your distribution or package manager of choice and don't want to replace that with a nightly download, keep in mind that you can download portable packages (eg: a If you are eager and can build from source then you may be able to try this out more quickly. |
I've built from Many many thanks! I haven't updated wezterm till now because things like Ctrl+C were incorrectly remapped. |
just checked, |
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 X11
Which Wayland compositor or X11 Window manager(s) are you using?
awesomewm
WezTerm version
wezterm 20230424-111459-de9d9bc5
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
Changing the fontsize with
action.wezterm.IncreaseFontSize
(decrease, reset as well) does not work anymore.It used to work a few days ago. I usually rebuild wezterm once per week.
To Reproduce
No response
Configuration
Expected Behavior
Changing fontsize should work again
Logs
Debug Overlay
wezterm version: 20230424-111459-de9d9bc5 x86_64-unknown-linux-gnu
Window Environment: X11 awesome
WebGPU: name=AMD Radeon Graphics (RADV RENOIR), device_type=IntegratedGpu, backend=Vulkan, driver=radv, driver_info=Mesa 23.0.2, vendor=4098, device=5686
Enter lua statements or expressions and hit Enter.
Press ESC or CTRL-D to exit
Anything else?
No response
The text was updated successfully, but these errors were encountered: