bug: work.nix tmux status-right depends on an unmanaged external script path #50

Closed
opened 2026-06-29 13:02:52 +01:00 by lyrathorpe · 0 comments
Owner

Problem

users/emmathorpe/work.nix wires the tmux status-right to an external script by absolute path:

set -g status-right "#(/run/current-system/sw/bin/bash $HOME/code/kube-tmux/kube.tmux 250 red black)"

$HOME/code/kube-tmux/kube.tmux is an unmanaged dependency outside this flake. If that repo is not cloned, the status line errors on every tmux refresh.

Impact

Broken/noisy tmux status on a fresh checkout of the work box until the side repo is manually cloned. The /run/current-system/sw/bin/{bash,docker} absolute paths are defensible (stable system-profile path) but could be tidied.

Suggested fix

Guard the path (only set status-right when the script exists), or vendor kube.tmux into the repo (e.g. a pkgs.writeShellScript) so it is always present.

## Problem `users/emmathorpe/work.nix` wires the tmux `status-right` to an external script by absolute path: ``` set -g status-right "#(/run/current-system/sw/bin/bash $HOME/code/kube-tmux/kube.tmux 250 red black)" ``` `$HOME/code/kube-tmux/kube.tmux` is an unmanaged dependency outside this flake. If that repo is not cloned, the status line errors on every tmux refresh. ## Impact Broken/noisy tmux status on a fresh checkout of the work box until the side repo is manually cloned. The `/run/current-system/sw/bin/{bash,docker}` absolute paths are defensible (stable system-profile path) but could be tidied. ## Suggested fix Guard the path (only set `status-right` when the script exists), or vendor `kube.tmux` into the repo (e.g. a `pkgs.writeShellScript`) so it is always present.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lyrathorpe/nixfiles#50