diff --git a/NEWS.org b/NEWS.org index f98bd89e..4c5fc8d3 100644 --- a/NEWS.org +++ b/NEWS.org @@ -3,20 +3,24 @@ * 1.12 (post 1.12.0 updates) - The 1.12 series has been opened for a fairly long time, and gained some - changes, some beyond mere bug-fixing. We decided to put off a new development - series (1.13 -> 1.14) until incompatible changes are required; for now working - in the 1.12 series seems a good way to get improvements to users more quickly. + The 1.12 series has been the stable one for a fairly long time, and gained some + changes in mean-time. Most of the changes are for big bugs, but some small new + features are available as well. We decided to put off a new development series + (1.13 -> 1.14) until incompatible changes are required; for now working in the + 1.12 series seems a good way to get improvements to users more quickly. - man documentation improvements - message composition has been reworked to avoid a number of problems user - reported - - - many small mu4e bugs fixed, usually very old ones + reported. It is now directly uses the Gnus machinery, but integrate inside + mu4e. - with 1.12.7, ~mu~ indexing is single-threaded again, to avoid cases of - database-corruption that have appeared. + database-corruption. This of course means that in *mu4e* you need to _wait_ + until indexing is ready before you can continue (*mu4e* will warn you). If you + see that warning often, perhaps your indexing is too slow, see the section + on "Speeding up indexing" in [[info:mu4e#Retrieval and indexing][Retrieval and indexing]] in the mu4e manual. + * 1.12 (released on February 24, 2024) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 4617542f..d39eaddd 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -545,16 +545,16 @@ because you are running your own mail-server, you can leave @t{mu4e} won't try to get new mail, but still re-index your messages. @subsection Speeding up indexing +@anchor{Speeding up indexing} -If you have a large number of e-mail messages in your store, -(re)indexing might take a while. The defaults for indexing are to -ensure that we always have correct, up-to-date information about your -messages, even if other programs have modified the Maildir. +If you have a large number of e-mail messages in your store, (re)indexing might +take a while. The defaults for indexing are to ensure that we always have +correct, up-to-date information about your messages, even if other programs have +modified the Maildir. -The downside of this thoroughness (which is the default) is that it is -relatively slow, something that can be noticeable with large e-mail -corpora on slow file-systems. For a faster approach, you can use the -following: +The downside of this thoroughness is that it is relatively slow, something that +can be especially noticeable with large e-mail corpora on slow file-systems. For +a faster approach, you can use the following: @lisp (setq