From: Pierre Neidhardt <ambrevar@gmail.com>
To: 18986@debbugs.gnu.org
Subject: bug#18986: #18986 Design bug in browse-url.el: browse-url-can-use-xdg-open's logic uses overly strict assumption
Date: Mon, 12 Feb 2018 17:23:26 +0100 [thread overview]
Message-ID: <87a7wep475.fsf@gmail.com> (raw)
In-Reply-To: <85lhnnw9t7.fsf@bertrandrussell.Speedport_W_723V_1_36_000>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Sorry for digging out this old issue, but it seemed that Florian's
suggestion (which was pretty good in my opinion) was never answered.
I've been battling with browse-url for longer than necessary, it seems
to me that there are just too many rough edges around xdg-open,
xdg-mime, ~/.config/mimeapps.list, `mailcap-mime-extensions'...
Having `browse-url-can-use-xdg-open' _and_ a customizable list of
default browser in `browse-url-default-browser' would help tremendously.
I'd like to add one more feature which could relieve non-DE users even further:
(defun browse-url-default-browser (url &rest args)
...
(apply
(cond
...
+ ((getenv "BROWSER") (executable-find (getenv "BROWSER")))
((memq system-type '(windows-nt ms-dos cygwin))
'browse-url-default-windows-browser)
The "BROWSER" environment variable is relativement common and if it is
set, it most probably means that the users did that themselves.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-02-12 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:04 Design bug in browse-url.el: browse-url-can-use-xdg-open's logic uses overly strict assumption Florian v. Savigny
2014-11-08 17:19 ` bug#18986: " Jan D.
2014-11-08 17:19 ` Jan D.
2014-11-08 18:05 ` Stefan Monnier
2014-11-15 12:31 ` Florian v. Savigny
2014-11-15 12:31 ` Florian v. Savigny
2018-02-12 16:23 ` Pierre Neidhardt [this message]
2018-02-12 17:47 ` bug#18986: #18986 " Eli Zaretskii
2018-02-12 17:51 ` Pierre Neidhardt
2018-02-12 18:42 ` Eli Zaretskii
2018-02-14 21:46 ` Pierre Neidhardt
2018-02-15 2:14 ` Noam Postavsky
2018-02-16 0:28 ` Pierre Neidhardt
2018-02-16 0:42 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7wep475.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=18986@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.