From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: David Edmondson <dme@dme.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 3/3] notmuch: Add support for listing the parent message
Date: Thu, 04 Nov 2010 16:06:39 +0530 [thread overview]
Message-ID: <m3zktpbcjs.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87hbfx4euv.fsf@ut.hh.sledj.net>
On Thu, 04 Nov 2010 09:28:40 +0000, David Edmondson <dme@dme.org> wrote:
> On Wed, 27 Oct 2010 22:56:57 +0530, "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> > From: Aneesh Kumar K.V <aneesh.kumar@gmail.com>
> >
> > When you have long thread, it would be nice to be able to
> > show the message to which the current message is a reply
>
> The patch fires up a new search, destroying my context. Shouldn't the
> parent message be visible in the current thread and, if so, perhaps just
> searching in the current buffer for it (and jumping back there) be
> possible? (Maybe even with a key to pop back to the child easily.)
>
It should actually stack up. That is, it fires up a new search but then a
'q' should bring back the old context. One of the thing i really
wanted to keep was the ability to go back to the old context with a key
binding which in this case is achieved by 'q'
-aneesh
next prev parent reply other threads:[~2010-11-04 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 17:26 [PATCH 1/3] emacs: Don't overload same-window-regexps Aneesh Kumar K.V
2010-10-27 17:26 ` [PATCH 2/3] notmuch: Add support for In-Reply-To in header Aneesh Kumar K.V
2010-10-27 17:26 ` [PATCH 3/3] notmuch: Add support for listing the parent message Aneesh Kumar K.V
2010-11-04 9:28 ` David Edmondson
2010-11-04 10:36 ` Aneesh Kumar K. V [this message]
2010-11-04 13:24 ` David Edmondson
2010-11-16 17:51 ` [PATCH] emacs: Accommodate message-mode updates David Edmondson
2010-11-19 16:01 ` Aneesh Kumar K. V
2010-11-19 16:06 ` David Edmondson
2010-11-19 16:35 ` Aneesh Kumar K. V
2010-11-19 17:12 ` 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=m3zktpbcjs.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).