On 2015-08-26 12:05, Axel Beckert wrote:
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
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
On 2015-08-26 18:05 +0200, Axel Beckert wrote:
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
On Wed, Aug 26, 2015 at 06:05:50PM +0200, Axel Beckert wrote:
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
Package: screen
Version: 4.3.1-1
Followup-For: Bug #622265
This isn't just mlterm. This breaks xterm, xterm-256color, etc. too -- i.e.
screen is now slightly incompatible with X environments in general. Yuck.
This munging of the TERM variable also breaks access to other systems, e.g.
Package: screen
Version: 4.0.3-14
As for TERM=screen.mlterm, the output of dircolors empties.
$ echo $TERM
mlterm
$ dircolors
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;...
export LS_COLORS
$ screen
$ echo $TERM
screen.mlterm
$ dircolors
LS_COLORS='';
export
6 matches
Mail list logo
