fzf tmux, Editor Integration, Troubleshooting, and Performance

Use fzf with tmux and editors, and fix common issues involving shell integration, source commands, and large repositories.

View
StandardDetailedCompact
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
## tmux, Vim, and Neovim integration
Run fzf through fzf-tmux
fzf-tmux -p 80%,60%

# Open the finder in a tmux popup or split-aware wrapper.

Open selected files in Vim or Neovim
fd --type f | fzf -m | xargs -r nvim

# Pass chosen files directly to your editor.

Use fzf-git.sh for Git object pickers
source ~/.fzf-git.sh

# Load Git-focused helper bindings built on fzf.

## Troubleshooting and performance
Inspect your default source command
printf '%s
' "$FZF_DEFAULT_COMMAND"

# Print the configured default command before running fzf.

Prefer fd over find for speed
export FZF_DEFAULT_COMMAND='fd --type f --hidden --follow --exclude .git'

# Switch your source command to fd for large trees.

Ignore hidden or VCS files unless needed
fd --type f --exclude .git --exclude node_modules | fzf

# Reduce list size to improve responsiveness.

Avoid broken matching on colored input
git status --short | fzf

# Use --ansi only when the input really contains ANSI color codes.

Remember shell functions are not external commands
# Child processes spawned by fzf cannot call a shell function unless you export or inline it.

# Use standalone commands for child processes spawned by fzf.

Recommended next

No recommendations yet.