From 2f7533d57ba03401c0d1f8ef2c08c888e1fb53dd Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Mon, 15 Feb 2010 20:37:17 +0200 Subject: [PATCH] * mu.1: update the dcoumentation on the maildir: parameter --- man/mu.1 | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/man/mu.1 b/man/mu.1 index ff725768..6f543221 100644 --- a/man/mu.1 +++ b/man/mu.1 @@ -153,6 +153,8 @@ starts searching at \fI\fR. By default, \fBmu\fR uses whatever the \fBMAILDIR\fR environment variable is set to; if that is not set, it tries \fI~/Maildir\fR \. In either case, the path must be \fBabsolute\fR. +Also please see the note on mixing sub-maildirs below. + .TP \fB\-r\fR, \fB\-\-reindex\fR re-index all mails, even ones that are already in the database. @@ -190,6 +192,13 @@ Also note that, before indexing is completed, searches for messages may fail, even if they have already been indexed, as some of the esssential database information will only be written in batches during the indexing process. +Furthermore, it is not recommended tot mix maildirs and sub-maildirs within +the hierarchy in the same database; for example, it's better not to index both +with \fB\-\-maildir\fR=~/MyMaildir and \fB\-\-maildir\fR=~/MyMaildir/foo, as +this may lead to unexpected results when searching with the the 'maildir:' +search parameter (see below). + + .SS A note on performance As a non-scientific benchmark, a simple test on the authors machine (a Thinkpad X61s laptop using Linux 2.6.31 and an ext3 file system) with no @@ -286,10 +295,15 @@ 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 + mu find maildir:/lists/running .fi +Note the starting '/'. If you want to match mails in the 'root' maildir, you +can do with a single '/': +.nf + mu find maildir:/ +.fi + .SS Find options