1 Fix the things that are causing the most pain to new users
2 ----------------------------------------------------------
3 1. A new import is tagging all messages as "inbox" -- total pain
5 2. Allow an easy way to get tags from directory names (if the user has them)
7 Emacs interface (notmuch.el)
8 ----------------------------
9 Add notmuch-bcc and notmuch-cc for setting default Bcc and Cc values,
10 (should affect the message-setup-hook).
12 Switch the notmuch-search view to use "notmuch search --format=json"
13 to fix large classes of bugs regarding poorly-escaped output and lame
14 regular expressions. (The most recently found, unfixed example is the
15 sender's name containing ';' which causes emacs to drop a search
16 result.) This may require removing the outer array from the current
17 "notmuch search --format=json" results.
19 Fix '*' to work by simply calling '+' or '-' on a region consisting of
22 Add a global keybinding table for notmuch, and then view-specific
23 tables that add to it.
25 Add a '|' binding from the search view.
27 Add support for choosing from one of the user's configured email
28 addresses for the From line.
30 Make 'notmuch-show-pipe-message have a private history.
32 Add support for a delete keybinding that adds a "deleted" tag to the
33 current message/thread and make searches not return deleted messages
34 by default, (unless the user asks explicitly for deleted messags in
37 Add support to "mute" a thread (add a "muted" tag and then don't
38 display threads in searches by default where any message of the thread
41 Make '=' count from the end rather than from the beginning if more
42 than half-way through the buffer.
44 Fix to automatically wrap long headers (for RFC compliance) before
45 sending. This should probably just be fixed in message-mode itself,
46 (but perhaps we can have a notmuch-message-mode that layers this on
49 Stop hiding the headers so much in the thread-view mode.
51 Allow opening a message in thread-view mode by clicking on either
54 Automatically open a message when navigating to it with N or P.
56 Change 'a' command in thread-view mode to only archive open messages.
58 Add a binding to open all closed messages.
60 Change the 'a'rchive command in the thread view to only archive open
65 Fix bash completion to complete multiple search options (both --first
66 and *then* --max-threads), and also complete value for --sort=
67 (oldest-first or newest-first).
69 notmuch command-line tool
70 -------------------------
71 Replace "notmuch reply" with "notmuch compose --reply <search-terms>".
72 This would enable a plain "notmuch compose" to be used to construct an
73 initial message, (which would then have the properly configured name
74 and email address in the From: line. We could also then easily support
75 "notmuch compose --from <something>" to support getting at alternate
78 Fix the --format=json option to not imply --entire-thread.
80 Implement "notmuch search --exclude-threads=<search-terms>" to allow
81 for excluding muted threads, (and any other negative, thread-based
82 filtering that the user wants to do).
84 Fix "notmuch show" so that the UI doesn't fail to show a thread that
85 is visible in a search buffer, but happens to no longer match the
86 current search. (Perhaps add a --matching=<secondary-search-terms>
87 option (or similar) to "notmuch show".) For now, this is being worked
88 around in the emacs interface by noticing that "notmuch show" returns
89 nothing and re-rerunning the command without the extra arguments.
91 Add a "--format" option to "notmuch search", (something printf-like
92 for selecting what gets printed).
94 Give "notmuch restore" some progress indicator.
96 Fix "notmuch restore" to operate in a single pass much like "notmuch
97 dump" does, rather than doing N searches into the database, each
98 matching 1/N messages.
100 Add a "-f <filename>" option to select an alternate configuration
103 Allow configuration for filename patterns that should be ignored when
106 Replace the "notmuch part --part=id" command with "notmuch show
107 --part=id", (David Edmonson wants to rewrite some of "notmuch show" to
108 provide more MIME-structure information in its output first).
110 Replace the "notmuch search-tags" command with "notmuch search
113 Fix to avoid this ugly message:
115 (process:17197): gmime-CRITICAL **: g_mime_message_get_mime_part: assertion `GMIME_IS_MESSAGE (message)' failed
116 Warning: Not indexing empty mime part.
118 This probably means adding a test case to generate that message,
119 filing an upstream bug against GMime, and then silencing the
120 notmuch-generated portion of the warning (so that once GMime is
121 fixed, this is all silent).
123 Simplify notmuch-reply to simply print the headers (we have the
124 original values) rather than calling GMime (which encodes) and adding
125 the confusing gmime-filter-headers.c code (which decodes).
129 Add an interface to accept a "key" and a byte stream, rather than a
132 Provide a sane syntax for date ranges. First, we don't want to require
133 both endpoints to be specified. For example it would be nice to be
134 able to say things like "since:2009-01-1" or "until:2009-01-1" and
135 have the other endpoint be implicit. Second we'd like to support
136 relative specifications of time such as "since:'2 months ago'". To do
137 any of this we're probably going to need to break down an write our
138 own parser for the query string rather than using Xapian's QueryParser
141 Make failure to read a file (such as a permissions problem) a warning
142 rather than an error (should be similar to the existing warning for a
145 Fix to use the *last* Message-ID header if multiple such headers are
146 encountered, (I noticed this is one thing that kept me from seeing the
147 same message-ID values as sup).
149 Add support for configuring "virtual tags" which are a tuple of
150 (tag-name, search-specification). The database is responsible for
151 ensuring that the virtual tag is always consistent.
153 Indicate to the user if two files with the same message ID have
154 content that is actually different in some interesting way. Perhaps
155 notmuch initially sees all changes as interesting, and quickly learns
156 from the user which changes are not interesting (such as the very
157 common mailing-list footer).
159 Fix notmuch_query_count_messages to share code with
160 notmuch_query_search_messages rather than duplicating code. (And
161 consider renaming it as well.)
163 Provide a mechanism for doing automatic address completion based on
164 notmuch searches. Here was one proposal made in IRC:
166 <cworth> I guess all it would really have to be would be a way
167 to configure a series of searches to try in turn,
168 (presenting ambiguities at a given single level, and
169 advancing to the next level only if one level
170 returned no matches).
171 <cworth> So then I might have a series that looks like this:
172 <cworth> notmuch search --output=address_from tag:address_book_alias
173 <cworth> notmuch search --output=address_to tag:sent
174 <cworth> notmuch search --output=address_from
175 <cworth> I think I might like that quite a bit.
176 <cworth> And then we have a story for an address book for
179 Provide a ~me Xapian synonym for all of the user's configured email
182 Add symbol hiding so that we don't risk leaking any private symbols
183 into the shared-library interface.
185 Audit all libnotmuch entry points to ensure that all Xapian calls are
186 wrapped in a try/catch block.
188 Fix the "count" functionality to be exact as Olly explained in IRC:
190 ojwb> cworth: if you set the check_at_least parameter to the
191 database size, get_matches_estimated() will be exact
195 Implement support for "tag:*" to expand to all tags.
197 Fix "notmuch search to:" to be less confusing. Many users expect this
198 to search for all messages with a To: header, but it instead searches
199 for all messages with the word "to". If we don't provide the first
200 behavior, perhaps we should exit on an error when a configured prefix
201 is provided with no value?
203 Support "*" in all cases and not just as a special case. That is, "* "
204 should also work, as well as "* and tag:inbox".
206 Implement a syntax for requesting set-theoertic operations on results
207 of multiple searches. For example, I would like to do:
209 "tag:inbox" SET-SUBTRACT "tag:muted"
213 "tag:notmuch and <date-range>" SET-INTERSECT
214 "tag:notmuch and not (tag:merged or tag:postponed)"
216 See id:3wdpr282yz2.fsf@testarossa.amd.com for more details on the
217 use cases of the above.
221 Store a reference term for every message-id that appears in
222 References. We just started doing this for newly-added documents, but
223 at the next convenient database-schema upgrade, we should go back and
224 fix old messages to be consistent.
226 Start indexing the List-Id header, (and re-index this header for
227 existing messages at the next database upgrade).
229 Start indexing the message file's directory and make it available for
230 search as "folder:" (and re-index this value for existing messages at
231 the next database upgrade).
233 Add support for the user to specify custom headers to be indexed (and
234 re-index these for existing messages at the next database upgrade).
238 Achieve 100% test coverage with the test suite.
242 Audit everything for dealing with out-of-memory (and drop xutil.c).
244 Investigate why the notmuch database is slightly larger than the sup
245 database for the same corpus of email.
247 Makefile should print message teaching user about LD_LIBRARY_PATH (or
248 similar) if libdir is not set to a directory examined by ldconfig.