From eed6c75556e18d943ac690598edceef0c4ee59d5 Mon Sep 17 00:00:00 2001 From: David Bremner Date: Fri, 9 May 2014 01:20:07 +0100 Subject: test: make test_emacs call post-command-hook The unread/read changes will use the post-command-hook. test_emacs does not call the post-command-hook. This adds a notmuch-test-progn which takes a list of commands as argument and executes them in turn but runs the post-command-hook after each one. The caller can batch operations (ie to stop post-command-hook from being interleaved) by wrapping the batch of operations inside a progn. We also explicitly run the post-command-hook before getting the output from a test; this makes sense as this will be a place the user would be seeing the information. --- test/test-lib.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/test-lib.sh') diff --git a/test/test-lib.sh b/test/test-lib.sh index 17deaaba..b9b8fe8c 100644 --- a/test/test-lib.sh +++ b/test/test-lib.sh @@ -1138,7 +1138,7 @@ test_emacs () { rm -f OUTPUT touch OUTPUT - ${TEST_EMACSCLIENT} --socket-name="$EMACS_SERVER" --eval "(progn $@)" + ${TEST_EMACSCLIENT} --socket-name="$EMACS_SERVER" --eval "(notmuch-test-progn $@)" } test_python() { -- cgit v1.2.3