Hi, Matthew Gabeler-Lee wrote: > This isn't just mlterm. This breaks xterm, xterm-256color, etc. too
I'm sorry, but while I can reproduce the issue with "env TERM=mlterm screen", I can't reproduce it with "env TERM=xterm-256color screen" (on Jessie). In the latter case, dircolors just look fine to me. Anyways, the terminfo definitions this bug is about are _not_ part of the screen package but part of the ncurses-term package. So if the terminal definitions for screen.mlterm needs to be changed, that should be a wishlist bug against ncurses-term, not screen. I'm tempted to reassign this bug report to ncurses-term. What do the ncurses-term maintainers (Cc'ed) think about this? > This munging of the TERM variable also breaks access to other > systems, e.g. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609656. That bug report is not really a bug about TERM variable munging but about screen not having a package relation to ncurses-term. > Some systems don't even think the munged TERM values are "real" and > cause problems like less complaining "WARNING: terminal is not fully > functional". That's IMHO a different issue. You should be able to work around it by either uninstalling ncurses-term locally or installing it remotely. IIRC if screen can't find the according terminfo entries, it won't use them and hence won't change $TERM to something more fancy than just "screen". Regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
