jerch

We took the state handling from [vt100.net](https://vt100.net/emu/dec_ansi_parser), which lists for OSC_STRING state: > event 00-17,19,1C-1F / ignore Paul Williams has tested that against multiple DEC VT devices, so I tend...

Sorry, I strongly disagree. The parser is the best tested thing we have in a continuity sense, thanks to Paul Williams. While xterm had to reverse engineer most things back...

We cannot easily change the parser rules, as it will have unforeseen side effects on the shape of sequences. OSC is specced to safely transmit only ASCII printables, so no...

I just checked ECMA-48 - it also allows 00/08-00/13 (BS, HT, LF, VT, FF CR) in OSC. Seems DEC had a stricter idea about OSC, idk why. So I am...

@NickLediet I'd say those are typos, which entered the stage in this PR #4612 (commit: 859c9ec) Interesting, that yarn on an older version would let this pass, as far as...

There were issues with the sogou pinyin in the past, plz also check the issue history, if there is a workaround.

@j4james "52" is fine by me, if it is not taken by something else. I don't have an extensive list of taken DA1 numbers (beside the old ones), maybe @textshell...

> I'm assuming only copy is required, because a lot of terminals won't support paste, and I think copying is what apps care about the most. Oh is that so?...

@j4james Yeah, I also would prefer the simplest possible idea here, as it increases the chance of adoption. I am not deep enough into copy&paste usage across console apps, so...

> I don't think we need anything as complicated as that to start with, because I've yet to see a terminal that prompts the user for clipboard writes. There are...