TODO: update entry on date range queries

[notmuch] / devel / TODO

diff --git a/devel/TODO b/devel/TODO
index 4dda6f4654895d5b1aa7edf0b4915bbd20d17156..e4f36c2cb8530fc0621b48fe9d05147432aae293 100644 (file)
--- a/devel/TODO
+++ b/devel/TODO
@@ -57,11 +57,6 @@ Automatically open a message when navigating to it with N or P.
 
 Change 'a' command in thread-view mode to only archive open messages.
 
 
 Change 'a' command in thread-view mode to only archive open messages.
 

-Add a binding to open all closed messages.
-
-Change the 'a'rchive command in the thread view to only archive open
-messages.
-

 Completion
 ----------
 Fix bash completion to complete multiple search options (both --first
 Completion
 ----------
 Fix bash completion to complete multiple search options (both --first


@@ -75,11 +70,6 @@ listing of duplicate messages, (distinct filenames with the same
 Message-ID). I'm not sure what the option should be named. Perhaps
 --with-duplicates ?
 
 Message-ID). I'm not sure what the option should be named. Perhaps
 --with-duplicates ?
 

-Add a -0 option to "notmuch search" so that one can safely deal with
-any filename with:
-
-       notmuch search --output=files -0 <terms> | xargs -0 <command>
-

 "notmuch setup" should use realpath() before replacing the
 configuration file. The ensures that the final target file of any
 intermediate symbolic links is what is actually replaced, (rather than
 "notmuch setup" should use realpath() before replacing the
 configuration file. The ensures that the final target file of any
 intermediate symbolic links is what is actually replaced, (rather than


@@ -92,8 +82,6 @@ and email address in the From: line. We could also then easily support
 "notmuch compose --from <something>" to support getting at alternate
 email addresses.
 
 "notmuch compose --from <something>" to support getting at alternate
 email addresses.
 

-Fix the --format=json option to not imply --entire-thread.
-

 Implement "notmuch search --exclude-threads=<search-terms>" to allow
 for excluding muted threads, (and any other negative, thread-based
 filtering that the user wants to do).
 Implement "notmuch search --exclude-threads=<search-terms>" to allow
 for excluding muted threads, (and any other negative, thread-based
 filtering that the user wants to do).


@@ -120,13 +108,6 @@ file.
 Allow configuration for filename patterns that should be ignored when
 indexing.
 
 Allow configuration for filename patterns that should be ignored when
 indexing.
 

-Replace the "notmuch part --part=id" command with "notmuch show
---part=id", (David Edmondson 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
 Fix to avoid this ugly message:
 
        (process:17197): gmime-CRITICAL **: g_mime_message_get_mime_part: assertion `GMIME_IS_MESSAGE (message)' failed


@@ -141,6 +122,14 @@ 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).
 
 original values) rather than calling GMime (which encodes) and adding
 the confusing gmime-filter-headers.c code (which decodes).
 

+Properly handle replying to multiple messages. Currently, the JSON
+reply format only supports a single message, but the default reply
+format accepts searches returning multiple messages. The expected
+behavior of replying to multiple messages is not obvious, and there
+are multiple ideas that might make sense. Some consensus needs to be
+reached on this issue, and then both reply formats should be updated
+to be consistent.
+

 notmuch library
 ---------------
 Add support for custom flag<->tag mappings. In the notmuch
 notmuch library
 ---------------
 Add support for custom flag<->tag mappings. In the notmuch


@@ -157,12 +146,13 @@ vs. tag-when-all-files-flagged (* above)).
 Add an interface to accept a "key" and a byte stream, rather than a
 filename.
 
 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
-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
+Improve syntax for date ranges queries. date:expr should be
+interpreted as date:expr..expr so that, for example, "date:2013-01-22"
+would cover the whole of the specified day (currently that's not even
+recognized as a date range expression). It might be nice to be able to
+use things like "since:2013-01-22" and "until:2013-01-22" as synonyms
+to "date:2013-01-22.." and "date:..2013-01-22", respectively. To do
+any of this we're probably going to need to break down and write our

 own parser for the query string rather than using Xapian's QueryParser
 class.
 
 own parser for the query string rather than using Xapian's QueryParser
 class.