From: Alexis <flexibeast@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Changes to message-mode and encoding in Emacs26
Date: Sat, 30 Sep 2017 00:12:22 +1000 [thread overview]
Message-ID: <87k20h7fw9.fsf@gmail.com> (raw)
In-Reply-To: <8360c18wz3.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex Bennée <alex.bennee@linaro.org>
>> Date: Tue, 26 Sep 2017 16:41:03 +0100
>>
>> If I force raw-text it seems to look fine. Any idea what's
>> going on?
>>
>> There is a bug raised with mu4e (the mail client using
>> message-mode):
>>
>> https://github.com/djcb/mu/issues/1081
>
> First, this kind of problems should be reported to the Emacs bug
> tracker, not here.
>
> And second, since this involves mu4e, any of its discussions
> should
> IMO include the mu4e developers, because we have no similar
> issues
> reported by people who use the bundled MUA packages (nor MH-E,
> AFAIK).
> So it sounds like mu4e is at least somehow involved in this.
i can't speak for other mu4e users, but the coding issue i've been
intermittently experiencing as a mu4e user is exactly as described
in
this bug report regarding RMAIL:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28266#17
More specifically, it's this:
"The encoding issue I mentioned seems to only apply to the
saving
of the mail buffer into the file specified in the FCC
header."
Alexis.
next prev parent reply other threads:[~2017-09-29 14: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 [this message]
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
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=87k20h7fw9.fsf@gmail.com \
--to=flexibeast@gmail.com \
--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).