aboutsummaryrefslogtreecommitdiff
path: root/scripts/zfs-replicate
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-19 13:01:19 -0500
committerCraig Jennings <c@cjennings.net>2026-05-19 13:01:19 -0500
commit685272399d7dbc35aea6028d6741963399d84e3f (patch)
tree33bf2ccae4ca1e1d11029b57be04af3e6ad561bd /scripts/zfs-replicate
parent924fec1f00e7ef5e497575488701e8c9eb2606f0 (diff)
downloadarchsetup-685272399d7dbc35aea6028d6741963399d84e3f.tar.gz
archsetup-685272399d7dbc35aea6028d6741963399d84e3f.zip
feat(tmux-util): add go subcommand (attach-or-create)
tmux-util go <name> attaches to a session named <name> if it exists, creates it otherwise. Behavior depends on whether the caller is already inside tmux: - Outside tmux: `tmux attach-session -t <name>` (existing) or `tmux new-session -s <name> -c $PWD` (new). - Inside tmux (TMUX env set): `tmux switch-client -t <name>` (existing) or `tmux new-session -d -s <name> -c $PWD` followed by `switch-client` (new). Attaching from inside tmux would nest sessions and break the outer view, so the inside path uses switch-client instead. The existence check uses `tmux has-session -t =<name>` with the leading `=` to force exact-match. Without it, tmux does prefix matching, which would let `go foo` resolve to a session named `foobar`. I added 6 new tests covering both inside/outside-tmux paths, both create/attach paths, plus error handling for missing or empty name arguments. fake-tmux picked up handlers for new-session (mutates state), attach-session and switch-client (record-only), and the `=`-prefix form of has-session. Total suite: 32 tests, all green.
Diffstat (limited to 'scripts/zfs-replicate')
0 files changed, 0 insertions, 0 deletions