Running `fzf -f whatever` with an `i3` keybinding fails

[a-pav]

Checklist

• [X] I have read through the manual page (man fzf)
• [X] I have searched through the existing issues
• [X] For bug reports, I have checked if the bug is reproducible in the latest version of fzf

Output of fzf --version

0.53.0 (c4a9ccd)

OS

• [X] Linux
• [ ] macOS
• [ ] Windows
• [ ] Etc.

Shell

• [X] bash
• [X] zsh
• [ ] fish

Problem / Steps to reproduce

I have this following script placed at ~/.config/0_conf/t.sh

#!/bin/sh

printf '%s\n' "running..." >> '/tmp/q'; # DEBUG
ls -al ~ | fzf -f conf >> /tmp/q

When I run this file directly inside the terminal, these lines are printed into /tmp/q file:

running...
drwxr-xr-x 61 pav     pav       4096 Jun 24 10:57 .config
-rw-rw-r--  1 pav     pav          0 Apr 20 11:20 .gitconfig

But when I trigger it with an i3 keybinding like:

bindsym --release $hyper+e exec --no-startup-id ~/.config/0_conf/t.sh

only

running...

is printed to /tmp/q file.

I'm not sure what is causing this. This is the first time ever I'm having such a strange issue with a program triggered by an i3 keybinding.

[a-pav]

I've been at this for more than I care to admit and just minutes after I create this issue, I found what the problem is: fzf is only set in PATH for the current shell session in ~/.fzf.zsh file.

Fix is

-ls -al ~ | fzf -f conf >> /tmp/q
+ls -al ~ | ~/.fzf/bin/fzf -f conf >> /tmp/q

Or properly setting the PATH system wide.