New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fzf-tmux not working #305
Comments
Here's my tmux.conf |
Thanks for the report. Can you check if the following patch to fzf-tmux helps? diff --git a/bin/fzf-tmux b/bin/fzf-tmux
index c723288..72ed1a7 100755
--- a/bin/fzf-tmux
+++ b/bin/fzf-tmux
@@ -107,7 +107,7 @@ fail() {
fzf="$(which fzf 2> /dev/null)" || fzf="$(dirname "$0")/fzf"
[ -x "$fzf" ] || fail "fzf executable not found"
-envs="env "
+envs="env TERM=$TERM "
[ -n "$FZF_DEFAULT_OPTS" ] && envs="$envs FZF_DEFAULT_OPTS=$(printf %q "$FZF_DEFAULT_OPTS")"
[ -n "$FZF_DEFAULT_COMMAND" ] && envs="$envs FZF_DEFAULT_COMMAND=$(printf %q "$FZF_DEFAULT_COMMAND")" |
Nice fix! That seems to have done the trick. Thanks again! |
Great, thanks for your assistance, I'll push the fix to master. |
Fix #305. ncurses can crash on invalid $TERM. fzf-tmux uses bash on a new pane so we have to make sure that the $TERM is consistent with that of the hosting shell.
Updated fzf-tmux to inherit the TERM value of the hosting shell and also updated fzf to gracefully stop on invalid $TERM. If you used Homebrew to install fzf, you can |
Here's the error message:
The text was updated successfully, but these errors were encountered: