thread: Removed unsed sort argument from _thread_add_matched_message

[notmuch] / TODO

diff --git a/TODO b/TODO
index 24c8e83fe961d3f847d71130973af2bf6c848c70..8312db106c849ef28684190353e8805be133ec4d 100644 (file)
--- a/TODO
+++ b/TODO
@@ -4,8 +4,6 @@ Fix the things that are causing the most pain to new users
 
 2. Allow an easy way to get tags from directory names (if the user has them)
 
 
 2. Allow an easy way to get tags from directory names (if the user has them)
 

-3. Fix Xapian defect #250 so tagging is fast.
-

 Emacs interface (notmuch.el)
 ----------------------------
 Enhance '+' and '-' in the search view to operate on an entire region
 Emacs interface (notmuch.el)
 ----------------------------
 Enhance '+' and '-' in the search view to operate on an entire region


@@ -16,14 +14,9 @@ the entire buffer.
 
 Add a global keybinding table for notmuch, and then view-specific
 tables that add to it.
 
 Add a global keybinding table for notmuch, and then view-specific
 tables that add to it.

-
-Add a command to archive all threads in a search view.

        
 Add a '|' binding from the search view.
 
        
 Add a '|' binding from the search view.
 

-When a thread has been entirely read, start out by closing all
-messages except those that matched the search terms.
-

 Add support for choosing from one of the user's configured email
 addresses for the From line.
 
 Add support for choosing from one of the user's configured email
 addresses for the From line.
 


@@ -40,6 +33,62 @@ has the "muted" tag).
 
 Fix i-search to open up invisible citations as necessary.
 
 
 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.
+
+Stop hiding the headers so much in the thread-view mode.
+
+Allow opening a message in thread-view mode by clicking on either
+line.
+
+Automatically open a message when navigating to it with N or P.
+
+Change 'a' command in thread-view mode to only archive open messages.
+
+Add a binding to open all closed messages.
+
+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.
 Portability
 -----------
 Fix configure script to test each compiler warning we want to use.


@@ -61,7 +110,9 @@ filtering that the user wants to do).
 Fix "notmuch show" so that the UI doesn't fail to show a thread that
 is visible in a search buffer, but happens to no longer match the
 current search. (Perhaps add a --matching=<secondary-search-terms>
 Fix "notmuch show" so that the UI doesn't fail to show a thread that
 is visible in a search buffer, but happens to no longer match the
 current search. (Perhaps add a --matching=<secondary-search-terms>

-option (or similar) to "notmuch show".)
+option (or similar) to "notmuch show".) For now, this is being worked
+around in the emacs interface by noticing that "notmuch show" returns
+nothing and re-rerunning the command without the extra arguments.

 
 Teach "notmuch search" to return many different kinds of results. Some
 ideas:
 
 Teach "notmuch search" to return many different kinds of results. Some
 ideas:


@@ -78,11 +129,7 @@ for selecting what gets printed).
 Add a "--count-only" (or so?) option to "notmuch search" for returning
 the count of search results.
 
 Add a "--count-only" (or so?) option to "notmuch search" for returning
 the count of search results.
 

-Add documented syntax for searching all threads/messages.
-
-Give "notmuch restore" some progress indicator. Until we get the
-Xapian bugs fixed that are making this operation slow, we really need
-to let the user know that things are still moving.
+Give "notmuch restore" some progress indicator.

 
 Fix "notmuch restore" to operate in a single pass much like "notmuch
 dump" does, rather than doing N searches into the database, each
 
 Fix "notmuch restore" to operate in a single pass much like "notmuch
 dump" does, rather than doing N searches into the database, each


@@ -91,32 +138,34 @@ matching 1/N messages.
 Add a "-f <filename>" option to select an alternate configuration
 file.
 
 Add a "-f <filename>" option to select an alternate configuration
 file.
 

-Fix notmuch.c to call add_timestamp/get_timestamp with path names
-relative to the database path. (Otherwise, moving the database to a
-new directory will result in notmuch creating new timestamp documents
-and leaving stale ones behind.)
+Allow configuration for filename patterns that should be ignored when
+indexing.

 
 

-Fix notmuch.c to use a DIR prefix for directory timestamps, (the idea
-being that it can then add other non-directory timestamps such as for
-noting how far back in the past mail has been indexed, and whether it
-needs to re-tag messages based on a theoretical "auto-tags"
-configuration file).
+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).

 
 

-Make "notmuch new" notice when a mail directory has gone more than a
-month without receiving new mail and use that to trigger the printing
-of the note that the user might want to mark the directory read-only.
+Replace the "notmuch search-tags" command with "notmuch search
+--output=tags".

 
 

