From: "John Lenz" <lenz@math.uic.edu>
To: "Tomi Ollila" <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: cli: add --include-html option to notmuch show
Date: Mon, 22 Jul 2013 11:49:18 -0500 [thread overview]
Message-ID: <notmuch-web-1374511758.1146370460@www.wuzzeb.org> (raw)
In-Reply-To: <m27ggj1x29.fsf@guru.guru-group.fi>
On Sun Jul 21 15:23 -0500 2013, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> On Tue, Jul 02 2013, John Lenz <lenz@math.uic.edu> wrote:
>
> > For my client, the largest bottleneck for displaying large threads is
> > exporting each html part individually since by default notmuch will not
> > show the json parts. For large threads there can be quite a few parts and
> > each must be exported and decoded one by one. Also, I then have to deal
> > with all the crazy charsets which I can do through a library but is a
> > pain.
>
> This looks like a useful option. I just wonder what effect does different
> charsets do to the output (is text/html content output verbatim (with just
> json/sexp escaping of '"' -characters).
>
> If you added test(s) showing what happens with different charsets
> (like one message having 3 text/html parts, one us-ascii, one iso-8859-1
> and one utf-8) that would make things clearer and (also) protect us from
> regressions.
>
Ok, I'll add some tests, but everything is converted to UTF-8 by gmime. If
you look, I didn't add any extra code actually. Instead I just changed
the if branch taken depending on the option and the content type. The existing
code already converted everything to UTF-8.
next prev parent reply other threads:[~2013-07-22 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 0:19 cli: add --include-html option to notmuch show John Lenz
2013-07-21 20:23 ` Tomi Ollila
2013-07-22 16:49 ` John Lenz [this message]
2013-07-25 2:36 ` John Lenz
2013-08-04 19:47 ` Tomi Ollila
2013-08-17 15:52 ` John Lenz
2013-08-18 11:25 ` Jani Nikula
2013-08-18 18:30 ` Tomi Ollila
2013-08-24 8:11 ` Mark Walters
2013-08-24 10:59 ` Jani Nikula
2013-08-24 15:29 ` [PATCH 1/1] test: test notmuch show --include-html option Tomi Ollila
2013-08-24 21:36 ` Mark Walters
2013-08-27 11:04 ` David Bremner
2013-08-27 11:03 ` cli: add --include-html option to notmuch show 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=notmuch-web-1374511758.1146370460@www.wuzzeb.org \
--to=lenz@math.uic.edu \
--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).