Add $FZF_COMPLETION_TMUX_LEGACY for Flexible tmux Integration #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update introduces the
$FZF_COMPLETION_TMUX_LEGACY
environment variable, giving users the flexibility to switch between the legacyfzf-tmux
wrapper and the modernfzf --tmux
integration. By default,$FZF_COMPLETION_TMUX_LEGACY
is set totrue
, preserving the current behavior. When set tofalse
, it leverages nativefzf --tmux
, fixing command interpretation issues like:The README has been updated with instructions for using the new environment variable and includes a tip on enabling fzf’s tmux mode (
export FZF_TMUX=1
) for smoother completion experiences, as suggested in the fzf README.Key Changes:
fzf_bash_completion_selector
to switch between legacy and native tmux handling based on$FZF_COMPLETION_TMUX_LEGACY
.Why This Change:
This fixes known issues with legacy
fzf-tmux
command interpretation while allowing users to switch to the more robust nativefzf --tmux
integration for enhanced reliability.Testing: