X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=NEWS;h=8ed8d835daeb7b92b46f91aa083168999bbd6c11;hb=853ee0b909f59c61bfc5773d0f64d357f4a59c94;hp=c0b865df02734ac8ddd754ed1287c9271af3ba3f;hpb=89c8d279480aa618bed5ef074f9166dbf818e6eb;p=notmuch diff --git a/NEWS b/NEWS index c0b865df..8ed8d835 100644 --- a/NEWS +++ b/NEWS @@ -1,6 +1,49 @@ Notmuch 0.23 (UNRELEASED) ========================= +General (Xapian 1.4+) +--------------------- + +Compiling against Xapian 1.4 enables several new features. + +Support for single argument date: queries + + `date:` is equivalent to `date:..`. + +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. + +Library +------- + +Bug fix for `notmuch_directory_set_mtime` + + Update cached mtime to match on-disk mtime. + +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 ----- @@ -11,6 +54,8 @@ Face customization is easier `notmuch-search-flagged-face` and `notmuch-search-unread-face` are now used by default. Customize `notmuch-faces` to modify them. +Omit User-Agent header by default when sending mail + Ruby Bindings ------------- @@ -26,7 +71,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.