New, general features
---------------------
-### Correct handling of interruptions during "notmuch new"
+### Correct handling of interruptions during `notmuch new`
- "notmuch new" now operates as a series of small, self-consistent
+ `notmuch new` now operates as a series of small, self-consistent
transactions, so it can correctly resume after an interruption or
crash. Previously, interruption could lose existing tags, fail to
detect messages on resume, or leave the database in a state
NB! This needs a db opened in READ-WRITE mode currently, or it will crash
the python process. The is a limitation (=bug) of the underlying libnotmuch.
- Fixes where we would not throw NotmuchErrors when we should (Justus Winter)
- - Update for n_d_find_message* API changes (see above).
+ - Update for `n_d_find_message*` API changes (see above).
Ruby bindings changes
---------------------
- Wrap new library functions `notmuch_database_{begin,end}_atomic.`
- Add new exception `Notmuch::UnbalancedAtomicError.`
- - Rename destroy to destroy! according to Ruby naming conventions.
+ - Rename destroy to destroy! according to Ruby naming conventions.
- Update for `n_d_find_message*` API changes (see above).
Emacs improvements
Reply formatting cleanup
------------------------
- "notmuch reply" no longer includes notification that non-leafnode
+ `notmuch reply` no longer includes notification that non-leafnode
MIME parts are being suppressed.