-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Change term overriding variable and improve error handling? #98
Comments
BTW I'm currently using |
BTW: |
I'm currently using Here is the content of looking-glass-client.desktop, which is already defined according to your suggestion:
|
Looks good to me. |
I was troubled by an stupid issue where I can launch other desktop entries but not the Looking Glass Client. Today I decided to investigate it.
Initially I though the desktop entry was bad but it worked with
gkk-launch
. I then launchnwg-drawer
in terminal and found that it is trying to runxterm-kitty
to launch a console program (which looking-glass-client is). I then realized thatnwg-drawer
uses $TERM as the default terminal, which is almost never going to give you a executable file name, since this variable denotes the terminal capabilities, not the binary itself.Unfortunately there is no standard way to indicate the preferred default terminal, but whatever that would be, it is not gonna be $TERM, and such silent failure is confusing, as there is no error in main menu, and no graphical error message when the terminal failed to launch.
I think we could use $TERMINAL as overriding variable instead (used by i3 and suggested in another post, and actually check if this is a valid terminal and tell the user. Or show a graphical error message when the terminal failed to launch.
The text was updated successfully, but these errors were encountered: