thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.4 2010-10-29T22:53:34Z 2010-10-29T22:53:34Z Carl Worth cworth@cworth.org 2010-10-29T22:53:34Z urn:sha1:3fe90a955e21bc6825e3d9b7ffaba31e1c3d0c8b Haippily, this works just fine, but we might as well test that. 2010-10-29T22:50:42Z Carl Worth cworth@cworth.org 2010-10-29T22:49:59Z urn:sha1:dec2d57fbcaf470e97c37cd40d2953b2404f07b6 This test verifies that the bug fix in the previous commit is working. 2010-10-28T18:45:50Z Carl Worth cworth@cworth.org 2010-10-28T18:45:50Z urn:sha1:4884f5496caa2cdc8749c5eefbdc264373403f22 Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID. 2010-10-28T01:43:09Z Carl Worth cworth@cworth.org 2010-10-28T01:43:09Z urn:sha1:76f1c84e6f8caf8768e2bd10a4db2954703b19b9 The reply is primarily taken care of by "notmuch reply" which is already thoroughly tested. But a recent bug is inserting a duplicate From header in the emacs-based reply. So exercise that bug here. 2010-10-28T00:08:09Z Carl Worth cworth@cworth.org 2010-10-28T00:08:09Z urn:sha1:1aae106be5576fb75c2813bef04486f40de07d52 We test that the message we sent via (fake) SMTP is included in the mail index after a "notmuch new". This verifies that the FCC setting indeed successfully saved the sent message within the notmuch mail store. 2010-10-28T00:06:26Z Carl Worth cworth@cworth.org 2010-10-28T00:06:26Z urn:sha1:7123e63b00c2e47c70c07967c98fa1d97a1c5870 Simply setting an explicit date is cleaner than letting the current, (arbitrary), date get generated for the email message and then constantly filtering that date out of search results. 2010-10-28T00:04:48Z Carl Worth cworth@cworth.org 2010-10-27T23:58:44Z urn:sha1:36dcbdeff6de2612e70fe58bdbc6c5b979b0eafa Previously, underlying emacs code was setting this header. Now, we do the right thing and query the notmuch configuration for the default value here. 2010-10-28T00:02:44Z Carl Worth cworth@cworth.org 2010-10-27T23:35:53Z urn:sha1:a3883a7e17171381b8b495ce6efd931c8f420c90 Now that the FCC code is fixed to use the notmuch database path, we can actually enable this by default, which should be highly useful for all new users of notmuch. 2010-10-27T17:48:40Z Carl Worth cworth@cworth.org 2010-10-27T17:48:40Z urn:sha1:6c65fcd9aaf9307f6b08ab6b2c70c380ad6d3018 Which would also allow the recently added test of sending an email message with the emacs interface to be a little more honest about the From address. 2010-10-27T17:42:46Z Carl Worth cworth@cworth.org 2010-10-27T17:42:46Z urn:sha1:102c57c825d22c8f4741332f1e02e08f66f6cd2f Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).