thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.17_rc2 2013-01-29T23:17:07Z 2013-01-29T23:17:07Z David Bremner bremner@debian.org 2013-01-29T23:06:37Z urn:sha1:f021a062888b7940fe7ee049a88ae176837bcd96 Instead of checking immediately for the watched process, delay a minute, or in the case that process-attributes returns nil, for two minutes. This is intended to cope with the case that process-attributes is unimplimented, and returns always returns nil. In this case, the watchdog check is the same as the two minute limit imposed by timeout. 2012-11-15T22:03:02Z Austin Clements amdragon@MIT.EDU 2012-11-15T19:49:52Z urn:sha1:65801835ee47dc4cada82c8a3ae16e8177a7919a This matches the current behavior of the buttonizer, so it passes, but many of these cases are not what you'd want (and some of them aren't even valid Xapian queries). The next patch will fix the handling of these cases and update the test. 2012-08-29T22:06:18Z Tomi Ollila tomi.ollila@iki.fi 2012-08-05T11:13:02Z urn:sha1:3c053bf81cf75ab37b906e748ea1edcf8af4b178 When running emacs tests using emacs 23.1.1 the tests block (until timeout) when emacs function (notmuch-test-wait) is called. There is an emacs bug #2930 titled: 23.0.92; `accept-process-output' and `sleep-for' do not run sentinel It seems this is present in emacs 23.1. Calling list-processes after accept-process-output seems work around this problem; in case Emacs version is 23.1 a defadvice is activated to do just that. 2012-08-29T22:06:07Z Tomi Ollila tomi.ollila@iki.fi 2012-08-05T11:13:01Z urn:sha1:f791cc9247dfac8640c8896bad9d9c1a1e70edfc notmuch-test-wait called sleep-for in a loop to wait unconditionally 0.1 seconds while waiting for process to exit. accept-process-output returns as soon as there is any data available from process, so using it avoids unnecessary fixed delays. Both of these functions run process sentinels. 2012-07-12T23:39:18Z Austin Clements amdragon@MIT.EDU 2012-07-09T21:42:39Z urn:sha1:f94a50d80af8c2a5513e58db954dd0b1910eb4a8 This advises the search process filter to make it process one character at a time in order to test the pessimal case for incremental search output parsing. The text parser fails this test because it gets tricked into thinking a parenthetical remark in a subject is the tag list. 2012-01-26T12:35:15Z David Edmondson dme@dme.org 2012-01-26T07:19:38Z urn:sha1:2f50524e27db2ca58f6543a2c73a5719d8d7f491 The body of the test may cause the current buffer to change. Ensure that the output goes to the correct buffer by switching back before inserting it. 2012-01-26T12:35:02Z David Edmondson dme@dme.org 2012-01-26T07:19:37Z urn:sha1:c70c7f86b83601231bac94db8a6596a1d729ae24 When using `visible-buffer-substring' to examine a buffer, the text properties are not useful, so don't include them. 2012-01-25T11:26:47Z David Edmondson dme@dme.org 2012-01-24T16:14:06Z urn:sha1:f92d7dee8fcf399bda361df82187523598bb09b4 2012-01-25T11:25:44Z David Edmondson dme@dme.org 2012-01-24T16:14:05Z urn:sha1:260975e8aff635b6b99db835ee8d40ec33ee916c Add a new test function to allow simpler testing of emacs functionality. `test_emacs_expect_t' takes one argument - a lisp expression to evaluate. The test passes if the expression returns `t', otherwise it fails and the output is reported to the tester. 2012-01-22T13:18:20Z Tomi Ollila tomi.ollila@iki.fi 2012-01-13T08:17:28Z urn:sha1:a04642043fa8f071e0dbc73a204fcc91dc3c8401 emacsclient --eval '(kill-emacs)' makes emacs versions 23.1 and 23.2 ask user input from running emacs. Redefining yes-or-no-p function when kill-emacs is executed for these emacs versions in test-lib.el avoids this test problem.