Here's an example that relates the problem : - chromium-browser uses xdg-open when unknown (magnet:) uri schemes are opened - xdg-open uses exo-open - exo-open does not know what to do and launch the web browser... I don't think it's a bug in chromium : using xdg-open is legitimate, and one expects xdg-open to call exo-open in xfce (it calls gnome-open in gnome). It would be very nice exo's handling of uri schemes be configurable, so one could associate any uri scheme to any desktop rc file, instead of giving back the responsability to open the right url to the browser. Regards, Jérémy.
There never was a concept of arbitrary URI schemes in Xfce. There is the x-scheme-handler/foo FreeDesktop.org standard now, which Xfce should support. The first step here is use it for Web Browser and Mail Reader. The second step is to add a page for managing arbitrary schemes.
I confirm this, currently adding x-scheme-handler/foo=fooapp.desktop to mimeapps.list does not make exo-open open foo:// urls in fooapp.desktop. Tried to add line to both standard [Added Associations] section of mimeapps.list and non-standard [Default Applications] section, which Thunar uses (which is a bug on its own).
Well, in xfce 4.10, exo-open magnet://?xt=urn:btih:31D... opens up my preferred torrent manager. But NOT exo-open magnet:?xt=urn:btih:31D... which is also a proper URI. So whoever "fixed" this since the initial report (thank you!), could perhaps have another look at it.
I'm not that familiar with Glib at all, but the documentation[1] says g_regex_* functions are Perl-compatible. In this case, the regex: ^([:alpha:][[:alnum:]\.+-]*):(//(([^@/]*@)?(([-[:alnum:]]+(\.[-[:alnum:]]+)*)(:([0-9]+))?))?)?(/?[^?\#]*)(\?[^\#]*)?(\#.*)? seems to correctly parse URLs[2] with scheme, authority, hostname, port, path, query, and fragment in backreferences \1, \4, \6, \9, \10, \11, and \12. At least in Python. :D [1]: https://developer.gnome.org/glib/2.37/glib-Perl-compatible-regular-expressions.html [2]: https://en.wikipedia.org/wiki/URI_scheme#Generic_syntax
The RFC-proposed regular expression[1] is a bit simpler, though. -_- [1]: https://tools.ietf.org/html/rfc3986#appendix-B
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/exo/-/issues/1. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev