notmuch/test/T170-sexp.sh, branch master

CLI/show: support --duplicate for structured output

2022-07-30T11:41:50Z

This introduces a new mandatory key for message structures, namely "duplicate". Per convention in devel/schemata this does _not_ increase the format version. This means that clients are responsible for checking that it exists, and not crashing if it does not. The main functional change is teaching mime_node_open to understand a 'duplicate' argument. Support for --duplicate in notmuch-reply would make sense, but we defer it to a later commit.

test: define and use notmuch_sexp_*_sanitize functions

2022-07-05T10:03:37Z

These are based on the equivalent functions for json. Like those, these are pretty simple-minded, and don't really understand the syntax.

CLI: print extra headers in structured output

2022-01-18T12:11:06Z

This is based on a patch from Johan Parin [1], which is in turn responding to a bug report / feature requiest from Jan Malkhovski. The update to the structured output documented in schemata is intended to be upward compatible, so the format version stays the same [1]: id:20191116162723.18343-1-johan.parin@gmail.com [2]: id:87h8sdemnr.fsf@oxij.org

test: source $NOTMUCH_SRCDIR/test/test-lib-emacs.sh

2021-06-03T12:29:27Z

Sourcing test-lib.sh will cd to TMP_DIRECTORY, so relative path in $0 will not work in previous version . $(dirname "$0")/test-lib-emacs.sh Now individual test scripts -- e.g. ./test/T310-emacs.sh will work.

test: split emacs functionality to its own file

2021-05-17T10:29:04Z

This way it's easier to identify the tests that do require emacs stuff. Signed-off-by: Felipe Contreras

cli/show: emit headers after emitting body

2019-05-29T11:02:32Z

This paves the way for emitting protected headers after verification and decryption, because it means that the headers will only be emitted after the body has been parsed. Signed-off-by: Daniel Kahn Gillmor

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

test: use source and build paths in T160-json.sh and T170-sexp.sh

2017-10-20T22:55:49Z

Make a distinction between source and build directories.

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: Perform T170 tests that don't require dtach before any that do.

2017-08-28T11:02:02Z

This avoids the later tests seeing different versions of the database depending on whether dtach is available.