Open wshanks opened 4 years ago
@willsALMANJ, thanks for reporting. I'll try to investigate what the problem with fzf-tmux
is first.
See junegunn/fzf#2166. Do you still think we need a fix other than $(which @(fzf_tmux_cmd))
?
Note that when fzf_tmux_cmd is not available, this xontrib will output the following on every fzf call:
fzf_tmux_cmd not in $PATH or xonsh.builtins.aliases
This can be fixed by suppressing the which output in fzf-widgets.sh:
if 'TMUX' in ${...} and $(which @(fzf_tmux_cmd) err>/dev/null):
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:https://github.com/laloch/xontrib-fzf-widgets/blob/62aacd796c96b9ac9682b57d165105419c162c8d/xontrib/fzf-widgets.xsh#L12
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.