unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: Chris Siebenmann <cks.emacsbugs-01@cs.toronto.edu>,
	Eli Zaretskii <eliz@gnu.org>,
	67360@debbugs.gnu.org
Subject: bug#67360: 29.1; MH-E forwarded email has a mangled default Subject header
Date: Sat, 30 Dec 2023 14:05:29 -0800	[thread overview]
Message-ID: <1842253.1703973929@olgas.newt.com> (raw)
In-Reply-To: <117576.1701056977@alto>

Thanks, Mike! My forwcomps only injects one header field so I never saw
this before. Uncommenting the Subject field made it possible to
reproduce this issue.

Yes, I agree that the code clearly wants to replace the Subject field,
not append to it, and this patch works for me as well. Please feel free
to commit the patch and resolve the issue. Thanks again!

Mike Kupfer <kupfer@rawbw.com> wrote:

> Eli Zaretskii wrote:
> 
> > > From: Chris Siebenmann <cks.emacsbugs-01@cs.toronto.edu>
> > > Date: Tue, 21 Nov 2023 19:49:24 -0500
> > > 
> > > If you attempt to forward an email message in MH-E with mh-forward
> > > (bound to eg 'f'), then the resulting Subject: of the draft message will
> > > be manged and come out as, for example:
> > > 
> > > 	Subject: test forwarding subject (fwd) Chris Siebenmann: test forwarding subject
> [...]
> > > I suspect that the intention is to replace any existing Subject:, or
> > > perhaps mh-forward assumes that the draft won't have one. Unfortunately
> > > for mh-forward, mh-insert-fields is specifically documented to *append*
> > > to the existing header field value, if there is one, not overwrite it,
> > > so the resulting Subject: of the draft is as we see here: the original
> > > subject created by 'forw', and then an appended Subject from mh-forward.
> > > This result is not terribly useful.
> 
> Indeed.
> 
> Yeah, mh-insert-fields seems like the wrong choice for Subject.  It's
> more suited for headers like To or Cc, when you might want to add to the
> existing list of recipients.  Replacing mh-insert-fields with
> mh-modify-header-field works for me.
> 
> diff --git a/lisp/mh-e/mh-comp.el b/lisp/mh-e/mh-comp.el
> index 92d31bf1826..0d1dcdf626a 100644
> --- a/lisp/mh-e/mh-comp.el
> +++ b/lisp/mh-e/mh-comp.el
> @@ -574,7 +574,7 @@ mh-forward
>          (setq orig-subject (mh-get-header-field "Subject:")))
>        (let ((forw-subject
>               (mh-forwarded-letter-subject orig-from orig-subject)))
> -        (mh-insert-fields "Subject:" forw-subject)
> +        (mh-modify-header-field "Subject" forw-subject t)
>          (goto-char (point-min))
>          ;; Set the local value of mh-mail-header-separator according to what is
>          ;; present in the buffer...
> 
> > > Reproduction in emacs -Q provided you have NMH and MH-E set up:
> > > * enter MH-E with 'M-x mh-rmail'
> > > * arrange to have some message in your inbox that you can forward, for
> > >   example by 'F r' to see all of your inbox.
> 
> Hide your personal forwcomps if you have one.
> 
> > > * display your test message to forward, eg cursor to it and hit Return
> > > * start to forward with 'f' or 'M-x mh-forward'.
> 
> mike
> 

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/, GnuPG ID:610BD9AD





  reply	other threads:[~2023-12-30 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  0:49 bug#67360: 29.1; MH-E forwarded email has a mangled default Subject header Chris Siebenmann
2023-11-22 14:42 ` Eli Zaretskii
2023-11-27  3:49   ` Mike Kupfer
2023-12-30 22:05     ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-31 16:44       ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 19:17         ` Eli Zaretskii
2024-01-01 18:35           ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 18:33 ` Bill Wohler 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=1842253.1703973929@olgas.newt.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=67360@debbugs.gnu.org \
    --cc=cks.emacsbugs-01@cs.toronto.edu \
    --cc=eliz@gnu.org \
    --cc=kupfer@rawbw.com \
    --cc=wohler@newt.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 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).