-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
use-kitty-keyboard-protocol = true doesn't work with tmux #599
Comments
Hey @jZhangTk thanks for the issue! Could you test with latest main? |
Thanks for the update, @raphamorim. I followed the instructions here and confirmed that the version is |
Thank you for testing @jZhangTk! Very interesting, I tested Rio and Kitty key inputs and looks is correct at least. Wondering what could be |
I assume it does work with kitty right? |
I did a bit of searching, and tested tmux with Kitty and Ghostty but looks the protocol doesn't really work there (at least with no configuration), found this as well tmux/tmux#3335 |
Interesting. It works fine for me on Kitty. What are you using to test the key press? I can test it on my side too. |
ah if it does work with kitty terminal then is likely to be a bug in Rio. I use the kitty cli https://sw.kovidgoyal.net/kitty/invocation/ , there's a command that I can test the inputs can you send me your tmux configuration as well? I will try to reproduce here |
When I was testing it, I commented out everything in I'm going to test the key press later today and let you know. |
I'm not sure if I did it right. I tried to run I should have provided this earlier. Here are the steps I'm using to test if
-- reopen a closed tab
vim.keymap.set('n', '<C-S-t>', '<cmd>tabnew#<CR>', { noremap = true, silent = true })
|
Environment:
I'm using the default config with only
use-kitty-keyboard-protocol = true
added. It works fine without tmux. However, once I launch tmux, it seems to stop working. E.g. I have a key mapping forctrl-shift-t
set up in Neovim, but it doesn't work when I use it within tmux.The text was updated successfully, but these errors were encountered: