notmuch/test/T190-multipart.sh, branch 0.32

cli/show: emit new whole-message crypto status output

2019-05-26T11:20:23Z

This allows MUAs that don't want to think about per-mime-part cryptographic status to have a simple high-level overview of the message's cryptographic state. Sensibly structured encrypted and/or signed messages will work fine with this. The only requirement for the simplest encryption + signing is that the message have all of its encryption and signing protection (the "cryptographic envelope") in a contiguous set of MIME layers at the very outside of the message itself. This is because messages with some subparts signed or encrypted, but with other subparts with no cryptographic protection is very difficult to reason about, and even harder for the user to make sense of or work with. For further characterization of the Cryptographic Envelope and some of the usability tradeoffs, see here: https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html#cryptographic-envelope

gmime-cleanup: tests should only care about gmime 3

2019-05-03T09:55:44Z

note that "notmuch-show for message with invalid From" is still broken in T310-emacs.sh. It would be good to debug what's going on there and try to get it fixed! signed-off-by: Daniel Kahn Gillmor

cli: notmuch show support for --include-html with --format=text

2018-11-24T13:12:30Z

cli: notmuch show support for --body=false with --format=text

2018-11-24T13:11:42Z

Fix typos as found by codespell

2018-03-24T23:09:54Z

Signed-off-by: Georg Faerber

test: use $(dirname "$0") for sourcing test-lib.sh

2017-10-20T22:52:49Z

Don't assume the tests are always run from within the source tree.

test: mark inclusion of headers as broken in gmime-2.x

2017-07-05T10:12:20Z

The output of headers here reflects an underlying bug / quirk of gmime-2.6.

test/multipart: reorganize creation of multipart message

2017-07-05T10:12:08Z

We want to have the bodies of the multipart available in a file on their own for planned modifications to tests.

test: standardize argument order to test_expect_equal_file

2017-04-06T17:37:02Z

It is annoying to debug failing tests when the interpretation of the diffs is reversed for some tests.

test: require test_begin_subtest before test_expect_success

2017-03-09T13:01:21Z

Unify the subtests by requiring test_begin_subtest before test_expect_success. (Similar change for test_expect_code will follow.) This increases clarity in the test scripts by having a separate line for the start of the subtest with the heading, and makes it possible to simplify the test infrastructure by making all subtests similar.