From: Michael Albinus <michael.albinus@gmx.de>
To: Bruno Victal <mirai@makinata.eu>
Cc: 66798@debbugs.gnu.org
Subject: bug#66798: 29.1; Debbugs leftover headers in message-mode
Date: Sat, 28 Oct 2023 19:34:40 +0200 [thread overview]
Message-ID: <87v8aqmz0v.fsf@gmx.de> (raw)
In-Reply-To: <6dc865b1-0a1a-432e-9088-bf90a0426108@makinata.eu> (Bruno Victal's message of "Sat, 28 Oct 2023 17:12:41 +0100")
Bruno Victal <mirai@makinata.eu> writes:
> Hi Michael,
Hi Bruno,
>> What is the problem with this header line? AFAIK, this header line is
>> removed when sending the message.
>
> The problem is that shows up in non-debbugs contexts which doesn't
> look right, why should starting a reply to a debbugs issue (and quitting
> without sending) start influencing message-mode everywhere, even going as
> far as influencing `M-x report-emacs-bug'?
> So far the only way I found to reset this is by restarting emacs.
It doesn't hurt. This header is an internal one for Gnus (I believe), in
order to mark an article as answered. You see a similar behavior with
the following scenario:
- Start Emacs
- M-x gnus
- Enter group nntp+news.gmane.io:gmane.emacs.bugs
- Reply to a message. The reply contains
X-Draft-From: ("nntp+news.gmane.io:gmane.emacs.bugs" 273449)
- Save the draft, close Gnus, close Emacs.
- Start Emacs
- M-x gnus
- Enter the nndraft:drafts group, edit the message.
- It still contains
X-Draft-From: ("nntp+news.gmane.io:gmane.emacs.bugs" 273449)
But I haven't touched the nntp+news.gmane.io:gmane.emacs.bugs group this
time. Honestly, there isn't a bug.
Best regards, Michael.
next prev parent reply other threads:[~2023-10-28 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 14:58 bug#66798: 29.1; Debbugs leftover headers in message-mode Bruno Victal
2023-10-28 16:06 ` Michael Albinus
2023-10-28 16:12 ` Bruno Victal
2023-10-28 17:34 ` Michael Albinus [this message]
2024-01-10 10:10 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8aqmz0v.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=66798@debbugs.gnu.org \
--cc=mirai@makinata.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).