thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.16 2012-08-06T11:52:45Z 2012-08-06T11:52:45Z David Bremner bremner@debian.org 2012-08-04T12:55:45Z urn:sha1:19c824c3fd7be29a2257cdd530ee23074c978d63 Since notmuch dump doesn't use positional arguments anymore, it seems better to be consistent. 2012-08-06T11:52:33Z David Bremner bremner@debian.org 2012-08-04T02:23:11Z urn:sha1:760e17488e6b11299f2971cf879b109b84816d14 The syntax --output=filename is a smaller change than deleting the output argument completely, and conceivably useful e.g. when running notmuch under a debugger. 2012-08-03T23:16:45Z Austin Clements amdragon@MIT.EDU 2012-08-03T01:14:48Z urn:sha1:624d1897ce70fde8a41f2ea245db2a5e27f16ce1 Format canonicalization of JSON output is no longer necessary, so remove it. Value canonicalization (e.g., normalizing thread IDs) is still necessary, so all of the sanitization functions remain. 2012-08-03T23:14:47Z Austin Clements amdragon@MIT.EDU 2012-08-03T01:14:47Z urn:sha1:a34bb1f9fad7c547eec5c254ce8274f190491186 Previously, we used a variety of ad-hoc canonicalizations for JSON output in the test suite, but were ultimately very sensitive to JSON irrelevancies such as whitespace. This introduces a new test comparison function, test_expect_equal_json, that first pretty-prints *both* the actual and expected JSON and the compares the result. The current implementation of this simply uses Python's json.tool to perform pretty-printing (with a fallback to the identity function if parsing fails). However, since the interface it introduces is semantically high-level, we could swap in other mechanisms in the future, such as another pretty-printer or something that does not re-order object keys (if we decide that we care about that). In general, this patch does not remove the existing ad-hoc canonicalization because it does no harm. We do have to remove the newline-after-comma rule from notmuch_json_show_sanitize and filter_show_json because it results in invalid JSON that cannot be pretty-printed. Most of this patch simply replaces test_expect_equal and test_expect_equal_file with test_expect_equal_json. It changes the expected JSON in a few places where sanitizers had placed newlines after commas inside strings. 2012-06-10T23:14:56Z Austin Clements amdragon@MIT.EDU 2012-06-09T19:14:17Z urn:sha1:b88030bda6da084ef74e41f588589fd98e773ad7 Previously, notmuch new only synchronized maildir flags to tags for files with a maildir "info" part. Since messages in new/ don't have an info part, notmuch would ignore them for flag-to-tag synchronization. This patch makes notmuch consider messages in new/ to be legitimate maildir messages that simply have no maildir flags set. The most visible effect of this is that such messages now automatically get the unread tag. 2012-06-10T23:13:19Z Austin Clements amdragon@MIT.EDU 2012-06-09T19:14:14Z urn:sha1:b0d0dab22abd80d826edee7260d1c9cbfdcffd56 Currently, notmuch new only synchronizes maildir flags to tags for files that have an "info" part. However, in maildir, new mail doesn't gain the info part until it moves from new/ to cur/. Hence, even though mail in new/ doesn't have an info part, it is still a maildir message and thus has maildir flags (though none of them set). The most visible effect of not synchronizing maildir flags for messages in new/ is that newly delivered messages don't get the unread tag (unless it is assigned by some other mechanism, like new.tags). This patch does *not* modify the test for messages in cur/ that do not have an "info" part. Unlike a message in new/, a message in cur/ without an info part is no longer a maildir message, and thus shouldn't be subject to maildir flag synchronization. 2012-03-02T12:35:02Z Mark Walters markwalters1009@gmail.com 2012-03-01T22:30:41Z urn:sha1:c8cf9e92d80f960bb8231b518c6967a7aab7f260 notmuch show outputs the exclude flag so many tests using notmuch show failed. This commit adds "excluded:0" or "excluded: false" to the expected outputs. After this commit there should be no failing tests. 2012-03-01T12:28:13Z Austin Clements amdragon@MIT.EDU 2012-02-20T00:26:26Z urn:sha1:86f89385c3bc34cd91002cc057f6a615b6ab76a9 This has three ramifications: - Blank To and Cc headers are no longer output for messages. - Dates are now canonicalized for messages, which means they always have a day of the week and GMT is printed +0000 (never -0000) - Invalid From message headers are handled slightly differently, since they get parsed by GMime now instead of notmuch. 2011-12-29T21:47:21Z Austin Clements amdragon@MIT.EDU 2011-12-29T02:34:43Z urn:sha1:66ecd9063f041329d50f6ca2f9260e3b724eb868 January 5, 2001 was a Tuesday, not a Friday. Jameson fixed this exact problem for the multipart test in ec2b0a98cc, but not for generate_message itself. As Jameson pointed out in ec2b0a98cc, if we want to test date parsing, we should do it separately. 2011-06-29T22:26:45Z Austin Clements amdragon@MIT.EDU 2011-06-29T07:10:55Z urn:sha1:47afbdfb7995d703987a273bccc3a60fedc6dd08 With the fix for the mtime race, this workaround is no longer necessary.