From: Andreas Schwab <schwab@linux-m68k.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: master d1c9310: DOn't use string-as-unibyte in Gnus
Date: Wed, 01 Feb 2017 11:24:43 +0100 [thread overview]
Message-ID: <87a8a6w6ms.fsf@linux-m68k.org> (raw)
In-Reply-To: <b4m4m0ecjsc.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 01 Feb 2017 19:00:51 +0900")
On Feb 01 2017, Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> Hi Lars,
>
> On Tue, 31 Jan 2017 16:58:08 +0000, Lars Ingebrigtsen wrote:
>> branch: master
>> commit d1c931009004aef847105b7bac6b6ffafd985b82
>> Author: Lars Ingebrigtsen <larsi@gnus.org>
>> Commit: Lars Ingebrigtsen <larsi@gnus.org>
>
>> DOn't use string-as-unibyte in Gnus
> [...]
>> * lisp/gnus/mml.el (mml-generate-mime-1): Ditto.
> [...]
>> --- a/lisp/gnus/mml.el
>> +++ b/lisp/gnus/mml.el
>> @@ -696,9 +696,10 @@ be \"related\" or \"alternate\"."
>> (set-buffer-multibyte nil)
>> (cond
>> ((cdr (assq 'buffer cont))
>> - (insert (string-as-unibyte
>> + (insert (encode-coding-string
>> (with-current-buffer (cdr (assq 'buffer cont))
>> - (buffer-string)))))
>> + (buffer-string))
>> + 'utf-8)))
Shouldn't that be raw-text?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-02-01 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170131165808.28198.10570@vcs.savannah.gnu.org>
[not found] ` <20170131165808.9F18722015F@vcs.savannah.gnu.org>
2017-02-01 10:00 ` master d1c9310: DOn't use string-as-unibyte in Gnus Katsumi Yamaoka
2017-02-01 10:20 ` Katsumi Yamaoka
2017-02-01 10:24 ` Andreas Schwab [this message]
2017-02-01 12:47 ` Lars Ingebrigtsen
2017-02-01 13:12 ` Andy Moreton
2017-02-01 15:35 ` Eli Zaretskii
2017-02-01 16:07 ` Andy Moreton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8a6w6ms.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).