screen-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [screen-devel] [bug #32469] 256 color capable terminal is not autode


From: Chris Jones
Subject: Re: [screen-devel] [bug #32469] 256 color capable terminal is not autodetected
Date: Mon, 14 Feb 2011 10:28:04 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Feb 14, 2011 at 03:13:43AM EST, Arkadiusz Miskiewicz wrote:

> URL:
>   <http://savannah.gnu.org/bugs/?32469>
> 
>                  Summary: 256 color capable terminal is not autodetected
>                  Project: GNU Screen
>             Submitted by: arekm
>             Submitted on: Mon 14 Feb 2011 09:13:41 AM CET
>                 Category: None
>                 Severity: 3 - Normal
>                 Priority: 5 - Normal
>                   Status: None
>                  Privacy: Public
>              Assigned to: None
>              Open/Closed: Open
>          Discussion Lock: Any
>                  Release: 4.0.3
>            Fixed Release: None
>          Planned Release: None
>            Work Required: None
> 
>     _______________________________________________________

> 
> Details:
> 
> I'm using 256 colors capable terminal (TERM=konsole-256color; kde
> konsole terminal). When I start screen it doesn't automaticly turn on
> 256 color support which is IMO very bad.
> 
> I have to add:
> 
> # terminfo and termcap for nice 256 color terminal # allow bold colors
> - necessary for some reason attrcolor b ".I" # tell screen how to set
> colors. AB = background, AF=foreground termcapinfo xterm
> 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'

I don't have this.

> # erase background with current bg color
> defbce "on"

Nor this.

> to my .screenrc to get it working somehow. It's unfortunately still
> not enough since screen sets TERM=screen-bce while it should set
> TERM=screen-256color-bce.

Then, you also need to add:
term 'screen-256color-bce'

> When looking for a solution I found few bugreports in distros
> bugtrackers about the same issue but no real (aka patch implementing
> autodetection) solution.

Not sure a patch is necessary, or even advisable.. since it's possible
to get it to work by issuing screen commands manually as demonstrated
above, it can be scripted, presumably giving more flexibility.. The way
vim does it for instance.

cj



reply via email to

[Prev in Thread] Current Thread [Next in Thread]