all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Changes to message-mode and encoding in Emacs26
Date: Fri, 29 Sep 2017 20:47:02 +0300	[thread overview]
Message-ID: <838tgx75yh.fsf@gnu.org> (raw)
In-Reply-To: <87k20h7fw9.fsf@gmail.com> (message from Alexis on Sat, 30 Sep 2017 00:12:22 +1000)

> From: Alexis <flexibeast@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Sat, 30 Sep 2017 00:12:22 +1000
> 
> 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."

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...



  parent reply	other threads:[~2017-09-29 17:47 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838tgx75yh.fsf@gnu.org \
    --to=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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.