X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=blobdiff_plain;f=TODO;h=f8fb76dac94a289748db1011b0135c93e0edb432;hp=c5c748f65f92f6180c8ebb9ef26bf05652a17b02;hb=a7f03d9f7c544cdc7662b936a390af91d199d8c7;hpb=c690420076b5b2597311085b7cde82f64deabe88 diff --git a/TODO b/TODO index c5c748f6..f8fb76da 100644 --- a/TODO +++ b/TODO @@ -1,25 +1,151 @@ -Write a "notmuch tag" command to add/remove tags from messages -matching a search query. +Fix the things that are causing the most pain to new users +---------------------------------------------------------- +1. A new import is tagging all messages as "inbox" -- total pain -Write a "notmuch show" that displays a single thread. +2. Allow an easy way to get tags from directory names (if the user has them) + +Emacs interface (notmuch.el) +---------------------------- +Enhance '+' and '-' in the search view to operate on an entire region +if set. + +Fix '*' to work by simply calling '+' or '-' on a region consisting of +the entire buffer. + +Add a global keybinding table for notmuch, and then view-specific +tables that add to it. + +Add a '|' binding from the search view. + +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). + +Fix i-search to open up invisible citations as necessary. + +Portability +----------- +Fix configure script to test each compiler warning we want to use. + +Completion +---------- +Fix bash completion to complete multiple search options (both --first +and *then* --max-threads), and also complete value for --sort= +(oldest-first or newest-first). + +notmuch command-line tool +------------------------- +Fix the --format=json option to not imply --entire-thread. + +Implement "notmuch search --exclude-threads=" to allow +for excluding muted threads, (and any other negative, thread-based +filtering that the user wants to do). + +Fix "notmuch show" so that the UI doesn't fail to show a thread that +is visible in a search buffer, but happens to no longer match the +current search. (Perhaps add a --matching= +option (or similar) to "notmuch show".) For now, this is being worked +around in the emacs interface by noticing that "notmuch show" returns +nothing and re-rerunning the command without the extra arguments. + +Teach "notmuch search" to return many different kinds of results. Some +ideas: + + notmuch search --output=threads # Default if no --output is given + notmuch search --output=messages + notmuch search --output=tags + notmuch search --output=addresses + notmuch search --output=terms + +Add a "--format" option to "notmuch search", (something printf-like +for selecting what gets printed). + +Add a "--count-only" (or so?) option to "notmuch search" for returning +the count of search results. + +Give "notmuch restore" some progress indicator. + +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 " option to select an alternate configuration +file. + +Allow configuration for filename patterns that should be ignored when +indexing. + +notmuch library +--------------- +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 +able to say things like "since:2009-01-1" or "until:2009-01-1" and +have the other endpoint be implicit. Second we'd like to support +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 +own parser for the query string rather than using Xapian's QueryParser +class. + +Make failure to read a file (such as a permissions problem) a warning +rather than an error (should be similar to the existing warning for a +non-mail file). + +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). -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. +Add support for the user to specify custom headers to be indexed. + +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. + +Indicate to the user if two files with the same message ID have +content that is actually different in some interesting way. Perhaps +notmuch initially sees all changes as interesting, and quickly learns +from the user which changes are not interesting (such as the very +common mailing-list footer). + +Fix notmuch_query_count_messages to share code with +notmuch_query_search_messages rather than duplicating code. (And +consider renaming it as well.) + +Provide a mechanism for doing automatic address completion based on +notmuch searches. Here was one proposal made in IRC: + + I guess all it would really have to be would be a way + to configure a series of searches to try in turn, + (presenting ambiguities at a given single level, and + advancing to the next level only if one level + returned no matches). + So then I might have a series that looks like this: + notmuch search --output=address_from tag:address_book_alias + notmuch search --output=address_to tag:sent + notmuch search --output=address_from + I think I might like that quite a bit. + And then we have a story for an address book for + non-emacs users. + +Provide a ~me Xapian synonym for all of the user's configured email +addresses. + +General +------- +Audit everything for dealing with out-of-memory (and drop xutil.c). + +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.