On Fri, 26 Feb 2010 11:55:19 -0800, Carl Worth wrote:
> On Fri, 26 Feb 2010 07:53:29 -0500, James Vasile
> wrote:
> > Maybe this retry loop should be put in notmuch itself?
>
> Perhaps it should. I've even imagined something that would queue a
> request into a daemon if the database isn't
On Fri, 26 Feb 2010 07:53:29 -0500, James Vasile
wrote:
> Maybe this retry loop should be put in notmuch itself?
Perhaps it should. I've even imagined something that would queue a
request into a daemon if the database isn't currently available.
But of course there are issues about whether the
It occurs to me that having generic ability to tell notmuch to retry
until the DB isn't locked might useful. So I put the functionality in a
script that can sit between notmuch and various clients. It will
simplify my emacs setup, and improve it since emacs's handling of
asynchronous processes
It occurs to me that having generic ability to tell notmuch to retry
until the DB isn't locked might useful. So I put the functionality in a
script that can sit between notmuch and various clients. It will
simplify my emacs setup, and improve it since emacs's handling of
asynchronous processes
On Fri, 26 Feb 2010 07:53:29 -0500, James Vasile ja...@hackervisions.org
wrote:
Maybe this retry loop should be put in notmuch itself?
Perhaps it should. I've even imagined something that would queue a
request into a daemon if the database isn't currently available.
But of course there are
