-
-
Notifications
You must be signed in to change notification settings - Fork 924
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
tmux over ssh #3541
Comments
For specificity: It happens when I try to do any ctrl+anything shortcut. both bash and tmux shortcuts. And I'm pretty sure this did not happen in past kitty versions. I moved to alacritty and is now moving back to kitty. |
See https://sw.kovidgoyal.net/kitty/faq.html#i-am-using-tmux-and-have-a-problem And I can tell you that doing ssh and then running tmux and pressing |
@kovidgoyal I love that its you maintaining kitty. Your so awesome man. Thanks for quick answer! |
You're welcome :) |
Wait... That did not answer me tho. I really need tmux over ssh for my work. I tried reading up on doc and various issues, but the issue still remain |
See what |
outside tmux or ssh:
when I ssh to server:
when I tmux:
|
Set it to |
I get this when I ssh into the server then @Luflosi
and no colors |
Then when trying to start tmux, I get this:
|
Does tmux print this error? Does |
That fixed the color issue. But ctrl+l or any tmux command still does not work. @Luflosi. And I appriciate you taking out time to help the ones with special needs |
Is |
What ctrl keys are you pressing? |
local machine or plain kitty:
Inside ssh without tmux:
Inside ssh with tmux:
|
@koekeishiya Im pressing forexample ctrl+l to clear the terminal, or ctrl+a AKA my tmux modifier. |
And this happens only inside tmux, not if you just ssh and press those |
yea :( |
[2000][leier@serverhost][] /home/leier$ 7;5uc7;5uc7;5u9;5u9;5u9;5u9;5u9;5u7;5uc8;5u8;5u8;5u8;5u |
Then its likely something in your tmux config, bisect it to find the |
I am also getting this issue, only started happening after updating kitty recently, not sure which commit caused the error I am also unable to press enter |
@leier69, @crepppy: Have you tried removing your tmux and shell config? It sounds like you have something enabling the new keyboard protocol introduced in version 0.20.0. |
I also started seeing this with the recent kitty update (0.20.0). No control keys work for me (e.g. C-c, C-z). |
I'm not sure if outside tmux:
inside tmux:
|
@nerdrew: Please read my comment and try that:
Your showkey output does indeed confirm that the new keyboard protocol is enabled inside tmux for you. |
Looking now. FWIW, I don't have a shell or tmux config for my user. Do you know how to only use default configs for tmux? |
What would enable the new keyboard protocol? That might be easier for me to search for in the running config :) |
From what I can tell, this happens with the default settings for my tmux (version 1.8). I.e. there is no |
Hm, okay. It does not happen for me with tmux 3.1c or 3.2. Version 1.8 is very old (8 years), so you should probably try upgrading it. You can provide an empty config for tmux with the
You can see how the protocol is enabled in the docs i linked:
So e.g. |
Upgrade: LOL. I wish. Appears to still be broken when starting tmux with |
Do you have tmux running? As I said, you have to use |
no, tmux is not running |
You need to ask the tmux developers why your version of tmux is doing that. And you can turn off extended keyboard mode with |
Interesting. |
If I start |
Derp. I mean |
Try doing it multiple times since its a stack. |
LOL. I needed to do |
Thanks! |
I have the same bug... And this resolve it. |
…ovidgoyal/kitty#3541" This reverts commit 8f283b1. It didn't work for subsequent connections - I'll just get a newer Tmux compiled where needed ¯\_(ツ)_/¯
OS: Arch Linux (btw)
Bug is on x11 and wayland.
Bug is not present using alacritty, or gnome terminal.
Bug:
I ssh and tmux works as expected on my server, but when I try to do control shortcusts in tmux or bash it does not work and prints random characters. Example bellow.
The text was updated successfully, but these errors were encountered: