vim: preserve the 'show everything' flag when finding next/prev buffer

[notmuch] / notmuch.1

diff --git a/notmuch.1 b/notmuch.1
index 2be77f992055896072578dadd8c316f78c3edb66..369ecba169e49862f5e779e01698d4b1df8b2a12 100644 (file)
--- a/notmuch.1
+++ b/notmuch.1
@@ -169,6 +169,8 @@ when sorting by
 .B newest\-first
 the threads will be sorted by the newest message in each thread.
 
 .B newest\-first
 the threads will be sorted by the newest message in each thread.
 

+.RE
+.RS 4

 By default, results will be displayed in reverse chronological order,
 (that is, the newest results will be displayed first).
 
 By default, results will be displayed in reverse chronological order,
 (that is, the newest results will be displayed first).
 


@@ -177,7 +179,7 @@ See the
 section below for details of the supported syntax for <search-terms>.
 .RE
 .TP
 section below for details of the supported syntax for <search-terms>.
 .RE
 .TP

-.BR show " <search-term>..."
+.BR show " [options...] <search-term>..."

 
 Shows all messages matching the search terms.
 
 
 Shows all messages matching the search terms.
 


@@ -187,6 +189,19 @@ message in date order). The output is not indented by default, but
 depth tags are printed so that proper indentation can be performed by
 a post-processor (such as the emacs interface to notmuch).
 
 depth tags are printed so that proper indentation can be performed by
 a post-processor (such as the emacs interface to notmuch).
 

+Supported options for
+.B show
+include
+.RS 4
+.TP 4
+.B \-\-entire\-thread
+
+By default only those messages that match the search terms will be
+displayed. With this option, all messages in the same thread as any
+matched message will be displayed.
+.RE
+
+.RS 4

 The  output format  is plain-text,  with all  text-content  MIME parts
 decoded. Various components in the output,
 .RB ( message ", " header ", " body ", " attachment ", and MIME " part ),
 The  output format  is plain-text,  with all  text-content  MIME parts
 decoded. Various components in the output,
 .RB ( message ", " header ", " body ", " attachment ", and MIME " part ),


@@ -207,13 +222,14 @@ See the
 .B "SEARCH SYNTAX"
 section below for details of the supported syntax for <search-terms>.
 .RE
 .B "SEARCH SYNTAX"
 section below for details of the supported syntax for <search-terms>.
 .RE

+.RE

 
 The
 .B reply
 command is useful for preparing a template for an email reply.
 
 The
 .B reply
 command is useful for preparing a template for an email reply.

-
-.TP
-.BR reply " <search-term>..."
+.RS 4
+.TP 4
+.BR reply " [options...] <search-term>..."

 
 Constructs a reply template for a set of messages.
 
 
 Constructs a reply template for a set of messages.
 


@@ -236,6 +252,21 @@ each line with '> ' and included in the body.
 
 The resulting message template is output to stdout.
 
 
 The resulting message template is output to stdout.
 

+Supported options for
+.B reply
+include
+.RS
+.TP 4
+.BR \-\-format= ( default | headers\-only )
+.RS
+.TP 4
+.BR default
+Includes subject and quoted message body.
+.TP
+.BR headers-only
+Only produces In-Reply-To, References, To, Cc, and Bcc headers.
+.RE
+

 See the
 .B "SEARCH SYNTAX"
 section below for details of the supported syntax for <search-terms>.
 See the
 .B "SEARCH SYNTAX"
 section below for details of the supported syntax for <search-terms>.


@@ -248,6 +279,7 @@ 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.
 .RE
 thread, replying to the entire thread allows for the reply to comment
 on issue found in multiple patches.
 .RE

+.RE

 
 The
 .B tag
 
 The
 .B tag