Supported options for <b>reply</b> include
- <b>--format=</b>(<b>default</b>|<b>json</b>|<b>sexp</b>|<b>headers-only</b>)
+ <b>--format=(default|json|sexp|headers-only)</b>
<b>default</b>
Includes subject and quoted message body as an RFC 2822
<b>json</b> Produces JSON output containing headers for a reply mes‐
sage and the contents of the original message. This out‐
- put can be used by a client to create a reply message
- intelligently.
+ put can be used by a client to create a reply message in‐
+ telligently.
- <b>sexp</b> Produces S-Expression output containing headers for a
- reply message and the contents of the original message.
+ <b>sexp</b> Produces S-Expression output containing headers for a re‐
+ ply message and the contents of the original message.
This output can be used by a client to create a reply
message intelligently.
headers.
<b>--format-version=N</b>
- Use the specified structured output format version. This is
- intended for programs that invoke <a href='../notmuch-1/'>notmuch</a>(1) internally. If
- omitted, the latest supported version will be used.
+ Use the specified structured output format version. This is in‐
+ tended for programs that invoke <a href='../notmuch-1/'>notmuch</a>(1) internally. If omit‐
+ ted, the latest supported version will be used.
- <b>--reply-to=</b>(<b>all</b>|<b>sender</b>)
+ <b>--reply-to=(all|sender)</b>
- <b>all</b> (default)
+ <b>all</b> <b>(default)</b>
Replies to all addresses.
<b>sender</b> Replies only to the sender. If replying to user's own
contains something other than only the user's addresses.
<b>--decrypt=(false|auto|true)</b>
- If <b>true</b>, decrypt any MIME encrypted parts found in the selected con‐
- tent (i.e., "multipart/encrypted" parts). Status of the decryption
- will be reported (currently only supported with --format=json and
- --format=sexp), and on successful decryption the multipart/encrypted
- part will be replaced by the decrypted content.
+ If <b>true</b>, decrypt any MIME encrypted parts found in the selected
+ content (i.e., "multipart/encrypted" parts). Status of the de‐
+ cryption will be reported (currently only supported with <b>--for-</b>
+ <b>mat=json</b> and <b>--format=sexp</b>), and on successful decryption the
+ multipart/encrypted part will be replaced by the decrypted con‐
+ tent.
- If <b>auto</b>, and a session key is already known for the message, then it
- will be decrypted, but notmuch will not try to access the user's
- secret keys.
+ If <b>auto</b>, and a session key is already known for the message,
+ then it will be decrypted, but notmuch will not try to access
+ the user's secret keys.
- Use <b>false</b> to avoid even automatic decryption.
+ Use <b>false</b> to avoid even automatic decryption.
- Non-automatic decryption expects a functioning <b>gpg-agent</b>(1) to pro‐
- vide any needed credentials. Without one, the decryption will likely
- fail.
+ Non-automatic decryption expects a functioning <b>gpg-agent</b>(1) to
+ provide any needed credentials. Without one, the decryption will
+ likely fail.
- Default: <b>auto</b>
+ Default: <b>auto</b>
- See <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7) for details of the supported syntax for
+ See <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7) for details of the supported syntax for
<search-terms>.
- Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
- matching a single message, (such as id:<message-id>), but it can be
+ Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
+ matching a single message, (such as id:<message-id>), but it can be
useful to reply to several messages at once. For example, when a series
- of patches are sent in a single thread, replying to the entire thread
- allows for the reply to comment on issues found in multiple patches.
- The default format supports replying to multiple messages at once, but
+ of patches are sent in a single thread, replying to the entire thread
+ allows for the reply to comment on issues found in multiple patches.
+ The default format supports replying to multiple messages at once, but
the JSON and S-Expression formats do not.
</pre>
<h2>SEE ALSO</h2>
<pre>
- <a href='../notmuch-1/'>notmuch</a>(1),
<a href='../notmuch-config-1/'>notmuch-config</a>(1), <a href='../notmuch-count-1/'>notmuch-count</a>(1), <a href='../notmuch-dump-1/'>notmuch-dump</a>(1), <a href='../notmuch-hooks-5/'>not‐</a>
- <a href='../notmuch-hooks-5/'>much-hooks</a>(5),
<a href='../notmuch-insert-1/'>notmuch-insert</a>(1), <a href='../notmuch-new-1/'>notmuch-new</a>(1), <a href='../notmuch-restore-1/'>notmuch-restore</a>(1),
+ <a href='../notmuch-1/'>notmuch</a>(1),
<a href='../notmuch-config-1/'>notmuch-config</a>(1), <a href='../notmuch-count-1/'>notmuch-count</a>(1), <a href='../notmuch-dump-1/'>notmuch-dump</a>(1), <a href='../notmuch-hooks-5/'>not‐</a>
+ <a href='../notmuch-hooks-5/'>much-hooks</a>(5),
<a href='../notmuch-insert-1/'>notmuch-insert</a>(1), <a href='../notmuch-new-1/'>notmuch-new</a>(1), <a href='../notmuch-restore-1/'>notmuch-restore</a>(1),
<a href='../notmuch-search-1/'>notmuch-search</a>(1), <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7), <a href='../notmuch-show-1/'>notmuch-show</a>(1), <a href='../notmuch-tag-1/'>not‐</a>
<a href='../notmuch-tag-1/'>much-tag</a>(1)
</pre>
<h2>COPYRIGHT</h2>
<pre>
- 2009-2018, Carl Worth and many others
+ 2009-2022, Carl Worth and many others
</pre>
-<h2>0.26</h2>
+<h2>0.35</h2>
projects / notmuch-wiki / blobdiff