cli/reply: use dedicated functions for reply to mapping

[notmuch] / NEWS

diff --git a/NEWS b/NEWS
index ab661d4df0eb143a136a38952e800e44ff45e02b..c0b865df02734ac8ddd754ed1287c9271af3ba3f 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,11 +1,50 @@
 Notmuch 0.23 (UNRELEASED)
 =========================
 
 Notmuch 0.23 (UNRELEASED)
 =========================
 

+Emacs
+-----
+
+Face customization is easier
+
+  New faces `notmuch-tag-unread`, `notmuch-tag-flagged`,
+  `notmuch-tag-deleted`, `notmuch-tag-added`,
+  `notmuch-search-flagged-face` and `notmuch-search-unread-face` are
+  now used by default. Customize `notmuch-faces` to modify them.
+

 Ruby Bindings
 -------------
 
 Add support for `notmuch_database_get_all_tags`
 
 Ruby Bindings
 -------------
 
 Add support for `notmuch_database_get_all_tags`
 

+Go Bindings
+-----------
+
+Go bindings moved to contrib
+
+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
+  both set to zero.
+  The same issue occured with sort modes.
+
+Notmuch 0.22.2 (2016-09-08)
+===========================
+
+Test Suite
+----------
+
+Silence gdb more
+
+  Have gdb write to a log file instead of stdout, hiding some more
+  (harmless) stderr chatter which causes test failures.
+
+Hardcode fingerprint in PGP/MIME tests
+
+  Make the tests more robust against changing GnuPG output formats.
+

 Notmuch 0.22.1 (2016-07-19)
 ===========================
 
 Notmuch 0.22.1 (2016-07-19)
 ===========================
 


@@ -444,13 +483,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.
 
   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
 
   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).
 
   to revert to the old behaviour (keeping the delivered message file
   and returning success even if indexing fails).