thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.15 2012-04-08T02:06:21Z 2012-04-08T02:06:21Z Mark Walters markwalters1009@gmail.com 2012-04-07T16:10:07Z urn:sha1:6478e1bc92d60bfd85ef8259a14754e2babe150b Systematically test the exclude options for search. Also move the search existing exclude tests into the new test. There is some overlap between the two sets of tests but many of the existing ones are there because they triggered bugs in the past so I have kept them to ensure coverage. 2012-03-18T12:14:23Z Mark Walters markwalters1009@gmail.com 2012-03-14T12:26:53Z urn:sha1:1351aafac1e8c77e6ee3d2f41ac7445d0e07238d This adds three tests for --output=messages searches. One test is for the case when one exclude tag does not occur in the Xapian database. This triggers a Xapian bug in some cases and causes the whole exclusion to fail. The next commit avoids this bug. 2012-03-18T12:14:23Z Mark Walters markwalters1009@gmail.com 2012-03-14T12:26:52Z urn:sha1:fb36741bf3e81548a6f742c536f910c783756248 The tests for the exclude code in search and count use the line notmuch config set search.exclude_tags = deleted which actually sets the exclude tags to be "=" and "deleted". Remove the "=" from this line. 2012-03-02T12:31:42Z Mark Walters markwalters1009@gmail.com 2012-03-01T22:30:39Z urn:sha1:c440e597f9a32c7050fa0cc553b6166941724588 notmuch-search.c now returns all matching threads even if it the match is a search.tag_excluded message (but with a mark indicating this). Update the test to reflect this. 2012-03-02T12:25:46Z Mark Walters markwalters1009@gmail.com 2012-03-01T22:30:35Z urn:sha1:98f5b0f09a816dfe5bc206f8b76c87223437e63d The tests test the new --no-exclude option to search and count. There were no existing tests for the exclude behaviour for count so added these too. 2012-01-23T23:21:18Z Pieter Praet pieter@praet.org 2012-01-23T04:22:34Z urn:sha1:ba33a15ec3ab80b175cf54d2584aa8acd1a2dc6e Currently, the 'search.exclude_tags' option is automatically set to "deleted;spam;" if it's missing from the config file. This violates the Principle of Least Surprise, so *only* set 'search.exclude_tags' to "deleted;spam;" if we didn't find a configuration file at all. This patch is actually Austin Clements' work: id:"20120117203211.GQ16740@mit.edu" 2012-01-23T23:19:26Z Pieter Praet pieter@praet.org 2012-01-23T04:22:33Z urn:sha1:6795c62a50815786fd168536371cf6b9ed817535 Currently, the 'search.exclude_tags' option is automatically set to "deleted;spam;" if it's missing from the config file. This violates the Principle of Least Surprise, so update the tests to *only* expect the exclusion of messages which are tagged "deleted" if the 'search.exclude_tags' option is explicitly set *and* contains that tag. 2012-01-17T01:06:35Z Austin Clements amdragon@MIT.EDU 2012-01-15T00:17:34Z urn:sha1:42a907992823030f070fc395a174f779998ca6f5 This adds a "search" section to the config file and an "auto_tag_exclusions" setting in that section. The search and count commands pass tag tags from the configuration to the library. 2012-01-01T03:04:01Z David Bremner bremner@debian.org 2012-01-01T02:15:02Z urn:sha1:7da6733e890b913281afd5061cf5a648094a1eb4 One is quoted printable, the other users 8 bit encoding. The latter triggers a bug in the python bindings due to missing call to g_mime_init. The corresponding test is marked broken in this commit. 2012-01-01T02:59:58Z David Bremner bremner@debian.org 2012-01-01T02:52:45Z urn:sha1:bebf80ea6847ebf1291fdc93e919d665f0658efc This seems a bit easier to maintain, and is more accurate since lines are not joined together.