finalise termprop APIs
I've committed the main termprop work (#2125 (closed)) to master. However, there are some issue still to be debated while we can still change things:
-
Should this be:
OSC 999 ; set ; ...
OSC 777 ; vte ; set ; ...
OSC 777 ; set ; ...
Currently it's 1. but I'm open to change.
-
Should
STRING
data be allowed to include the tab character? It'd be easy to add an escape for that. -
Speaking of escaping string data, due to the need to have a separator, currently
;
(semi-colon) is reserved and must be escaped. That's a minor inconvenience when preparing the data for sending. We could use a different separator, but all non-control characters would have the same problem; and using a control character (e.g. U+001E RS) would mean changing the parser to accept control character inside the control string, which I really don't want to do. We could alternatively switch this to aDCS
orAPC
control string. -
Any other data types that would be useful beyond the ones added here?
-
Comments on the API? Anything missing, anything inconvenient to use that could be improved?