URL: <https://savannah.gnu.org/bugs/?66543>
Summary: OSC 11 and primary device attributes responses sent
in wrong order
Group: GNU Screen
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
Discussion Lock: Any
Release: 5.0.0
Fixed Release: None
Planned Release: None
Work Required: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sun 08 Dec 2024 04:23:35 PM UTC By: Anonymous
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.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66543>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
