unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
blob 3dcc646cfa1353d72e3658e45bc5fcf451ca7487 6292 bytes (raw)
name: doc/man1/notmuch.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
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
 
=======
notmuch
=======

SYNOPSIS
========

**notmuch** [option ...] **command** [arg ...]

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

Notmuch is a command-line based program for indexing, searching,
reading, and tagging large collections of email messages.

This page describes how to get started using notmuch from the command
line, and gives a brief overview of the commands available. For more
information on e.g. **notmuch show** consult the **notmuch-show(1)** man
page, also accessible via **notmuch help show**

The quickest way to get started with Notmuch is to simply invoke the
``notmuch`` command with no arguments, which will interactively guide
you through the process of indexing your mail.

NOTE
====

While the command-line program ``notmuch`` provides powerful
functionality, it does not provide the most convenient interface for
that functionality. More sophisticated interfaces are expected to be
built on top of either the command-line interface, or more likely, on
top of the notmuch library interface. See https://notmuchmail.org for
more about alternate interfaces to notmuch. The emacs-based interface to
notmuch (available under **emacs/** in the Notmuch source distribution)
is probably the most widely used at this time.

OPTIONS
=======

Supported global options for ``notmuch`` include

``--help`` [command-name]
    Print a synopsis of available commands and exit. With an optional
    command name, show the man page for that subcommand.

``--version``
    Print the installed version of notmuch, and exit.

``--config=FILE``
    Specify the configuration file to use. This overrides any
    configuration file specified by ${NOTMUCH\_CONFIG}.

``--uuid=HEX``
    Enforce that the database UUID (a unique identifier which persists
    until e.g. the database is compacted) is HEX; exit with an error
    if it is not. This is useful to detect rollover in modification
    counts on messages. You can find this UUID using e.g. ``notmuch
    count --lastmod``

All global options except ``--config`` can also be specified after the
command. For example, ``notmuch subcommand --uuid=HEX`` is equivalent
to ``notmuch --uuid=HEX subcommand``.

COMMANDS
========

SETUP
-----

The **notmuch setup** command is used to configure Notmuch for first
use, (or to reconfigure it later).

The setup command will prompt for your full name, your primary email
address, any alternate email addresses you use, and the directory
containing your email archives. Your answers will be written to a
configuration file in ${NOTMUCH\_CONFIG} (if set) or
${HOME}/.notmuch-config . This configuration file will be created with
descriptive comments, making it easy to edit by hand later to change the
configuration. Or you can run **notmuch setup** again to change the
configuration.

The mail directory you specify can contain any number of sub-directories
and should primarily contain only files with individual email messages
(eg. maildir or mh archives are perfect). If there are other, non-email
files (such as indexes maintained by other email programs) then notmuch
will do its best to detect those and ignore them.

Mail storage that uses mbox format, (where one mbox file contains many
messages), will not work with notmuch. If that's how your mail is
currently stored, it is recommended you first convert it to maildir
format with a utility such as mb2md before running **notmuch setup .**

Invoking ``notmuch`` with no command argument will run **setup** if the
setup command has not previously been completed.

OTHER COMMANDS
--------------

Several of the notmuch commands accept search terms with a common
syntax. See **notmuch-search-terms**\ (7) for more details on the
supported syntax.

The **search**, **show**, **address** and **count** commands are used
to query the email database.

The **reply** command is useful for preparing a template for an email
reply.

The **tag** command is the only command available for manipulating
database contents.

The **dump** and **restore** commands can be used to create a textual
dump of email tags for backup purposes, and to restore from that dump.

The **config** command can be used to get or set settings in the notmuch
configuration file.

CUSTOM COMMANDS
---------------

If the given command is not known to notmuch, notmuch tries to execute
the external **notmuch-<subcommand>** in ${PATH} instead. This allows
users to have their own notmuch related tools to be run via the
notmuch command. By design, this does not allow notmuch's own commands
to be overridden using external commands.

OPTION SYNTAX
-------------

All options accepting an argument can be used with '=' or ':' as a
separator. Except for boolean options (wihch would be ambiguous), a
space can also be used as a separator. The following are all
equivalent:

::

   notmuch --config=alt-config config get user.name
   notmuch --config:alt-config config get user.name
   notmuch --config alt-config config get user.name

ENVIRONMENT
===========

The following environment variables can be used to control the behavior
of notmuch.

**NOTMUCH\_CONFIG**
    Specifies the location of the notmuch configuration file. Notmuch
    will use ${HOME}/.notmuch-config if this variable is not set.

**NOTMUCH\_TALLOC\_REPORT**
    Location to write a talloc memory usage report. See
    **talloc\_enable\_leak\_report\_full** in **talloc(3)** for more
    information.

**NOTMUCH\_DEBUG\_QUERY**
    If set to a non-empty value, the notmuch library will print (to
    stderr) Xapian queries it constructs.

SEE ALSO
========

**notmuch-address(1)**,
**notmuch-compact(1)**,
**notmuch-config(1)**,
**notmuch-count(1)**,
**notmuch-dump(1)**,
**notmuch-hooks(5)**,
**notmuch-insert(1)**,
**notmuch-new(1)**,
**notmuch-properties(7)**,
**notmuch-reindex(1)**,
**notmuch-reply(1)**,
**notmuch-restore(1)**,
**notmuch-search(1)**,
**notmuch-search-terms(7)**,
**notmuch-show(1)**,
**notmuch-tag(1)**

The notmuch website: **https://notmuchmail.org**

CONTACT
=======

Feel free to send questions, comments, or kudos to the notmuch mailing
list <notmuch@notmuchmail.org> . Subscription is not required before
posting, but is available from the notmuchmail.org website.

Real-time interaction with the Notmuch community is available via IRC
(server: irc.freenode.net, channel: #notmuch).

debug log:

solving 3dcc646c ...
found 3dcc646c in https://yhetil.org/notmuch/20200507192645.124644-1-dkg@fifthhorseman.net/
found d2cd8da5 in https://yhetil.org/notmuch.git/
preparing index
index prepared:
100644 d2cd8da55cb99e0d20792fdbe326e415bd0109f7	doc/man1/notmuch.rst

applying [1/1] https://yhetil.org/notmuch/20200507192645.124644-1-dkg@fifthhorseman.net/
diff --git a/doc/man1/notmuch.rst b/doc/man1/notmuch.rst
index d2cd8da5..3dcc646c 100644

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

index at:
100644 3dcc646cfa1353d72e3658e45bc5fcf451ca7487	doc/man1/notmuch.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).