You are not logged in.
I've been using wayland and labwc for the past few months and its generally been great.
When using the terminal ctrl+a, ctrl+e, and other commands all work as expected.
However, when I SSH into a remote server ctrl+a, ctrl+e, backspace and other commands do not function.
Any suggestions for how to fix this?
Last edited by anthillsocial (2025-03-18 10:51:20)
Offline
Bogus $TERM environment or missing terminfo?
This most likely has nothing to do with "wayland" or "labwc", your terminal emulator however might be relevant.
Online
It's the same for every terminal app I use which makes me suspect its a wayland issue.
When I switch back to X11 all is fine!
T
Offline
To be clear, you expect ctrl+a and ctrl+e to navigate the terminals cursor, not something completely unrelated, like window management?
Wayland is the ssh client, the ssh server is a constant?
Running xterm on (x)wayland, ctrl+a and ctrl+e work, but after "ssh foo.com" they don't?
(The overally problem isn't new and frequently happens when the ssh server cannot make use of the $TERM variable because it lacks the corresponding terminfo, home and end typically likewise don't work)
Online
RE: you expect ctrl+a and ctrl+e to navigate the terminals cursor, not something completely unrelated, like window management?
Yes. Exactly.
So I just tried running xterm and ctrl+a and ctrl+e work as expected!
Though, its not working with foot or other wayland terminal apps, so it sounds like the "ssh server cannot make use of the $TERM variable".
So, what might be the fix so I can use foot in this case?
Offline
Do you control the server?
https://archlinux.org/packages/extra/x8 … -terminfo/
Otherwise your best shot is lying by setting a different $TERM (which depends on the degree to which foot is compatible w/ eg. xterm)
You might also get away w/ moving a multiplexer like tmux inbetween (assuming the server knows that, because its terminfo part of ncurses)
Online
Brilliant advice - thanks!!
RE: Do you control the server?
Only partially - which is the route of the issue... I spun up another and the issue goes away!
Offline