<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - xdg-open does not spawn terminal for Terminal=true" href="https://bugs.freedesktop.org/show_bug.cgi?id=92514#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - xdg-open does not spawn terminal for Terminal=true" href="https://bugs.freedesktop.org/show_bug.cgi?id=92514">bug 92514</a> from <a class="email" href="mailto:t_glaessle@gmx.de" title="Thomas Gläßle <t_glaessle@gmx.de>"> Thomas Gläßle</a> <pre>> We should probably start installing xdg-terminal then and use it from xdg-open when Terminal=true. I didn't know about xdg-terminal. Using a dedicated tool like this makes probably more sense than the ad-hoc hack I included above. However, I noticed two main drawbacks in the `terminal_generic` implementation that currently render the tool useless in the absence of a desktop-environment (which is the only case where the tool would be invoked by xdg-open): 1. the $TERM variable does not necessarily correspond to a binary on the system - Using urxvt, the variable is set to 'rxvt-unicode-256color' - Using terminator, the variable is set to 'xterm' by default, but I usually change it to 'xterm-256color', because that worked better in some circumstances (don't remember what exactly) 2. there is no way to use arbitrary terminals. E.g. terminator uses `-x` instead of `-e` > I'd like to encourage use of [...] gvfs-open/kde-open(5)... xdg-open already uses these commands in the presence of a desktop environment. Do you suggest to use and require either of these tools even for systems without desktop environment?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>