result.) This may require removing the outer array from the current
"notmuch search --format=json" results.
-Fix '*' to work by simply calling '+' or '-' on a region consisting of
-the entire buffer, (this would avoid one race condition---while still
-leaving other race conditions---but could also potentially make '*' a
-very expensive operation).
-
Add a global keybinding table for notmuch, and then view-specific
tables that add to it.
by default, (unless the user asks explicitly for deleted messages in
the search query).
-Add keybindings for next/previous thread.
-
Add support to "mute" a thread (add a "muted" tag and then don't
display threads in searches by default where any message of the thread
has the "muted" tag).
reached on this issue, and then both reply formats should be updated
to be consistent.
+Return docid-based queries in thread search results, instead of
+message-id-based queries. These are much more compact and much faster
+to later query. This will require support from the library, both for
+retrieving docids (probably as an opaque "get a query that identifies
+this message") and for docid queries.
+
notmuch library
---------------
Add support for custom flag<->tag mappings. In the notmuch
Audit all libnotmuch entry points to ensure that all Xapian calls are
wrapped in a try/catch block.
-Fix the "count" functionality to be exact as Olly explained in IRC:
-
- ojwb> cworth: if you set the check_at_least parameter to the
- database size, get_matches_estimated() will be exact
-
Fix the threading of a message that has a References: header but no
In-Reply-To: header (see id:"87lixxnxpb.fsf@yoom.home.cworth.org").