From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Cc: Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: [PATCH] emacs: use 'gnus-decoded in notmuch-mm-display-part-inline ()
Date: Wed, 23 May 2012 12:20:21 +0200 [thread overview]
Message-ID: <87obpfurkq.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <1337533094-5467-1-git-send-email-tomi.ollila@iki.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> When mail message is read from emacs, the message structure
> obtained may contain parts which have content included
> (`text/plain` for example) and other parts where content is not
> included (`text/html` for example).
>
> In case content is included, the string is already available in
> emacs' internal format and therefore mm-... functions should not
> attempt to do further decoding for the data in temp buffer
> provided for it.
>
> Currently when reply buffer is created,
> notmuch-mm-display-part-inline () is used to provided quoted reply
> content. This change makes the mm-... functions called by it use
> 'gnus-decoded as charset whenever the content is already available.
>
> File .../emacs-23.3/lisp/gnus/mm-uu.el mentions:
> "`gnus-decoded' is a fake charset, which means no further decoding."
> ---
>
> I propose this patch is taken into 0.13.1.
LGTM. I use it in my private branch. The bug fixed by this patch is
really annoying.
>
> Please note that I'm not entirely sure my description above
> is right. So those who knows more of these issues please check
> my "facts".
Your description matches with what I found in
id:"871umc1int.fsf@steelpick.2x.cz".
Thanks,
-Michal
next prev parent reply other threads:[~2012-05-23 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 16:58 [PATCH] emacs: use 'gnus-decoded in notmuch-mm-display-part-inline () Tomi Ollila
2012-05-23 10:20 ` Michal Sojka [this message]
2012-05-24 1:52 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obpfurkq.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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 public inbox
https://yhetil.org/notmuch.git/
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).