[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changes to message-mode and encoding in Emacs26
From: |
Eli Zaretskii |
Subject: |
Re: Changes to message-mode and encoding in Emacs26 |
Date: |
Mon, 02 Oct 2017 20:25:11 +0300 |
> From: Alex Bennée <alex.bennee@linaro.org>
> Cc: help-gnu-emacs@gnu.org
> Date: Mon, 02 Oct 2017 18:12:29 +0100
>
> >> (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.
If the text in 'buf' is already encoded, why does the code call
message-encode-message-body -- that would encode an already encoded
message, and could be the root cause of the problem.
> >> 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)
What list is that?
A temporary buffer's name begins with a space, so you need to specify
its name explicitly when "C-x b" prompts for it, instead of relying on
completion.