James Holderness

I should mention that one of the other ideas I had considered was using mode queries, and then you could potentially have two of them - one for copying and...

> And if a TE wants to guard even clipboard-write by user permission, maybe let the DA state shift: I don't think we need anything as complicated as that to...

> I also suggest to leave the buffer details out of this, so a TE indicating OSC52 support has at least write-access to one "clipboard buffer" Well I was hoping...

I've now tested 18 terminals that have some form of `OSC 52` support. There are definitely others, but that seems like a representative sample to start with. And of that...

> I'm not sure how much terminal feature "detection" fiddling with DA1 will break. I don't see this being an issue. Modern terminals quite frequently change their `DA1` report as...

> I would relax the definition of working to: the text the application supplied can be use in some kind of clipboard. Not requiring the one used by specific gestures,...

OK, below is my proposal for the specification. If everyone here is happy with this, I'd like to invite a few more terminal devs to comment. If we can get...

> Just a remark regarding polite vs. harsh wording. From my limited tech/scientific wording background I often see there "may" in the meaning of MUST, where SHOULD gets replaced by...

OK, I think all your feedback is good, but to avoid debating this forever, I decided to cut out the stuff that I think we can live without for now....

@dnkl, @gnachman, @ismail-yilmaz, @wez: We've been discussing the idea of extending the `DA` report to include another feature number that would indicate a minimal level of support for `OSC 52`....