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 12:21:25 +1000 [thread overview]
Message-ID: <87ing16i56.fsf@gmail.com> (raw)
In-Reply-To: <838tgx75yh.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I'm confused: are you using mu4e or are you using Rmail? These
> are
> two different packages, and AFAIK they don't share any code.
>
> Also, bug#28266 explicitly says that the issue happens when
> sendmail.el is used as the MUA, which means it's not about
> message.el,
> a completely different MUA.
>
> So I think these are probably two different issues, although the
> result is similar. There are many ways to get raw bytes in
> Emacs when
> you want non-ASCII characters, and not all of them are due to
> the same
> bug...
i use mu4e, not Rmail; i was addressing your earlier remark:
> we have no similar issues reported by people who use the bundled
> MUA
> packages
i thought that the fact that both an mu4e user (me) and an Rmail
user
(Charles) are experiencing the same issue ("The encoding issue I
mentioned seems to only apply to the saving of the mail buffer
into the
file specified in the FCC header") /even though/ mu4e uses
message.el
and Rmail doesn't, might indicate a common cause lying deeper in
Emacs'
internals.
But if you think that this is just a coincidence of results, and
that
there are actually two different issues in play, i'll certainly
defer to
your knowledge and experience. Hopefully next time the issue
appears for
me, i'll be able to narrow it down to a minimal working example.
Alexis.
next prev parent reply other threads:[~2017-09-30 2:21 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 [this message]
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=87ing16i56.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).