X-Git-Url: https://git.notmuchmail.org/git?a=blobdiff_plain;f=devel%2FTODO;h=eb757af5da2ab3c75099189dfc6c0de020f107bb;hb=1dd76ab9b681d6f1f59e7f076015e8f12f45f477;hp=4dda6f4654895d5b1aa7edf0b4915bbd20d17156;hpb=d43f6c00b351424e903c2f2b71c34bc5902b467e;p=notmuch

diff --git a/devel/TODO b/devel/TODO
index 4dda6f46..eb757af5 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -92,8 +92,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.
 
-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).
@@ -141,6 +139,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).
 
+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