You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem using fzf-tmux with xonsh. I am not actually sure what the problem is but when I call fzf-tmux inside of a tmux session started from xonsh a window opens, some kind of traceback appears, and then the window disappears before I can read it. I had never tried to use fzf-tmux before using this xontrib, so this problem had never bothered me. With the published xontrib, the key bindings don't work inside of tmux for me because they try to use the problematic fzf-tmux. #1 fixes the problem for me but only because it introduced a bug that prevents fzf-tmux from ever being used. This line:
What would your preference be for addressing this? I can think of three options:
Remove all support for fzf-tmux. Just use fzf.
Replace fzf-tmux support with a $fzf_bin variable that when set is used instead of fzf (then the user could choose between fzf and fzf-tmux in .xonshrc).
Retain fzf-tmux support but also implement the $fzf_bin variable which would override it.
What I hope you don't choose is just to implement the @(...) fix I described above because that will lead to the xontrib always using (the broken, for me) fzf-tmux instead of fzf inside of tmux.
The text was updated successfully, but these errors were encountered:
I have a problem using
fzf-tmux
withxonsh
. I am not actually sure what the problem is but when I callfzf-tmux
inside of atmux
session started fromxonsh
a window opens, some kind of traceback appears, and then the window disappears before I can read it. I had never tried to usefzf-tmux
before using this xontrib, so this problem had never bothered me. With the published xontrib, the key bindings don't work inside oftmux
for me because they try to use the problematicfzf-tmux
. #1 fixes the problem for me but only because it introduced a bug that preventsfzf-tmux
from ever being used. This line:xontrib-fzf-widgets/xontrib/fzf-widgets.xsh
Line 12 in 62aacd7
should really be:
What would your preference be for addressing this? I can think of three options:
fzf-tmux
. Just usefzf
.fzf-tmux
support with a$fzf_bin
variable that when set is used instead offzf
(then the user could choose betweenfzf
andfzf-tmux
in .xonshrc).fzf-tmux
support but also implement the$fzf_bin
variable which would override it.What I hope you don't choose is just to implement the
@(...)
fix I described above because that will lead to the xontrib always using (the broken, for me)fzf-tmux
instead offzf
inside of tmux.The text was updated successfully, but these errors were encountered: