PATH not recognized from fish shell? #318

dinodino commented 2024年03月04日 11:26:47 +01:00

I am not sure if there is a problem with my fuzzel config or the problem lies somewhere else but, Ill give it a shot here:
  ~ ❯ echo $PATH  3m 4s 11:26:29 /var/lib/flatpak/exports/bin /usr/local/sbin /usr/local/bin /usr/bin /usr/sbin /sbin /bin
When I run fuzzel from CLI (fish shell) it shows the flatpak apps.

When I run it from my riverwm keybind
 ~ ❯ cat .config/river/init | grep fuzzel 11:26:56 riverctl map normal Super D spawn 'fuzzel'

It doesn't show any flatpaks. So I assume somehow it doesn't get the path like it does when run from cli.

Any idea what could be the issue here or how I can pinpoint it better?

I am not sure if there is a problem with my fuzzel config or the problem lies somewhere else but, Ill give it a shot here: `  ~ ❯ echo $PATH  3m 4s 11:26:29 /var/lib/flatpak/exports/bin /usr/local/sbin /usr/local/bin /usr/bin /usr/sbin /sbin /bin` When I run fuzzel from CLI (fish shell) it shows the flatpak apps. When I run it from my riverwm keybind `  ~ ❯ cat .config/river/init | grep fuzzel 11:26:56 riverctl map normal Super D spawn 'fuzzel'` It doesn't show any flatpaks. So I assume somehow it doesn't get the path like it does when run from cli. Any idea what could be the issue here or how I can pinpoint it better?

markstos commented 2024年03月04日 12:48:33 +01:00

Fuzzel is looking for .desktop files, not binaries.

https://wiki.archlinux.org/title/Desktop_entries

This is not a Fuzzel issue.

Fuzzel is looking for .desktop files, not binaries. https://wiki.archlinux.org/title/Desktop_entries This is not a Fuzzel issue.

lukeflo commented 2024年05月13日 15:55:03 +02:00

Having a similar experience using sway wm. Executables from all $PATH locations are shown when I run fuzzel from the command line, but my custom executables under ~/.local/bin are not recongnized if I invoke it via the key-combo set in my sway-config.

By default, of course, fuzzel only looks for desktop entries (as @markstos mentioned), but since PR #284 has been merged, the --list-executables-in-path option provides the possibility to list other binaries too. Thus, it would be great to know how this (minor) problem could be solved generally.

BTW, I set the list-executables-in-path option via the fuzzel.ini and not as flag to the command itself. But that should make no difference I guess.

Looking forward for some ideas.

Having a similar experience using `sway` wm. Executables from *all* `$PATH` locations are shown when I run `fuzzel` from the command line, but my custom executables under `~/.local/bin` are not recongnized if I invoke it via the key-combo set in my `sway`-config. By default, of course, `fuzzel` only looks for desktop entries (as @markstos mentioned), but since [PR #284](https://codeberg.org/dnkl/fuzzel/pulls/284) has been merged, the `--list-executables-in-path` option provides the possibility to list other binaries too. Thus, it would be great to know how this (minor) problem could be solved generally. BTW, I set the `list-executables-in-path` option via the `fuzzel.ini` and not as flag to the command itself. But that should make no difference I guess. Looking forward for some ideas.

markstos commented 2024年05月13日 16:00:07 +02:00

This is still not a Fuzzel issue, but your custom $PATH not being set in Sway so it's not part of the environment when Fuzzel is launched.

You need to look up how to set environment variables when launching Sway.

This is still not a Fuzzel issue, but your custom `$PATH` not being set in Sway so it's not part of the environment when Fuzzel is launched. You need to look up how to set environment variables when launching Sway.

lukeflo commented 2024年05月13日 22:36:30 +02:00

@markstos thanks for your fast reply. Indeed, it solved the problem. I thought adding to the PATH in .zprofile was early enough, but since sway is executed earlier, I had to move the code to /etc/profile. Now all custom executables are visible.

I don't know where flatpak adds to the PATH since I'm not using it. But might be worth a look to overcome the initial issue by the OP.

@markstos thanks for your fast reply. Indeed, it solved the problem. I thought adding to the `PATH` in `.zprofile` was early enough, but since `sway` is executed earlier, I had to move the code to `/etc/profile`. Now all custom executables are visible. I don't know where `flatpak` adds to the `PATH` since I'm not using it. But might be worth a look to overcome the initial issue by the OP.