bugGNU Screen - Bugs: bug #66543, OSC 11 and primary device...

 
 

bug #66543: OSC 11 and primary device attributes responses sent in wrong order

Submitter:  None
Submitted:  Sun 08 Dec 2024 04:23:35 PM UTC
   
 
Category:  Program Logic Severity:  3 - Normal
Priority:  * 5 - Normal Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  5.0.0
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 08 Dec 2024 04:23:35 PM UTC, original submission:  

When presented with OSC 11 and then primary device attributes, screen 5.0.0 responds in the wrong order:

$ printf '\033]11;?\a\033[c';read
^[[?1;2c^[]11;rgb:0000/0000/0000^G

I sent primary DA (\033[c) after OSC 11, so the expected response would be:
^[]11;rgb:0000/0000/0000^G^[[?1;2c

For comparison, here's XTerm (without screen):
$ printf '\033]11;?\a\033[c';read
^[]11;rgb:0000/0000/0000^G^[[?63;1;2;4;6;9;15;16;22;28c

(The actual contents of primary DA don't matter here; just the order.)

This is a problem in programs that send a number of queries (including OSC 11), and expect only user input to be sent after the last query (in this case primary DA). In such programs, screen's OSC 11 response will bleed into user input.

Anonymous

 

(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

 

CC list is empty

 

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.

 

No changes have been made to this item

Back to the top

Powered by Savane 3.14-573e.
Corresponding source code