Troubleshooting

Troubleshooting

Config not loading (shows default git:4 instead of custom labels)

Cause: On macOS, dirs::config_dir() returns ~/Library/Application Support/, not ~/.config/. Fixed in v2.0.0 — the app now checks ~/.config/ first.

Fix: Ensure your config is at ~/.config/tmux-quickselect/config.toml.

Popup flashes and closes immediately

Cause: The tmux keybinding was calling nu --login -c 'qs --tmux' (old Nushell version).

Fix: Update tmux.conf:

bind-key O display-popup -E -w 70% -h 60% "qs --tmux"

Then reload: tmux source-file ~/.config/tmux/tmux.conf

qs command not found after install

Cause: Binary not in PATH, or shell function not sourced.

Fix:

1. Check binary: command qs --version (bypasses shell functions)
2. If missing, copy: cp target/release/qs /opt/homebrew/bin/qs
3. Source shell wrapper in your rc file

zoxide error when running qs

Cause: The qs shell function wraps the binary — it runs command qs, takes stdout, and passes it to cd. If qs fails or outputs nothing, cd "" triggers zoxide's error.

Fix: This only happens outside a real terminal (e.g., running from a script). In normal interactive use, the TUI renders to stderr and path goes to stdout correctly.

Deep search is slow

Cause: Recursive scan walks up to 6 levels deep across all configured directories. Large trees with many nested folders take time.

Workaround: The scan is lazy (only runs on first / press per session). Keep configured directories focused. The scan skips: node_modules, target, .git, .next, dist, build, .cache, vendor, __pycache__, .venv, coverage.

Git status shows wrong indicators

Cause: git2 opens the repo at the directory level. If a directory isn't a git repo root, status won't be detected.

Note: Status detection is synchronous — many repos may slow initial render slightly.