On 6/6/19 6:56 PM, Jakub Wilk wrote:
> * Rhonda D'Vine <rho...@deb.at>, 2019-06-06, 16:27:
>> what's yout TERM on the host, when you mosh to the server?
>
> Terminal on the local side doesn't seem to matter; I can reproduce the
> bug in any of the following:
> * Linux console (TERM=linux)
> * urxvt (TERM=rxvt)
> * xterm (TERM=xterm)
>
> On the remote server, it's TERM=xterm.
>
>> Is there any tmux or screen involved?
>
> No.
>
>> Are both the server from which you mosh out of and the remote server
>> buster?
>
> The local machine is unstable.
>
>> This might be related: https://github.com/irssi/irssi/issues/753
>
> Aha, thanks. I guess mosh's xterm emulation isn't quite right...
>
> Irssi upstream recommends setting TERM to something else on the server
> side, but AFAIK there's no dedicated terminal definition for mosh. :-/
>
> I've set TERM=vte (even though mosh and VTE are unrelated) as a
> work-around for now; it fixes the bug and I haven't seen any bad side
> effects so far.
Glad this helped. I noticed a few strangenesses with respect to mosh
instead of ssh myself, like certain utf8 characters not getting
displayed, which was kinda weird. I think there is a bit fishy stuff
going on in mosh, unsure if it might be related to different mosh
versions on both ends (but both buster and unstable have the same, so
that's not the case here), but it certainly mixes some bits up.
Are you fine with closing this bugreport then? I am more leaning
towards that it might be mosh in play here than irssi, we could also
reassign?
Thanks,
Rhonda
