X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=dcfe28ba4c634f38eb5daf4e296bd570af5d33de;hb=2d4847b0b970fc27581ea5e86b0502cbcd92ce78;hp=9dde8c4922a5e43aa2bca17837c9c8451df8c97d;hpb=ad04c8c6b3d8c29a905d9f5f92256fc2bd64be5e;p=notmuch-wiki
diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn
index 9dde8c4..dcfe28b 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
@@ -17,7 +17,7 @@
To make replying to email easier, notmuch reply takes an existing set
of messages and constructs a suitable mail template. The Reply-to:
header (if any, otherwise From:) is used for the To: address. Unless
- --reply-to=sender is specified, values from the To: and Cc: headers are
+ --reply-to=sender is specified, values from the To: and Cc: headers are
copied, but not including any of the current user's email addresses (as
configured in primary_mail or other_email in the .notmuch-config file)
in the recipient list.
@@ -34,67 +34,73 @@
Supported options for reply include
- --format=(default|json|sexp|headers-only)
+ --format=(default|json|sexp|headers-only)
- default
- Includes subject and quoted message body.
+ default
- 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.
+ Includes subject and quoted message body as an RFC 2822
+ message.
- 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.
+ json
- headers-only
- Only produces In-Reply-To, References, To, Cc, and Bcc
- headers.
+ 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.
- --format-version=N
+ sexp
- Use the specified structured output format version. This is
+ 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)
+ --reply-to=(all|sender)
- all (default)
- Replies to all addresses.
+ all (default)
- 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.
+ Replies to all addresses.
- --decrypt
+ sender
- 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
+ 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
+ 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
+ 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.
@@ -102,17 +108,31 @@
This command supports the following special exit status codes
- 20 The requested format version is too old.
+ 20
+
+ The requested format version is too old.
- 21 The requested format version is too new.
+ 21
+
+ The requested format version is too new.
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.16
+0.18