X-Git-Url: https://git.notmuchmail.org/git?a=blobdiff_plain;f=NEWS;h=f1d549996abc689a39cf235424bd8d6602af7cd3;hb=320f86c30a51017c2afd1b5ac02aaf2cb0affcd7;hp=12506cfa2316e567de2a92c81692fe2c31666d8f;hpb=bb390f89a1599f4767fbf7fc7cb1f01aba22b9ae;p=notmuch

diff --git a/NEWS b/NEWS
index 12506cfa..f1d54999 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,50 @@
-Notmuch 0.17~rc3 (2013-12-07)
-=============================
+Notmuch 0.18 (UNRELEASED)
+=========================
+
+Command-Line Interface
+----------------------
+
+`notmuch dump` now defaults to `batch-tag` format.
+
+  The old format is still available with `--format=sup`.
+
+`notmuch new` has a --quiet option
+
+  This option suppresses the progress and summary reports.
+
+Emacs Interface
+---------------
+
+Changed format for saved searches
+
+  The format for `notmuch-saved-searches` has changed, but old style
+  saved searches are still supported. The new style means that a saved
+  search can store the desired sort order for the search, and it can
+  store a separate query to use for generating the count notmuch
+  shows.
+
+  The variable is fully customizable and any configuration done
+  through customize should *just work*, with the additional options
+  mentioned above. For manual customization see the documentation for
+  `notmuch-saved-searches`.
+
+  IMPORTANT: a new style notmuch-saved-searches variable will break
+  previous versions of notmuch-emacs (even search will not work); to
+  fix remove the customization for notmuch-saved-searches.
+
+  If you have a custom saved search sort function (not unsorted or
+  alphabetical) then the sort function will need to be
+  modified. Replacing (car saved-search) by (notmuch-saved-search-get
+  saved-search :name) and (cdr saved-search) by
+  (notmuch-saved-search-get saved-search :query) should be sufficient.
+
+Bug fix for saved searches with newlines in them
+
+  Split lines confuse `notmuch count --batch`, so we remove embedded
+  newlines before calling notmuch count.
+
+Notmuch 0.17 (2013-12-30)
+=========================
 
 Incompatible change in SHA1 computation
 ---------------------------------------