From: Tomi Ollila <tomi.ollila@iki.fi>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: emacs complains about encoding?
Date: Wed, 16 May 2012 12:24:37 +0300 [thread overview]
Message-ID: <m23970bhre.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <878vgsbprq.fsf@nikula.org>
On Wed, May 16 2012, Jani Nikula wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>> IT h\344ppens.
>>
>> Attempting to reply to this email should expose the problem.
>>
>> \304\344li\366 \344l\344 ly\366, \366\366li\344 l\344ikkyy.
(\nnn text above hand-(query)-replaced)
>
> The problem bisected to f6c170fabca8f39e74705e3813504137811bf162
> ("emacs: Correctly quote non-text/plain parts in reply"). The commit
> reverts cleanly, replying without it now.
>
> Tomi, it would be great if you could post your message as a patch to the
> test suite.
Haa, It doesn't matter which is the original encoding of the message;
notmuch reply id:20120515194455.B7AD5100646@guru.guru-group.fi
where notmuch show --format=raw ^^^ outputs (among other lines):
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
and
notmuch reply id:"878vgsbprq.fsf@nikula.org"
where notmuch show --format=raw ^^^ outputs (among other lines):
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
produce correct reply content, both in utf-8.
So it is the emacs side which breaks replies.
I'll see what kind of test cases I can create...
>
> BR,
> Jani.
Tomi
next prev parent reply other threads:[~2012-05-16 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:"878vgzrvik.fsf@beesknees.cern.ch">
2012-05-15 19:44 ` emacs complains about encoding? Tomi Ollila
2012-05-15 20:04 ` Tomi Ollila
2012-05-16 6:31 ` Jani Nikula
2012-05-16 9:24 ` Tomi Ollila [this message]
2012-05-20 15:34 ` Adam Wolfe Gordon
2012-05-22 12:53 ` Michal Sojka
2012-05-22 13:21 ` Tomi Ollila
2012-05-23 10:15 ` Michal Sojka
2012-06-03 5:40 ` Adam Wolfe Gordon
2012-05-11 8:07 David Belohrad
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=m23970bhre.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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 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).