man: fix formatting of some man-page references

Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
This commit is contained in:
Jeremy Sowden 2023-08-19 11:39:17 +01:00
parent 0b62640962
commit 671a958085
3 changed files with 5 additions and 5 deletions

View File

@ -5,7 +5,7 @@ otherwise.
0. success
2. no matches found. Try a different query
11. database schema mismatch. You need to re-initialize ~mu~, see *mu-init(1*)
11. database schema mismatch. You need to re-initialize ~mu~, see *mu-init(1)*
19. failed to acquire lock. Some other program has exclusive access to the mu database
# Local Variables:

View File

@ -51,20 +51,20 @@ reach a speed of a few hundred messages per second.
*mu index* guesses the top-level Maildir to do its job; if it guesses wrong, you
can use the =--maildir= option to specify the top-level directory that should be
processed. See the *mu-index*(1) man page for more details.
processed. See the *mu-index(1)* man page for more details.
Normally, *mu index* visits all the directories under the top-level Maildir;
however, you can exclude certain directories (say, the 'trash' or 'spam'
folders) by creating a file called =.noindex= in the directory. When *mu* sees such
a file, it will exclude this directory and its sub-directories from indexing.
Also see *.noupdate* in the *mu-index*(1) manpage.
Also see *.noupdate* in the *mu-index(1)* manpage.
* SEARCHING YOUR E-MAIL
After you have indexed your mail, you can start searching it. By default, the
search results are printed on standard output. Alternatively, the output can
take the form of Maildir with symbolic links to the found messages. This enables
integration with e-mail clients; see the *mu-find*(1) man page for details, the
integration with e-mail clients; see the *mu-find(1)* man page for details, the
syntax of the search parameters and so on. Here, we just give some examples for
common cases.

View File

@ -83,7 +83,7 @@ Note that a =pure not= - e.g. searching for *not apples* is quite a 'heavy' quer
* REGULAR EXPRESSIONS AND WILDCARDS
The language supports matching basic PCRE regular expressions, see *pcre(3*).
The language supports matching basic PCRE regular expressions, see *pcre(3)*.
Regular expressions are enclosed in *//*. Some examples:
#+begin_example