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: Fri, 22 Sep 2017 12:49:07 +0200 Message-ID: <87ingbt3do.fsf@wavexx.thregr.org> References: <871svax7fy.fsf@wavexx.thregr.org> <83lgth6hqc.fsf@gnu.org> <87y3xhx5zw.fsf@wavexx.thregr.org> <83a82dz0ad.fsf@gnu.org> <87a81yea51.fsf@mouse.gnus.org> <87lgl7tcrn.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1506077419 9339 195.159.176.226 (22 Sep 2017 10:50:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 22 Sep 2017 10:50:19 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 27.0.50 Cc: 25645@debbugs.gnu.org, Lars Ingebrigtsen To: Alexis Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Sep 22 12:50:13 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 1dvLXB-00025k-C9 for geb-bug-gnu-emacs@m.gmane.org; Fri, 22 Sep 2017 12:50:13 +0200 Original-Received: from localhost ([::1]:57938 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dvLXF-0002IP-Fp for geb-bug-gnu-emacs@m.gmane.org; Fri, 22 Sep 2017 06:50:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60272) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dvLX4-0002Dh-VY for bug-gnu-emacs@gnu.org; Fri, 22 Sep 2017 06:50:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dvLX0-0006vj-4U for bug-gnu-emacs@gnu.org; Fri, 22 Sep 2017 06:50:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43616) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dvLX0-0006vX-1b for bug-gnu-emacs@gnu.org; Fri, 22 Sep 2017 06:50:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dvLWz-0002f5-Nt for bug-gnu-emacs@gnu.org; Fri, 22 Sep 2017 06:50:01 -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: Fri, 22 Sep 2017 10:50:01 +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.150607735610175 (code B ref 25645); Fri, 22 Sep 2017 10:50:01 +0000 Original-Received: (at 25645) by debbugs.gnu.org; 22 Sep 2017 10:49:16 +0000 Original-Received: from localhost ([127.0.0.1]:52297 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dvLWG-0002e3-KX for submit@debbugs.gnu.org; Fri, 22 Sep 2017 06:49:16 -0400 Original-Received: from erc.thregr.org ([46.43.2.63]:54378) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dvLWE-0002du-5v for 25645@debbugs.gnu.org; Fri, 22 Sep 2017 06:49:14 -0400 Original-Received: from [2a02:27e8:20:9049:56ee:75ff:fec2:8bfb] (helo=localhost) by erc.thregr.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1dvLW7-0008Hl-UG (envelope-from ); Fri, 22 Sep 2017 12:49:08 +0200 In-reply-to: <87lgl7tcrn.fsf@gmail.com> 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:137229 Archived-At: On Fri, Sep 22 2017, Alexis wrote: > i've not yet been able to consistently reproduce it, so haven't yet been > able to narrow down whether the issue is with mu4e or with Emacs. (Maybe > something has changed in Emacs that mu4e needs to become aware of). i'll > try to work on this as soon as i can, unless Yuri is able to produce an > MRE first. :-) I didn't find the time yet. I wanted to make a minimal test case using only message-mode.