Skip to content
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

Cannot map ctrl+tab to next_tab #801

Closed
chdsbd opened this issue Aug 10, 2018 · 5 comments
Closed

Cannot map ctrl+tab to next_tab #801

chdsbd opened this issue Aug 10, 2018 · 5 comments

Comments

@chdsbd
Copy link

chdsbd commented Aug 10, 2018

Hello,

I've been trying to map ctrl+tab to next_tab. Here is my config:

clear_all_shortcuts yes
map ctrl+tab next_tab
map cmd+t new_tab

I'm able to create a new tab with cmd+tab, but ctrl+tab fails to cycle to the next tab.

I think I'm missing some obvious.

@kovidgoyal
Copy link
Owner

Works for me, remember that if you are on macOS ctrl means the control key on the keyboard. And your keyboard shortcut should not conflict with any globally defined shortcuts/hotkeys.

@chdsbd
Copy link
Author

chdsbd commented Aug 11, 2018

I ran kitty --debug-keyboard and it seems like the ctrl+tab sequence is not being received. Trying with ctrl+i worked.

ctrl+tab is the standard way to change tabs on macOS, so maybe it's not being handled somewhere in the interface between kitty and macOS.

Did you test ctrl+tab on macOS? I've tried this on 10.13 and 10.12 with no success.

UPDATE:

Here is a post talking about this edge case https://www.chromium.org/developers/os-x-keyboard-handling

UPDATE 2: Do you think this is a bug with GLFW?

@kovidgoyal
Copy link
Owner

kovidgoyal commented Aug 11, 2018

Ah macOS -- yeah you are out of luck there. Apple's control freakyness means there is no good way to handle keys Apple has decided should belong to cocoa without jumping through a ton of hoops. Not being a cocoa developer, I have no clue what those hoops might be. But, patches are welcome.

@chdsbd
Copy link
Author

chdsbd commented Aug 11, 2018

Thanks for the quick response and fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants