Gnus development mailing list
 help / color / mirror / Atom feed
From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Does Gnus automatically run 'notmuch new' if configured?
Date: Sat, 26 Sep 2020 06:59:49 +0530	[thread overview]
Message-ID: <m21ripmik2.fsf@codeisgreat.org> (raw)
In-Reply-To: <87mu1ditjz.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 25 Sep 2020 11:45:52 -0700")

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

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

>> (defadvice gnus (after gnus-notmuch-new activate)
>> (your-run-notmuch-new-function))

> Rather than an advice, I would just add your function to the
> `gnus-startup-hook', as well.

There was one more enquiry in this regard. Probably most of the Gnus
users are using splitting as well... probably, and I am sure "notmuch
new" should be run after the splitting action is over. Is there a hook
for that?


  parent reply	other threads:[~2020-09-26  1:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  8:32 Pankaj Jangid
2020-09-24 16:42 ` Eric Abrahamsen
2020-09-24 17:55 ` Adam Sjøgren
2020-09-25  4:00   ` Pankaj Jangid
2020-09-25  6:05     ` Eric Abrahamsen
2020-09-25  7:51       ` Pankaj Jangid
2020-09-25  8:09   ` Eric S Fraga
2020-09-25  9:31     ` Adam Sjøgren
2020-09-25 14:44       ` Pankaj Jangid
2020-09-25 16:31         ` Eric Abrahamsen
2020-09-25 17:47           ` Pankaj Jangid
2020-09-25 18:16             ` Adam Sjøgren
2020-09-25 18:45             ` Eric Abrahamsen
2020-09-25 18:52               ` Adam Sjøgren
2020-09-26  1:29               ` Pankaj Jangid [this message]
2020-09-26 11:48                 ` Adam Sjøgren
2020-09-26 17:08                   ` Pankaj Jangid
2020-09-25 18:25       ` Adam Sjøgren

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m21ripmik2.fsf@codeisgreat.org \
    --to=pankaj@codeisgreat.org \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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.
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 NNTP newsgroup(s).