<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T220-reply.sh, branch 0.26</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.26</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.26'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-10-20T22:52:49Z</updated>
<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>Add additional munged reply-to tests</title>
<updated>2017-07-15T00:23:52Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-07-14T20:14:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8492298a613e8e666d0f3054dadcb98b72a65ae4'/>
<id>urn:sha1:8492298a613e8e666d0f3054dadcb98b72a65ae4</id>
<content type='text'>
The reply-to munging code might behave differently whether there's an
exact match on the strings or not, or whether the string is a raw
addr-spec instead of an name-addr.  These tests cover those variations
(i also had to tweak json output further below when this new test was
added).
</content>
</entry>
<entry>
<title>Ensure that "notmuch reply" succeeds during testing.</title>
<updated>2017-07-15T00:23:52Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-07-14T20:14:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=23a4d09773ebdb8b3b5d45b6fa5196190228f52d'/>
<id>urn:sha1:23a4d09773ebdb8b3b5d45b6fa5196190228f52d</id>
<content type='text'>
In some (bad!) cases, "notmuch reply" might fail, or might even
segfault.  If this happens, it indicates a bug, and the test suite
should notice it.
</content>
</entry>
<entry>
<title>cli/show: list all filenames of a message in the formatted output</title>
<updated>2017-02-26T11:41:33Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-25T13:31:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=14c60cf168ac3b0f277188c16e6012b7ebdadde7'/>
<id>urn:sha1:14c60cf168ac3b0f277188c16e6012b7ebdadde7</id>
<content type='text'>
Instead of just having the first filename for the message, list all
duplicate filenames of the message as a list in the formatted
outputs. This bumps the format version to 3.
</content>
</entry>
<entry>
<title>cli/reply: return internet address list from get header funcs</title>
<updated>2016-09-17T12:11:07Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2016-09-13T17:14:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=536b1f9df989915161024d2334e206f538d59f9b'/>
<id>urn:sha1:536b1f9df989915161024d2334e206f538d59f9b</id>
<content type='text'>
Pass in GMimeMessage to simplify To/Cc/Bcc headers. We'll eventually
remove the notmuch message passing altogether, but keep both for now
to not make too big changes at once.

Getting the headers from GMimeMessage using GMime functions fixes the
error on duplicate Cc headers reported by Daniel Kahn Gillmor
&lt;dkg@fifthhorseman.net&gt; in id:87d1ngv95p.fsf@alice.fifthhorseman.net.

Get rid of an intermediate function.

The small annoyance is the ownership differences in the address lists.
</content>
</entry>
<entry>
<title>test: add known broken test for reply to message with multiple Cc headers</title>
<updated>2016-09-17T11:41:29Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2016-09-13T17:14:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=36416c74e09d07fe3dfff79900171f15c4671412'/>
<id>urn:sha1:36416c74e09d07fe3dfff79900171f15c4671412</id>
<content type='text'>
As Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt; reports in
id:87d1ngv95p.fsf@alice.fifthhorseman.net, notmuch show combines
multiple Cc: fields into one, while notmuch reply does not. While such
messages are in violation of RFC 5322, it would be reasonable to
expect notmuch to be consistent. Add a known broken test to document
this expectation.

This also starts a new "broken" corpus for messages which are broken.

Details:

The original message is formatted using the message printing in
notmuch-show.c. For Cc:, it uses g_mime_message_get_recipients(),
which apparently combines all Cc: fields into one internally.

The addresses in the reply headers, OTOH, are based on headers queried
through libnotmuch. It boils down to g_mime_object_get_header() in
lib/message-file.c, which returns only the first occurence of header.
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
<entry>
<title>test: renamed test scripts to format T\d\d\d-name.sh</title>
<updated>2014-01-13T18:16:46Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2014-01-09T15:18:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a755c9d6a9099366cc82ba3a4bee8e6d2b83d529'/>
<id>urn:sha1:a755c9d6a9099366cc82ba3a4bee8e6d2b83d529</id>
<content type='text'>
All test scripts to be executed are now named as T\d\d\d-name.sh,
numers in increments of 10.

This eases adding new tests and developers to see which are test scripts
that are executed by test suite and in which order.
</content>
</entry>
</feed>
