docs: support-matrix legend vs DECSCLM and the modifiable-but-unimplemented DEC modes #391
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#391
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
support-matrix.mdlegend and the vt-compliance "Consumed without effect" set disagree at the edges:CSI ? 4 h/l) is 🚫, although it is consumed, soft-tracked (felis-grid/src/sink.rs~885-889) and DECRQM-modifiable (KNOWN_MODIFIABLE_DEC_MODES,modes.rs~28). That is the same residue as the ⚠️?12row.docs/reference/protocols/vt-compliance.md(~262) calls "Consumed without effect" the complete set, but?4,?18,?19,?34, … (listed at ~235) are absent from it.Decide either to add a consumed-without-effect row for the modifiable-but-unimplemented DEC modes (and mark DECSCLM ⚠️), or to reword the legend so that 🚫 can coexist with parser consumption.
Decision: add a "consumed without effect" row for the modifiable-but-unimplemented DEC modes (
?4,?18,?19,?34, … as listed in vt-compliance.md) and mark DECSCLM ⚠️, keeping the legend's rule that anything the parser consumes and drops is ⚠️. Make the vt-compliance "complete set" list match.