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

~/.mu -> ~/.cache/mu

Browse Source
This commit is contained in:
Dominik Schrempf
2020-04-19 13:02:48 +02:00
parent 06e63d9f09
commit ccbd81f6ef
7 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
man/mu-index.1
View File

@ -169,9 +169,9 @@ dominated by operations in the Xapian database now.
.SH FILES
\fBmu\fR stores logs of its operations and queries in \fI<muhome>/mu.log\fR
(by default, this is \fI~/.mu/mu.log\fR). Upon startup, \fBmu\fR checks the
(by default, this is \fI~/.cache/mu/mu.log\fR). Upon startup, \fBmu\fR checks the
size of this log file. If it exceeds 1 MB, it will be moved to
\fI~/.mu/mu.log.old\fR, overwriting any existing file of that name, and start
\fI~/.cache/mu/mu.log.old\fR, overwriting any existing file of that name, and start
with an empty log file. This scheme allows for continued use of \fBmu\fR
without the need for any manual maintenance of log files.

2
man/mu.1
View File

@ -137,7 +137,7 @@ to \fI~/.mu\fR, which now requires \fI\-\-muhome=~/.mu\fR.
\fB\-d\fR, \fB\-\-debug\fR
makes \fBmu\fR generate extra debug information,
useful for debugging the program itself. By default, debug information goes to
the log file, \fI~/.mu/log/mu.log\fR. It can safely be deleted when \fBmu\fR is
the log file, \fI~/.cache/mu/mu.log\fR. It can safely be deleted when \fBmu\fR is
not running. When running with \fB--debug\fR option, the log file can grow
rather quickly. See the note on logging below.