Skip to content

docs: say which tmux lemonaid and follow mode need - #44

Open
timblass wants to merge 1 commit into
petergaultney:mainfrom
timblass:docs/tmux-minimum-version
Open

docs: say which tmux lemonaid and follow mode need#44
timblass wants to merge 1 commit into
petergaultney:mainfrom
timblass:docs/tmux-minimum-version

Conversation

@timblass

@timblass timblass commented Sep 3, 2026

Copy link
Copy Markdown

馃崑:
Docs only. Nothing in the code changes.

The repo did not say which tmux it needs. I hit this on tmux 3.5a: with follow mode on, the sidebar stayed in the window it was in when I switched windows.

The cause is in the follow hook. hook_condition() and _came_from() in src/lemonaid/tmux/follow.py use the #{!:...} format operator, which tmux added in 3.6 (from tmux's CHANGES, "CHANGES FROM 3.5a TO 3.6": "add ! and !! for not and not-not"). On an older tmux that term expands to an empty string, so the hook's condition is never true and nothing joins the pane into the new window. Everything else the tmux integration uses is older: pane options and array hooks are from 3.0, run-shell -C and format arithmetic from 3.2.

This PR:

  • adds a "tmux version" subsection to docs/tmux.md under Setup, stating 3.0 as the floor for lemonaid and 3.6 for follow mode, with the reason
  • points to it from the Follow mode section
  • adds a Troubleshooting entry for the symptom
  • names the versions on the tmux bullet in the README
  • adds a CHANGES.md entry under an "Unreleased" heading, with no version bump, since that felt like yours to do at release time. Happy to drop the entry or fold it into whatever you prefer.

The follow hook uses the #{!:...} format operator, which tmux added in
3.6. On 3.5a it expands to nothing, so the hook's condition is never
true and the sidebar stays in the window it was in. Nothing in the
code changes; the README, docs/tmux.md, and CHANGES.md now state the
minimum (3.0 for lemonaid, 3.6 for follow mode) and there is a
troubleshooting entry for the symptom.
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