update documentation
This commit is contained in:
@ -1002,11 +1002,8 @@ mu4e-compose.")
|
||||
path))
|
||||
|
||||
(defun mu4e-personal-addresses()
|
||||
"Get the user's personal addresses, if any. If none are set on the server-side,
|
||||
fall back to the obsolete `mu4e-user-mail-address-list'."
|
||||
(let ((addrs (and mu4e~server-props
|
||||
(plist-get mu4e~server-props :personal-addresses))))
|
||||
(if addrs addrs mu4e-user-mail-address-list)))
|
||||
"Get the user's personal addresses, if any."
|
||||
(when mu4e~server-props (plist-get mu4e~server-props :personal-addresses)))
|
||||
|
||||
(defun mu4e-server-version()
|
||||
"Get the server version, which should match mu4e's."
|
||||
|
||||
@ -394,9 +394,10 @@ have your e-mail messages stored in a
|
||||
@emph{maildir}@footnote{@url{https://en.wikipedia.org/wiki/Maildir};
|
||||
in this manual we use the term `maildir' for both the standard and the
|
||||
hierarchy of maildirs that store your messages} --- a specific
|
||||
directory structure with one-file-per-message. If you are already
|
||||
using a maildir, you are lucky. If not, some setup is required:
|
||||
directory structure with one-file-per-message.
|
||||
|
||||
If you are already using a maildir, you are lucky. If not, some setup
|
||||
is required:
|
||||
@itemize
|
||||
@item @emph{Using an external IMAP or POP server} --- if you are using an
|
||||
@abbr{IMAP} or @abbr{POP} server, you can use tools like @t{getmail},
|
||||
@ -410,6 +411,9 @@ a maildir as well, maybe in combination with @t{procmail}. A bit of
|
||||
googling should be able to provide you with the details.
|
||||
@end itemize
|
||||
|
||||
The maildir must be on a single file-system; and symbolic links are
|
||||
not supported.
|
||||
|
||||
@node Initializing the message store
|
||||
@section Initializing the message store
|
||||
|
||||
|
||||
Reference in New Issue
Block a user