The problem with trying firefox before xdg-open and htmlview is that if firefox is installed, it will be used and the user's browser choice (which he has set in GNOME, KDE, or using the $BROWSER environment variable, or perhaps by other means) is ignored. xdg-open and htmlview on the other hand will try to invoke the user's chosen browser. Because of that, I still suggest the order xdg-utils, htmlview, and only after them specific browsers - reopening for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
But setting $BROWSER is much more rare than setting up one's preferences via a modern desktop environment's "preferred applications" or somesuch option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Try xdg-open first
Logged In: YES
user_id=201273
Originator: NO
Applied, with modifications.
Logged In: YES
user_id=32457
Originator: YES
The problem with trying firefox before xdg-open and htmlview is that if firefox is installed, it will be used and the user's browser choice (which he has set in GNOME, KDE, or using the $BROWSER environment variable, or perhaps by other means) is ignored. xdg-open and htmlview on the other hand will try to invoke the user's chosen browser. Because of that, I still suggest the order xdg-utils, htmlview, and only after them specific browsers - reopening for that.
Logged In: YES
user_id=201273
Originator: NO
Yes, and fontforge will also look at the BROWSER environment variable, so if that is set the list order is irrelevant.
Logged In: YES
user_id=32457
Originator: YES
But setting $BROWSER is much more rare than setting up one's preferences via a modern desktop environment's "preferred applications" or somesuch option.
Thanks.
I don't know when it happened, but the code is already in git.
Closing "pro forma".