Closed Star-veil closed 4 months ago
Kitty should be recognized natively, if it's in your $PATH. From the past experience Nix users do weird stuff with their config :P. Might be a symlink issue? Or the $PATH being set after Walker is being launched.
Try setting the terminal in the config explicitly.
{
"terminal": "kitty"
}
That might not help, if your $PATH is not set correctly before launching Walker.
It actually tries to launch them now, but now it returns:
exec: "vesktop": executable file not found in $PATH
exec: "lutris": executable file not found in $PATH
etc..
That might not help, if your $PATH is not set correctly before launching Walker.
I'm assuming it's this then, no idea what I could have that messes with this
Environment variables, such as path, are different when run as a systemd service. I didnt have time to figure out a solution yet though
Ok, i'll close this here then for now, since it's not related to Walker.
I'm on nixOS, I installed walker using the homemanager module; I have three different scenarios:
walker --gapplication-service
, same as above, works fine and speeds up following launchesprograms.walker.runAsService = true;
, walker manages to open just fine, but when trying to launch something it returnsterminal is not set
and doesn't do anything, I am able to continue scrolling through the entries without the possibility to run it. Killing the service and running it again withwalker --gapplication-service
works fine.