X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=84c06bf96abf36de4a1f2576122e03afc7372bc7;hb=33799cf96fa2cede69b6f6e545c4da16f2898b9d;hp=41320dc1383cff6107fcccd84532088b291329b6;hpb=3f2dd8baa80b5c6d15318694659eae04cdd77345;p=notmuch-wiki
diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn
index 41320dc..84c06bf 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
@@ -15,82 +15,90 @@
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.
-
- 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
+ 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
+ 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
+ Finally, the original contents of the emails are quoted by prefixing
each line with '> ' and included in the body.
The resulting message template is output to stdout.
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
+ 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.
+ 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 inâ
+ telligently.
- 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.
+ sexp 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-only
- Only produces In-Reply-To, References, To, Cc, and Bcc
- headers.
+ headers-only
+ Only produces In-Reply-To, References, To, Cc, and Bcc
+ headers.
- --format-version=N
+ --format-version=N
+ Use the specified structured output format version. This is inâ
+ tended for programs that invoke notmuch(1) internally. If omitâ
+ ted, the latest supported version will be used.
- 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)
- 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.
- 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=(false|auto|true)
+ If true, 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.
- --decrypt
+ If auto, 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 seâ
+ cret keys.
- 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 the multipart/encrypted
- part will be replaced by the decrypted content.
+ Use false to avoid even automatic decryption.
- See notmuch-search-terms(7) for details of the supported syntax for
+ Non-automatic decryption expects a functioning gpg-agent(1) to proâ
+ vide any needed credentials. Without one, the decryption will likely
+ fail.
+
+ Default: auto
+
+ 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.
@@ -105,9 +113,20 @@
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), notâ
+ much-tag(1)
+
+
+AUTHOR
+
+ Carl Worth and many others
+
+
+COPYRIGHT
+
+ 2009-2021, Carl Worth and many others
-Notmuch 0.15.2
+0.32