From 759a88687f934a9f3f424159c9d50a51d0ecb980 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Thu, 21 Oct 2021 21:46:59 +0300 Subject: [PATCH] NEWS.org: Update --- NEWS.org | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/NEWS.org b/NEWS.org index 01096586..54625135 100644 --- a/NEWS.org +++ b/NEWS.org @@ -26,18 +26,29 @@ - Before installing, it is recommended that you *remove* any older versions of ~mu~ and especiall ~mu4e~, since they may conflict with the newere ones. - - =mu= now requires C++17 support for building (this is in preparation for code - that actually _uses_ C++17) + - =mu= now requires C++17 support for building + + - The server protocol (as used my mu4e) has seen a number of updates, to + allow for faster rendering. *** mu4e - the old mu4e-view is *gone*; only the gnus-based one remains. This allowed for removing quite a bit of old code. + - the mu4e message rendering is much faster (a factor of 3+), which + makes displaying big results snappier. This required some updates in the + headers handling and in the server protocol. + + - ~mu4e-index-updated-hook~ now fires after indexing completed, regardless of + whether anything changed (before, it fired only is something changed). In + your hook-functions (or elsewhere) you can check if anything changed using + the new variable ~mu4e-index-update-status~. + - a lot of the internals have been changed: - - =mu4e= is slowly moving from using the =~= to the more common =--= separator for - private functions; i.e., =mu4e-foo= becomes =mu4e--foo=. + - =mu4e= is slowly moving from using the =~= to the more common =--= separator + for private functions; i.e., =mu4e-foo= becomes =mu4e--foo=. - =mu4e-utils.el= had become a bit of a dumping ground for bits of code; it's gone now, with the functionality move to topic-specific files -- @@ -64,7 +75,8 @@ *** guile - the guile interface has been deprecated. It may be revamped at some point, - but will be different from the curren one. To be removed after 1.8.x + but will be different from the current one, which is to be removed after + 1.8.x * 1.6 (released, as of July 27 2021)