[bug] command entries do not start
Pato05 opened this issue · 1 comments
Pato05 commented
As seen in the logs (or also by piping ./sway-launcher-desktop | cat
), for some reason, it prepends -e
to every command, making it fail to start.
Logs:
Starting launcher instance with the following providers: desktop user command
Launching command: -e firefox
Pato05 commented
Out of curiosity, I checked out to v1.5.2
and it works as intended. It seems that the issue is basically the TERMINAL_COMMAND
variable which is set to $TERM -e
(in v1.5.2) and $TERMINAL -e
(in master); and, at least in my case, $TERMINAL
isn't set, but $TERM
is.
TL;DR as a workaround: set the TERMINAL_COMMAND environment variable via env