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

* mu-find.1: updated / more precisely describe matching

Browse Source
This commit is contained in:
Dirk-Jan C. Binnema
2010-11-20 14:40:23 +02:00
parent c6021bcc57
commit 7e96b1b483
1 changed files with 38 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
man/mu-find.1
View File

@ -31,20 +31,23 @@ If you want to make your own constructions (using \fBAND\fR, \fBOR\fR,
them as a unit; for example to find mails with oranges OR mandarins in the them as a unit; for example to find mails with oranges OR mandarins in the
subject-field, you can use: subject-field, you can use:
.nf .nf
mu find 'subject:orange OR subject:mandarin' less mu find 'subject:orange OR subject:mandarin'
.fi .fi
\fBmu find\fR does not distinguish between uppercase or lowercase for search
terms.
\fBmu\fR relies on the Xapian database for its searching capabilities, so it \fBmu\fR relies on the Xapian database for its searching capabilities, so it
offers all the search functionality that Xapian offers; for all the details, see: offers all the search functionality that Xapian offers; for all the details,
see:
\fIhttp://xapian.org/docs/queryparser.html\fR \fIhttp://xapian.org/docs/queryparser.html\fR
Note that queries are logged in \fI<mu-home>/mu.log\fR. One special feature of \fBmu\fR is that is does not distinguish between
uppercase and lowercase, nor the accented or unaccented versions of
characters. All match. In general, \fBmu\fR tries to be 'eager' in matching,
as filtering out unwanted results is usually preferrable over non matching
messages.
In older versions of mu, queries were logged in \fI<mu-home>/mu.log\fR;
however, since version 0.9 mu no longer does this.
The basic way to search a message is to type some words matching it, as you The basic way to search a message is to type some words matching it, as you
would do in an internet search engine. For example, would do in an internet search engine. For example,
@ -53,11 +56,32 @@ would do in an internet search engine. For example,
mu find monkey banana mu find monkey banana
.fi .fi
will find all message that contain both 'monkey' and 'banana'. Matching is will find all messages that contain both 'monkey' and 'banana' in either body
case-insensitive and accent-insensitive; thus or subject or one of the address-fields (to/from/cc).
Note that due to the way to Xapian query parser functions, the match with
e-mail addresses may fail, because Xapian handles characters like '@', '.' (as
seen in e-mail addresses) in a special way. However, you can match those still
if you an explicit search prefix; in other words, if, for example:
.nf .nf
mu find Mönkey BÄNANA mu find foo@example.com
.fi
does not work,
.nf
mu find f:foo@example.com
.fi
might.
As mentioned, matching is case-insensitive and accent-insensitive;
thus
.nf
mu find Mönkey BÄNAÑå
.fi .fi
yields the same results as the example above. yields the same results as the example above.
@ -183,9 +207,9 @@ Thus, for example, to sort messages by date, you could specify:
$ mu find fahrrad --fields "d f s" --sortfield=date --descending $ mu find fahrrad --fields "d f s" --sortfield=date --descending
.fi .fi
Note, if you specify a sortfield, by default, they are sorted in descending Note, if you specify a sortfield, by default, messages are sorted in
order (e.g., from lowest to highest). This is usually a good choice, but for descending order (e.g., from lowest to highest). This is usually a good
dates it may be more useful to sort in the opposite direction. choice, but for dates it may be more useful to sort in the opposite direction.
.TP .TP
\fB\-\-xquery\fR \fB\-\-xquery\fR