X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=blobdiff_plain;f=NEWS;h=0fd6d724ffec39092de582a1382bcbcee1285002;hp=edbca4cd9075698397e9fc5e5366a0d978a7866f;hb=18e720314fce5836f89b72c469e7a3d596f9ae7e;hpb=d25d33ff2d818d5a423e07b7f465add9c970dc75

diff --git a/NEWS b/NEWS
index edbca4cd..0fd6d724 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,42 @@
 Notmuch 0.23 (UNRELEASED)
 =========================
 
+General (Xapian 1.4+)
+---------------------
+
+Compiling against Xapian 1.4 enables several new features.
+
+Support for single argument date: queries
+
+  `date:<expr>` is equivalent to  `date:<expr>..<expr>`.
+
+Support for blocking opens
+
+  When opening a database notmuch by default will wait for another
+  process to release a write lock, rather than returning an error.
+
+Support for named queries
+
+  Named queries (also known as 'saved searches') can be defined with a
+  `query:name` format. The expansion of these queries is stored in the
+  database and they can be used from any notmuch client.
+
+CLI
+---
+
+Support for compile time options
+
+  A group of `built_with` keys is now supported for notmuch
+  config. Initial keys in this group are `compact`, `field_processor`,
+  and `retry_lock`.
+
+Dump/Restore support for configuration information
+
+  Any configuration information stored in the database (initially just
+  named queries) is dumped and restored. Any new information in the
+  dump format is prefixed by '#' to allow existing scripts to ignore
+  it.
+
 Emacs
 -----
 
@@ -26,7 +62,7 @@ Add support for `notmuch_threads_t` and `notmuch_thread_t`
 Fixed constant values so they are not all zero anymore.
 
   Previously, it was impossible to open writable database handles,
-  because DATABASE_MODE_READ_ONLY and DATABASE_MODE_READ_WRITE were
+  because `DATABASE_MODE_READ_ONLY` and `DATABASE_MODE_READ_WRITE` were
   both set to zero.
   The same issue occured with sort modes.
 
@@ -483,13 +519,13 @@ Stopped `notmuch dump` failing if someone writes to the database
   process already has the write lock the dump will not start, so
   script callers should still check the return value.
 
-`notmuch insert` requires succesful message indexing for success status
+`notmuch insert` requires successful message indexing for success status
 
   Previously the `notmuch insert` subcommand indicated success even if
   the message indexing failed, as long as the message was delivered to
   file system. This could have lead to delivered messages missing
   tags, etc. `notmuch insert` is now more strict, also requiring
-  succesful indexing for success status. Use the new `--keep` option
+  successful indexing for success status. Use the new `--keep` option
   to revert to the old behaviour (keeping the delivered message file
   and returning success even if indexing fails).