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: Tue, 07 Feb 2017 18:31:15 +0100 Message-ID: <87y3xhx5zw.fsf@wavexx.thregr.org> References: <871svax7fy.fsf@wavexx.thregr.org> <83lgth6hqc.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1486488743 4473 195.159.176.226 (7 Feb 2017 17:32:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 7 Feb 2017 17:32:23 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 26.0.50.4 Cc: 25645@debbugs.gnu.org, Lars Ingebrigtsen To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Feb 07 18:32:15 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 1cb9cl-0000lz-1n for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Feb 2017 18:32:15 +0100 Original-Received: from localhost ([::1]:55626 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cb9cq-0005iS-Lj for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Feb 2017 12:32:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cb9cb-0005f2-DV for bug-gnu-emacs@gnu.org; Tue, 07 Feb 2017 12:32:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cb9cY-0005TT-Rp for bug-gnu-emacs@gnu.org; Tue, 07 Feb 2017 12:32:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:32794) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cb9cY-0005TN-P8 for bug-gnu-emacs@gnu.org; Tue, 07 Feb 2017 12:32:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cb9cY-0004vS-HG for bug-gnu-emacs@gnu.org; Tue, 07 Feb 2017 12:32:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Yuri D'Elia Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Feb 2017 17:32: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: Original-Received: via spool by 25645-submit@debbugs.gnu.org id=B25645.148648868218881 (code B ref 25645); Tue, 07 Feb 2017 17:32:02 +0000 Original-Received: (at 25645) by debbugs.gnu.org; 7 Feb 2017 17:31:22 +0000 Original-Received: from localhost ([127.0.0.1]:59225 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cb9bu-0004uT-HZ for submit@debbugs.gnu.org; Tue, 07 Feb 2017 12:31:22 -0500 Original-Received: from e.thregr.org ([80.68.88.20]:33672) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cb9bt-0004uK-28 for 25645@debbugs.gnu.org; Tue, 07 Feb 2017 12:31:21 -0500 Original-Received: from [2a02:27e8:20:9049:56ee:75ff:fe83:444c] (helo=localhost) by e.thregr.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1cb9bn-0008AZ-5e; Tue, 07 Feb 2017 18:31:15 +0100 In-reply-to: <83lgth6hqc.fsf@gnu.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:129088 Archived-At: 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.