You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The SSH Kitten does not store custom port numbers. When new_tab_with_cwd or new_os_window_with_cwd are used, an error message briefly appears detailing that ssh was unable to connect on port 22 rather than the custom port provided.
To Reproduce
Steps to reproduce the behavior:
Choose your favourite keybinding for new_os_window_with_cwd.
Use the SSH Kitten, but with a port number that's not 22. E.g.: kitten ssh some@where -p 1234
Spam the previous keybinding and try to read the text on the window that briefly appears.
See the following:
ssh: connect to host domainnamegoeshere port 22: Connection refused
Describe the bug
The SSH Kitten does not store custom port numbers. When
new_tab_with_cwd
ornew_os_window_with_cwd
are used, an error message briefly appears detailing that ssh was unable to connect on port 22 rather than the custom port provided.To Reproduce
Steps to reproduce the behavior:
new_os_window_with_cwd
.kitten ssh some@where -p 1234
Minimal kitty.conf
Environment details
The text was updated successfully, but these errors were encountered: