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

* mu.1: updated man page

Browse Source
This commit is contained in:
Dirk-Jan C. Binnema
2010-02-11 20:18:50 +02:00
parent a165bb1de4
commit dda9de5573
1 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
man/mu.1
View File

@ -41,6 +41,11 @@ clients. This manpage contains examples of both.
for indexing (analyzing) the contents of your Maildirs, and storing the for indexing (analyzing) the contents of your Maildirs, and storing the
information in a database information in a database
.TP
\fBcleanup\fR
for removing messages from the database for which there is no longer a
corresponding message file in the file system
.TP .TP
\fBfind\fR \fBfind\fR
for finding messages in your database, using certain search parameters (see for finding messages in your database, using certain search parameters (see
@ -168,11 +173,10 @@ messages (using \fB\-\-maildir\fR). For this reason, it is necessary to run
format. \fBmu index\fR will issue a warning about this. format. \fBmu index\fR will issue a warning about this.
.TP .TP
\fB\-u\fR, \fB\-\-autoupgrade\fR \fB\-u\fR, \fB\-\-autoupgrade\fR automatically use \fB\-y\fR, \fB\-\-empty\fR
automatically use \fB\-y\fR, \fB\-\-empty\fR when \fBmu\fR notices that the when \fBmu\fR notices that the database version is not up-to-date. This option
database version is not up-to-date. This option is for use in cron scripts is for use in cron scripts and the like, so they won't require any user
etc., so they won't require any user interaction, even when mu introduces a interaction, even when mu introduces a new database vesion.
new database vesion.
.TP .TP
@ -273,16 +277,26 @@ search fields and their abbreviations:
from,f Message sender from,f Message sender
subject,s Message subject subject,s Message subject
to,t To: recipient to,t To: recipient
maildir,m Maildir maildir,m Maildir
msgid,i Message-ID msgid,i Message-ID
.fi .fi
The Maildir field describes the directory path starting \fBafter\fR the
Maildir-base path, and before the \fI/cur/\fR or \fI/new/\fR part. So for
example, if there's a message with the file name
\fI~/Maildir/lists/running/cur/1234.213:2,\fR, you could find it (and all the
other messages in the same maildir) with:
.nf
mu find maildir:lists/running
.fi
.SS Find options .SS Find options
The \fBfind\fR-command has various options that influence the way \fBmu\fR The \fBfind\fR-command has various options that influence the way \fBmu\fR
displays the results. If you don't specify anything, the defaults are displays the results. If you don't specify anything, the defaults are
\fI\-\-fields="d f s"\fR, \fI\-\-sortfield=date\fR and \fI\-\-descending\fR. \fI\-\-fields="d f s"\fR, \fI\-\-sortfield=date\fR and \fI\-\-descending\fR.
.TP .TP
\fB\-f\fR, \fB\-\-fields\fR=\fI<fields>\fR \fB\-f\fR, \fB\-\-fields\fR=\fI<fields>\fR
@ -303,7 +317,7 @@ search parameters:
.nf .nf
t \fBt\fRo: recipient t \fBt\fRo: recipient
c \fBcfRc: (Carbon-Copy) recipient c \fBc\fRc: (Carbon-Copy) recipient
d Sent \fBd\fRate of the message d Sent \fBd\fRate of the message
f Message sender (\fBf\fRrom:) f Message sender (\fBf\fRrom:)
g Message flags (fla\fBg\fRs) g Message flags (fla\fBg\fRs)