-
v1.12.12bed7e6bd · ·
stable version 1.12.12 New stable version. Some small fixes and doc updates; big new thing are the new SCM bindings (under scm/), which will replace the long-deprecated old bindings (under guile/). Overall: - In 'mu init', --my-address has been renamed into --personal-address for consistency. The old name still works. Mu4e: - Emacs bookmarks can be now also be created for mu4e queries; see the mu4e-emacs-bookmark-policy defcustom - Support dash when completing maildirs - Add defcustom for mu4e-compose-jump-to-reasonable-place, so it can be overridden, e.g. in compose hooks. - In mu4e, make indexing snappier when there no new messages SCM: - Experimental new Guile bindings under scm/, including a reference manual and unit tests. -
v1.12.10998a6448 · ·
Stable release 1.12.10 Some bugfixes, documentation improvements minor features; some internal rework. - add --format=json2 for `mu find`, which produces a bit more 'idiomatic' json - close notifications once done - more informative mu4e-analyze-last-query (include all parameters) - Make mu4e-maildir-shortcut and mu4e-bookmarks understand a property :hide-if-no-unread, which hides the maildir/bookmark from the main-view if there are no unread messages which the corresponding query.
-
v1.12.960340c52 · ·
Stable version 1.12.9 - Some fixes and documentation improvements, as well as some new features: - new command mu4e-analyze-last-query which shows information about how the server interpreted the last query; this can be useful if you don't get the result you expected. - When you ask for bookmarks or maildirs through mu4e-search-bookmark or mu4e-search-maildir, unread counts are displayed in the (default) completions UI next to the maildir or bookmark. If you don't want to see these counts, set mu4e-hide-short-counts to non-nil. - experimental: a "transient" menu, which provides easy access to some common (and some not so common) functions in mu4e. For now, you can enable this with: (require 'mu4e-transient) (global-set-key (kbd "C-c m") #'mu4e-transient-menu) This requires you to have the "transient" package, which means Emacs 28 or later or alternatively you can install it manually. As stated, it's experimental and will be change / expanded over time, but already I find it quite useful. - gnus mailing-list management commands such as gnus-mailing-list-subscribe, gnus-mailing-list-unsubscribe now also work in mu4e. Also available through the transient menu. - The mu server uses PCRE-compatible regexps (for addresses), which are not necessarily compatible with Emacs regular expressions. However, mu4e can now automatically translate; this depends on the ~pcre2el~ package which the user should install when using regular expression-addresses. - the cleanup phase after indexing has been sped up significantly - updated documentation; man-pages and mu4e reference manual -
v1.12.88c0f136a · ·
Release 1.12.8 New stable release, with bug fixes and a few featurerettes: - documentation improvements - removal of the old threading option and cleanup - 'lazy' indexing is even lazier (faster) - make references (the References:/In-reply-to: headers) searchable (with "references:" or "ref:" - add new combination-field "related:" to search by msgid: _or_ references: In mu4e (see docstrings for details): - new command 'mu4e-view-jump-to-mime-part', to jump to some mime part by number. - new variable mu4e-trash-without-flag, if set to non-nil, "trashing" a message will _not_ add the "T" flag.
-
v1.12.70f16b22b · ·
stable release 1.12.7 - many documentation fixes - mu4e: fix some mu4e-compose-captured-message corner case (#2745) - mu4e: fix 'user-agent' field (#2750) - few tiny tweaks However biggest change is regarding mu's "threadiness" with respect to Xapian. For a while, some people, ran into Xapian database corruptions (I've seen it very occasionally, some people more often); issue #2706. I don't know the precise cause, but it seems to be related to using threads with Xapian; the mu code in this area hasn't changed much, so perhaps newer Xapian versions are less forgiving? Anyway, this is all speculation. Database corruption with mu is not catastrophic, since you can always rebuild it without data-loss; however, it's still annoying and we'd obviously want to avoid that. 1.12.7 includes a change to make the database access single-threaded again, which seems to help for this problem. We're really returning to the behavior some older versions of mu, with the difference that now you'll get a message in mu4e Cannot handle command while indexing, please retry later. Hope that doesn't inconvenience people too much. Might have a deeper look into when I have some more time and not in the 1.12.x series. (there's a meson flag to keep the existing behavior, see the commit message).
-
v1.12.6f1923fff · ·
Stable release 1.12.6 - improved documentation: man-pages, mu4e reference manual, README - new function `mu4e-save-message`, to save a copy of the message at point - reduce logging a bit - fix mu4e-compose-pre-hook which broke with the 1.12.5 changes - fix bookmark support (bookmark-make-record-function)