To: notmuch@notmuchmail.org
In-Reply-To: <87iq8o76r8.fsf@uf.hh.sledj.net>
References: <87iq8o76r8.fsf@uf.hh.sledj.net>
From: David Edmondson <dme@dme.org>
Date: Wed, 24 Mar 2010 07:32:41 +0000
Message-ID: <87d3yudvja.fsf@uf.hh.sledj.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] JSON based emacs UI
Precedence: list

On Mon, 22 Mar 2010 14:47:39 +0000, David Edmondson <dme@dme.org> wrote:
> I've pushed the first stage of a JSON based emacs UI to the repository
> at http://github.com/dme/notmuch (it's in the "master" branch).
> 
> This is intended to be functionally equivalent to the current UI, though
> HTML display is not present (see below).
> 
> This is lightly tested, but if anyone else wants to give it a try I
> would be interested in feedback. There were a couple of places in the
> current code where I wasn't completely sure of the intention, so I may
> have inadvertently diverged (notmuch-show-rewind is a good example).
> 
> For HTML display and other improved MIME support my intention is to
> enhance notmuch to allow single parts to be output (something like:
> "notmuch show --part=2 id:k74hf87df.fsf@fish.org") and use that from the
> UI code. No idea when I'll get to it, though.

"notmuch part --part=2 id:k74hf87df.fsf@fish.org" support is pushed now
and notmuch-show.el updated to use it.

An attempt is made to inline all parts, including guessing the type of
application/octet-stream parts using mailcap (so a file called
"foo.patch" sent as type application/octet-stream will be displayed
using diff-mode formatting).

Image inlining doesn't work, even for simple image/jpeg attachments. I'm
still puzzling over this - the output from 'notmuch part' seems fine,
but the lisp code to generate the image and insert it at the right place
is broken.

Inline images in HTML are also likely problematic - I'm not sure that I
have the framework in place for handling images specified using the cid:
prefix.

Next is to fix images and persuade notmuch to be more verbose about the
detailed MIME structure of messages.

As always, feedback (especially if something breaks) appreciated.

dme.
-- 
David Edmondson, http://dme.org