From: Alexis <flexibeast@fastmail.fm>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Yuri D'Elia <wavexx@thregr.org>, 25645@debbugs.gnu.org
Subject: bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26
Date: Fri, 22 Sep 2017 17:26:20 +1000 [thread overview]
Message-ID: <87lgl7tcrn.fsf@gmail.com> (raw)
In-Reply-To: <87a81yea51.fsf@mouse.gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Lars, any news on this issue?
>
> I'm unable to reproduce the error, and I don't think it should
> block
> the release, since it doesn't seem to affect many people.
In addition to myself, at least several other mu4e users seem to
have
been affected by this:
https://groups.google.com/forum/#!topic/mu-discuss/dIj3W_R-M4A
https://groups.google.com/forum/#!topic/mu-discuss/NJgRONE7Xuk
https://groups.google.com/forum/#!topic/mu-discuss/MaYcS5uRcsM
https://groups.google.com/forum/#!topic/mu-discuss/RC1Scq2wCe4
and maybe:
https://groups.google.com/forum/#!topic/mu-discuss/dxfpdcidtoc
i've not yet been able to consistently reproduce it, so haven't
yet been
able to narrow down whether the issue is with mu4e or with
Emacs. (Maybe
something has changed in Emacs that mu4e needs to become aware
of). i'll
try to work on this as soon as i can, unless Yuri is able to
produce an
MRE first. :-)
Alexis.
next prev parent reply other threads:[~2017-09-22 7:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 17:00 bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26 Yuri D'Elia
2017-02-07 17:19 ` Eli Zaretskii
2017-02-07 17:31 ` Yuri D'Elia
2017-09-02 13:40 ` Eli Zaretskii
2017-09-13 18:17 ` Lars Ingebrigtsen
2017-09-22 7:26 ` Alexis [this message]
2017-09-22 10:49 ` Yuri D'Elia
2017-09-13 18:16 ` Lars Ingebrigtsen
2017-09-13 20:18 ` Yuri D'Elia
2017-09-13 20:35 ` Lars Ingebrigtsen
2017-09-13 20:43 ` Yuri D'Elia
2017-10-03 14:27 ` bug#25645: reproducer? Alex Bennée
2017-10-03 15:36 ` Eli Zaretskii
2017-10-04 0:31 ` Alex Bennée
2017-10-04 5:51 ` Eli Zaretskii
2017-10-04 8:46 ` Alex Bennée
2017-10-04 9:27 ` Eli Zaretskii
2017-10-09 13:47 ` Eli Zaretskii
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=87lgl7tcrn.fsf@gmail.com \
--to=flexibeast@fastmail.fm \
--cc=25645@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=wavexx@thregr.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.