From: David Bremner <david@tethera.net>
To: Jan Detke <jandetke@outlook.com>, notmuch@notmuchmail.org
Subject: Re: Usage of hooks w/ notmuch
Date: Fri, 23 Jun 2023 19:42:32 +0300 [thread overview]
Message-ID: <875y7ef7uv.fsf@tethera.net> (raw)
In-Reply-To: <PAVPR08MB9401747A5A783C285C4A06E1C223A@PAVPR08MB9401.eurprd08.prod.outlook.com>
Jan Detke <jandetke@outlook.com> writes:
> I got a problem using hooks with notmuch (Version 0.37-3). I specified
> the hook directory under [database] in my notmuch config. The script
> (post-new.sh) is executable and works when invoked manually in the
> terminal, but it does not get executed after invoking notmuch
> new. There is no additional output given in the terminal.
You need to follow the naming in notmuch-hooks(5) exactly, so
<hook_dir>/post-new rather than <hook-dir>/post-new.sh
d
prev parent reply other threads:[~2023-06-23 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 11:45 Usage of hooks w/ notmuch Jan Detke
2023-06-23 16:42 ` David Bremner [this message]
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y7ef7uv.fsf@tethera.net \
--to=david@tethera.net \
--cc=jandetke@outlook.com \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).