X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=79ef1ff32a92e217f7b5e7b54309862d0566650e;hb=87440cbc1d12fc3a860289b11d7b850b538dcf3d;hp=2e879d7aea2f480179c5c1b961922d1522fd4872;hpb=59c3b4d66ce19a9dde85e65d5fc5c150e23de209;p=notmuch-wiki
diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn
index 2e879d7..79ef1ff 100644
--- a/manpages/notmuch-reply-1.mdwn
+++ b/manpages/notmuch-reply-1.mdwn
@@ -7,7 +7,7 @@
SYNOPSIS
- notmuch reply [options...] <search-term>...
+ notmuch reply [option ...] <search-term> ...
DESCRIPTION
@@ -33,69 +33,62 @@
The resulting message template is output to stdout.
Supported options for reply include
-
- --format=(default|json|sexp|headers-only)
-
- default
- Includes subject and quoted message body as an RFC 2822
- message.
-
- json
- 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.
-
- sexp
- Produces S-Expression output containing headers for a
- reply message and the contents of the original message.
- This output can be used by a client to create a reply
- message intelligently.
-
- headers-only
- Only produces In-Reply-To, References, To, Cc, and Bcc
- headers.
-
- --format-version=N
-
- Use the specified structured output format version. This is
- intended for programs that invoke notmuch(1) internally. If
- omitted, the latest supported version will be used.
-
- --reply-to=(all|sender)
-
- all (default)
- Replies to all addresses.
-
- sender
- Replies only to the sender. If replying to user's own
- message (Reply-to: or From: header is one of the user's
- configured email addresses), try To:, Cc:, and Bcc:
- headers in this order, and copy values from the first
- that contains something other than only the user's
- addresses.
-
- --decrypt
-
- Decrypt any MIME encrypted parts found in the selected con-
- tent (ie. "multipart/encrypted" parts). Status of the
- decryption will be reported (currently only supported with
- --format=json and --format=sexp) and on successful decryp-
- tion the multipart/encrypted part will be replaced by the
- decrypted content.
-
- Decryption expects a functioning gpg-agent(1) to provide any
- needed credentials. Without one, the decryption will fail.
-
- See notmuch-search-terms(7) for details of the supported syntax for
+ --format=(default|json|sexp|headers-only)
+
+ default
+ Includes subject and quoted message body as an RFC 2822
+ message.
+
+ json 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.
+
+ sexp Produces S-Expression output containing headers for a
+ reply message and the contents of the original message.
+ This output can be used by a client to create a reply
+ message intelligently.
+
+ headers-only
+ Only produces In-Reply-To, References, To, Cc, and Bcc
+ headers.
+
+ --format-version=N
+ Use the specified structured output format version. This is
+ intended for programs that invoke notmuch(1) internally. If
+ omitted, the latest supported version will be used.
+
+ --reply-to=(all|sender)
+
+ all (default)
+ Replies to all addresses.
+
+ sender Replies only to the sender. If replying to user's own
+ message (Reply-to: or From: header is one of the user's
+ configured email addresses), try To:, Cc:, and Bcc: headâ
+ ers in this order, and copy values from the first that
+ contains something other than only the user's addresses.
+
+ --decrypt
+ Decrypt any MIME encrypted parts found in the selected conâ
+ tent (ie. "multipart/encrypted" parts). Status of the decrypâ
+ tion will be reported (currently only supported with --forâ
+ mat=json and --format=sexp) and on successful decryption the
+ multipart/encrypted part will be replaced by the decrypted
+ content.
+
+ Decryption expects a functioning gpg-agent(1) to provide any
+ needed credentials. Without one, the decryption will fail.
+
+ See notmuch-search-terms(7) for details of the supported syntax for
<search-terms>.
- Note: It is most common to use notmuch reply with a search string
- matching a single message, (such as id:<message-id>), but it can be
+ Note: It is most common to use notmuch reply 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.
@@ -110,10 +103,20 @@
SEE ALSO
- notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
- much-hooks(5), notmuch-insert(1), notmuch-new(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-new(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
+
+ 2014, Carl Worth and many others
-Notmuch 0.17
+0.19