Yofi launches through terminal but not through sway config

[cm320]

Other launchers like dmenu and rofi launch fine setting the $menu as the command that opens it from terminal.

Output of swaymsg exec yofi results [common/ipc-client.c:67] Unable to connect to /run/user/1001/sway-ipc.1001.1158.sock

Have exhausted my google-fu and don't know what next to do

[l4l]

swaymsg exec yofi works for me, what's your terminal? Also make sure that $SWAYSOCK is a valid socket file.

Anyway that's a sway message from here. So I suppose it's an issue of swaymsg, not yofi's. This one might be related: swaywm/sway#6451 and perhaps sway troubleshooting at arch wiki might help.

[pragmaticmero]

I've had the same problem, the solution is to... well
set $menu "yofi apps"
or more specifically and error proof.
bindsym Mod4+d exec "yofi apps"
It seems that "yofi apps" works, it's just a specification of what mode of yofi you want to start with, the default is yofi.

Did I get the issue wrong? omg. I need to learn more english then.

[l4l]

That's quite a strange behavior, may I ask you for stderr log of sway? There may be be some hint.

yofi apps actually avoids blacklist handling (that one is a bug), perhaps it related somehow.

[exul]

I ran into a similar issue, except that swaymsg exec yofi wouldn't produce any output (with exit code 0) while running yofi from the terminal worked just fine. In my case the issue was that I installed yofi via cargo, resulting the binary being placed in $HOME/.cargo/bin/yofi. This combined with adding $HOME/.cargo/bin via set -U fish_user_paths $HOME/.cargo/bin $fish_user_paths meant that fish knew about the path, but sway didn't.
P.S. posting this as a comment of this issue, since that's what my search engine found when looking for a solution for the above problem.