Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] command entries do not start #67

Open
Pato05 opened this issue Aug 29, 2022 · 1 comment
Open

[bug] command entries do not start #67

Pato05 opened this issue Aug 29, 2022 · 1 comment

Comments

@Pato05
Copy link

Pato05 commented Aug 29, 2022

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
Copy link
Author

Pato05 commented Aug 29, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant