thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23.3 2016-11-25T00:22:12Z 2016-11-25T00:22:12Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-11-23T17:57:22Z urn:sha1:d31161c212368a592c5d92e3d181a986d49fcc20 GnuPG 2.1.16 is now injecting the full issuer fingerprint in its signatures, which makes them about 32 octets larger when ascii-armored. This change in size means that the size of the MIME parts will vary depending on the version of gpg that the user has installed. at any rate, the signature part should be non-zero (this is true for basically any MIME part), so we just test for that instead of an exact size. 2016-10-22T15:18:43Z Tomi Ollila tomi.ollila@iki.fi 2016-10-20T08:19:45Z urn:sha1:c008dd13523bb1356653fa8678cfe5d26a6feb82 Otherwise use whatever user environment has set for TERM so that there is more chance to test on users' actual environments. 2016-10-22T15:13:55Z Tomi Ollila tomi.ollila@iki.fi 2016-10-20T08:19:44Z urn:sha1:a3ee732c522947a17329704aef2a099946420f52 2016-09-24T13:10:40Z Tomi Ollila tomi.ollila@iki.fi 2016-09-24T12:43:27Z urn:sha1:b57426a43549ac5434c0f793e184f1b0b955f7e0 In case of the test script is to be relaunced under valgrind, or --tee is requested, use the $BASH shell variable to locate the command interpreter. The $SHELL variable is re-set by non-interactive shells so in case the shell uses some other shell (e.g. zsh) for interactive use these bash scripts continue to work. 2016-09-24T13:05:04Z David Bremner david@tethera.net 2016-09-13T02:24:43Z urn:sha1:5292e9b1ae60bbb66466f126463b3d6f0bf6a3b6 This is a strange corner case where the removing of the user's address from the To: header does the wrong thing. If we think it is worth (eventually) fixing, this test can serve as a reminder. 2016-09-22T11:11:42Z David Bremner david@tethera.net 2016-09-22T11:11:42Z urn:sha1:1d4812fd616dbabb11eed0f3718fa7827d69355f notmuch_status_t is an integer type, printing it as a string is a very bad idea. 2016-09-21T21:14:25Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-07-08T09:15:36Z urn:sha1:693ca8d8a80438ce1e361e7e6d22288f52a11c55 We want to be able to query the properties directly, like: notmuch count property:foo=bar which should return a count of messages where the property with key "foo" has value equal to "bar". 2016-09-21T21:14:25Z David Bremner david@tethera.net 2016-06-13T01:05:55Z urn:sha1:651da30c0941081cf730930fc1a7cac34954ca0e This somewhat mimics the config line parsing, except there can be arbitrarily many key value pairs, so one more level of looping is required. 2016-09-21T21:14:25Z David Bremner david@tethera.net 2016-06-13T01:05:54Z urn:sha1:b7345d277ec5f562000c0e740e6515c2a84f9c76 Part of providing extensibility via properties is to make sure that user data is not lost. Thus we need to be able to dump and restore properties. 2016-09-21T21:14:25Z David Bremner david@tethera.net 2016-06-13T01:05:52Z urn:sha1:58fe8fce1d1b7b86b4914a5a476ff21411c84082 This is a thin wrapper around the string map iterator API just introduced.