From: David Bremner Date: Tue, 17 Jan 2012 12:47:51 +0000 (-0400) Subject: Start devel directory for developer tools and documentation. X-Git-Tag: debian/0.12_rc1-1~197 X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=commitdiff_plain;h=d51b7842149dcaedd02c4e5b6ba74a5bccd926a9 Start devel directory for developer tools and documentation. We had a lot of back and forth about the name of this directory, but nothing very conclusive. In the end, I just chose "devel" just to move on. --- diff --git a/RELEASING b/RELEASING deleted file mode 100644 index 88dab04e..00000000 --- a/RELEASING +++ /dev/null @@ -1,113 +0,0 @@ -Here are the steps to follow to create a new notmuch release. - -These steps assume that a process (not described here) has already -been followed to determine the features and bug fixes to be included -in a release, and that adequate testing by the community has already -been performed. The little bit of testing performed here is a safety -check, and not a substitute for wider testing. - -OK, so the code to be released is present and committed to your git -repository. From here, there are just a few steps to release: - -1) Verify that the NEWS file is up to date. - - Read through the entry at the top of the NEWS file and see if - you are aware of any major features recently added that are - not mentioned there. If so, please add them, (and ask the - authors of the commits to update NEWS in the future). - -2) Verify that the library version in lib/Makefile.local is correct - - See the instructions there for how to increment it. - - The version should have been updated with any commits that - added API _in a non-upwardly compatible_ way, but do check - that that is the case. The command below can be useful for - inspecting header-file changes since the last release X.Y: - - git diff X.Y..HEAD -- lib/notmuch.h - - Commit this change, if any. - -3) Update the debian/libnotmuchX.symbols file - - If the library version changed at all (step 2) it probably - means that symbols have changed/been added, in which case the - debian symbols file also needs to be updated: - - dpkg-buildpackage -uc -us - dpkg-gensymbols -plibnotmuchX | patch -p0 - - Carefully review the changes to debian/libnotmuch1.symbols to - make sure there are no unexpected changes. Remove any debian - versions from symbols. - - Commit this change, if any. - -4) Upgrade the version in the file "version" - - The scheme for the release number is as follows: - - A major milestone in usability causes an increase in the major - number, yielding a two-component version with a minor number - of 0, (such as "1.0" or "2.0"). - - Otherwise, releases with changes in features cause an increase - in the minor number, yielding a two-component version, (such - as "1.1" or "1.2"). - - Finally, releases that do not change "features" but are merely - bug fixes either increase the micro number or add it (starting - at ".1" if not present). So a bug-fix release from "1.0" would - be "1.0.1" and a subsequent bug-fix release would be "1.0.2" - etc. - - When you are happy with the file 'version', run - - make update-versions - - to propagate the version to the other places needed. - - Commit these changes. - -5) Create an entry for the new release in debian/changelog - - The syntax of this file is tightly restricted, but the - available emacs mode (see the dpkg-dev-el package) helps. - The entries here will be the Debian-relevant single-line - description of changes from the NEWS entry. And the version - must match the version in the next step. - - Commit this change. - - XXX: It would be great if this step were automated as part of - release, (taking entries from NEWS and the version from the - version file, and creating a new commit, etc.) - -6) Run "make release" which will perform the following steps. - - Note: in order to really upload anything, set the make variable - REALLY_UPLOAD=yes - - * Ensure that the version consists only of digits and periods - * Ensure that version and debian/changelog have the same version - * Verify that the source tree is clean - * Compile the current notmuch code (aborting release if it fails) - * Run the notmuch test suite (aborting release if it fails) - * Check that no release exists with the current version - * Make a signed tag - * Generate a tar file from this tag - * Generate a .sha1 sum file for the tar file and GPG sign it. - * Commit a (delta for a) copy of the tar file using pristine-tar - * Tag for the debian version - * if REALLY_UPLOAD=yes - - push the signed tag to the origin - XXX FIXME push debian tag - - scp tarball to web site - * Provide some text for the release announcement (see below). - -7) Send a message to notmuch@notmuchmail.org to announce the release. - - Use the text provided from "make release" above, (if for some - reason you lose this message, "make release-message" prints - it again for you. diff --git a/TODO b/TODO deleted file mode 100644 index 4dda6f46..00000000 --- a/TODO +++ /dev/null @@ -1,285 +0,0 @@ -Fix the things that are causing the most pain to new users ----------------------------------------------------------- -1. A new import is tagging all messages as "inbox" -- total pain - -Emacs interface (notmuch.el) ----------------------------- -Add notmuch-bcc and notmuch-cc for setting default Bcc and Cc values, -(should affect the message-setup-hook). - -Switch the notmuch-search view to use "notmuch search --format=json" -to fix large classes of bugs regarding poorly-escaped output and lame -regular expressions. (The most recently found, unfixed example is the -sender's name containing ';' which causes emacs to drop a search -result.) This may require removing the outer array from the current -"notmuch search --format=json" results. - -Fix '*' to work by simply calling '+' or '-' on a region consisting of -the entire buffer, (this would avoid one race condition---while still -leaving other race conditions---but could also potentially make '*' a -very expensive operation). - -Add a global keybinding table for notmuch, and then view-specific -tables that add to it. - -Add a '|' binding from the search view. - -Add support for choosing from one of the user's configured email -addresses for the From line. - -Make 'notmuch-show-pipe-message have a private history. - -Add support for a delete keybinding that adds a "deleted" tag to the -current message/thread and make searches not return deleted messages -by default, (unless the user asks explicitly for deleted messages in -the search query). - -Add keybindings for next/previous thread. - -Add support to "mute" a thread (add a "muted" tag and then don't -display threads in searches by default where any message of the thread -has the "muted" tag). - -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). - -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. - -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 -and *then* --max-threads), and also complete value for --sort= -(oldest-first or newest-first). - -notmuch command-line tool -------------------------- -Add support to "notmuch search" and "notmuch show" to allow for -listing of duplicate messages, (distinct filenames with the same -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 | xargs -0 - -"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 -any symbolic link). - -Replace "notmuch reply" with "notmuch compose --reply ". -This would enable a plain "notmuch compose" to be used to construct an -initial message, (which would then have the properly configured name -and email address in the From: line. We could also then easily support -"notmuch compose --from " to support getting at alternate -email addresses. - -Fix the --format=json option to not imply --entire-thread. - -Implement "notmuch search --exclude-threads=" to allow -for excluding muted threads, (and any other negative, thread-based -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= -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. - -Add a "--format" option to "notmuch search", (something printf-like -for selecting what gets printed). - -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 -matching 1/N messages. - -Add a "-f " option to select an alternate configuration -file. - -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 - 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 ---------------- -Add support for custom flag<->tag mappings. In the notmuch -configuration file this could be - - [maildir] - synchronize_flags = R:replied; D*:deleted; S:~unread; - -In the library interface this could be implemented with an array of -structures to define the mapping (flag character, tag name, -inverse-sense bit (~ above), and tag-when-any-file-flagged -vs. tag-when-all-files-flagged (* above)). - -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 -own parser for the query string rather than using Xapian's QueryParser -class. - -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). - -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 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. - -Indicate to the user if two files with the same message ID have -content that is actually different in some interesting way. Perhaps -notmuch initially sees all changes as interesting, and quickly learns -from the user which changes are not interesting (such as the very -common mailing-list footer). - -Fix notmuch_query_count_messages to share code with -notmuch_query_search_messages rather than duplicating code. (And -consider renaming it as well.) - -Provide a mechanism for doing automatic address completion based on -notmuch searches. Here was one proposal made in IRC: - - I guess all it would really have to be would be a way - to configure a series of searches to try in turn, - (presenting ambiguities at a given single level, and - advancing to the next level only if one level - returned no matches). - So then I might have a series that looks like this: - notmuch search --output=address_from tag:address_book_alias - notmuch search --output=address_to tag:sent - notmuch search --output=address_from - I think I might like that quite a bit. - And then we have a story for an address book for - non-emacs users. - -Provide a ~me Xapian synonym for all of the user's configured email -addresses. - -Add symbol hiding so that we don't risk leaking any private symbols -into the shared-library interface. - -Audit all libnotmuch entry points to ensure that all Xapian calls are -wrapped in a try/catch block. - -Fix the "count" functionality to be exact as Olly explained in IRC: - - ojwb> cworth: if you set the check_at_least parameter to the - database size, get_matches_estimated() will be exact - -Fix the threading of a message that has a References: header but no -In-Reply-To: header (see id:"87lixxnxpb.fsf@yoom.home.cworth.org"). - -Search syntax -------------- -Implement support for "tag:*" to expand to all tags. - -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: - - "tag:inbox" SET-SUBTRACT "tag:muted" - - as well as: - - "tag:notmuch and " SET-INTERSECT - "tag:notmuch and not (tag:merged or tag:postponed)" - - See id:3wdpr282yz2.fsf@testarossa.amd.com for more details on the - use cases of the above. - -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. - -Start indexing the List-Id header, (and re-index this header 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). - -Save filenames for files detected as "not an email file" in the -database. This would allow for two things: 1. Optimizing "notmuch new" -to not have to look at these files again (since they are potentially -large so the detection could be potentially slow). 2. A "notmuch -search" syntax could be added to allow the user to find these files, -(and perhaps delete them or move them away as appropriate). - -Fix filesystem/notmuch-new race condition by not updating database -mtime for a directory if it is the same as the current mtime. - -Test suite ----------- -Achieve 100% test coverage with the test suite. - -General -------- -Audit everything for dealing with out-of-memory (and drop xutil.c). - -Investigate why the notmuch database is slightly larger than the sup -database for the same corpus of email. - -Makefile should print message teaching user about LD_LIBRARY_PATH (or -similar) if libdir is not set to a directory examined by ldconfig. diff --git a/devel/RELEASING b/devel/RELEASING new file mode 100644 index 00000000..88dab04e --- /dev/null +++ b/devel/RELEASING @@ -0,0 +1,113 @@ +Here are the steps to follow to create a new notmuch release. + +These steps assume that a process (not described here) has already +been followed to determine the features and bug fixes to be included +in a release, and that adequate testing by the community has already +been performed. The little bit of testing performed here is a safety +check, and not a substitute for wider testing. + +OK, so the code to be released is present and committed to your git +repository. From here, there are just a few steps to release: + +1) Verify that the NEWS file is up to date. + + Read through the entry at the top of the NEWS file and see if + you are aware of any major features recently added that are + not mentioned there. If so, please add them, (and ask the + authors of the commits to update NEWS in the future). + +2) Verify that the library version in lib/Makefile.local is correct + + See the instructions there for how to increment it. + + The version should have been updated with any commits that + added API _in a non-upwardly compatible_ way, but do check + that that is the case. The command below can be useful for + inspecting header-file changes since the last release X.Y: + + git diff X.Y..HEAD -- lib/notmuch.h + + Commit this change, if any. + +3) Update the debian/libnotmuchX.symbols file + + If the library version changed at all (step 2) it probably + means that symbols have changed/been added, in which case the + debian symbols file also needs to be updated: + + dpkg-buildpackage -uc -us + dpkg-gensymbols -plibnotmuchX | patch -p0 + + Carefully review the changes to debian/libnotmuch1.symbols to + make sure there are no unexpected changes. Remove any debian + versions from symbols. + + Commit this change, if any. + +4) Upgrade the version in the file "version" + + The scheme for the release number is as follows: + + A major milestone in usability causes an increase in the major + number, yielding a two-component version with a minor number + of 0, (such as "1.0" or "2.0"). + + Otherwise, releases with changes in features cause an increase + in the minor number, yielding a two-component version, (such + as "1.1" or "1.2"). + + Finally, releases that do not change "features" but are merely + bug fixes either increase the micro number or add it (starting + at ".1" if not present). So a bug-fix release from "1.0" would + be "1.0.1" and a subsequent bug-fix release would be "1.0.2" + etc. + + When you are happy with the file 'version', run + + make update-versions + + to propagate the version to the other places needed. + + Commit these changes. + +5) Create an entry for the new release in debian/changelog + + The syntax of this file is tightly restricted, but the + available emacs mode (see the dpkg-dev-el package) helps. + The entries here will be the Debian-relevant single-line + description of changes from the NEWS entry. And the version + must match the version in the next step. + + Commit this change. + + XXX: It would be great if this step were automated as part of + release, (taking entries from NEWS and the version from the + version file, and creating a new commit, etc.) + +6) Run "make release" which will perform the following steps. + + Note: in order to really upload anything, set the make variable + REALLY_UPLOAD=yes + + * Ensure that the version consists only of digits and periods + * Ensure that version and debian/changelog have the same version + * Verify that the source tree is clean + * Compile the current notmuch code (aborting release if it fails) + * Run the notmuch test suite (aborting release if it fails) + * Check that no release exists with the current version + * Make a signed tag + * Generate a tar file from this tag + * Generate a .sha1 sum file for the tar file and GPG sign it. + * Commit a (delta for a) copy of the tar file using pristine-tar + * Tag for the debian version + * if REALLY_UPLOAD=yes + - push the signed tag to the origin + XXX FIXME push debian tag + - scp tarball to web site + * Provide some text for the release announcement (see below). + +7) Send a message to notmuch@notmuchmail.org to announce the release. + + Use the text provided from "make release" above, (if for some + reason you lose this message, "make release-message" prints + it again for you. diff --git a/devel/TODO b/devel/TODO new file mode 100644 index 00000000..4dda6f46 --- /dev/null +++ b/devel/TODO @@ -0,0 +1,285 @@ +Fix the things that are causing the most pain to new users +---------------------------------------------------------- +1. A new import is tagging all messages as "inbox" -- total pain + +Emacs interface (notmuch.el) +---------------------------- +Add notmuch-bcc and notmuch-cc for setting default Bcc and Cc values, +(should affect the message-setup-hook). + +Switch the notmuch-search view to use "notmuch search --format=json" +to fix large classes of bugs regarding poorly-escaped output and lame +regular expressions. (The most recently found, unfixed example is the +sender's name containing ';' which causes emacs to drop a search +result.) This may require removing the outer array from the current +"notmuch search --format=json" results. + +Fix '*' to work by simply calling '+' or '-' on a region consisting of +the entire buffer, (this would avoid one race condition---while still +leaving other race conditions---but could also potentially make '*' a +very expensive operation). + +Add a global keybinding table for notmuch, and then view-specific +tables that add to it. + +Add a '|' binding from the search view. + +Add support for choosing from one of the user's configured email +addresses for the From line. + +Make 'notmuch-show-pipe-message have a private history. + +Add support for a delete keybinding that adds a "deleted" tag to the +current message/thread and make searches not return deleted messages +by default, (unless the user asks explicitly for deleted messages in +the search query). + +Add keybindings for next/previous thread. + +Add support to "mute" a thread (add a "muted" tag and then don't +display threads in searches by default where any message of the thread +has the "muted" tag). + +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). + +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. + +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 +and *then* --max-threads), and also complete value for --sort= +(oldest-first or newest-first). + +notmuch command-line tool +------------------------- +Add support to "notmuch search" and "notmuch show" to allow for +listing of duplicate messages, (distinct filenames with the same +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 | xargs -0 + +"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 +any symbolic link). + +Replace "notmuch reply" with "notmuch compose --reply ". +This would enable a plain "notmuch compose" to be used to construct an +initial message, (which would then have the properly configured name +and email address in the From: line. We could also then easily support +"notmuch compose --from " to support getting at alternate +email addresses. + +Fix the --format=json option to not imply --entire-thread. + +Implement "notmuch search --exclude-threads=" to allow +for excluding muted threads, (and any other negative, thread-based +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= +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. + +Add a "--format" option to "notmuch search", (something printf-like +for selecting what gets printed). + +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 +matching 1/N messages. + +Add a "-f " option to select an alternate configuration +file. + +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 + 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 +--------------- +Add support for custom flag<->tag mappings. In the notmuch +configuration file this could be + + [maildir] + synchronize_flags = R:replied; D*:deleted; S:~unread; + +In the library interface this could be implemented with an array of +structures to define the mapping (flag character, tag name, +inverse-sense bit (~ above), and tag-when-any-file-flagged +vs. tag-when-all-files-flagged (* above)). + +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 +own parser for the query string rather than using Xapian's QueryParser +class. + +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). + +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 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. + +Indicate to the user if two files with the same message ID have +content that is actually different in some interesting way. Perhaps +notmuch initially sees all changes as interesting, and quickly learns +from the user which changes are not interesting (such as the very +common mailing-list footer). + +Fix notmuch_query_count_messages to share code with +notmuch_query_search_messages rather than duplicating code. (And +consider renaming it as well.) + +Provide a mechanism for doing automatic address completion based on +notmuch searches. Here was one proposal made in IRC: + + I guess all it would really have to be would be a way + to configure a series of searches to try in turn, + (presenting ambiguities at a given single level, and + advancing to the next level only if one level + returned no matches). + So then I might have a series that looks like this: + notmuch search --output=address_from tag:address_book_alias + notmuch search --output=address_to tag:sent + notmuch search --output=address_from + I think I might like that quite a bit. + And then we have a story for an address book for + non-emacs users. + +Provide a ~me Xapian synonym for all of the user's configured email +addresses. + +Add symbol hiding so that we don't risk leaking any private symbols +into the shared-library interface. + +Audit all libnotmuch entry points to ensure that all Xapian calls are +wrapped in a try/catch block. + +Fix the "count" functionality to be exact as Olly explained in IRC: + + ojwb> cworth: if you set the check_at_least parameter to the + database size, get_matches_estimated() will be exact + +Fix the threading of a message that has a References: header but no +In-Reply-To: header (see id:"87lixxnxpb.fsf@yoom.home.cworth.org"). + +Search syntax +------------- +Implement support for "tag:*" to expand to all tags. + +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: + + "tag:inbox" SET-SUBTRACT "tag:muted" + + as well as: + + "tag:notmuch and " SET-INTERSECT + "tag:notmuch and not (tag:merged or tag:postponed)" + + See id:3wdpr282yz2.fsf@testarossa.amd.com for more details on the + use cases of the above. + +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. + +Start indexing the List-Id header, (and re-index this header 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). + +Save filenames for files detected as "not an email file" in the +database. This would allow for two things: 1. Optimizing "notmuch new" +to not have to look at these files again (since they are potentially +large so the detection could be potentially slow). 2. A "notmuch +search" syntax could be added to allow the user to find these files, +(and perhaps delete them or move them away as appropriate). + +Fix filesystem/notmuch-new race condition by not updating database +mtime for a directory if it is the same as the current mtime. + +Test suite +---------- +Achieve 100% test coverage with the test suite. + +General +------- +Audit everything for dealing with out-of-memory (and drop xutil.c). + +Investigate why the notmuch database is slightly larger than the sup +database for the same corpus of email. + +Makefile should print message teaching user about LD_LIBRARY_PATH (or +similar) if libdir is not set to a directory examined by ldconfig.