From: Yuri D'Elia <wavexx@thregr.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25645@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
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 [thread overview]
Message-ID: <87y3xhx5zw.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <83lgth6hqc.fsf@gnu.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).
> 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.
next prev parent reply other threads:[~2017-02-07 17:31 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 [this message]
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
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=87y3xhx5zw.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=25645@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.