mu4e.texi: update documentation

Use the new toggles.

mu4e/mu4e.texi

@@ -950,10 +950,7 @@ M-left,\     previous query
 M-right      next query
 
 O            change sort order
-P            toggle threading
+P            toggle search property
-Q            toggle full-search
-V            toggle skip-duplicates
-W            toggle include-related
 
 marking
 -------
@@ -1037,14 +1034,14 @@ The header field used for sorting is indicated by ``@t{V}'' or
 variable @code{mu4e-use-fancy-chars}}, indicating the sort order
 (descending or ascending, respectively).
 
-You can change the sort order by clicking the corresponding column with
+You can change the sort order by clicking the corresponding column with the
-the mouse, or with @kbd{M-x mu4e-headers-change-sorting} (@key{O}); note
+mouse, or with @kbd{M-x mu4e-headers-change-sorting} (@key{O}); note that not
-that not all fields can be used for sorting. You can toggle threading
+all fields can be used for sorting. You can toggle threading on/off through
-on/off using @kbd{M-x mu4e-headers-toggle-threading} or @key{P}. For
+@kbd{M-x mu4e-headers-toggle-property} or @key{Pt}. For both of these functions,
-both of these functions, unless you provide a prefix argument
+unless you provide a prefix argument (@key{C-u}), the current search is updated
-(@key{C-u}), the current search is updated immediately using the new
+immediately using the new parameters. You can toggle full-search
-parameters. You can toggle full-search (@ref{Searching}) using @kbd{M-x
+(@ref{Searching}) through @kbd{M-x mu4e-headers-toggle-property} as well; or
-mu4e-headers-toggle-full-search} or @key{Q}.
+@key{Pf}.
 
 Note that with threading enabled, the sorting is exclusively by date,
 regardless of the column clicked.
@@ -1274,6 +1271,9 @@ b            search bookmark
 B            edit bookmark before search
 j            jump to maildir
 
+O            change sort order
+P            toggle search property
+
 M-left       previous query
 M-right      next query
 
@@ -1728,12 +1728,11 @@ order for this to work properly you need to pass your address to
 executing a query for messages that happen to have the property of being in a
 certain folder (maildir).
 
-Normally, queries return up to @code{mu4e-headers-results-limit} (default:
+Normally, queries return up to @code{mu4e-headers-results-limit} (default: 500)
-500) results. That is usually more than enough, and makes things significantly
+results. That is usually more than enough, and makes things significantly
 faster. Sometimes, however, you may want to show @emph{all} results; you can
-enable this with @kbd{M-x mu4e-headers-toggle-full-search}, or by customizing
+enable this with @kbd{M-x mu4e-headers-toggle-property}, or by customizing the
-the variable @code{mu4e-headers-full-search}. This applies to all search
+variable @code{mu4e-headers-full-search}. This applies to all search commands.
-commands.
 
 You can also influence the sort order and whether threads are shown or not;
 see @ref{Sorting and threading}.
@@ -3798,10 +3797,12 @@ completion.
 Set @code{mu4e-cache-maildir-list} to @code{t} (make sure to read
 its docstring).
 
-@subsection How can I hide messages from the search results?
+@subsection How can I hide certain messages from the search results?
-See the variable @code{mu4e-headers-hide-predicate}.
+See the variables @code{mu4e-headers-hide-predicate} and
+@code{mu4e-headers-hide-enabled}. The latter can be toggled through
+@code{mu4e-headers-toggle-property}.
 
-For example, to filter out GMail's spam, set it to:
+For example, to filter out GMail's spam folder, set it to:
 @lisp
 (setq mu4e-headers-hide-predicate
      (lambda (msg)