mirror of https://github.com/djcb/mu.git
* index.html: updates for the mu homepage
This commit is contained in:
parent
9f43230160
commit
6a62a52015
|
@ -47,29 +47,28 @@ a.menu:hover {color: #ff0000; text-decoration: underline; }
|
||||||
|
|
||||||
<h2><a name="welcome">welcome to mu</a></h2>
|
<h2><a name="welcome">welcome to mu</a></h2>
|
||||||
|
|
||||||
<p>E-mail is the 'flow' in the work flow of many people. Consequently,
|
<p>For many people, e-mail is the 'flow' in their work-flow. One one spends
|
||||||
one spends a <em>lot</em> of time searching for old e-mails, to dig up
|
a <em>lot</em> of time searching for old e-mails, to dig up some important
|
||||||
some important piece of information. With people having tens of
|
piece of information. With people having tens of thousands of e-mails (or
|
||||||
thousands of e-mails (or more), this is becoming harder and
|
more), this is becoming harder and harder. How to find that one message in the
|
||||||
harder. How to find that one e-mail in an evergrowing haystack?
|
evergrowing information haystack?
|
||||||
|
|
||||||
<p>Enter <strong>mu</strong>. 'mu' is a set of command-line tools for
|
<p>Enter <strong>mu</strong>. 'mu' is a set of command-line tools for
|
||||||
Linux/Unix that enable you to quickly find the e-mails you are looking
|
Linux/Unix that enable you to quickly find the e-mails you are looking for,
|
||||||
for, assuming that you store your e-mails in Maildirs (e-mail
|
assuming that you store your e-mails in Maildirs (e-mail directories).
|
||||||
directories).
|
|
||||||
|
|
||||||
<h3>how does it work?</h3>
|
<h3>how does it work?</h3>
|
||||||
|
|
||||||
<p>First there is <tt>mu index</tt> which fills a database with
|
<p>First, you need to <i>index</i> your messages. Indexing means filling a
|
||||||
information about all your e-mails; this may take a couple of minutes
|
database with information about your e-mails; this may take a couple of
|
||||||
the first time you do it, but after that it's a lot faster.
|
minutes the first time you do it, but after that it's a lot
|
||||||
|
faster. <tt>mu</tt> indexes your mail with the <tt>index</tt> command:
|
||||||
<pre>
|
<pre>
|
||||||
$ mu index
|
$ mu index
|
||||||
</pre>
|
</pre>
|
||||||
It tries to pick reasonable defaults, but you can of course specify
|
It tries to pick reasonable defaults, but you can specify your own options as
|
||||||
your own options. You can run <tt>mu index</tt> periodically to keep
|
well. You could run <tt>mu index</tt> periodically to keep your database
|
||||||
your database up-to-date.
|
up-to-date. Or you could trigger it after new mails has arrived.
|
||||||
|
|
||||||
<p>After building the database, it's easy to search for messages. For example:
|
<p>After building the database, it's easy to search for messages. For example:
|
||||||
<ul>
|
<ul>
|
||||||
|
|
Loading…
Reference in New Issue