fzf-tmux: Executes fzf in env-based shell #2691
Open
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 allows executing fzf in a user-defined shell, rather than just using the bash. I noticed that both fzf and fzf-tmux has different behavior due to different shell environment (fzf runs in the commandline shell, but fzf-tmux always executes fzf in bash).
This behavior got prominent when using fzf.fish plugin that had a fish autoloaded function to preview file contents. In fzf it ran succesfully, but in fzf-tmux it threw an error due to missing function in bash.