mirror of https://github.com/djcb/mu.git
NEWS.org: update documentation
This commit is contained in:
parent
0d9d99df99
commit
0c6719eb96
25
NEWS.org
25
NEWS.org
|
@ -5,6 +5,15 @@
|
|||
|
||||
*** mu
|
||||
|
||||
- There's a new subcommand ~mu init~ to initialize the mu database, which
|
||||
takes the ~--maildir~ and ~--my-address~ parameters that ~index~ used to take.
|
||||
These parameters are persistent so ~index~ does not need them anymore.
|
||||
|
||||
~init~ only needs to be run once or when changing these parameters.
|
||||
|
||||
- There is another new subcommand ~mu info~ to get information about the mu
|
||||
database.
|
||||
|
||||
- The contacts cache (as uses in ~mu cfind~ and mu4e contact-completion) is
|
||||
now stored as part of the Xapian database rather than as a separate file.
|
||||
|
||||
|
@ -14,21 +23,12 @@
|
|||
passing ~--muhome=~/.mu~ to various ~mu~ commands, or setting ~(setq
|
||||
mu4e-mu-home "~/.mu")~ for mu4e.
|
||||
|
||||
Otherwise, after upgrading, you may wish to delete the old location to recover
|
||||
some diskspace.
|
||||
Otherwise, after upgrading, you may wish to delete the old location to
|
||||
recover some diskspace.
|
||||
|
||||
- The ~--xbatchsize~ and ~--autoupgrade~ options for indexing are gone now; both
|
||||
are determined implicitly now.
|
||||
|
||||
- The ~--maildir~ parameter is only used when initializing the database, and
|
||||
it is stored in that database. Afterwards that its value is used; which
|
||||
means you cannot change the parameter without rebuilding and this is by
|
||||
design.
|
||||
|
||||
- The ~--my-address~ parameter is persistent as well, but can be overwritten;
|
||||
note that an updated value only applies to the messages indexed /after/ the
|
||||
change.
|
||||
|
||||
- There is a new sub-command ~mfind~, which works just like ~find~, but uses
|
||||
some mu4e-defaults ~--skip-dups~ and ~--include-related~.
|
||||
|
||||
|
@ -44,6 +44,9 @@
|
|||
of those should migrate to ~mu4e-contact-process-function~; see its
|
||||
docstring for details.
|
||||
|
||||
- ~mu4e~ no longer uses the ~mu4e-maildir~ and ~mu4e-user-mail-address-list~
|
||||
variables, instead getting the information from ~mu~ (see above).
|
||||
|
||||
- Christophe Troestler contributed support for Gnus' calender-invitation
|
||||
handling in mu4e (i.e., you should be able to accept/reject invitations
|
||||
etc.). It's very fresh code, and likely it'll be tweaked in the future.
|
||||
|
|
|
@ -154,17 +154,6 @@ the attachment dir. See Info node `(mu4e) Attachments' for details."
|
|||
:group 'mu4e
|
||||
:safe 'stringp)
|
||||
|
||||
(defcustom mu4e-user-mail-address-list `(,user-mail-address)
|
||||
"List of e-mail addresses to consider 'my email addresses'.
|
||||
I.e. addresses whose presence in an email imply that it is a
|
||||
personal message. Note that the local part (the part before '@')
|
||||
of e-mail addresses is case-sensitive, as per RFC531. In
|
||||
practice however, most of the mail systems do not distinguish
|
||||
addresses based on the case, so the emails in this list will be
|
||||
matched case-insensitively."
|
||||
:type '(repeat (string :tag "Address"))
|
||||
:group 'mu4e)
|
||||
|
||||
;; don't use the older vars anymore
|
||||
(make-obsolete-variable 'mu4e-user-mail-address-regexp
|
||||
'mu4e-user-mail-address-list "0.9.9.x")
|
||||
|
|
Loading…
Reference in New Issue