alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e.texi: minor update

Browse Source
This commit is contained in:
Dirk-Jan C. Binnema
2020-04-08 11:25:51 +03:00
parent 26fb011026
commit 4584b61ea1
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
mu4e/mu4e.texi
View File

@ -3873,14 +3873,14 @@ In general, the same queries for @command{mu} and @t{mu4e} should
yield the same results. If they differ, this is usually because one of yield the same results. If they differ, this is usually because one of
the following reasons: the following reasons:
@itemize @itemize
@item different default options: @item different options:
mu4e defaults to having @t{mu4e-headers-include-related} and @t{mu4e} defaults to having @t{mu4e-headers-include-related}, and
@t{mu4e-headers-results-limit} set to 500. However, the command-line @t{mu4e-headers-results-limit} set to 500. However, the command-line
@command{mu find}'s corresponding @t{--include-related} is false, and @command{mu find}'s corresponding @t{--include-related} is false, and
there's no limit (@t{--maxnum}). there's no limit (@t{--maxnum}).
@item reverse sorting: @item reverse sorting:
The results may be different when only one @t{mu4e} and @command{mu The results may be different when @t{mu4e} and @command{mu find} do
find} do not both sort their results in the same direction. not both sort their results in the same direction.
@item shell quoting issues: @item shell quoting issues:
Depending on the shell, various shell metacharacters in search query Depending on the shell, various shell metacharacters in search query
(such as @t{*}) may be expanded by the shell before @command{mu} ever (such as @t{*}) may be expanded by the shell before @command{mu} ever