X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-new-1.mdwn;h=caba2acd8643e2ae0a221303dabe320a6562840b;hb=219490b75a85ca18d449168575a0c7538e71612e;hp=f8026ea0c6ae1c8962daa15fb46966341cd7e71d;hpb=e9e606f333685696ecc9979b8813b0838b9e969e;p=notmuch-wiki
diff --git a/manpages/notmuch-new-1.mdwn b/manpages/notmuch-new-1.mdwn
index f8026ea..caba2ac 100644
--- a/manpages/notmuch-new-1.mdwn
+++ b/manpages/notmuch-new-1.mdwn
@@ -2,12 +2,12 @@
NAME
- notmuch-new - Incorporate new mail into the notmuch database.
+ notmuch-new - incorporate new mail into the notmuch database
SYNOPSIS
- notmuch new [--no-hooks]
+ notmuch new [options]
DESCRIPTION
@@ -18,36 +18,81 @@
full-text indexing on new messages that are found. Each new message
will automatically be tagged with both the inbox and unread tags.
- You should run notmuch new once after first running notmuch setup to
+ You should run notmuch new once after first running notmuch-setup(1) to
create the initial database. The first run may take a long time if you
have a significant amount of mail (several hundred thousand messages or
more). Subsequently, you should run notmuch new whenever new mail is
- delivered and you wish to incorporate it into the database. These sub-
+ delivered and you wish to incorporate it into the database. These subâ
sequent runs will be much quicker than the initial run.
- Invoking notmuch with no command argument will run new if notmuch setup
- has previously been completed, but notmuch new has not previously been
- run.
+ Invoking notmuch with no command argument will run new if not-
+ much-setup(1) has previously been completed, but notmuch new has not
+ previously been run.
notmuch new updates tags according to maildir flag changes if the
- maildir.synchronize_flags configuration option is enabled. See notmuch-
- config(1) for details.
+ maildir.synchronize_flags configuration option is enabled. See notâ
+ much-config(1) for details.
- The new command supports hooks. See notmuch-hooks(5) for more details
+ The new command supports hooks. See notmuch-hooks(5) for more details
on hooks.
Supported options for new include
- --no-hooks
+ --no-hooks
+ Prevents hooks from being run.
- Prevents hooks from being run.
+ --quiet
+ Do not print progress or results.
+
+ --verbose
+ Print file names being processed. Ignored when combined with
+ --quiet.
+
+ --decrypt=(true|nostash|auto|false)
+ If true, when encountering an encrypted message, try to decrypt
+ it while indexing, and stash any discovered session keys. If
+ auto, try to use any session key already known to belong to this
+ message, but do not attempt to use the user's secret keys. If
+ decryption is successful, index the cleartext of the message.
+
+ Be aware that the index is likely sufficient (and the session
+ key is certainly sufficient) to reconstruct the cleartext of the
+ message itself, so please ensure that the notmuch message index
+ is adequately protected. DO NOT USE --decrypt=true or --de-
+ crypt=nostash without considering the security of your index.
+
+ See also index.decrypt in notmuch-config(1).
+
+ --full-scan
+ By default notmuch-new uses directory modification times
+ (mtimes) to optimize the scanning of directories for new mail.
+ This option turns that optimization off.
+
+
+EXIT STATUS
+
+ This command supports the following special exit status code
+
+ 75 (EX_TEMPFAIL)
+ A temporary failure occurred; the user is invited to retry.
SEE ALSO
- notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
- much-hooks(5), notmuch-reply(1), notmuch-restore(1), notmuch-search(1),
- notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+ notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notâ
+ much-hooks(5), notmuch-insert(1), notmuch-reply(1), notmuch-restore(1),
+ notmuch-search(1), notmuch-search-terms(7), notmuch-show(1), notâ
+ much-tag(1)
+
+
+AUTHOR
+
+ Carl Worth and many others
+
+
+COPYRIGHT
+
+ 2009-2022, Carl Worth and many others
-Notmuch 0.13.2
+0.35