From: Richard M Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, 2017@emacsbugs.donarmstrong.com
Subject: bug#2017: 23.0.60; C-c in Rmail re-encodes quoted-printable parts
Date: Sun, 25 Jan 2009 13:14:38 -0500 [thread overview]
Message-ID: <E1LR9VG-0008Tm-Vi@fencepost.gnu.org> (raw)
In-Reply-To: <uk58kuda5.fsf@gnu.org> (message from Eli Zaretskii on Sat, 24 Jan 2009 13:57:54 +0200)
There are 2 bugs here: (1) Rmail should not re-encode the text in any
way, and (2) it should never touch the headers.
The code in rmail-cease-edit is meant to re-encode the entire message
in cases where rmail-show-message decoded the entire message. It should
not operate in the case you described.
(setq character-coding (mail-fetch-field "content-transfer-encoding")
is supposed to get the encoding specified by the message header for
the entire message, and it ought not notice anything specified
in/for individual mime parts.
When this fails for you, what value does character-coding get? If it
is non-nil, can you step thru mail-fetch-field and see how that
happened?
Is it that the header specifies this field
and the message also has mime parts?
If so, rmail-cease-edit needs to operate only on the "body"
and not on any mime parts.
In addition, rmail-cease-edit ought to check for editing done in
message headers, and install the edited headers into the message.
Ideally it should make a list of the headers initially shown
so that it can tell if the user deleted any headers and delete those
from the message.
next prev parent reply other threads:[~2009-01-25 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u7i42tgk4.fsf@gnu.org>
2009-01-24 11:57 ` bug#2017: 23.0.60; C-c in Rmail re-encodes quoted-printable parts Eli Zaretskii
2009-01-25 18:14 ` Richard M Stallman [this message]
2009-02-07 15:35 ` bug#2017: marked as done (23.0.60; C-c in Rmail re-encodes quoted-printable parts) Emacs bug Tracking System
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=E1LR9VG-0008Tm-Vi@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=2017@emacsbugs.donarmstrong.com \
--cc=eliz@gnu.org \
/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.