From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/3] Introduce the add command
Date: Sat, 13 Jul 2013 18:45:43 -0600 [thread overview]
Message-ID: <1373762746-22308-1-git-send-email-awg+notmuch@xvx.ca> (raw)
Hi everyone,
The recent introduction of insert inspired me to finally add a feature I've
been wanting: a command to index a specific file in the maildir. My usecase
for this is that I have an inotify-based script that watches for new mail
and calls notmuch new when new mail shows up. Running notmuch new in this
situation is overkill, since I know exactly what's changed. A faster command
that just adds a single file reduces contention on the database lock.
This series introduces a new command, "notmuch add", which indexes a file
that already exists in the maildir. It is implemented in notmuch-insert.c
because it uses the basic infrastructure introduced for the insert command.
Missing man page for now - wanted to get the code out first for review.
-- Adam
Adam Wolfe Gordon (3):
cli: Return an error code from add_message_to_database
cli: Introduce the add command
test: Add simple tests for the add command
notmuch-client.h | 3 +++
notmuch-insert.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++---
notmuch.c | 2 ++
test/insert | 35 +++++++++++++++++++++++++++++++++
4 files changed, 94 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-14 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 0:45 Adam Wolfe Gordon [this message]
2013-07-14 0:45 ` [PATCH 1/3] cli: Return an error code from add_message_to_database Adam Wolfe Gordon
2013-07-14 0:45 ` [PATCH 2/3] cli: Introduce the add command Adam Wolfe Gordon
2013-07-14 0:45 ` [PATCH 3/3] test: Add simple tests for " Adam Wolfe Gordon
2013-07-17 15:23 ` [PATCH 0/3] Introduce " Tomi Ollila
2013-07-19 14:48 ` Jameson Graef Rollins
2013-07-21 8:16 ` Mark Walters
2013-07-21 20:25 ` Jameson Graef Rollins
2013-07-21 21:47 ` Vladimir Marek
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=1373762746-22308-1-git-send-email-awg+notmuch@xvx.ca \
--to=awg+notmuch@xvx.ca \
--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).