CERBERUS/kitty
1
0
Fork 0
mirror of https://github.com/kovidgoyal/kitty.git synced 2026-09-05 17:28:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

clarify behavior of leading and trailing commas in the graphics protocol

Browse source
This commit is contained in:
Kovid Goyal 2026-08-20 15:49:38 +05:30
parent 4fd834a5e7
commit 9b29654e90
No known key found for this signature in database
GPG key ID: 06BC317B515ACE7C
1 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/graphics-protocol.rst
View file

@ -254,10 +254,12 @@ All graphics escape codes are of the form::
This is a so-called *Application Programming Command (APC)*. Most terminal
emulators ignore APC codes, making it safe to use.
The control data is a comma-separated list of ``key=value`` pairs. The payload
is arbitrary binary data, :rfc:`base64 <4648>` encoded to prevent interoperation problems
with legacy terminals that get confused by control codes within an APC code.
The meaning of the payload is interpreted based on the control data.
The control data is a comma-separated list of ``key=value`` pairs, trailing or
leading commas are undefined implementations may ignore them or reject the
escape code entirely. The payload is arbitrary binary data, :rfc:`base64
<4648>` encoded to prevent interoperation problems with legacy terminals that
get confused by control codes within an APC code. The meaning of the payload is
interpreted based on the control data.
The first step is to transmit the actual image data.