1 .TH NOTMUCH-SHOW 1 2013-07-28 "Notmuch 0.16"
3 notmuch-show \- show messages matching the given search terms
7 .RI "[" options "...] <" search-term ">..."
11 Shows all messages matching the search terms.
13 See \fBnotmuch-search-terms\fR(7)
14 for details of the supported syntax for <search-terms>.
16 The messages will be grouped and sorted based on the threading (all
17 replies to a particular message will appear immediately after that
18 message in date order). The output is not indented by default, but
19 depth tags are printed so that proper indentation can be performed by
20 a post-processor (such as the emacs interface to notmuch).
27 .B \-\-entire\-thread=(true|false)
31 outputs all messages in the thread of any message matching the search
32 terms; if false, it outputs only the matching messages. For
36 this defaults to true. For other formats, this defaults to false.
41 .B \-\-format=(text|json|sexp|mbox|raw)
45 .BR text " (default for messages)"
47 The default plain-text format has all text-content MIME parts
48 decoded. Various components in the output,
49 .RB ( message ", " header ", " body ", " attachment ", and MIME " part ),
50 will be delimited by easily-parsed markers. Each marker consists of a
51 Control-L character (ASCII decimal 12), the name of the marker, and
52 then either an opening or closing brace, ('{' or '}'), to either open
53 or close the component. For a multipart MIME message, these parts will
60 The output is formatted with Javascript Object Notation (JSON). This
61 format is more robust than the text format for automated
62 processing. The nested structure of multipart MIME messages is
63 reflected in nested JSON output. By default JSON output includes all
64 messages in a matching thread; that is, by default,
68 .B "\-\-entire\-thread"
69 The caller can disable this behaviour by setting
70 .B \-\-entire\-thread=false
76 The output is formatted as an S-Expression (sexp). This
77 format is more robust than the text format for automated
78 processing. The nested structure of multipart MIME messages is
79 reflected in nested S-Expression output. By default,
80 S-Expression output includes all messages in a matching thread;
85 .B "\-\-entire\-thread"
86 The caller can disable this behaviour by setting
87 .B \-\-entire\-thread=false
94 All matching messages are output in the traditional, Unix mbox format
95 with each message being prefixed by a line beginning with "From " and
96 a blank line separating each message. Lines in the message content
97 beginning with "From " (preceded by zero or more '>' characters) have
98 an additional '>' character added. This reversible escaping
99 is termed "mboxrd" format and described in detail here:
103 http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html
110 .BR raw " (default for a single part, see \-\-part)"
112 For a message or an attached message part, the original, raw content
113 of the email message is output. Consumers of this format should expect
114 to implement MIME decoding and similar functions.
116 For a single part (\-\-part) the raw part content is output after
117 performing any necessary MIME decoding. Note that messages with a
118 simple body still have two parts: part 0 is the whole message and part
121 For a multipart part, the part headers and body (including all child
124 The raw format must only be used with search terms matching single
131 .BR \-\-format-version=N
133 Use the specified structured output format version. This is intended
134 for programs that invoke \fBnotmuch\fR(1) internally. If omitted, the
135 latest supported version will be used.
142 Output the single decoded MIME part N of a single message. The search
143 terms must match only a single message. Message parts are numbered in
144 a depth-first walk of the message MIME structure, and are identified
145 in the 'json', 'sexp' or 'text' output formats.
152 Compute and report the validity of any MIME cryptographic signatures
153 found in the selected content (ie. "multipart/signed" parts). Status
154 of the signature will be reported (currently only supported with
155 --format=json and --format=sexp), and the multipart/signed part
156 will be replaced by the signed data.
163 Decrypt any MIME encrypted parts found in the selected content
164 (ie. "multipart/encrypted" parts). Status of the decryption will be
165 reported (currently only supported with --format=json and
166 --format=sexp) and on successful decryption the multipart/encrypted
167 part will be replaced by the decrypted content.
169 Decryption expects a functioning \fBgpg-agent\fR(1) to provide any
170 needed credentials. Without one, the decryption will fail.
177 .BR \-\-exclude=(true|false)
179 Specify whether to omit threads only matching search.tag_exclude from
180 the search results (the default) or not. In either case the excluded
181 message will be marked with the exclude flag (except when output=mbox
182 when there is nowhere to put the flag).
184 If --entire-thread is specified then complete threads are returned
185 regardless (with the excluded flag being set when appropriate) but
186 threads that only match in an excluded message are not returned when
196 .B \-\-body=(true|false)
198 If true (the default)
200 includes the bodies of the messages in the output; if false,
203 is only implemented for the json and sexp formats and it is incompatible with
206 This is useful if the caller only needs the headers as body-less
207 output is much faster and substantially smaller.
212 is to display a single thread of email messages. For this, use a
213 search term of "thread:<thread-id>" as can be seen in the first
214 column of output from the
220 This command supports the following special exit status codes
224 The requested format version is too old.
227 The requested format version is too new.
231 \fBnotmuch\fR(1), \fBnotmuch-config\fR(1), \fBnotmuch-count\fR(1),
232 \fBnotmuch-dump\fR(1), \fBnotmuch-hooks\fR(5),
233 \fBnotmuch-insert\fR(1), \fBnotmuch-new\fR(1),
234 \fBnotmuch-reply\fR(1), \fBnotmuch-restore\fR(1),
235 \fBnotmuch-search\fR(1), \fBnotmuch-search-terms\fR(7),