Skip to content

Docs(api): Describe the tmux Server object - #47

Merged
tony merged 1 commit into
masterfrom
docs-server-object-description
Oct 2, 2026
Merged

tony merged 1 commit into
masterfrom
docs-server-object-description

Conversation

@tony

@tony tony commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Server documentation led with its transport rather than the tmux objects callers manage. Java and Kotlin now explain sessions, windows, panes, socket selection, and the difference between closing this handle and stopping tmux. Kotlin keeps its suspend and Java interoperability contracts explicit.

Validation: ./gradlew :libtmux-mcp:test check passed on Temurin 25 in 4m 16s, including Javadoc link validation, formatting, and the native test suites. This changes API comments only.

why: Server's transport does not explain its role in tmux.

what:
- Lead Java and Kotlin Server documentation with the tmux object model.
- Explain socket selection, session queries and resource cleanup.
- Keep Kotlin suspend and Java interoperability behavior explicit.
@tony
tony merged commit 72d7bbe into master Oct 2, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant