1 [[!meta date="2011-10-01"]]
3 Notmuch 0.9 (2011-10-01)
4 ========================
9 ### Correct handling of interruptions during `notmuch new`
11 `notmuch new` now operates as a series of small, self-consistent
12 transactions, so it can correctly resume after an interruption or
13 crash. Previously, interruption could lose existing tags, fail to
14 detect messages on resume, or leave the database in a state
15 temporarily or permanently inconsistent with the mail store.
22 `notmuch_database_begin_atomic` and `notmuch_database_end_atomic`
23 allow multiple database operations to be performed atomically.
25 `notmuch_database_find_message_by_filename` does exactly what it says.
29 `notmuch_database_find_message` (and `n_d_f_m_by_filename`) now return
30 a status indicator and uses an output parameter for the
31 message. This change required changing the SONAME of libnotmuch to
34 Python bindings changes
35 -----------------------
37 - Re-encode python unicode objects to utf-8 before passing back to
39 - Support `Database().begin_atomic()/end_atomic()`
40 - Support `Database().find_message_by_filename()`
41 NB! This needs a db opened in READ-WRITE mode currently, or it will crash
42 the python process. The is a limitation (=bug) of the underlying libnotmuch.
43 - Fixes where we would not throw NotmuchErrors when we should (Justus Winter)
44 - Update for `n_d_find_message*` API changes (see above).
49 - Wrap new library functions `notmuch_database_{begin,end}_atomic.`
50 - Add new exception `Notmuch::UnbalancedAtomicError.`
51 - Rename destroy to destroy! according to Ruby naming conventions.
52 - Update for `n_d_find_message*` API changes (see above).
57 * Add gpg callback to crypto sigstatus buttons to retrieve/refresh
59 * Add `notmuch-show-refresh-view` function (and corresponding binding)
60 to refresh the view of a notmuch-show buffer.
62 Reply formatting cleanup
63 ------------------------
65 `notmuch reply` no longer includes notification that non-leafnode
66 MIME parts are being suppressed.