<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-client.h, branch 0.20</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.20</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.20'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-03-11T07:04:00Z</updated>
<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>cli: Introduce "notmuch address" command</title>
<updated>2014-11-05T22:19:12Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2014-11-05T00:25:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5c27136e64dab2f90995de0bfa37c54186a2fae1'/>
<id>urn:sha1:5c27136e64dab2f90995de0bfa37c54186a2fae1</id>
<content type='text'>
This moves address-related functionality from search command to the
new address command. The implementation shares almost all code and
some command line options.

Options --offset and --limit were intentionally not included in the
address command, because they refer to messages numbers, which users
do not see in the output. This could confuse users because, for
example, they could see more addresses in the output that what was
specified with --limit. This functionality can be correctly
reimplemented for address subcommand later.

Also useless values of --exclude flag were not included in the address
command.

This was inspired by a patch from Jani Nikula.
</content>
</entry>
<entry>
<title>dump: support gzipped and atomic output</title>
<updated>2014-04-12T10:59:44Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-03-29T01:14:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3c13bc0321baaf340663779d6fce2b1f34c1c2c3'/>
<id>urn:sha1:3c13bc0321baaf340663779d6fce2b1f34c1c2c3</id>
<content type='text'>
The main goal is to support gzipped output for future internal
calls (e.g. from notmuch-new) to notmuch_database_dump.

The additional dependency is not very heavy since xapian already pulls
in zlib.

We want the dump to be "atomic", in the sense that after running the
dump file is either present and complete, or not present.  This avoids
certain classes of mishaps involving overwriting a good backup with a
bad or partial one.
</content>
</entry>
<entry>
<title>cli: abstract dump file open from the dump command</title>
<updated>2014-03-30T22:23:16Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-03-25T17:48:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3863755f6d9f3e7666c1484822384c036a4426c3'/>
<id>urn:sha1:3863755f6d9f3e7666c1484822384c036a4426c3</id>
<content type='text'>
Also expose the dump function to the rest of notmuch. No functional
changes, except for slight improvement in error handling.
</content>
</entry>
<entry>
<title>search: Add stable queries to thread search results</title>
<updated>2013-11-09T00:43:29Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-10-24T15:19:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=abeac48522ded66e2f0e9aae704482355cb46e6a'/>
<id>urn:sha1:abeac48522ded66e2f0e9aae704482355cb46e6a</id>
<content type='text'>
These queries will match exactly the set of messages currently in the
thread, even if more messages later arrive.  Two queries are provided:
one for matched messages and one for unmatched messages.

This can be used to fix race conditions with tagging threads from
search results.  While tagging based on a thread: query can affect
messages that arrived after the search, tagging based on stable
queries affects only the messages the user was shown in the search UI.

Since we want clients to be able to depend on the presence of these
queries, this ushers in schema version 2.
</content>
</entry>
<entry>
<title>cli: Separate current and deprecated format version</title>
<updated>2013-11-09T00:13:58Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-10-24T15:19:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a24cd45568872d49c05bdd6193876cce6f01fe80'/>
<id>urn:sha1:a24cd45568872d49c05bdd6193876cce6f01fe80</id>
<content type='text'>
Previously, the CLI would print a deprecation warning if a client
requested any format version other than the current one.  However, if
we add fields that are backwards-compatible, but want clients to be
able to depend on, we need to bump the version, but that doesn't make
the older version deprecated.

Hence, separate out the "minimum active" version and only print a
warning for requests below this version number.
</content>
</entry>
<entry>
<title>notmuch-compact: Initial commit of CLI</title>
<updated>2013-10-10T00:47:13Z</updated>
<author>
<name>Ben Gamari</name>
<email>bgamari.foss@gmail.com</email>
</author>
<published>2013-10-02T20:30:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=241a88ce2f3c8d76b5a63a202d8455757c0e751e'/>
<id>urn:sha1:241a88ce2f3c8d76b5a63a202d8455757c0e751e</id>
<content type='text'>
Introduce the user command exposing the new compaction facility.

Signed-off-by: Ben Gamari &lt;bgamari.foss@gmail.com&gt;
</content>
</entry>
<entry>
<title>cli: add --include-html option to notmuch show</title>
<updated>2013-08-27T10:57:36Z</updated>
<author>
<name>John Lenz</name>
<email>lenz@math.uic.edu</email>
</author>
<published>2013-07-02T00:19:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f735a85c28a3c6b6e38ecaba04029a917c6d6830'/>
<id>urn:sha1:f735a85c28a3c6b6e38ecaba04029a917c6d6830</id>
<content type='text'>
For my client, the largest bottleneck for displaying large threads is
exporting each html part individually since by default notmuch will not
show the json parts.  For large threads there can be quite a few parts and
each must be exported and decoded one by one.  Also, I then have to deal
with all the crazy charsets which I can do through a library but is a
pain.

Therefore, this patch adds an --include-html option that causes the
text/html parts to be included as part of the output of show.

diff man/man1/notmuch-show.1
</content>
</entry>
<entry>
<title>cli: add insert command</title>
<updated>2013-06-29T17:42:20Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2013-06-23T12:20:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9439a1ec0cbb60e75925a5a17e8284fcaccf51df'/>
<id>urn:sha1:9439a1ec0cbb60e75925a5a17e8284fcaccf51df</id>
<content type='text'>
The notmuch insert command reads a message from standard input,
writes it to a Maildir folder, and then incorporates the message into
the notmuch database.  Essentially it moves the functionality of
notmuch-deliver into notmuch.

Though it could be used as an alternative to notmuch new, the reason
I want this is to allow my notmuch frontend to add postponed or sent
messages to the mail store and notmuch database, without resorting to
another tool (e.g. notmuch-deliver) nor directly modifying the maildir.
</content>
</entry>
</feed>
