On 2017-10-26, David Edmondson wrote:
> After the changes to use `make-process', the Carbon port of emacs on
> macOS (often referred to as emacs-mac or the railwaycat port) will ask
> about killing the stderr buffer after any `notmuch-search':
>
> Debugger entered--Lisp error: (quit)
>
On 2017-02-28, David Bremner wrote:
> FWIW, these changes are pretty unrelated at an implimentation
> level. The key fetching is done from emacs, while the
> verification is done in the notmuch binary.
I presumed the verification was done in Emacs as well. But I
can see how asynchronous
Allow me add to this RFE.
On 2017-02-28, Steven Allen wrote:
> Currently, notmuch fetches keys synchronously. This can be
> *very* slow (I fetch keys over tor) and locks up emacs for the
> duration. Therefore, this fetch really should be
> asynchronous.
Even with all keys already present
On 2014-13-11, David Bremner wrote:
> notmuch-deliver has no commits for about 2.5 years.
> notmuch-insert has all the features that deliver does, and as
> far as I understand the error handling has now caught up.
Once upon a time I spoke out against the removal of
notmuch-deliver:
On 2014-13-11, David Bremner da...@tethera.net wrote:
notmuch-deliver has no commits for about 2.5 years.
notmuch-insert has all the features that deliver does, and as
far as I understand the error handling has now caught up.
Once upon a time I spoke out against the removal of
notmuch-deliver:
Hello,
On 2013-04-09, David Bremner wrote:
> David Belohrad writes:
>
>> is actually someone using notmuch deliver?
I am using notmuch-deliver with maildrop. This allows me to
filter and tag based on any header field of the message.
>> [...]
>
> notmuch-deliver is replaced by notmuch insert
