Re: Does Gnus automatically run 'notmuch new' if configured?

[Pankaj Jangid <pankaj@codeisgreat.org>]

On Fri, Sep 25 2020, Eric Abrahamsen wrote:

> Ahem, I may have led you astray with `async-shell-command', which is
> mostly meant to be called interactively -- in which case you usually
> want to see the output. In lisp code that runs in the background,
> you're better off using `start-process', where you can tell it not to
> keep the output:

I had explored a little bit of `start-process` and `call-process` when I
was reading help on `async-shell-comman`. But then I thought these are
low level methods and I don't need that much control.

> (start-process "unnecessary label" nil "/path/to/notmuch" '("new"))

This is nice. I am using this now. Just a correction. Last argument is
not list. List was giving error. I am using below code,

(start-process "notmuch" "*Notmuch*" "notmuch" "new")

Now, I have another related question - which hook is best for the
purpose? Currently I am using `gnus-after-getting-new-news-hook`. But
that is run only when I press `g` (gnus-group-get-new-news). It seems
that the hook is not invoked when I start Gnus. Also the hook is
probably invoked before splitting.

Since I am using `nnml` backend, there are couple of choices for my
use-case. One is `nnmail-read-incoming-mail`. The documentation also
says, "use this hook to notify any mail watch programs". But I also use
simple splittig (`nnmail-split-methods`). And the documentation also has
a `nnmail-split-hook`. But from the documentation it looks like that
this hook is run, after the splitting has started, and not after the
splitting is over -

--8<---------------cut here---------------start------------->8---
‘nnmail-split-hook’
     Hook run in the buffer where the mail headers of each message is
     kept just before the splitting based on these headers is done.  The
     hook is free to modify the buffer contents in any way it sees
     fit—the buffer is discarded after the splitting has been done, and
     no changes performed in the buffer will show up in any files.
     ‘gnus-article-decode-encoded-words’ is one likely function to add
     to this hook.
--8<---------------cut here---------------end--------------->8---

In such case if I run `notmuch new` then the indexing might create links
to non-existing paths.

Any other hook that you can think of?