search

abenz1267 / walker

Application launcher similar to Rofi etc. . Wayland native.
MIT License
263 stars 12 forks source link

Unexpected keybind behaviour when used with Hyprland. #45

Closed leslie-kretai closed 1 month ago

leslie-kretai commented 1 month ago

When walker is called from shell it runs just fine.

If set to be executed from a keybind in Hyprland such as below:

bind = SUPER, R, exec, walker

It will fail to launch and result in a lockfile being made. I was able to work around it by instead doing:

bind = SUPER, R, exec, alacritty -e zsh -c walker

However it will also display the terminal it was ran in instead of hiding it like Clipse does when I run a similar bind setup for that. I didn't see anything in the readme or the wiki on the recommended way to configure it for use in Hyprland, so I'm just curious if i've misconfigured this or if this is a bug.

abenz1267 commented 1 month ago

I'm on Hyprland as well. Make sure that neither /tmp/walker.lock nor /tmp/walker-service.lock exist before launching.

I also just have bind = ALT, RETURN, exec, walker in my config. And for running the service i have exec-once=walker --gapplication-service.