View Single Post
Old 10-02-2015, 11:59 AM   #4
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Nope, what you have done is disabled detection of xfce4.
As a result, xdg-open uses its own open_generic() fallback (which parses desktop files) instead of open_xfce() which calls in turn on exo-open (part of xfce, and the true cause of the problem).

It's not so much that xdg-open is broken, it's just designed to work with a bunch of broken desktop-specific openers -- half of which are broken, and xdg-open does nothing to fix the problem.
Some desktops work fine with xdg-open, if their branded opener plays nice with encoded file urls.



But hey, that's "fixing" it too -- there must be some reason why drop-in replacements for xdg-open are so popular.
Some people seem to think the founding principle of xdg-open is entirely flawed.

Last edited by eschwartz; 10-02-2015 at 01:24 PM.
eschwartz is offline   Reply With Quote