GNU bug report logs - #28671
25.2; double transfer-encoding in rmailedit for complex mime messages

Previous Next

Full log

Message #11 received at 28671 <at> debbugs.gnu.org (full text, mbox):

From: Ken Olum <kdo <at> cosmos.phy.tufts.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: kdo <at> cosmos.phy.tufts.edu, 28671 <at> debbugs.gnu.org
Subject: Re: bug#28671: 25.2;
 double transfer-encoding in rmailedit for complex mime messages
Date: Mon, 02 Oct 2017 13:47:20 -0400

[Message part 1 (text/plain, inline)]

Here is a test file.  Edit the first message and make some change (e.g.,
to the subject header).  Then the body will end up base64 encoded
twice.  If you then go to the next message, the headers will have extra
lines at the top due to marker problems.  The patch should fix these
problems.

Here's a new patch with the simplified code as you suggested, and
here's a change log entry:

----------------------------------------------------------------------
2017-10-02  Ken Olum  <kdo <at> cosmos.phy.tufts.edu>

	Fix problems when editing raw message (Bug#28671)

	* lisp/mail/rmailedit.el (rmail-cease-edit): if rmail-old-mime-state
	is set, meaning that we are editing the raw message, do not
	encode it again.  Delete old body after, not before, inserting
	new, to avoid moving marker at beginning of next message.
----------------------------------------------------------------------

                                        Ken

[rmail-test (application/octet-stream, attachment)]

[rmailedit.patch (text/x-diff, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.