X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=blobdiff_plain;f=TODO;h=85ef2f586e2ffa4cbd21671569043c0cb57a4cd5;hp=f8fb76dac94a289748db1011b0135c93e0edb432;hb=2fbb6d05a931b23c307aee3af05ab488c6bca425;hpb=a7f03d9f7c544cdc7662b936a390af91d199d8c7 diff --git a/TODO b/TODO index f8fb76da..85ef2f58 100644 --- a/TODO +++ b/TODO @@ -33,6 +33,51 @@ has the "muted" tag). Fix i-search to open up invisible citations as necessary. +Make '=' count from the end rather than from the beginning if more +than half-way through the buffer. + +Fix to automatically wrap long headers (for RFC compliance) before +sending. This should probably just be fixed in message-mode itself, +(but perhaps we can have a notmuch-message-mode that layers this on +top). + +Implement Fcc and use it for all messages, (whether a new composition, +a reply, or a forward). This again may require a notmuch-message-mode +that extends message-mode. + +Emacs saved-search interface +---------------------------- +Here's a proposal Carl wrote (id:87einafy4u.fsf@yoom.home.cworth.org): + + So what I'm imagining for the default notmuch view is something like + this: + + Welcome to notmuch. + + Notmuch search: _________________________________________ + + Saved searches: + + 55,342 All messages + 22 Inbox + + Recent searches: + + 1 from:"someone special" and tag:unread + 34 tag:notmuch and tag:todo + + Click (or press Enter) on any search to see the results. + Right-click (or press Space) on any recent search to save it. + + So the "saved searches" portion of the view is basically just what + notmuch-folder displays now. Above that there's an obvious place to + start a new search, (in a slightly more "web-browser-like" way than the + typical mini-buffer approach). + + All recent searches appear in the list at the bottom automatically, and + there's the documented mechanism for saving a search, (giving it a name + and having it appear above). + Portability ----------- Fix configure script to test each compiler warning we want to use. @@ -85,8 +130,32 @@ file. Allow configuration for filename patterns that should be ignored when indexing. +Replace the "notmuch part --part=id" command with "notmuch show +--part=id", (David Edmonson wants to rewrite some of "notmuch show" to +provide more MIME-structure information in its output first). + +Replace the "notmuch search-tags" command with "notmuch search +--output=tags". + +Fix to avoid this ugly message: + + (process:17197): gmime-CRITICAL **: g_mime_message_get_mime_part: assertion `GMIME_IS_MESSAGE (message)' failed + Warning: Not indexing empty mime part. + + This probably means adding a test case to generate that message, + filing an upstream bug against GMime, and then silencing the + notmuch-generated portion of the warning (so that once GMime is + fixed, this is all silent). + +Simplify notmuch-reply to simply print the headers (we have the +original values) rather than calling GMime (which encodes) and adding +the confusing gmime-filter-headers.c code (which decodes). + notmuch library --------------- +Add an interface to accept a "key" and a byte stream, rather than a +filename. + 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 @@ -106,8 +175,6 @@ 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 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. @@ -141,11 +208,43 @@ notmuch searches. Here was one proposal made in IRC: Provide a ~me Xapian synonym for all of the user's configured email addresses. +Database changes +---------------- +Store a reference term for every message-id that appears in +References. We just started doing this for newly-added documents, but +at the next convenient database-schema upgrade, we should go back and +fix old messages to be consistent. + +Start indexing the List-Id header, (and re-index this header for +existing messages at the next database upgrade). + +Start indexing the message file's directory ana make it available for +search as "folder:" (and re-index this value for existing messages at +the next database upgrade). + +Add support for the user to specify custom headers to be indexed (and +re-index these for existing messages at the next database upgrade). + +Test suite +---------- +Start testing --format=json. + +Achieve 100% test coverage with the test suite. + +Modularize test suite (to be able to run individual tests). + +Summarize test results at the end. + +Fix the insane quoting nightmare of the test suite, (and once we do +that we can actually test the implicit-phrase search feature such as +"notmuch search 'body search (phrase)'" + +Test "notmuch reply" choosing the correct email address from the +Received header when no configured email address appears in To or Cc. + 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.