thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.9 2011-10-09T11:26:08Z 2011-10-09T11:26:08Z Jameson Graef Rollins jrollins@finestructure.net 2011-10-09T03:21:26Z urn:sha1:808fbff530319fe841f2f3c5b607d2ce3f0c424d The first test tests that the notmuch-show-refresh-view function produces the exact same output for an unmodified show buffer. This test should pass since the relevant functionality has already been applied. The second test tests show refresh for a show buffer that has been modified by navigation and message visibility toggling. Ideally refresh-view should preserve this state of the notmuch-show buffer. Unfortunately it currently does not, so this test is know to be broken and is marked as such. 2011-10-06T13:13:20Z Jameson Graef Rollins jrollins@finestructure.net 2011-06-08T19:30:08Z urn:sha1:5d21d5ea0c6d2113aab9eb7f29463b09e7eacca5 In reply, the quoted text does not need to mention that the original message had "application/pgp-signed" or "application/pgp-encrypted" parts. 2011-10-06T13:12:28Z Jameson Graef Rollins jrollins@finestructure.net 2011-06-08T19:30:06Z urn:sha1:a53422fedcfc232b6e4f4bb9cb24a622710dd5d5 There's no reason to output "Non-text part:" lines for parts that are not leaf nodes, eg. multipart/* and message/rfc822. We fix the text here to test for their absence. The next patch will fix reply accordingly. 2011-09-25T12:12:48Z David Bremner bremner@debian.org 2011-09-25T12:12:48Z urn:sha1:2697f623ae1534b669e182934ade124bd9cfd7ad Without redirection, this produced some slightly confusing output in case gdb was present. 2011-09-25T01:45:33Z David Bremner bremner@debian.org 2011-09-25T01:45:33Z urn:sha1:c468f3703efc869d62d976ba177e2d0afd7b08ad The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning. 2011-09-24T23:00:29Z Austin Clements amdragon@mit.edu 2011-01-29T16:25:56Z urn:sha1:bff30540d86c77aacbc2c133c83aa7ccee823b48 This addresses atomicity of tag synchronization, the last atomicity problems in notmuch new. Each message add or remove is wrapped in its own atomic section, so interrupting notmuch new doesn't lose progress. 2011-09-13T12:31:46Z David Bremner bremner@debian.org 2011-09-13T12:31:46Z urn:sha1:73ed66a501537fc145b6b6250513ec94c7b7e659 The documentation claims this is more robust, and it seems to work fine to switch to the _file variant. 2011-09-13T12:28:08Z David Bremner bremner@debian.org 2011-09-10T22:02:34Z urn:sha1:05a522c5fa00bd6e0dc15e8cb858cdc45db801bf This is required because test_expect_equal_failure went away. 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-01-28T18:03:24Z urn:sha1:9ade8160a6a3f6f55996d7a58dc2cd81a6df8395 This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant. 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-05-12T13:11:36Z urn:sha1:003e718020b335f329f852ff1a3da23873d2ff6e This makes test_expect_* return non-zero if the test fails, so the caller can make decisions based on this, such as setting test prerequisites.