TODO: Add some tasks, delete some tasks.

A new item from IRC discussion, (speeding up "notmuch restore"), as
well as a bug I just hit myself, (content from citations is not being
indexed).

While here, notce that several items have recently been completed ('?'
now displays documentation, not function names; we have a search
binding from notmush-show-mode; and "notmuch new" responds to SIGINT
by flushing). Finally, the item regarding optimizing chunky searching
is irrelevant since we dropped chunky searching in favor of the much
better streamed searching.
This commit is contained in:
Carl Worth 2009-12-02 17:18:51 -08:00
parent 115b7c15b8
commit 656709b5ed

22
TODO
View file

@ -8,9 +8,6 @@ Fix the things that are causing the most pain to new users
Emacs interface (notmuch.el) Emacs interface (notmuch.el)
---------------------------- ----------------------------
Make the keybindings help ('?') display the summary of each command's
documentation, not the function name.
Add a global keybinding table for notmuch, and then view-specific Add a global keybinding table for notmuch, and then view-specific
tables that add to it. tables that add to it.
@ -18,8 +15,6 @@ Add a command to archive all threads in a search view.
Add a '|' binding from the search view. Add a '|' binding from the search view.
Add a binding to run a search from notmuch-show-mode.
When a thread has been entirely read, start out by closing all When a thread has been entirely read, start out by closing all
messages except those that matched the search terms. messages except those that matched the search terms.
@ -68,6 +63,10 @@ Give "notmuch restore" some progress indicator. Until we get the
Xapian bugs fixed that are making this operation slow, we really need Xapian bugs fixed that are making this operation slow, we really need
to let the user know that things are still moving. to let the user know that things are still moving.
Fix "notmuch restore" to operate in a single pass much like "notmuch
dump" does, rather than doing N searches into the database, each
matching 1/N messages.
Add a "-f <filename>" option to select an alternate configuration Add a "-f <filename>" option to select an alternate configuration
file. file.
@ -76,10 +75,6 @@ relative to the database path. (Otherwise, moving the database to a
new directory will result in notmuch creating new timestamp documents new directory will result in notmuch creating new timestamp documents
and leaving stale ones behind.) and leaving stale ones behind.)
Ensure that "notmuch new" is sane if its first, giant indexing session
gets interrupted, (that is, ensure that any results indexed so far are
flushed).
Fix notmuch.c to use a DIR prefix for directory timestamps, (the idea Fix notmuch.c to use a DIR prefix for directory timestamps, (the idea
being that it can then add other non-directory timestamps such as for being that it can then add other non-directory timestamps such as for
noting how far back in the past mail has been indexed, and whether it noting how far back in the past mail has been indexed, and whether it
@ -100,10 +95,12 @@ indexing.
notmuch library notmuch library
--------------- ---------------
Index content from citations, please.
Provide a sane syntax for date ranges. First, we don't want to require Provide a sane syntax for date ranges. First, we don't want to require
both endpoints to be specified. For example it would be nice to be both endpoints to be specified. For example it would be nice to be
able to say things like "since:2009-01-1" or "until:2009-01-1" and able to say things like "since:2009-01-1" or "until:2009-01-1" and
have the other enpoint be implicit. Second we'de like to support have the other enpoint be implicit. Second we'd like to support
relative specifications of time such as "since:'2 months ago'". To do relative specifications of time such as "since:'2 months ago'". To do
any of this we're probably going to need to break down an write our any of this we're probably going to need to break down an write our
own parser for the query string rather than using Xapian's QueryParser own parser for the query string rather than using Xapian's QueryParser
@ -128,11 +125,6 @@ Add support for configuring "virtual tags" which are a tuple of
(tag-name, search-specification). The database is responsible for (tag-name, search-specification). The database is responsible for
ensuring that the virtual tag is always consistent. ensuring that the virtual tag is always consistent.
Think about optimizing chunked searches (max-threads > 0) to avoid
repeating work. That would be saving state from the previous chunk and
reusing it if the next search is the next chunk with the same search
string.
General General
------- -------
Audit everything for dealing with out-of-memory (and drop xutil.c). Audit everything for dealing with out-of-memory (and drop xutil.c).