The only available binary under /usr/bin is env to allow writing portable scripts (e.g. #!/usr/bin/env bash shebang). But reading the past issues, doing /usr/bin/env infocmp would result in a regression on MacOS where we want to ensure the system infocmp is used. Maybe the condition could call infocmp differently depending on the OS (e.g. use uname -s), or test if the executable exits and try to fallback to the one from the env if it does not?
Workaround: Add the previous command to .tmux.conf.local:
The change made in 2cf4d9a10415f58612c1a387fbeb9c0efe79d751 breaks 256-color support on NixOS which does not have
/usr/bin/infocmp
:The only available binary under
/usr/bin
isenv
to allow writing portable scripts (e.g.#!/usr/bin/env bash
shebang). But reading the past issues, doing/usr/bin/env infocmp
would result in a regression on MacOS where we want to ensure the systeminfocmp
is used. Maybe the condition could callinfocmp
differently depending on the OS (e.g. useuname -s
), or test if the executable exits and try to fallback to the one from the env if it does not?Workaround: Add the previous command to
.tmux.conf.local
: