X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=9dde8c4922a5e43aa2bca17837c9c8451df8c97d;hb=ad04c8c6b3d8c29a905d9f5f92256fc2bd64be5e;hp=5e1e6d71a519ec34871920ce52ea59aa0b0c4984;hpb=33b367e699bbcc8fecd001fab8033a4e91b13450;p=obsolete%2Fnotmuch-wiki
diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn
index 5e1e6d7..9dde8c4 100644
--- a/manpages/notmuch-reply-1.mdwn
+++ b/manpages/notmuch-reply-1.mdwn
@@ -1,128 +1,118 @@
NOTMUCH-REPLY(1)
NAME
-
- notmuch-reply - Constructs a reply template for a set of messages.
+ notmuch-reply - constructs a reply template for a set of messages
SYNOPSIS
-
- notmuch reply [options...] <search-term>...
+ notmuch reply [options...] <search-term>...
DESCRIPTION
-
Constructs a reply template for a set of messages.
-
-
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
- copied, but not including any of the current user's email addresses (as
+ 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.
-
-
It also builds a suitable new subject, including Re: at the front (if
not already present), and adding the message IDs of the messages being
replied to to the References list and setting the In-Reply-To: field
correctly.
-
-
Finally, the original contents of the emails are quoted by prefixing
- each line with '> ' and included in the body.
-
+ each line with '> ' and included in the body.
-
The resulting message template is output to stdout.
-
-
Supported options for reply include
-
-
- --format=(default|json|headers-only)
-
+ --format=(default|json|sexp|headers-only)
-
default
Includes subject and quoted message body.
-
-
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
+ 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
+ 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
- content (ie. "multipart/encrypted" parts). Status of the
- decryption will be reported (currently only supported with
- --format=json) and the multipart/encrypted part will be
- replaced by the decrypted content.
-
+ 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.
-
- See notmuch-search-terms(7) for details of the supported syntax for
- .
+ 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
+ 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
+ the JSON and S-Expression formats do not.
+EXIT STATUS
- Note: It is most common to use notmuch reply with a search string
- matching a single message, (such as 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
- the JSON format does not.
+ This command supports the following special exit status codes
+
+ 20 The requested format version is too old.
+
+ 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-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), notmuch-
+ tag(1)
-Notmuch 0.13.2
+Notmuch 0.16