notmuch reply: Process headers a bit more accurately.

[notmuch] / TODO

diff --git a/TODO b/TODO
index ac4e1d1826ad8c5a25b50b519999c1a1323ed121..d2a787a7d14a66ba902264fa8dbf163982a58016 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,25 +1,22 @@
-Add a talloc context as the first argument to each command in
-notmuch.c.
+Emacs interface (notmuch.el)
+----------------------------
+Make hidden components self documenting, such as:

 
 

-Write a notmuch man page.
+       [24-line citation, press 'c' to display.]

 
 

-Compile and install a libnotmuch library.
+Add support to compose a reply to the current messaage.
+
+notmuch command-line tool
+-------------------------
+Give "notmuch restore" some progress indicator. Until we get the
+Xapian bugs fixed that are making this operation slow, we really need
+to let the user know that things are still moving.

 
 Make "notmuch setup" not index all messages, but only what it can do
 in a reasonable amount of time, (then add "notmuch index" so the user
 can complete the job when convenient).
 
 
 Make "notmuch setup" not index all messages, but only what it can do
 in a reasonable amount of time, (then add "notmuch index" so the user
 can complete the job when convenient).
 

-Fix to use the *last* Message-ID header if multiple such headers are
-encountered, (I noticed this is one thing that kept me from seeing the
-same message-ID values as sup).
-
-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).
-
-Fix notmuch.c to call add_timestamp/get_timestampt with path names
+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
 and leaving stale ones behind.)
 relative to the database path. (Otherwise, moving the database to a
 new directory will result in notmuch creating new timestamp documents
 and leaving stale ones behind.)


@@ -30,8 +27,36 @@ noting how far back in the past mail has been indexed, and whether it
 needs to re-tag messages based on a theoretical "auto-tags"
 configuration file).
 
 needs to re-tag messages based on a theoretical "auto-tags"
 configuration file).
 

+Make "notmuch new" notice when a mail directory has gone more than a
+month without receiving new mail and use that to trigger the printing
+of the note that the user might want to mark the directory read-only.
+
+Also make "notmuch new" optionally able to just mark those month-old
+directories read-only on its own. (Could conflict with low-volume
+lists such as announce lists if they are setup to deliver to their own
+maildirs.)
+
+notmuch library
+---------------
+Actually compile and install a libnotmuch shared library.
+
+Fix to use the *last* Message-ID header if multiple such headers are
+encountered, (I noticed this is one thing that kept me from seeing the
+same message-ID values as sup).
+
+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).
+
+General
+-------

 Audit everything for dealing with out-of-memory (and drop xutil.c).
 
 Write a test suite.
 
 Achieve 100% test coverage with the test suite.
 Audit everything for dealing with out-of-memory (and drop xutil.c).
 
 Write a test suite.
 
 Achieve 100% test coverage with the test suite.

+
+Investigate why the notmuch database is slightly larger than the sup
+database for the same corpus of email.