-Also make "notmuch new" optionally able to just mark those month-old
-directories read-only on its own. (Could conflict with low-volume
-lists such as announce lists if they are setup to deliver to their own
-maildirs.)
+Fix to avoid this ugly message:

 
 

-Allow configuration for filename patterns that should be ignored when
-indexing.
+       (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
 ---------------
 
 notmuch library
 ---------------

-Index content from citations, please.
+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
 
 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


@@ -131,17 +180,12 @@ Make failure to read a file (such as a permissions problem) a warning
 rather than an error (should be similar to the existing warning for a
 non-mail file).
 
 rather than an error (should be similar to the existing warning for a
 non-mail file).
 

-Add support for files that are moved or deleted (which obviously need
-to be handled differently).
-

 Actually compile and install a libnotmuch shared library.
 
 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).
 
 Actually compile and install a libnotmuch shared library.
 
 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.
 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.


@@ -175,60 +219,75 @@ notmuch searches. Here was one proposal made in IRC:
 Provide a ~me Xapian synonym for all of the user's configured email
 addresses.
 
 Provide a ~me Xapian synonym for all of the user's configured email
 addresses.
 

-General
--------
-Audit everything for dealing with out-of-memory (and drop xutil.c).
+Add symbol hiding so that we don't risk leaking any private symbols
+into the shared-library interface.

 
 

-Write a test suite.
+Audit all libnotmuch entry points to ensure that all Xapian calls are
+wrapped in a try/catch block.

 
 

-Achieve 100% test coverage with the test suite.
+Search syntax
+-------------
+Implement support for "tag:*" to expand to all tags.

 
 

-Investigate why the notmuch database is slightly larger than the sup
-database for the same corpus of email.
+Fix "notmuch search to:" to be less confusing. Many users expect this
+to search for all messages with a To: header, but it instead searches
+for all messages with the word "to". If we don't provide the first
+behavior, perhaps we should exit on an error when a configured prefix
+is provided with no value?
+
+Support "*" in all cases and not just as a special case. That is, "* "
+should also work, as well as "* and tag:inbox".
+
+Implement a syntax for requesting set-theoertic operations on results
+of multiple searches. For example, I would like to do:

 
 

-Xapian
-------
-Fix defect #250
+       "tag:inbox" SET-SUBTRACT "tag:muted"

 
 

-       replace_document should make minimal changes to database file
-       http://trac.xapian.org/ticket/250
+    as well as:

 
 

-       It looks like it's going to be easy to fix. Here's the file to
-       change:
+       "tag:notmuch and <date-range>" SET-INTERSECT
+       "tag:notmuch and not (tag:merged or tag:postponed)"

 
 

-               xapian-core/backends/flint/flint_database.cc
+    See id:3wdpr282yz2.fsf@testarossa.amd.com for more details on the
+    use cases of the above.

 
 

-       And look for:
+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.

 
 

-         // FIXME - in the case where there is overlap between the new
-         // termlist and the old termlist, it would be better to compare the
-         // two lists, and make the minimum set of modifications required.
-         // This would lead to smaller changesets for replication, and
-         // probably be faster overall
+Start indexing the List-Id header, (and re-index this header for
+existing messages at the next database upgrade).

 
 

-       So I think this might be as easy as just walking over two
-       sorted lists looking for differences.
+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.

 
 

-       Note that this is in the currently default "flint" backend,
-       but the Xapian folks are probably more interested in fixing
-       the in-development "chert" backend. So the patch to get
-       upstreamed there will probably also fix:
+Achieve 100% test coverage with the test suite.

 
 

-               xapian-core/backends/chert/chert_database.cc
+Modularize test suite (to be able to run individual tests).

 
 

-       (I'm hoping the fix will be the same---an identical comment
-       exists there.)
+Summarize test results at the end.

 
 

-       Also, if you want to experiment with the chert backend,
-       compile current Xapian source and run notmuch with
-       XAPIAN_PREFER_CHERT=1. I haven't tried that yet, but there are
-       claims that a chert database can be 40% smaller than an
-       equivalent flint database.
+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)'"

 
 

-Report this bug:
+Test "notmuch reply" choosing the correct email address from the
+Received header when no configured email address appears in To or Cc.

 
 

-       "tag:foo and tag:bar and -tag:deleted" goes insane
+General
+-------
+Audit everything for dealing with out-of-memory (and drop xutil.c).

 
 

-       This seems to be triggered by a Boolean operator next to a
-       token starting with a non-word character---suddenly all the
-       Boolean operators get treated as literal tokens)
+Investigate why the notmuch database is slightly larger than the sup
+database for the same corpus of email.