all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Ignacio Casso <ignaciocasso@hotmail.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 14:41:44 +0200	[thread overview]
Message-ID: <87tu8ozqev.fsf@gmail.com> (raw)
In-Reply-To: <AM4PR0601MB20813E67135C0E41921FDE4EC6A89@AM4PR0601MB2081.eurprd06.prod.outlook.com> (Ignacio Casso's message of "Sun, 12 Jun 2022 13:44:31 +0200")

>>>>> On Sun, 12 Jun 2022 13:44:31 +0200, Ignacio Casso <ignaciocasso@hotmail.com> said:


    Ignacio> Sorry if my report is not clear enough, or if the bug is actually in the
    Ignacio> website reply button, I don't really know much about email technical
    Ignacio> details.

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. 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*"

Thanks

Robert
-- 





  parent reply	other threads:[~2022-06-13 12:41 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 [this message]
2022-06-13 13:17   ` Ignacio Casso
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=87tu8ozqev.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=55926@debbugs.gnu.org \
    --cc=ignaciocasso@hotmail.com \
    --cc=larsi@gnus.org \
    --cc=manikulin@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.