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 Enhance '+' and '-' in the search view to operate on an entire region
12 Fix '*' to work by simply calling '+' or '-' on a region consisting of
15 Add a global keybinding table for notmuch, and then view-specific
16 tables that add to it.
18 Add a '|' binding from the search view.
20 Add support for choosing from one of the user's configured email
21 addresses for the From line.
23 Make 'notmuch-show-pipe-message have a private history.
25 Add support for a delete keybinding that adds a "deleted" tag to the
26 current message/thread and make searches not return deleted messages
27 by default, (unless the user asks explicitly for deleted messags in
30 Add support to "mute" a thread (add a "muted" tag and then don't
31 display threads in searches by default where any message of the thread
34 Fix i-search to open up invisible citations as necessary.
36 Make '=' count from the end rather than from the beginning if more
37 than half-way through the buffer.
39 Emacs saved-search interface
40 ----------------------------
41 Here's a proposal Carl wrote (id:87einafy4u.fsf@yoom.home.cworth.org):
43 So what I'm imagining for the default notmuch view is something like
48 Notmuch search: _________________________________________
57 1 from:"someone special" and tag:unread
58 34 tag:notmuch and tag:todo
60 Click (or press Enter) on any search to see the results.
61 Right-click (or press Space) on any recent search to save it.
63 So the "saved searches" portion of the view is basically just what
64 notmuch-folder displays now. Above that there's an obvious place to
65 start a new search, (in a slightly more "web-browser-like" way than the
66 typical mini-buffer approach).
68 All recent searches appear in the list at the bottom automatically, and
69 there's the documented mechanism for saving a search, (giving it a name
70 and having it appear above).
74 Fix configure script to test each compiler warning we want to use.
78 Fix bash completion to complete multiple search options (both --first
79 and *then* --max-threads), and also complete value for --sort=
80 (oldest-first or newest-first).
82 notmuch command-line tool
83 -------------------------
84 Fix the --format=json option to not imply --entire-thread.
86 Implement "notmuch search --exclude-threads=<search-terms>" to allow
87 for excluding muted threads, (and any other negative, thread-based
88 filtering that the user wants to do).
90 Fix "notmuch show" so that the UI doesn't fail to show a thread that
91 is visible in a search buffer, but happens to no longer match the
92 current search. (Perhaps add a --matching=<secondary-search-terms>
93 option (or similar) to "notmuch show".) For now, this is being worked
94 around in the emacs interface by noticing that "notmuch show" returns
95 nothing and re-rerunning the command without the extra arguments.
97 Teach "notmuch search" to return many different kinds of results. Some
100 notmuch search --output=threads # Default if no --output is given
101 notmuch search --output=messages
102 notmuch search --output=tags
103 notmuch search --output=addresses
104 notmuch search --output=terms
106 Add a "--format" option to "notmuch search", (something printf-like
107 for selecting what gets printed).
109 Add a "--count-only" (or so?) option to "notmuch search" for returning
110 the count of search results.
112 Give "notmuch restore" some progress indicator.
114 Fix "notmuch restore" to operate in a single pass much like "notmuch
115 dump" does, rather than doing N searches into the database, each
116 matching 1/N messages.
118 Add a "-f <filename>" option to select an alternate configuration
121 Allow configuration for filename patterns that should be ignored when
124 Replace the "notmuch part --part=id" command with "notmuch show
125 --part=id", (David Edmonson wants to rewrite some of "notmuch show" to
126 provide more MIME-structure information in its output first).
128 Replace the "notmuch search-tags" command with "notmuch search
133 Add an interface to accept a "key" and a byte stream, rather than a
136 Provide a sane syntax for date ranges. First, we don't want to require
137 both endpoints to be specified. For example it would be nice to be
138 able to say things like "since:2009-01-1" or "until:2009-01-1" and
139 have the other endpoint be implicit. Second we'd like to support
140 relative specifications of time such as "since:'2 months ago'". To do
141 any of this we're probably going to need to break down an write our
142 own parser for the query string rather than using Xapian's QueryParser
145 Make failure to read a file (such as a permissions problem) a warning
146 rather than an error (should be similar to the existing warning for a
149 Actually compile and install a libnotmuch shared library.
151 Fix to use the *last* Message-ID header if multiple such headers are
152 encountered, (I noticed this is one thing that kept me from seeing the
153 same message-ID values as sup).
155 Add support for configuring "virtual tags" which are a tuple of
156 (tag-name, search-specification). The database is responsible for
157 ensuring that the virtual tag is always consistent.
159 Indicate to the user if two files with the same message ID have
160 content that is actually different in some interesting way. Perhaps
161 notmuch initially sees all changes as interesting, and quickly learns
162 from the user which changes are not interesting (such as the very
163 common mailing-list footer).
165 Fix notmuch_query_count_messages to share code with
166 notmuch_query_search_messages rather than duplicating code. (And
167 consider renaming it as well.)
169 Provide a mechanism for doing automatic address completion based on
170 notmuch searches. Here was one proposal made in IRC:
172 <cworth> I guess all it would really have to be would be a way
173 to configure a series of searches to try in turn,
174 (presenting ambiguities at a given single level, and
175 advancing to the next level only if one level
176 returned no matches).
177 <cworth> So then I might have a series that looks like this:
178 <cworth> notmuch search --output=address_from tag:address_book_alias
179 <cworth> notmuch search --output=address_to tag:sent
180 <cworth> notmuch search --output=address_from
181 <cworth> I think I might like that quite a bit.
182 <cworth> And then we have a story for an address book for
185 Provide a ~me Xapian synonym for all of the user's configured email
190 Store a reference term for every message-id that appears in
191 References. We just started doing this for newly-added documents, but
192 at the next convenient database-schema upgrade, we should go back and
193 fix old messages to be consistent.
195 Start indexing the List-Id header, (and re-index this header for
196 existing messages at the next database upgrade).
198 Start indexing the message file's directory ana make it available for
199 search as "folder:" (and re-index this value for existing messages at
200 the next database upgrade).
202 Add support for the user to specify custom headers to be indexed (and
203 re-index these for existing messages at the next database upgrade).
207 Start testing --format=json.
209 Achieve 100% test coverage with the test suite.
211 Modularize test suite (to be able to run individual tests).
213 Summarize test results at the end.
215 Fix the insane quoting nightmare of the test suite, (and once we do
216 that we can actually test the implicit-phrase search feature such as
217 "notmuch search 'body search (phrase)'"
219 Test "notmuch reply" choosing the correct email address from the
220 Received header when no configured email address appears in To or Cc.
224 Audit everything for dealing with out-of-memory (and drop xutil.c).
226 Investigate why the notmuch database is slightly larger than the sup
227 database for the same corpus of email.