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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Yuri D'Elia <wavexx <at> thregr.org>
Cc: 25645 <at> debbugs.gnu.org, larsi <at> gnus.org
Subject: Re: bug#25645: 26.0.50;
 message.el: Fcc+handler results in write coding issues in emacs 26
Date: Sat, 02 Sep 2017 16:40:26 +0300

> From: Yuri D'Elia <wavexx <at> thregr.org>
> Date: Tue, 07 Feb 2017 18:31:15 +0100
> Cc: 25645 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>
> 
> 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).

Lars, any news on this issue?

Thanks.

Previous Next

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