<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-show.c, branch 0.22</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.22</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.22'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-11-19T11:47:29Z</updated>
<entry>
<title>cli: content disposition values are not case-sensitive</title>
<updated>2015-11-19T11:47:29Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-26T09:35:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1abc33833149f6c71850c1b6f4bdeca38c718023'/>
<id>urn:sha1:1abc33833149f6c71850c1b6f4bdeca38c718023</id>
<content type='text'>
Per RFC 2183, the values for Content-Disposition values are not
case-sensitive. While at it, use the gmime function for getting at the
disposition string instead of referencing the field directly.

This fixes attachment display and quoting in notmuch show and reply,
respectively.
</content>
</entry>
<entry>
<title>cli: update to use new count API</title>
<updated>2015-10-05T22:51:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-27T15:31:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e7b420a85446fa469df77e24c11f8afa06a2592e'/>
<id>urn:sha1:e7b420a85446fa469df77e24c11f8afa06a2592e</id>
<content type='text'>
Essentially replace each call to notmuch_count_* with the corresponding
_st call, followed by print_status_query.
</content>
</entry>
<entry>
<title>cli: convert remainder of CLI to n_q_search_{messages,threads}_st</title>
<updated>2015-09-23T11:03:34Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-06T13:15:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6cdd34a4c762c954426f586d514a3e041c1db3b0'/>
<id>urn:sha1:6cdd34a4c762c954426f586d514a3e041c1db3b0</id>
<content type='text'>
I think it would be no real problem to cut and paste the gdb based
error message test from count to the other clients modified here, but
I'm not currently convinced it's worth the trouble since the code path
being tested is almost the the same, and the tests are relatively
heavyweight.
</content>
</entry>
<entry>
<title>cli/lib: remove support for GMime 2.4</title>
<updated>2015-08-26T23:01:45Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-08-16T15:33:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=005c2f0df17de8afdf9f67b923d26f2358236171'/>
<id>urn:sha1:005c2f0df17de8afdf9f67b923d26f2358236171</id>
<content type='text'>
It's becoming a maintenance burden to do anything things with the
crypto glue code twice, once for 2.4 and once for 2.6. I don't have
any 2.4 version available to test on my development machine anymore,
so the 2.4 specific code paths are likely not very well tested.
</content>
</entry>
<entry>
<title>cli: add global option "--uuid"</title>
<updated>2015-08-14T16:23:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-04-05T22:39:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f76d8f82dd004cf14426a91e8a80dcd2a4b97317'/>
<id>urn:sha1:f76d8f82dd004cf14426a91e8a80dcd2a4b97317</id>
<content type='text'>
The function notmuch_exit_if_unmatched_db_uuid is split from
notmuch_process_shared_options because it needs an open notmuch
database.

There are two exceptional cases in uuid handling.

1) notmuch config and notmuch setup don't currently open the database,
   so it doesn't make sense to check the UUID.

2) notmuch compact opens the database inside the library, so we either
   need to open the database just to check uuid, or change the API.
</content>
</entry>
<entry>
<title>cli: define shared options, use for --help and --version</title>
<updated>2015-06-01T05:32:54Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-04-05T13:13:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0018a8d787a98f80c665061daa9b0c73839d3666'/>
<id>urn:sha1:0018a8d787a98f80c665061daa9b0c73839d3666</id>
<content type='text'>
Unfortunately it seems trickier to support --config globally

The non-trivial changes are in notmuch.c; most of the other changes
consists of blindly inserting two lines into every subcommand.
</content>
</entry>
<entry>
<title>CLI: make gpg binary used by libgmime configurable.</title>
<updated>2015-03-11T07:04:00Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-12-09T20:01:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c883e632bf0a3692fa4ca7aa77604e0e60820295'/>
<id>urn:sha1:c883e632bf0a3692fa4ca7aa77604e0e60820295</id>
<content type='text'>
Previously we set up a way for the top level notmuch command to choose
which gpg binary was invoked by libgmime. In this commit we add the
(mostly boilerplate) code to allow the notmuch-config command to read
and write this path, and use it in the appropriate struct.

Update tests for new default variable
</content>
</entry>
<entry>
<title>CLI: set up infrastructure to make path to gpg configurable.</title>
<updated>2015-03-09T07:19:28Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-12-09T20:01:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=21ecd7369aa2aa24d26775c3fe5edcb437914774'/>
<id>urn:sha1:21ecd7369aa2aa24d26775c3fe5edcb437914774</id>
<content type='text'>
GMIME takes a path to gpg, but we hardcode that path.  In this commit
we set up argument passing and option storage to allow this path to
specified in the top level notmuch command.
</content>
</entry>
<entry>
<title>notmuch-show: detect NULL pointer returned from notmuch_query_search_threads</title>
<updated>2014-01-25T00:24:11Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-01-23T12:24:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ecbb29e8cea404faab2ef55b06431942ee329941'/>
<id>urn:sha1:ecbb29e8cea404faab2ef55b06431942ee329941</id>
<content type='text'>
We want to return an error status, not 0 or (worse) segfault.
</content>
</entry>
<entry>
<title>cli: clean up exit status code returned by the cli commands</title>
<updated>2014-01-18T18:45:26Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-01-10T21:28:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c7453773064efbd0b2cd17b15ba483edbd28ce1e'/>
<id>urn:sha1:c7453773064efbd0b2cd17b15ba483edbd28ce1e</id>
<content type='text'>
Apart from the status codes for format mismatches, the non-zero exit
status codes have been arbitrary. Make the cli consistently return
either EXIT_SUCCESS or EXIT_FAILURE.
</content>
</entry>
</feed>
