Create a guideline of minimal terminal parsing capabilities
I'm not sure if this is in scope, but i think it would be quite important to have a document to point terminal implementers to that defines minimal parsing requirements for terminals in a clear way.
This could also serve as a document that defines what sequences other new proposals could use as a framework.
I think this should for now be focused on correctly parsing valid sequences because that is much easier to agree upon and implement in the very much diverse space of parsing structures in terminals. In a way that would also guide applications in what nicely formed sequences that should ideally emit.
One reason i'm opening this ticket is because it seems the of the newer/simpler terminal implementation some seem to ignore intermediates (
!\"#$%&'()*+,-./) and prefixes (
<=>?) in many cases, but this is essential code space we want to use for new sequences. I've recently got some fixes merged into the linux kernel, but it would be great to avoid newer terminals falling into the same traps and have something to point to that reflects consensus.