From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Yuri D'Elia Newsgroups: gmane.emacs.bugs Subject: bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26 Date: Wed, 13 Sep 2017 22:18:06 +0200 Message-ID: <87tw06s681.fsf@wavexx.thregr.org> References: <871svax7fy.fsf@wavexx.thregr.org> <87fubqea6n.fsf@mouse.gnus.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1505333954 27438 195.159.176.226 (13 Sep 2017 20:19:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Sep 2017 20:19:14 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 26.0.50 Cc: 25645@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Sep 13 22:19:10 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dsE7p-00071F-NH for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Sep 2017 22:19:09 +0200 Original-Received: from localhost ([::1]:44425 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dsE7w-0004Oc-Q7 for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Sep 2017 16:19:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dsE7n-0004Hd-Pa for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2017 16:19:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dsE7i-0004gs-S0 for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2017 16:19:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58442) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dsE7i-0004gV-O3 for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2017 16:19:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dsE7i-0003yB-IZ for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2017 16:19:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Yuri D'Elia Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Sep 2017 20:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25645 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: unreproducible Original-Received: via spool by 25645-submit@debbugs.gnu.org id=B25645.150533389915205 (code B ref 25645); Wed, 13 Sep 2017 20:19:02 +0000 Original-Received: (at 25645) by debbugs.gnu.org; 13 Sep 2017 20:18:19 +0000 Original-Received: from localhost ([127.0.0.1]:38889 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dsE71-0003xB-9u for submit@debbugs.gnu.org; Wed, 13 Sep 2017 16:18:19 -0400 Original-Received: from erc.thregr.org ([46.43.2.63]:60642) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dsE6y-0003x1-QG for 25645@debbugs.gnu.org; Wed, 13 Sep 2017 16:18:17 -0400 Original-Received: from [151.38.80.34] (helo=localhost) by erc.thregr.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1dsE6s-0007Gl-Qc (envelope-from ); Wed, 13 Sep 2017 22:18:11 +0200 In-reply-to: <87fubqea6n.fsf@mouse.gnus.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:136935 Archived-At: On Wed, Sep 13 2017, Lars Ingebrigtsen wrote: >> It works as expected with emacs 25.2, but fails on 26 when the body >> contains unicode characters. Somehow when the mail is encoded in quoted >> printable with an utf-8 charset, the buffer seem to contain raw bytes as >> if the buffer has an incorrect buffer-file-coding-system. > > I'm unable to reproduce this bug. If I put > > Fcc: /tmp/fcc > > in my headers and enter text like "föo" in the body, the file is saved > as it should be. Adding an Fcc is not enough, if you read the initial report, the issue is triggered by attempting to call write-file within a message-fcc-handler-function.