Bug#930037: irssi + mosh: badly rendered status lines

2019-10-02 Thread Sven Joachim
Control: forwarded -1 https://github.com/mobile-shell/mosh/issues/1064 On 2019-08-02 18:25 +0200, Jakub Wilk wrote: > Control: reassign -1 mosh 1.3.2-2.1 > Control: affects -1 + irssi > > This happens because mosh doesn't implement the repetition operator > (see bug #933053). Thanks. Meanwhile

Bug#930037: irssi + mosh: badly rendered status lines

2019-08-02 Thread Jakub Wilk
Control: reassign -1 mosh 1.3.2-2.1 Control: affects -1 + irssi This happens because mosh doesn't implement the repetition operator (see bug #933053). Minimal reproducer: $ printf 'mo\33[5b\n' mo But in xterm proper it is: $ printf 'mo\33[5b\n' moo -- Jakub Wilk

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-07 Thread Thomas Dickey
On Thu, Jun 06, 2019 at 07:08:59PM +0200, Jakub Wilk wrote: > * Thomas Dickey , 2019-06-05, 18:57: > >A "typescript" from the "script" program would show what escape sequences > >irrsi is using when producing the problematic image. > > Attached. > > -- > Jakub Wilk The only difference that I

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-07 Thread Rhonda D'Vine
On 6/6/19 6:56 PM, Jakub Wilk wrote: > * Rhonda D'Vine , 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

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-06 Thread Jakub Wilk
* Thomas Dickey , 2019-06-05, 18:57: A "typescript" from the "script" program would show what escape sequences irrsi is using when producing the problematic image. Attached. -- Jakub Wilk bad_6.1+20181013-2.typescript Description: Binary data good_6.0+20161126-1+deb9u2.typescript

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-06 Thread Jakub Wilk
* Rhonda D'Vine , 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,

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-06 Thread Rhonda D'Vine
Hey. what's yout TERM on the host, when you mosh to the server? Is there any tmux or screen involved? Are both the server from which you mosh out of and the remote server buster? Or does a mosh to localhost work there? This might be related: https://github.com/irssi/irssi/issues/753

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-05 Thread Thomas Dickey
On Wed, Jun 05, 2019 at 09:07:16PM +0200, Jakub Wilk wrote: > Package: irssi,mosh,ncurses-base > Version: irssi/1.2.0-2 > Version: mosh/1.3.2-2.1+b1 > Version: ncurses-base/6.1+20181013-2 > > After a stretch→buster upgrade, the blue status lines in Irssi are no longer > displayed correctly; see

Bug#930037: irssi + mosh: badly rendered status lines

2019-06-05 Thread Jakub Wilk
Package: irssi,mosh,ncurses-base Version: irssi/1.2.0-2 Version: mosh/1.3.2-2.1+b1 Version: ncurses-base/6.1+20181013-2 After a stretch→buster upgrade, the blue status lines in Irssi are no longer displayed correctly; see the attached screenshots. This seems to happen only under mosh.