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).