bugGNU Screen - Bugs: bug #23646, Incorrect smacs in terminfo/TERMCAP

 
 

bug #23646: Incorrect smacs in terminfo/TERMCAP

Submitted by:  Micah Cowan <micahcowan>
Submitted on:  Thu 19 Jun 2008 11:45:40 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Priority: 5 - NormalStatus: Invalid
Privacy: PublicAssigned to: Micah Cowan <micahcowan>
Open/Closed: ClosedRelease: None
Fixed Release: NonePlanned Release: None
Work Required: 0 - Hours

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 21 Jun 2008 07:18:11 PM UTC, comment #1:

An excellent description of why this is not a bug is on the screen-devel mailing list:

http://lists.gnu.org/archive/html/screen-devel/2008-06/msg00020.html

Summary: before one can expect smacs and rmacs to do something special, one must send enacs. terminfo(5) doesn't make this particularly clear, but the Open Group's XCurses standard does.

Micah Cowan <micahcowan>In charge of this item.
Thu 19 Jun 2008 11:45:40 PM UTC, original submission:

My analysis from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144178:

It looks to me as if the fault is in the terminfo description for screen.

Screen does in fact understand ^N/^O, and processes them according to ISO-2022. It does not simply pass them through, but rather processes them itself, to invoke the G1 character set to GL.

However, screen's default value for "charset" is "BBBB02", which uses US-ASCII as the G1 character set. Setting it to "B0BB02" uses the box-drawing characters for G1, which would cause ^N/^O to behave as you expect them to (and would render the terminfo description accurately).

Another way to invoke the box-drawing character set to G1 would be:

(Note the ')', rather than '(').

That would cause no immediately visible change, but ^N/^O would start working as you expect.

Note that, if you're running in UTF-8 mode, screen apparently uses the Unicode box characters, rather than the parent terminal's smacs feature.

So, to sum up, either the terminfo description (and screen's $TERMCAP) should specify '\E(0' / '\E)B', or else screen should default to "B0BB02" for the value of "charset".

Micah Cowan <micahcowan>In charge of this item.

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by micahcowan (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 21 Jun 2008 07:18:11 PM UTCmicahcowanStatusConfirmed=>Invalid
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1