Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes: > + > + Note: ``--decrypt=stash`` requires a writable database. > + Otherwise, ``notmuch show`` operates entirely in read-only mode. I would rephrase this as "requires write access to the database"; otherwise it sounds like "writable" (or lack) is persistent property of databases. > +# show the message using stashing decryption > +test_begin_subtest "stash decryption during show" > +output=$(notmuch show --decrypt=stash tag:encrypted subject:002 | awk '/^\014part}/{ f=0 }; { if (f) { print $0 } } /^\014part{ ID: 3/{ f=1 }') > +expected='This is a test encrypted message with a wumpus.' > +test_expect_equal \ > + "$output" \ > + "$expected" > + This is a bit hard to follow. I think it would be better to isolate this kind of parsing in a function in test-lib.sh; then at least the name would suggest the intent. > +test_begin_subtest "search should now show the contents" I think the point is not that it _shows_ the contents, but that it finds them > +output=$(notmuch search wumpus) > +expected='thread:0000000000000003 2000-01-01 [1/1] Notmuch Test Suite; test encrypted message for cleartext index 002 (encrypted inbox unread)' > +if [ $NOTMUCH_HAVE_GMIME_SESSION_KEYS -eq 0 ]; then > + test_subtest_known_broken > +fi > +test_expect_equal \ > + "$output" \ > + "$expected" _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch