thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.22 2016-04-12T23:14:43Z 2016-04-12T23:14:43Z David Bremner david@tethera.net 2016-04-09T01:49:49Z urn:sha1:deb4e5567c42afe834d83868b9337277256a0d66 This is mainly for the test suite. We already expect the tests to be run in the same environment as configure was run, at least to get the name of the python interpreter. So we are not really imposing a new restriction. 2016-01-29T21:45:46Z David Bremner david@tethera.net 2015-08-16T17:41:13Z urn:sha1:a530a1706aa96cd20d7053bd91ecc5bfbee17756 The test is pretty much cut and paste from the PGP/MIME version, with obvious updates taken from notmuch output. This also requires setting up gpgsm infrastucture. 2016-01-29T21:45:46Z David Bremner david@tethera.net 2015-08-16T17:41:12Z urn:sha1:ef30770dfa0fbef4e91ec90d6ce21b5a55b15375 Test the ability of notmuch-mua-mail to send S/MIME signed (and encrypted) messages; this really relies on existing functionality in message-mode. The generated keys and messages will later be useful for testing the notmuch CLI. 2016-01-27T02:50:58Z David Bremner david@tethera.net 2016-01-23T12:49:26Z urn:sha1:12534d5c4b02498173b0c63d063ae0a3c845b957 test_C and notmuch_search_files_sanitize were giving different output on the same path, which is not technically wrong, but slightly confusing. 2015-12-30T15:28:30Z Michal Sojka sojkam1@fel.cvut.cz 2015-12-29T08:52:17Z urn:sha1:a9fec12a0804113596c927d45f627f8b874aab67 ALTERNATE_EDITOR causes emacsclient to run an alternate editor if the emacs server is not ready. This can collide with intended functionality in test-lib.sh. If the ALTERNATE_EDITOR is set but empty, emacsclient runs emacs daemon and tries to connect to it. When this happens the emacs run by test-lib.sh fails to start the server and the subsequent attempts to use the server fail because the daemon started by emacsclient does not know about notmuch-test-progn. This leads to test suite failure due to time out on any emacs test. 2015-08-13T21:52:51Z Austin Clements aclements@csail.mit.edu 2014-10-13T06:20:02Z urn:sha1:98ee460eaa98f1428aecf03dd39fcf314e6f62c0 This exposes the committed database revision to library users along with a UUID that can be used to detect when revision numbers are no longer comparable (e.g., because the database has been replaced). 2015-08-07T19:56:39Z Tomi Ollila tomi.ollila@iki.fi 2015-08-06T09:13:36Z urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741 The files (test) scripts source (with builtin command `.`) provides information which the scripts depend, and without the `source` to succeed allowing script to continue may lead to dangerous situations (e.g. rm -rf "${undefined_variable}"/*). At the end of all source (.) lines construct ' || exit 1' was added; In our case the script script will exit if it cannot find (or read) the file to be sourced. Additionally script would also exits if the last command of the sourced file exited nonzero. 2015-08-07T19:18:59Z David Bremner david@tethera.net 2015-08-01T09:44:56Z urn:sha1:d0553ad524f241ba42f685cba6745c8a3a9ba20a Previously we globally modified these variables, which tended to cause problems for people using message-mode, but not notmuch-mua-mail, to send mail. User visible changes: - Calling notmuch-fcc-header-setup is no longer optional. OTOH, it seems to do the right thing if notmuch-fcc-dirs is set to nil. - The Fcc header is visible during message composition - The name in the mode line is changed, and no longer matches exactly the menu label. - Previously notmuch-mua-send-and-exit was never called. Either we misunderstood define-mail-user-agent, or it had a bug. So there was no difference if the user called message-send-and-exit directly. Now there will be. - User bindings to C-c C-c and C-c C-s in message-mode-map are overridden. The user can override them in notmuch-message-mode-map, but then they're on their own for Fcc handling. 2015-08-04T07:19:18Z David Bremner david@tethera.net 2015-08-02T06:40:55Z urn:sha1:23d86773b9e1b8111921af94f7f14ea0867eaee2 The configure script chooses "python" if both python and python{2,3} exist exists, so this could change the version of python used to run the test suite. The checking for ${NOTMUCH_PYTHON} in the test suite is arguably over-engineering, since the configure step will fail if it can't find it. 2015-06-14T16:00:52Z David Bremner david@tethera.net 2015-06-01T07:09:02Z urn:sha1:d9567dd5b5b6f9e4c5bcc45776a08c5578f1650d This is pretty much a line by line translation of the existing python tests, with two new tests for the count API.