From: Alexander Botero-Lowry <alex.boterolowry@gmail.com>
To: Carl Worth <cworth@cworth.org>, Alex Ghitza <aghitza@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: viewing text/html (inline or otherwise)
Date: Tue, 09 Feb 2010 16:43:20 -0800 [thread overview]
Message-ID: <861vgtvs2f.fsf@fortitudo.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87iqa6lz1b.fsf@yoom.home.cworth.org>
On Tue, 09 Feb 2010 16:22:56 -0800, Carl Worth <cworth@cworth.org> wrote:
> On Tue, 09 Feb 2010 21:28:25 +1100, Alex Ghitza <aghitza@gmail.com> wrote:
> > Ideally, I'd like to be able to see what's hidden behind the
> > "Non-text part: text/html", and if it could happen inline that would be
> > great. I would also entertain the idea of opening an external browser
> > window, if that's the way this has to go.
>
> We actually had some support for inline viewing of HTML message parts
> for a while. I reverted the code only because it was slowing down
> rendering of non-HTML messages. And I did that with the expectation that
> the code would appear again shortly with the obvious optimization to not
> do any extra work for non-HTML messages.
EBUSY...
I'll get around to it, I continue to run ancient notmuch with my patch
still in place though because I find it basically unuseable without it,
so I hope to get some free time to pull the change back up and add the
optimization (which is to check the type of the mime part before trying
to do an mm-display-parts on it, so that you save the time of the
dissection if it's not needed).
alex
next prev parent reply other threads:[~2010-02-10 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 10:28 viewing text/html (inline or otherwise) Alex Ghitza
2010-02-10 0:22 ` Carl Worth
2010-02-10 0:43 ` Alexander Botero-Lowry [this message]
2010-02-10 6:40 ` Alex Ghitza
2010-02-10 8:14 ` Sebastian Spaeth
2010-02-10 6:10 ` Keith Packard
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=861vgtvs2f.fsf@fortitudo.i-did-not-set--mail-host-address--so-tickle-me \
--to=alex.boterolowry@gmail.com \
--cc=aghitza@gmail.com \
--cc=cworth@cworth.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).