From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Changes to message-mode and encoding in Emacs26
Date: Mon, 02 Oct 2017 18:12:29 +0100 [thread overview]
Message-ID: <87tvzhzd6q.fsf@linaro.org> (raw)
In-Reply-To: <83d16535by.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex Bennée <alex.bennee@linaro.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
>> Date: Mon, 02 Oct 2017 09:36:07 +0100
>>
>> I haven't narrowed it down yet but is certainly during message-do-fcc.
>> It's hard to tell because the work takes place in a temporary buffer but
>> I'm currently looking at the code that does:
>>
>> (when file
>> (with-temp-buffer
>> (insert-buffer-substring buf)
>> (message-clone-locals buf)
>> (message-encode-message-body)
>>
>> And wondering how that might of changed.
>
> Is 'buf' a unibyte buffer or a multibyte buffer?
buf is the source buffer and yes it will be a multibyte buffer by virtue
of utf-8 encoding and special characters.
>
>> Any idea how to examine the current with-temp-buffer while stepping
>> through in edebug?
>
> You can "C-x b" when Emacs is stopped in Edebug.
The with-temp-buffer doesn't show up on the list until later (where it
is a duplicate created for the purpose of saving the email)
>
> (Why are we still discussing this issue on this list?)
I was responding to Alexis but I can create a new emacs-devel message if
you want or just post directly to the bugs. I feel we are getting close.
--
Alex Bennée
next prev parent reply other threads:[~2017-10-02 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 15:41 Changes to message-mode and encoding in Emacs26 Alex Bennée
2017-09-29 13:18 ` Eli Zaretskii
2017-09-29 14:12 ` Alexis
2017-09-29 14:42 ` Alex Bennée
2017-09-29 17:47 ` Eli Zaretskii
2017-09-30 2:21 ` Alexis
2017-10-02 8:36 ` Alex Bennée
2017-10-02 16:03 ` Eli Zaretskii
2017-10-02 17:12 ` Alex Bennée [this message]
2017-10-02 17:25 ` Eli Zaretskii
2017-10-03 14:07 ` Alex Bennée
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=87tvzhzd6q.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).