Repository navigation
Conversation
why: A shared 3.3a floor does not make every control, buffer, shell or layout operation safe on that release. Readers had no page that says which features need a newer tmux, what a library does below it, and which ports have evidence for their refusal. what: - Add the optional features to the tmux support guide: library-managed control mode from 3.7, named buffer deletion and rename from 3.4, captured run-shell output outside 3.3 and 3.4, exact 3.7 break-pane and name restrictions, split percentages sent as -l N%, and layout validation below 3.4 - Define the five support states (Non-operative, Timing-sensitive, Operative with synchronization, Qualified, Unverified) and give the native state for each affected release - Name what the Python, tmuxp, Go and Rust changes enforce, and mark every other port Unverified until its change has checked evidence - State that guards cover library-chosen operations and literal command items, not opaque shell text or configured alias bodies - Update the guides index card to mention optional features
why: The optional-feature page is only useful while each feature keeps its own requirement, the states use the contract's names and results name ports instead of summarizing them as a ratio. what: - Require a table row for each optional feature with its tmux release - Require a defining row for each of the five support states - Reject ratios such as "5/8" or "five of eight" and require every port group in the port table Verified: the check passes; dropping the Unverified row, changing the named-buffer requirement to 3.3 and replacing a port group with a "five of eight" count each make it fail on the matching case, and the restored page passes.
tony
force-pushed
the
bump-min-tmux-000
branch
from
October 17, 2026 13:38
2a58002 to
99df2a3
Compare
tony
force-pushed
the
bump-min-tmux-001
branch
2 times, most recently
from
October 17, 2026 16:34
24dd014 to
ad179f0
Compare
tony
force-pushed
the
bump-min-tmux-000
branch
from
October 17, 2026 17:54
564121d to
7a7a677
Compare
tony
force-pushed
the
bump-min-tmux-001
branch
from
October 17, 2026 17:54
ad179f0 to
3d7407a
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Record each optional tmux feature's requirement on the tmux support guide, separately from the 3.3a core minimum, with the five support states and what each port does. This is stacked on the core minimum change.
paste-buffer -d -bstays on 3.3a)run-shellstdoutbreak-paneand names with:or.-l N%; raw-prefused on 3.4The guide defines Non-operative, Timing-sensitive, Operative with synchronization, Qualified and Unverified, gives the native state on each affected release, and states that guards cover library-chosen operations and literal command items but not opaque shell text or alias bodies. The port table names what Python, tmuxp, Go and Rust enforce; every other port is marked Unverified, and no result is summarized as a count.
A new check (
site/test/tmux-support-page.test.ts) requires a table row per feature with its release, a defining row per state, every port group in the port table, and no ratio.Validation (local; same environment and component runs as the core change):
docs/deliberate-break-support-page.login the evidence folder).Not qualified: port rows rest on those ports' pull request descriptions, not on a run of their code here, and Qualified there means native Linux runs. The assembled-site build and publication audit run in hosted CI.
Closes #147.