From: Ignacio Casso <ignaciocasso@hotmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: manikulin@gmail.com, 55926@debbugs.gnu.org, larsi@gnus.org
Subject: bug#55926: 29.0.50; message.el does not normalize In-Reply-To field from web links
Date: Mon, 13 Jun 2022 15:17:15 +0200 [thread overview]
Message-ID: <DB6PR0601MB20872386E082107167FB93ECC6AB9@DB6PR0601MB2087.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <87tu8ozqev.fsf@gmail.com>
> One way to check is to put a call to `message' in `message-mailto'
> just after the call to `interactive' to log exactly what's being sent
> to emacs.
>
> Something like
>
> (message "message-mailto received '%s'" url)
>
> and then take a look in "*Messages*"
I've advised `message-mailto' with a message as the one you suggested,
but it seems that function is not being called. What is being called is
`browse-url' -> `browse-url-mail' -> `compose-mail' -> `message-mail',
already defined in message.el. By that time some fields, like "from" and "to",
have already been extracted from the URL, but the In-Reply-To field is
still in the OTHER-HEADERS argument, pending to be parsed.
> I took a look at `message-mailto', and it pretty much just inserts
> what's been passwed to it, so I suspect itʼs an issue with the website
> reply button.
So yes, it probably just inserts what's been passed to it, and if it's
the reply button the one that should ensure that the In-Reply-To field
is normalized, then the bug is in that side. Still, maybe message.el
could ensure that it's normalized anyway just in case?
Regards,
Ignacio
next prev parent reply other threads:[~2022-06-13 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 11:44 bug#55926: 29.0.50; message.el does not normalize In-Reply-To field from web links Ignacio Casso
2022-06-13 12:34 ` Lars Ingebrigtsen
2022-06-13 13:02 ` Ignacio Casso
2022-06-13 14:47 ` Lars Ingebrigtsen
2022-06-13 12:41 ` Robert Pluim
2022-06-13 13:17 ` Ignacio Casso [this message]
2022-06-13 16:14 ` Max Nikulin
2022-06-13 16:33 ` Eli Zaretskii
2022-06-14 16:11 ` Max Nikulin
2022-06-14 16:27 ` Robert Pluim
2022-06-15 16:14 ` Max Nikulin
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=DB6PR0601MB20872386E082107167FB93ECC6AB9@DB6PR0601MB2087.eurprd06.prod.outlook.com \
--to=ignaciocasso@hotmail.com \
--cc=55926@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manikulin@gmail.com \
--cc=rpluim@gmail.com \
/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.