<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T350-crypto.sh, branch 0.28</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.28</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.28'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-12-29T20:45:55Z</updated>
<entry>
<title>cli/reply: make --decrypt take a keyword</title>
<updated>2017-12-29T20:45:55Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=af8255fb7159652a7d4e1fe4f1398302e1746cce'/>
<id>urn:sha1:af8255fb7159652a7d4e1fe4f1398302e1746cce</id>
<content type='text'>
This brings the --decrypt argument to "notmuch reply" into line with
the other --decrypt arguments (in "show", "new", "insert", and
"reindex").  This patch is really just about bringing consistency to
the user interface.

We also use the recommended form in the emacs MUA when replying, and
update test T350 to match.
</content>
</entry>
<entry>
<title>cli/show: make --decrypt take a keyword.</title>
<updated>2017-12-29T20:45:46Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8ea4a99d74737929f58568505e41c94f65a14743'/>
<id>urn:sha1:8ea4a99d74737929f58568505e41c94f65a14743</id>
<content type='text'>
We also expand tab completion for it, update the emacs bindings, and
update T350, T357, and T450 to match.

Make use of the bool-to-keyword backward-compatibility feature.
</content>
</entry>
<entry>
<title>test: use $(dirname "$0") for sourcing test-lib.sh</title>
<updated>2017-10-20T22:52:49Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-25T20:38:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a863de1e43ee34f6f5794a2759fdceb287e851aa'/>
<id>urn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa</id>
<content type='text'>
Don't assume the tests are always run from within the source tree.
</content>
</entry>
<entry>
<title>tests: prepare for more crypto tests (using add_gnupg_home)</title>
<updated>2017-10-14T13:53:42Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-10T05:49:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ee5df7d7db895a427aa1e4343b2c8f794a0b2d73'/>
<id>urn:sha1:ee5df7d7db895a427aa1e4343b2c8f794a0b2d73</id>
<content type='text'>
Move add_gnupg_home to test-lib.sh to prepare it for reuse.
</content>
</entry>
<entry>
<title>lib: index the content-type of the parts of encrypted messages</title>
<updated>2017-09-17T23:01:19Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-09-16T14:59:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f4ac5ecd5c6db78982a0730059061cbe946ca079'/>
<id>urn:sha1:f4ac5ecd5c6db78982a0730059061cbe946ca079</id>
<content type='text'>
This is a logical followup to "lib: index the content type of
signature parts", which will make it easier to record the message
structure of all messages.
</content>
</entry>
<entry>
<title>lib: index the content type of signature parts</title>
<updated>2017-09-17T23:01:00Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-16T14:59:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=55c047ee0b0c9081ead76925ee1adaeb858264dd'/>
<id>urn:sha1:55c047ee0b0c9081ead76925ee1adaeb858264dd</id>
<content type='text'>
It's useful (*) to be able to easily find messages with certain types
of signatures. Having the mimetype: prefix searches fail for some
content types is also genuinely surprising (*). Index the content type
of signature parts.

While at it, switch to the gmime convenience constants for content and
signature part indexes.

*) At least for developers of email software!
</content>
</entry>
<entry>
<title>test: signed and encrypted part content type indexing</title>
<updated>2017-09-17T23:00:43Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-16T14:59:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=30c276146596769177e1e3c200d8bb94d4cf8531'/>
<id>urn:sha1:30c276146596769177e1e3c200d8bb94d4cf8531</id>
<content type='text'>
Add known broken subtests for searching signed and encrypted messages
using mimetype: prefix search for the content-types of signed and
encrypted parts.
</content>
</entry>
<entry>
<title>test/crypto: remove headers more robustly</title>
<updated>2017-09-03T11:06:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-09-01T23:59:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ec37900c5f0316e1f7345fe413402e6dc8bb9547'/>
<id>urn:sha1:ec37900c5f0316e1f7345fe413402e6dc8bb9547</id>
<content type='text'>
In [1], Vladimir Panteleev observed that the In-Reply-To and
References headers could be wrapped in the 'default' output format of
notmuch-reply, depending on the version of Emacs creating the
message. In my own experiments notmuch-reply sometimes wraps headers
with only one message-id if that message-id is long enough. However it
happens, this causes the previous approach using grep to fail.

Since I found the proposed unwrapping shell fragment in [1] a bit hard
to follow, I decided to write a little python script instead. Then
Tomi suggested a slight generalization of my script, and here we are.

[1] id:20170817175145.3204-7-notmuch@thecybershadow.net
</content>
</entry>
<entry>
<title>test/crypto: mark extra space in userid as a bug in gmime-2.6</title>
<updated>2017-07-14T20:58:09Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T00:29:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a58c75fdf6120aa3861e95a4a61fa268dee6a690'/>
<id>urn:sha1:a58c75fdf6120aa3861e95a4a61fa268dee6a690</id>
<content type='text'>
I can't see the space in the output of gpg -K --with-colons
</content>
</entry>
<entry>
<title>test/crypto: add test for corrupted signatures</title>
<updated>2017-07-05T10:36:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T17:47:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=87ca29b7a737a9b52f1916156aef9511939b4376'/>
<id>urn:sha1:87ca29b7a737a9b52f1916156aef9511939b4376</id>
<content type='text'>
Have an empty list of signatures is not the nicest mechanism to signal
complete failure to verify, but it's the one we currently have.
</content>
</entry>
</feed>
