When a thread has been entirely read, start out by closing all
messages except those that matched the search terms.
+Add support for choosing from one of the user's configured email
+addresses for the From line.
+
+Make 'notmuch-show-pipe-message have a private history.
+
+Add support for a delete keybinding that adds a "deleted" tag to the
+current message/thread and make searches not return deleted messages
+by default, (unless the user asks explicitly for deleted messags in
+the search query).
+
+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).
+
Portability
-----------
Fix configure script to test each compiler warning we want to use.
Xapian bugs fixed that are making this operation slow, we really need
to let the user know that things are still moving.
+Add a "-f <filename>" option to select an alternate configuration
+file.
+
Fix notmuch.c to call add_timestamp/get_timestamp with path names
relative to the database path. (Otherwise, moving the database to a
new directory will result in notmuch creating new timestamp documents
lists such as announce lists if they are setup to deliver to their own
maildirs.)
+Allow configuration for filename patterns that should be ignored when
+indexing.
+
notmuch library
---------------
Add support for files that are moved or deleted (which obviously need
Add support for the user to specify custom headers to be indexed.
-Add support for automatic tagging of new messages based on particular
-search criteria, (likely using an InMemory database for the new
-messages).
+Add support for configuring "virtual tags" which are a tuple of
+(tag-name, search-specification). The database is responsible for
+ensuring that the virtual tag is always consistent.
General
-------
Investigate why the notmuch database is slightly larger than the sup
database for the same corpus of email.
+
+Xapian
+------
+Fix defect #250
+
+ replace_document should make minimal changes to database file
+ http://trac.xapian.org/ticket/250
+
+ It looks like it's going to be easy to fix. Here's the file to
+ change:
+
+ xapian-core/backends/flint/flint_database.cc
+
+ And look for:
+
+ // FIXME - in the case where there is overlap between the new
+ // termlist and the old termlist, it would be better to compare the
+ // two lists, and make the minimum set of modifications required.
+ // This would lead to smaller changesets for replication, and
+ // probably be faster overall
+
+ So I think this might be as easy as just walking over two
+ sorted lists looking for differences.
+
+ Note that this is in the currently default "flint" backend,
+ but the Xapian folks are probably more interested in fixing
+ the in-development "chert" backend. So the patch to get
+ upstreamed there will probably also fix:
+
+ xapian-core/backends/chert/chert_database.cc
+
+ (I'm hoping the fix will be the same---an identical comment
+ exists there.)
+
+ Also, if you want to experiment with the chert backend,
+ compile current Xapian source and run notmuch with
+ XAPIAN_PREFER_CHERT=1. I haven't tried that yet, but there are
+ claims that a chert database can be 40% smaller than an
+ equivalent flint database.
+
+Report this bug:
+
+ "tag:foo and tag:bar and -tag:deleted" goes insane
+
+ This seems to be triggered by a Boolean operator next to a
+ token starting with a non-word character---suddenly all the
+ Boolean operators get treated as literal tokens)
projects / notmuch / blobdiff