On Sun, Nov 25, 2012 at 05:16:02PM +0100, Axel Beckert wrote: > It's not a bug, it's a feature! (SCNR) And a very old one, too, dating > back to screen 3.0. And 'TERM="screen.linux" is not known in stable' > is wrong. :-) Let me explain: > > Kurt Roeckx wrote: > > When trying to connect to hosts running stable from a screen, I > > get the error that "screen.linux" is unknown. > > This may happen, yes. It may also happen if you connect from a Squeeze > workstation to a Wheezy box: > > It happens if you're running screen on a Linux virtual console and the > host you're starting screen on has the package ncurses-term installed > (e.g. pulled in by rxvt-unicode-256color) while the box you're ssh'ing > to hasn't. > > Background: ncurses-term contains /usr/share/terminfo/s/screen.linux, > also in Squeeze. screen checks if the local host knows about > screen.$TERM and if so, uses that one. From screen/src/ChangeLog: [...] > So to fix this issue for you, please install either ncurses-term on > your stable box, too, or remove it from your wheezy/sid box and the > problem should vanish.
That doesn't seem to be the case. I have ncurses-term installed on both the local and remote systems, and screen quite recently started using "screen.xterm-256color", which breaks dircolors. If I run "ls", I get monochrome. If I run "TERM=screen ls", I get colors. - Josh Triplett
