From: Max Nikulin <email@example.com>
Subject: Re: mailto link issue in 9.5.5 and 9.6.6
Date: Fri, 9 Jun 2023 22:58:36 +0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 09/06/2023 16:19, Ihor Radchenko wrote:
> Max Nikulin writes:
> Fixed. https://git.sr.ht/~bzg/worg/commit/60bed811
>>> nil("mailto:email@example.com" (nil))
>> when `browse-url-mailto-function' is set to nil. However docstring to
>> this variable allows nil (perhaps there is really an Emacs bug). Now I
>> am puzzled why setting `browse-url-mailto-function' to
>> `browse-url-default-browser' does not help. I have no idea what should
>> be suggested to users instead of nil.
> This is Emacs bug that should be reported.
> I do not think that we need to document every workaround for Emacs bugs.
> Especially given that Emacs 29 is just around the corner.
Debian bookworm (that is about to be released) has Emacs-28.
It is preferable to have a link clearly describing a workaround, at
least to a specific comment at debbugs. However I believe, it is better
to describe a recipe in Org FAQ and to retain users from customizing
`org-link-parameters' if no web page may be suggested instead.
Anyway we do not have a workaround yet.
prev parent reply other threads:[~2023-06-09 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 2:12 mailto link issue in 9.5.5 and 9.6.6 Scott Randby
2023-06-05 6:00 ` Ihor Radchenko
2023-06-05 19:21 ` Scott Randby
2023-06-05 19:48 ` Ihor Radchenko
2023-06-05 21:40 ` Scott Randby
2023-06-06 6:05 ` Ihor Radchenko
2023-06-06 15:00 ` Scott Randby
2023-06-06 14:30 ` Max Nikulin
2023-06-06 14:49 ` Scott Randby
2023-06-09 15:47 ` Max Nikulin
2023-06-07 12:56 ` Ihor Radchenko
2023-06-08 15:47 ` Max Nikulin
2023-06-08 18:28 ` Scott Randby
2023-06-09 9:19 ` Ihor Radchenko
2023-06-09 15:58 ` Max Nikulin [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).