-
-
Notifications
You must be signed in to change notification settings - Fork 786
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
cmd+shift+] doesn't work #4251
Comments
Have you tried binding it to |
Yes, I've tried every variation I could think of. |
I decided to build wezterm from main branch and it worked {
key = '{',
mods = 'CTRL | SHIFT | ALT',
action = wezterm.action.RotatePanes 'Clockwise'
},
{
key = '}',
mods = 'CTRL | SHIFT | ALT',
action = wezterm.action.RotatePanes 'CounterClockwise'
},
|
I built from source and I had no luck getting the keybinding to work. I tried multiple variations of the configuration. |
{
mods = "ALT|SHIFT",
key = "}",
action = act.Multiple({
act.SendKey({ mods = "CTRL", key = "b" }),
act.SendKey({ key = "n" }),
}),
} |
Run wezterm with |
As mentioned previously:
Nothing gets shown on the logs when I trigger the keybinding I'm hoping to configure 😢 |
Take a look at: $ wezterm show-keys --lua | grep TabRelative | grep CMD I'm on linux at the moment, so it looks a little different for me: $ wezterm show-keys --lua | grep TabRelative | grep SUPER
{ key = '[', mods = 'SHIFT|SUPER', action = act.ActivateTabRelative(-1) },
{ key = ']', mods = 'SHIFT|SUPER', action = act.ActivateTabRelative(1) },
{ key = '{', mods = 'SUPER', action = act.ActivateTabRelative(-1) },
{ key = '{', mods = 'SHIFT|SUPER', action = act.ActivateTabRelative(-1) },
{ key = '}', mods = 'SUPER', action = act.ActivateTabRelative(1) },
{ key = '}', mods = 'SHIFT|SUPER', action = act.ActivateTabRelative(1) }, I think you need to hit all of those combos otherwise macos will prioritize the menubar shortcut, which happens before wezterm has a chance to process the key combination. |
That was it @wez! I ended up overwriting the app shortcut to something else so I can use |
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?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
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
I'm unable to setup the keybinding
cmd+shift+]
on macOS.To Reproduce
I've added the appropriate config.key table entry for configuring the mapping.
Configuration
I've tried the following in the keys section.
I've also tried this:
Expected Behavior
I expect the binding to be honored and run the defined action.
Logs
No response
Anything else?
cmd+]
and everything works as expected. It's when I try to bind to}
(shift+]
) that it does not work.CMD+]
CTRL+SHIFT+]
but when I switch it forCMD
orHYPER
the program never registers the key event.The text was updated successfully, but these errors were encountered: