-Write a "notmuch tag" command to add/remove tags from messages
-matching a search query.
+Add back full-text indexing, (see last version of
+notmuch-index-message.c in the archives).
+
+Investigate using just a simple hash while constructing threads during
+"notmuch setup", then just writing out to Xapian in one shot at the
+end without haivng to rewrite documents nor look anything up.
+
+Rename notmuch_thread_results_t and notmuch_message_results_t to
+notmuch_threads_t and notmuch_messages_t respectively.
+
+Add a talloc context as the first argument to each command in
+notmuch.c.
Write a "notmuch show" that displays a single thread.
encountered, (I noticed this is one thing that kept me from seeing the
same message-ID values as sup).
-Think about this race condition:
-
- A client executes "notmuch search"
- Then executes "notmuch show" on a thread
- While user is reading, new mail is added to database for the thread
- Client asks for the thread to be archived.
-
- The bug here is that email that was never read will be
- archived. That's bad. With the command set above, the user can
- avoid the problem by just not running "notmuch new" while reading
- mail, but the same problems exists with the API. One possible
- solution would be to store an additional timestamp with each mail
- document for the time it was added to the database. Then searches
- could return a timestamp, and the client could pass that same
- timestamp back to the archive command to not modify any messages
- with a timestamp newer than what's passed.
+Audit everything for dealing with out-of-memory (and drop xutil.c).
+
+Write a test suite.
+
+Achieve 100% test coverage with the test suite.
projects / notmuch / blobdiff