* mu4e.texi: document thread marking functionality

emacs/mu4e.texi

@@ -317,8 +317,8 @@ for example, when using GMail+@abbr{IMAP} (but @emph{not} with
 GMail+@abbr{POP3}), this interferes with GMail's handling of the sent messages
 folder, and you may end up with duplicate messages.
 
-For this, since @t{mu4e} 0.9.8.3, there is the variable
+Since @t{mu4e} 0.9.8.3, there is the variable
-@code{mu4e-sent-messages-behavior}, which takes a symbol. The default is
+@code{mu4e-sent-messages-behavior} for, which takes a symbol. The default is
 @code{'sent} which, as mentioned, causes the message to be copied to your
 sent-messages folder. Other possible values are @code{'trash} (so the sent
 message is copied to the trash-folder (@code{mu4e-trash-folder}), and
@@ -521,6 +521,7 @@ DEL,D        mark for immediate deletion
 m            mark for moving to another maildir folder
 u            unmark message at point
 %            mark based on a regular expression
+T,t          mark whole thread, subthread
 
 R,F,C        reply/forward/compose
 E            edit (only allowed for draft messages)
@@ -542,8 +543,9 @@ q,z          leave the headers buffer
 @end verbatim
 
 @subsection Marking messages
+@anchor{Marking messages}
 
-All mark/unmark commands support the current @emph{region} (i.e., selection)
+The mark/unmark commands support the current @emph{region} (i.e., selection)
 -- so, for example, if you the select a number of message and then press
 @key{DEL}, all selected message will be marked for deletion.
 
@@ -551,12 +553,17 @@ The two-step mark-execute sequence is similar to what @t{dired} and a number
 of other emacs-based programs do. @t{mu4e} tries to be as quick as possible
 while still trying to protect you from accidents.
 
+You can also mark all messages that match a certain regular expression with
+@key{%}. In addition you can mark all messages in the current thread (@key{T})
+or sub-thread (@key{t}).
+
 When you try to do a new search, or refresh the headers buffer while you still
 have marked messages, normally you will be asked what to do with those marks
 -- whether to @emph{apply} them before leaving, @emph{ignore} them or to
 @emph{cancel} the operation. This behavior can be influenced with the variable
 @code{`mu4e-headers-leave-behavior'} -- see its documentation.
 
+
 @subsection Actions
 
 @code{mu4e-hdrs-action} (@key{a}) lets you pick some custom action to perform
@@ -675,6 +682,7 @@ DEL,D        mark for immediate deletion
 m            mark for moving to another maildir folder
 u            unmark message at point
 %            mark based on a regular expression
+T,t          mark whole thread, subthread
 
 R,F,C        reply/forward/compose
 E            edit (only allowed for draft messages)
@@ -695,9 +703,7 @@ H            get help
 q,z          leave the message view
 @end verbatim
 
-Note that @key{x}, which means 'execute actions on marked messages' is not
+For the marking commands, please refer to @ref{Marking messages}.
-available in this view, to reduce the risk of accidents. You need to go back
-to the headers view to effectuate the actions.
 
 @subsection Opening and saving attachments
 
@@ -1546,7 +1552,11 @@ answers.
 @item @emph{How can I quickly delete/move/trash a lot of messages?} You can
 select ('mark' in emacs-speak) the messages; the actions you then take (e.g.,
 @key{DEL} for delete, @key{m} for move and @key{t} for trash) will apply to
-@emph{all} selected messages
+@emph{all} selected messages. You can also use functions like
+@code{mu4e-hdrs-mark-thread} (@key{T}), @code{mu4e-hdrs-mark-subthread}
+(@key{t}) to mark whole threads at the same time, and
+@code{mu4e-hdrs-mark-matches} (@key{%}) to mark all messages matching a
+certain regular expression.
 @item @emph{How can I use @t{BBDB}?} Currently, there is no built-in for
 address management with @t{BBDB}; instead, we recommend @ref{Maintaining an
 address-book with org-contacts} for now.
@@ -1599,11 +1609,7 @@ there (yet), and the author can use it as a todo-list.
 
 @itemize
 @item @emph{Thread handling is incomplete.} While threads are calculated and are
-visible in the headers buffer, there is no functionality to manipulate them
+visible in the headers buffer, you can now collapse/open them.
-(e.g., collapse the thread, or delete a whole thread at once). But note that
-you can manipulate a number of consecutive messages at once by selecting
-them, and then using one of the manipulation commands, such as
-@code{mu4e-mark-for-move} or @code{mu4e-mark-for-delete}.
 @item @emph{No support for crypto when reading mail}. Currently, you cannot
 conveniently read encrypted mail or check signatures. For outgoing messages,
 it should work though, using the built-in mechanisms.
@@ -1616,13 +1622,9 @@ headers.}. Yes -- don't do that.
 sent.} Same for the drafts-folder.
 @item @emph{The key-bindings are @emph{somewhat} hard-coded} That is, the main
 menu assumes the default key-bindings, as do the clicks-on-bookmarks.
-@item @emph{Attachments are not accessible in draft/sent messages}. Currently,
-attachments in saved messages are special strings, which are transformed into
-the actual attachments when sending. However, you cannot access them afterwards.
 @end itemize
 
 
-
 @node How it works
 @appendix How it works