mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-12-22 01:14:53 +01:00
man: Update notmuch-reply man page for JSON format.
This commit is contained in:
parent
5abc9c1097
commit
71855b72f7
1 changed files with 8 additions and 2 deletions
|
@ -37,12 +37,17 @@ Supported options for
|
|||
include
|
||||
.RS
|
||||
.TP 4
|
||||
.BR \-\-format= ( default | headers\-only )
|
||||
.BR \-\-format= ( default | json | headers\-only )
|
||||
.RS
|
||||
.TP 4
|
||||
.BR default
|
||||
Includes subject and quoted message body.
|
||||
.TP
|
||||
.BR json
|
||||
Produces JSON 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.
|
||||
.TP
|
||||
.BR headers\-only
|
||||
Only produces In\-Reply\-To, References, To, Cc, and Bcc headers.
|
||||
.RE
|
||||
|
@ -73,7 +78,8 @@ 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 issue found in multiple patches.
|
||||
on issues found in multiple patches. The default format supports
|
||||
replying to multiple messages at once, but the JSON format does not.
|
||||
.RE
|
||||
.RE
|
||||
|
||||
|
|
Loading…
Reference in a new issue