-
Notifications
You must be signed in to change notification settings - Fork 608
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
wrong xdg-terminal call #355
Comments
I still don't see how I can fix this to work with all terminals.. You can fix it by updating your rofi configuration. xdg-terminal still is not available on my distro's. Not sure what has changed since previous time. |
I wonder on which distro xdg-terminal is not available. Anyways, since xdg-terminal is included in rofi-sensible-script. but later will be called with So what changed since previous time is that xdg-terminal is listed in rofi-sensible-script. But is runs I patched rofi to use xdg-terminal directly on my distribution and will ship it like that for now. |
I am on debian testing and apt-file search xdg-terminal returns nothing. Same goes for ubuntu 14.04. We are going back into the same discussion again.. If I 'fix' xdg-terminal I will break a lot of other (more commonly used) terminals. WHY THE BASDRF!@#!@#!@ CANT TERMINALS FOLLOW A STANDARD. (I am not happy with distributions shipping 'patched' rofi's. We have a config file for a reason, if people want to use it, they can tweak it themself) |
might be better to make rofi see if there is a /etc/rofi.conf and read that first as 'defaults'. |
xdg-terminal is not in xdg-utils because they never added it in the correct list: the line is commented-out ; it was added as a draft script and nobody moved it to the install list. Another important point: it only accepts one argument. So it is not fully usable for rofi, as you can have several words (ssh mode, or run mode by typing them, or drun mode). |
@DaveDavenport Okay. Thanks for that hint. I don't see what you mean with one argument. Could you explain a little more please? If you mean launching several programs this doesn't seem to work with xterm either afaik. There is no |
I will remove xdg-terminal from the rofi-sensible-terminal things and I will make rofi read the /etc/rofi.conf file This way distro can force default behavior in a sane way. |
Very good. Thank you. |
@jubalh openSUSE is just patching xdg-utils heavily. Freedesktop.org one can only use one argument. Fedora is not shipping xdg-terminal, nor does Ubuntu/Debian as @DaveDavenport told you. Same goes for Gentoo and ArchLinux. Accumulating rofi configuration is good, but you better make openSUSE fix your broken xdg-terminal too… |
@sardemff7 It seems you are right. Its only available because they patch it. Well heavily is still a bit exaggerated in my opinion :-) I will see if it makes sense to propose another patch to openSUSE's xdg-utils to make Anyways I think @DaveDavenport solution is good here. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
Version: 0.15.12
Configuration
Default
Steps to reproduce
What behaviour you see
rofi -key-run F2
Rofi is launched in daemon mode.
listening to the following keys:
* window on
* run on F2
* ssh on
xdg-terminal: unexpected option '-e'
Try 'xdg-terminal --help' for more information.
What behaviour you expect to see
I have discussed this already in #201
xdg-terminal doesnt support the
-e
option.Still xdg-* is the way to go if one wants portable opening solutions under Linux.
The text was updated successfully, but these errors were encountered: