From: Austin Clements <amdragon@MIT.EDU>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v2] emacs: Add support for saved search accelerators
Date: Sun, 13 Jul 2014 10:32:35 -0400 [thread overview]
Message-ID: <20140713143235.GA4660@mit.edu> (raw)
In-Reply-To: <87bnstfiha.fsf@maritornes.cs.unb.ca>
Quoth David Bremner on Jul 13 at 11:20 am:
> Austin Clements <amdragon@MIT.EDU> writes:
>
> > The right answer might be something between notmuch-go and dme's
> > patch. Currently notmuch-go uses a hard-coded set of searches, while
> > dme's patch derives them from the saved searches.
>
> I'm not really looking for a solution for my own use, just wearing my
> integration manager hat. In that context, a second set of hard coded
> saved searches would be a blocker.
Sorry, it seems my email wasn't clear. Does notmuch-go address your
user unfriendliness concerns with dme's patch?
If so, we should combine notmuch-go's UI with dme's customizable key
bindings and think about pushing that (clearly we wouldn't push
notmuch-go as it is).
next prev parent reply other threads:[~2014-07-13 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:16 [RFC] [PATCH] emacs: Add support for saved search accelerators David Edmondson
2014-05-06 16:41 ` Mark Walters
2014-05-07 11:21 ` [PATCH v2] emacs: Add support for saved search accelerator keys David Edmondson
2014-05-07 11:21 ` [PATCH v2] emacs: Add support for saved search accelerators David Edmondson
2014-05-08 9:14 ` Mark Walters
2014-05-10 21:04 ` Aaron Ecay
2014-05-12 6:07 ` David Edmondson
2014-06-06 13:12 ` Mark Walters
2014-07-12 19:31 ` David Bremner
2014-07-13 3:50 ` Austin Clements
2014-07-13 14:20 ` David Bremner
2014-07-13 14:32 ` Austin Clements [this message]
2014-07-13 15:06 ` Mark Walters
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=20140713143235.GA4660@mit.edu \
--to=amdragon@mit.edu \
--cc=david@tethera.net \
--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).