all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 25645@debbugs.gnu.org
Subject: bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26
Date: Wed, 13 Sep 2017 20:16:16 +0200	[thread overview]
Message-ID: <87fubqea6n.fsf@mouse.gnus.org> (raw)
In-Reply-To: <871svax7fy.fsf@wavexx.thregr.org> (Yuri D'Elia's message of "Tue, 07 Feb 2017 18:00:01 +0100")

Yuri D'Elia <wavexx@thregr.org> writes:

> 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.

Could the problem be in your handler?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2017-09-13 18:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 17:00 bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26 Yuri D'Elia
2017-02-07 17:19 ` Eli Zaretskii
2017-02-07 17:31   ` Yuri D'Elia
2017-09-02 13:40     ` Eli Zaretskii
2017-09-13 18:17       ` Lars Ingebrigtsen
2017-09-22  7:26         ` Alexis
2017-09-22 10:49           ` Yuri D'Elia
2017-09-13 18:16 ` Lars Ingebrigtsen [this message]
2017-09-13 20:18   ` Yuri D'Elia
2017-09-13 20:35     ` Lars Ingebrigtsen
2017-09-13 20:43       ` Yuri D'Elia
2017-10-03 14:27 ` bug#25645: reproducer? Alex Bennée
2017-10-03 15:36   ` Eli Zaretskii
2017-10-04  0:31     ` Alex Bennée
2017-10-04  5:51       ` Eli Zaretskii
2017-10-04  8:46         ` Alex Bennée
2017-10-04  9:27           ` Eli Zaretskii
2017-10-09 13:47           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fubqea6n.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=25645@debbugs.gnu.org \
    --cc=wavexx@thregr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.