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

mu: Default to XDG Base Directory Specification

Browse Source 
Instead of using ~/.mu, use the XDG Base Directory Specification, typically:
  ~/.cache/xapian
  ~/.cache/mu.log
  ~/.cache/parts
  ~/.config/bookmarks

Update dependencies, documentation.
This commit is contained in:
Dirk-Jan C. Binnema
2019-07-12 17:36:08 +03:00
parent 003d0a39b5
commit 632f383c38
11 changed files with 156 additions and 343 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
mu4e/mu4e.texi
View File

@ -12,7 +12,7 @@
@c %**end of header
@copying
Copyright @copyright{} 2012-2018 Dirk-Jan C. Binnema
Copyright @copyright{} 2012-2019 Dirk-Jan C. Binnema
@quotation
Permission is granted to copy, distribute and/or modify this document
@ -2637,8 +2637,9 @@ invoke those function even in that case.
the current context is also visible in the mode-line when in
headers, view or main mode.
@item You can set any kind of variable; including settings for mail servers etc.
However, settings such as @code{mu4e-maildir} and @code{mu4e-mu-home} are
not changeable after they have been set without quitting @t{mu4e} first.
However, settings such as @code{mu4e-maildir} and @code{mu4e-mu-home}
are not changeable after they have been set without quitting @t{mu4e}
first.
@item @code{leave-func} (if defined) for the context we are leaving, is invoked
before the @code{enter-func} (if defined) of the
context we are entering.
@ -3917,7 +3918,7 @@ Use @kbd{M-x mu4e-update-index}
errors like:}
@verbatim
mu: mu_store_new_writable: xapian error
'Unable to get write lock on ~/.mu/xapian: already locked
'Unable to get write lock on ~/.cache/mu/xapian: already locked
@end verbatim
@emph{What to do about this?} You get this error because the underlying
Xapian database is locked by some other process; it can be opened only once in
@ -4736,10 +4737,10 @@ log-buffer is called @t{*mu4e-log*}, and in the @ref{Main view}, @ref{Headers
view} and @ref{Message view}, there's a keybinding @key{$} that takes you
there. You can quit it by pressing @key{q}.
Logging can be a bit resource-intensive, so you may not want to leave it on
all the time. By default, the log only maintains the most recent 1200
lines. @t{mu} itself keeps a log as well, you can find this it in
@t{<MUHOME>/log/mu.log}, typically @t{~/.mu/log/mu.log}.
Logging can be a bit resource-intensive, so you may not want to leave
it on all the time. By default, the log only maintains the most recent
1200 lines. @t{mu} itself keeps a log as well, you can find it in
@t{<MUHOME>/mu.log}, on Unix typically @t{~/.cache/mu/mu.log}.
@node GNU Free Documentation License
@appendix GNU Free Documentation License