Troubleshooting¶
Solutions to common issues with tpack.
Key bindings (prefix + I, prefix + U) are not defined
Cause: tmux version too old, or ZSH tmux plugin interfering.
Solution:
- Check your tmux version:
tmux -V. tpack requires tmux 1.9 or higher. - If you have the ZSH tmux plugin installed, try disabling it to see if tpack works.
Plugins don't load when using tmux -f /path/to/config
Cause: Known issue with tmux's -f flag and set -g @plugin syntax.
Solution: Use the alternative plugin definition syntax:
set -g @tpm_plugins ' \
tmuxpack/tpack \
tmux-plugins/tmux-sensible \
tmux-plugins/tmux-resurrect \
'
run '~/.tmux/plugins/tpm/tpm'
Then reload: tmux source /path/to/config
Strange characters appear when installing or updating plugins
Cause: The tmuxline.vim plugin can interfere with tpack's output.
Solution: Uninstall tmuxline.vim and try again.
'failed to connect to server' when sourcing tmux.conf
Cause: Running tmux source outside of a tmux session.
Solution: Make sure you run tmux source ~/.tmux.conf from inside a running tmux session.
tpack returned exit code 2 (Windows / Cygwin)
Cause: Windows line endings (CRLF) in plugin files, often caused by git's core.autocrlf setting.
Solution: Convert all files to Unix line endings:
tpack returned exit code 127 (macOS with Homebrew tmux)
Cause: tmux's run-shell command uses a shell that doesn't read user configs, so Homebrew-installed binaries aren't found.
Solution: Add the Homebrew prefix to tmux's PATH. Find your prefix:
Then add this to tmux.conf before any run commands: