X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=83010f24a93c95f88d611b532d1d0b6abc378904;hb=46b88668029f0f014c4ecf7a220b7a99a13776f3;hp=3340075b367fac4639fa33bbca0413c3d3a87d78;hpb=e9ff6d27277272084823c2d973a62921c62cf9ff;p=notmuch-wiki diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 3340075..83010f2 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -23,12 +23,12 @@ 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 + 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. @@ -37,26 +37,26 @@ --format=(default|json|sexp|headers-only) default - Includes subject and quoted message body as an RFC 2822 + 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 + 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 + 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 + 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) @@ -64,32 +64,32 @@ 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 + 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 + 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â + 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 + 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 + 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. @@ -104,8 +104,8 @@
- 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(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)@@ -117,7 +117,7 @@
- 2009-2016, Carl Worth and many others + 2009-2017, Carl Worth and many others-