X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=3340075b367fac4639fa33bbca0413c3d3a87d78;hb=e9ff6d27277272084823c2d973a62921c62cf9ff;hp=203b57d4b695e4cee51089e4957a1fe66c28e494;hpb=aeb851d55ecf79d2e8a8c9a1a99fd73ef1a7ac06;p=notmuch-wiki diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 203b57d..3340075 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -2,12 +2,12 @@

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 [option ...] <search-term> ...

DESCRIPTION

@@ -15,12 +15,13 @@ 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 - configured in primary_mail or other_email in the .notmuch-config file) - in the recipient list. + of messages and constructs a suitable mail template. Its To: address is + set according to the original email in this way: if the Reply-to: + header is present and different from any To:/Cc: address it is used, + otherwise From: header is used. 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 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 @@ -33,61 +34,90 @@ 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: 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>. - --format=(default|json|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. - - headers-only - Only produces In-Reply-To, References, To, Cc, and Bcc - headers. - - --reply-to=(all|sender) - - all (default) - Replies to all addresses. + 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. + - 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. +

EXIT STATUS

+
+       This command supports the following special exit status codes
 
-              --decrypt
+       20     The requested format version is too old.
 
-                  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  the  multipart/encrypted  part  will be
-                  replaced by the decrypted content.
+       21     The requested format version is too new.
+
- See notmuch-search-terms(7) for details of the supported syntax for - <search-terms>. +

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),   not‐
+       much-tag(1)
+
- 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 format does not. +

AUTHOR

+
+       Carl Worth and many others
-

SEE ALSO

+

COPYRIGHT

-       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)
+       2009-2016, Carl Worth and many others
-

Notmuch 0.13.2

+

0.22