unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
blob d8cb77f5dbeb146421c4aec3cdb5ebb4992580fd 2560 bytes (raw)
name: doc/man1/notmuch-new.rst 	 # note: path name is non-authoritative(*)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
 
===========
notmuch-new
===========

SYNOPSIS
========

**notmuch** **new** [options]

DESCRIPTION
===========

Find and import any new messages to the database.

The **new** command scans all sub-directories of the database,
performing 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 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 subsequent 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.

**notmuch new** updates tags according to maildir flag changes if the
**maildir.synchronize\_flags** configuration option is enabled. See
**notmuch-config(1)** for details.

The **new** command supports hooks. See **notmuch-hooks(5)** for more
details on hooks.

Supported options for **new** include

    ``--no-hooks``
        Prevents hooks from being run.

    ``--quiet``
        Do not print progress or results.

    ``--try-decrypt=(true|auto|false)``

        If ``true``, when encountering an encrypted message, try to
        decrypt it while indexing.  If decryption is successful, index
        the cleartext itself.  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.

        Be aware that the index is likely
        sufficient to reconstruct the cleartext of the message itself,
        so please ensure that the notmuch message index is adequately
        protected.  DO NOT USE ``--try-decrypt=true`` without
        considering the security of your index.

        See also ``index.try_decrypt`` in **notmuch-config(1)**.

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)**,
**notmuch-hooks(5)**,
**notmuch-insert(1)**,
**notmuch-reply(1)**,
**notmuch-restore(1)**,
**notmuch-search(1)**,
**notmuch-search-terms(7)**,
**notmuch-show(1)**,
**notmuch-tag(1)**

debug log:

solving d8cb77f5 ...
found d8cb77f5 in https://yhetil.org/notmuch/20171025065203.24403-12-dkg@fifthhorseman.net/
found bc26aa48 in https://yhetil.org/notmuch.git/
preparing index
index prepared:
100644 bc26aa4806a7e07400708a9f35b8f832009302be	doc/man1/notmuch-new.rst

applying [1/1] https://yhetil.org/notmuch/20171025065203.24403-12-dkg@fifthhorseman.net/
diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst
index bc26aa48..d8cb77f5 100644

Checking patch doc/man1/notmuch-new.rst...
Applied patch doc/man1/notmuch-new.rst cleanly.

index at:
100644 d8cb77f5dbeb146421c4aec3cdb5ebb4992580fd	doc/man1/notmuch-new.rst

(*) Git path names are given by the tree(s) the blob belongs to.
    Blobs themselves have no identifier aside from the hash of its contents.^

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