Repository navigation
docs: Correct tmux and mux design guidance - #681
Merged
Merged
Conversation
[Low impact] The documentation changes appear safe to merge; no concrete new defect was found.
|
Reddimus
changed the base branch from
feat/focused-media-context-menu
to
main
October 27, 2026 20:27
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
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.
The tmux and mux-daemon proposals described removed code as current functionality and gave incorrect protocol examples. Clarify what ships today, correct control-mode framing and byte decoding, and remove unsupported implementation-size claims. The tmux proposal is shorter and links to the protocol references.
Validation: isolated native tmux 3.8 protocol fixture; protocol-owner source checks; full
just gauntleton the combined source. This changes two design documents only.