bugGNU Screen - Bugs: bug #32469, 256 color capable terminal is not...

 
 

bug #32469: 256 color capable terminal is not autodetected

Submitter:  Arkadiusz Miskiewicz <arekm>
Submitted:  Mon 14 Feb 2011 08:13:41 AM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  * 5 - Normal Status:  Invalid
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Release:  4.0.3
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 05 Sep 2015 04:44:22 PM UTC, comment #1: 

Screen auto detects colors just fine

If it is still a problem with newer versions please reopen and provide faulty terminfo file.

Amadeusz Sławiński <amade>
Group administrator
Mon 14 Feb 2011 08:13:41 AM UTC, original submission:  

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'
# erase background with current bg color
defbce "on"

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.

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

Arkadiusz Miskiewicz <arekm>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by amade (Posted a comment)
  • -email is unavailable- added by arekm (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-09-05 amade StatusNone Invalid
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code