GNU bug report logs - #25645
26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26

Previous Next

Package: emacs;

Reported by: Yuri D'Elia <wavexx <at> thregr.org>

Date: Tue, 7 Feb 2017 17:01:01 UTC

Severity: normal

Tags: unreproducible

Found in version 26.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Yuri D'Elia <wavexx <at> thregr.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25645 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26
Date: Tue, 07 Feb 2017 18:31:15 +0100
On Tue, Feb 07 2017, Eli Zaretskii wrote:
> If you get raw bytes in the buffer, the culprit is in the code which
> inserted those bytes, or read them from some file.

Yes, the content of the buffer is generated by
message-encode-message-body in message.el itself.

You only need to insert an unicode letter in the message's buffer to
trigger the issue when recoding to qp-utf8.

I wrote to Lars prior to filing this report (cc-ed).

> This is expected when there are raw bytes in the buffer.  The problem
> is elsewhere.

Since the fcc-handler is expected to do something with the buffer (write
it out), I expect message.el to preset the buffer coding system if the
buffer becomes unibyte in nature.




This bug report was last modified 7 years and 286 days ago.

Previous Next


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