Won't launch

[Geraint]

When ever I try to launch this, I get the following error message:

'/home/my-user-name/.tmux/plugins/tmux-fzf/scripts/.sh' returned 127

I notice the part of the filename before the extension is missing.

I'm running tmux 2.6 on WSL.

[sainnhe]

Please checkout #1 branch to see if it solves this problem.

[Geraint]

Yeah, its launching as expected now.

[Geraint]

Many thanks for fixing this.

[sainnhe]

I've merged #1 to master, now you can checkout master branch and update this plugin.

[leveled]

Hey @sainnhe, I'm running into the same issue. I'm on the latest version of the plugin.

Tmux Version: 2.3
OS: Debian 10

[sainnhe]

@leveled Very sorry, I've tried tmux 2.3 on my surfacepro/archlinux, but still cannot reproduce.

Please try minimal tmux configuration(with installation command only), and reinstall this plugin.

Btw, I think this may be related to the version of bash. What's your bash version?

[Gerrit-K]

I can confirm the issue on at least three setups. All of them run on the same .tmux.conf with minimal requirements (tpm + tmux-fzf). Moreover I should note that I use the tmux zsh plugin (including autostart).

1. Raspbian GNU/Linux 9 (stretch), 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
   • zsh 5.3.1 (arm-unknown-linux-gnueabihf)
   • GNU bash, version 4.4.12(1)-release (arm-unknown-linux-gnueabihf)
   • tmux 2.3
2. WSL, Debian GNU/Linux 9 (stretch), 4.4.0-17134-Microsoft #706-Microsoft Mon Apr 01 18:13:00 PST 2019 x86_64 GNU/Linux
   • zsh 5.3.1 (x86_64-debian-linux-gnu)
   • GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
   • tmux 2.8
3. Linux Mint 19.2, 4.15.0-65-generic, Support for multi-word new session title #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
   • zsh 5.4.2 (x86_64-ubuntu-linux-gnu)
   • GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
   • tmux 2.6

I don't see any common denominator here, but if I find the time, I'll start some debugging.

[sainnhe]

It seems that some people still have this problem, but I'm unable to reproduce this on my Arch Linux on PC and Debian Server(debian 9.11 stretch). I have no idea what is going on.

Help wanted.

[Gerrit-K]

Okay, so here's what I've got so far:

The mentioned error occurs when ITEM is empty at main.sh:18. This can basically only happen if something is going wrong in .fzf-tmux. My first guess was that the embedded script might be outdated (and it is) but that's not the issue.

In my case, the issue is that tmux could not find fzf (more on that below). This results in the fallback at .fzf-tmux:10 which sets fzf="$(dirname "$0")/fzf. This fallback makes perfectly sense for the original script along with the compiled binary which is stored at this exact location. Obviously though, the fzf binary is not present in this folder (since it's not part of this repo), so the next line fails with fzf executable not found. This error however is printed to stderr, so it's not only not propagated up to the calling command substitution but also eaten up by tmux (i.e. tmux doesn't print stderr, e.g. tmux run-shell 'echo foo >&2' has no output). This made the error very difficult to spot.

So why is fzf not found? To begin with, I'm currently running zsh as my default shell and configured zplugin to manage lots of scripts, tools and helpers, one of which is fzf. Zplugin is very careful to not pollute global directories, so it stores all binaries in user-local paths and only propagates them to the current shell. The problem is that tmux somehow still uses bash instead of zsh, so zplugin is not loaded and therefore fzf is not in $PATH. The only thing I still don't get is why (any hints on this are appreciated). I've set the corresponding options (at least the ones I know of) but it doesn't work:

~ $ tmux show-options -g | grep default-
default-command "/usr/bin/zsh"
default-shell "/usr/bin/zsh"
~ $ tmux run 'echo $SHELL'
/bin/bash

So technically, it's not an issue with tmux-fzf, but all of the above is very specific to my case. For others it might be best to start checking whether tmux is able to find fzf: tmux run-shell 'command -v fzf'

[sainnhe]

@Gerrit-K Very helpful. Thanks! I've updated README.