On 2011-03-14 21:27:29 +0100, Marc Lehmann wrote:
> > > Is it a bug in rxvt-unicode, ncurses-base (which provides
> > > /lib/terminfo/r/rxvt-unicode, but perhaps following recommendations
> > > by rxvt-unicode developers) or screen (which sends "is2")?
> 
> Almost certainly screen - ncurses programs do the right thing and don't
> reset the terminal *after* configuring it.

screen doesn't reset the terminal after configuring it. This can be
seen with xterm and gnome-terminal.

> I don't know what screen tries to accomplish, but if it wants a clean
> state, then it needs to output all the intiialisation sequences *before*
> configuring the terminal, as obviously configuration can be lost when
> intiialisaing the terminal.

Perhaps. It seems to make sense. However the terminfo(5) man page
doesn't document that it should be done in this order.

> And if screen outputs is2 but not the other sequences as required by
> terminfo, that's an even bigger wtf. There is no reason to do so, and that
> *will* break things.

I don't know what screen does exactly, but

  tput smcup
  tput init
  tput rmcup

works in xterm, but not in rxvt-unicode. This may be the problem
with screen.

> > > Even if one considers that screen does something bad and should be
> > > fixed, the incompatibility between rxvt-unicode and other terminals
> > > (xterm, gnome-terminal) can be annoying.
> 
> Hmm, which incompatibility is there?

See above. Unless the above sequence is incorrect...

> "tput init" is the canonical way to bring your terminal into a clean
> state after a curses program (or screen, which loves to crash...)
> crashed. The change just implemented that.

No, this is "tput reset" that brings the terminal into a clean state.
"tput init" doesn't do that in at least two major terminals: xterm
and gnome-terminal.

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to