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

* some manpage fixes

Browse Source
This commit is contained in:
djcb
2012-05-04 17:14:52 +03:00
parent 1bbca9e1eb
commit 858c874fbd
2 changed files with 6 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
man/mu-cfind.1
View File

@ -67,13 +67,13 @@ sets the output format to the given value. The following are available:
contact was found. Anything else leads to a non-zero return value, for contact was found. Anything else leads to a non-zero return value, for
example: example:
.sh .nf
| code | meaning | | code | meaning |
|------+--------------------------------| |------+--------------------------------|
| 0 | ok | | 0 | ok |
| 1 | general error | | 1 | general error |
| 2 | no matches (for 'mu cfind') | | 2 | no matches (for 'mu cfind') |
.si .fi
.SH INTEGRATION WITH MUTT .SH INTEGRATION WITH MUTT

10
man/mu-find.1
View File

@ -1,4 +1,4 @@
.TH MU FIND 1 "April 2012" "User Manuals" .TH MU FIND 1 "May 2012" "User Manuals"
.SH NAME .SH NAME
@ -213,17 +213,13 @@ another example would be:
$ mu find date:2009-05-05/12:23..2010-06-02/17:18 $ mu find date:2009-05-05/12:23..2010-06-02/17:18
.fi .fi
An important point here is that the date matches are against local the local
time zone active the time when the mu database was filled (using \fBmu
index\fR).
\fBmu\fR also understand relative dates, in the form of a posiive number \fBmu\fR also understand relative dates, in the form of a posiive number
followed by h (hour), d (day), w (week), m (30 days) or y (365 days). Some followed by h (hour), d (day), w (week), m (30 days) or y (365 days). Some
examples will explain this: examples to explain this:
.nf .nf
5h five hours in the past 5h five hours in the past
2w one week in the past 2w two weeks in the past
3m three times 30 days in the past 3m three times 30 days in the past
1y 365 days in the past 1y 365 days in the past
.fi .fi