unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: JSON based emacs UI
Date: Thu, 25 Mar 2010 10:11:38 +0530	[thread overview]
Message-ID: <87tys557y5.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87d3yudvja.fsf@uf.hh.sledj.net>

On Wed, 24 Mar 2010 07:32:41 +0000, David Edmondson <dme@dme.org> wrote:
> 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).
> 

Is there a way to get the inline patches shown similar to
diff-mode not just the attached patches ?

-aneesh

  parent reply	other threads:[~2010-03-25  4:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 14:47 JSON based emacs UI David Edmondson
2010-03-22 15:52 ` David Edmondson
2010-03-24  7:32 ` David Edmondson
2010-03-24 15:41   ` David Edmondson
2010-03-25  4:41   ` Aneesh Kumar K. V [this message]
2010-03-25  9:14     ` David Edmondson
2010-03-26  4:46       ` Aneesh Kumar K. V
2010-03-26  8:26         ` David Edmondson
2010-03-26  9:07   ` Jesse Rosenthal
2010-03-26 12:28     ` David Edmondson
2010-03-26 14:51 ` Aneesh Kumar K. V
2010-03-26 19:38   ` David Edmondson
2010-03-28 17:03     ` Fernando Carrijo
2010-03-28 17:07       ` Fernando Carrijo
2010-03-29  9:17       ` David Edmondson
2010-03-29  9:27         ` Aneesh Kumar K. V
2010-03-29 14:17         ` Sebastian Spaeth
2010-03-29 14:59         ` Fernando Carrijo
2010-03-28  1:41 ` Sebastian Spaeth
2010-03-28  5:46   ` Michal Sojka
2010-03-29  7:49     ` Sebastian Spaeth
2010-03-29  9:03       ` Michal Sojka
2010-03-29  9:19   ` David Edmondson

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=87tys557y5.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=dme@dme.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).