<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-client.h, branch 0.12</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.12</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.12'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-02-17T12:04:34Z</updated>
<entry>
<title>add support for user-specified files &amp; directories to ignore</title>
<updated>2012-02-17T12:04:34Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-02-15T09:17:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ce1e720de64270a7cbb4bc3fba2c7fe081de3edc'/>
<id>urn:sha1:ce1e720de64270a7cbb4bc3fba2c7fe081de3edc</id>
<content type='text'>
A new configuration key 'new.ignore' is used to determine which
files and directories user wants not to be scanned as new mails.

Mark the corresponding test as no longer broken.
This work merges my previous attempts and Andreas Amann's work
in id:"ylp7hi23mw8.fsf@tyndall.ie"
</content>
</entry>
<entry>
<title>cli: use notmuch_bool_t for boolean fields in notmuch_show_params_t</title>
<updated>2012-02-12T16:58:20Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-02-06T19:57:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b'/>
<id>urn:sha1:c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b</id>
<content type='text'>
Use notmuch_bool_t instead of int for entire_thread, raw, and decrypt
boolean fields in notmuch_show_params_t. No functional changes.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>show: Introduce mime_node formatter callback</title>
<updated>2012-01-25T11:21:40Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-23T23:33:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7430a42e23ee775818f84ed75f417302da694152'/>
<id>urn:sha1:7430a42e23ee775818f84ed75f417302da694152</id>
<content type='text'>
This callback is the gateway to the new mime_node_t-based formatters.
This maintains backwards compatibility so the formatters can be
transitioned one at a time.  Once all formatters are converted, the
formatter structure can be reduced to only message_set_{start,sep,end}
and part, most of show_message can be deleted, and all of
show-message.c can be deleted.
</content>
</entry>
<entry>
<title>mime node: Record depth-first part numbers</title>
<updated>2012-01-25T11:19:22Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-23T23:33:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a66e65d604c5e658daa97acbb9d0487788863521'/>
<id>urn:sha1:a66e65d604c5e658daa97acbb9d0487788863521</id>
<content type='text'>
This makes the part numbers readily accessible to formatters.
Hierarchical part numbering would be a more natural and efficient fit
for MIME and may be the way to go in the future, but depth-first
numbering maintains compatibility with what we currently do.
</content>
</entry>
<entry>
<title>search: rename auto_exclude_tags to {search, }exclude_tags</title>
<updated>2012-01-23T23:17:16Z</updated>
<author>
<name>Pieter Praet</name>
<email>pieter@praet.org</email>
</author>
<published>2012-01-23T04:22:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=649a9f5f3a3749374284dc757250345db8d5c7ad'/>
<id>urn:sha1:649a9f5f3a3749374284dc757250345db8d5c7ad</id>
<content type='text'>
All other config-related functions and args include the section
title in their name, so for the sake of consistency, mirror that.

Also, the "auto"matic part is a given, so that was dropped.
</content>
</entry>
<entry>
<title>Add compatibility with gmime 2.6</title>
<updated>2012-01-21T12:52:34Z</updated>
<author>
<name>Thomas Jost</name>
<email>schnouki@schnouki.net</email>
</author>
<published>2012-01-20T09:39:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=00b5623d1a21d886b564d031e30749e5d02e4ae6'/>
<id>urn:sha1:00b5623d1a21d886b564d031e30749e5d02e4ae6</id>
<content type='text'>
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.

This is mostly based on id:"8762i8hrb9.fsf@bookbinder.fernseed.info".

This was tested against both gmime 2.6.4 and 2.4.31. With gmime 2.4.31, the
crypto tests all work fine (as expected). With gmime 2.6.4, one crypto test is
currently broken (signature verification with signer key unavailable), most
likely because of a bug in gmime which will hopefully be fixed in a future
version.
</content>
</entry>
<entry>
<title>search: Support automatic tag exclusions</title>
<updated>2012-01-17T01:06:35Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-15T00:17:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=42a907992823030f070fc395a174f779998ca6f5'/>
<id>urn:sha1:42a907992823030f070fc395a174f779998ca6f5</id>
<content type='text'>
This adds a "search" section to the config file and an
"auto_tag_exclusions" setting in that section.  The search and count
commands pass tag tags from the configuration to the library.
</content>
</entry>
<entry>
<title>Utility function to seek in MIME trees in depth-first order.</title>
<updated>2011-12-26T02:21:04Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2011-12-24T18:52:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5d1ac7d1d351c6f122ddaa44d3c82ec68d45178c'/>
<id>urn:sha1:5d1ac7d1d351c6f122ddaa44d3c82ec68d45178c</id>
<content type='text'>
This function matches how we number parts for the --part argument to
show.  It will allow us to jump directly to the desired part, rather
than traversing the entire tree and carefully tracking whether or not
we're "in the zone".
</content>
</entry>
<entry>
<title>Introduce a generic tree-like abstraction for MIME traversal.</title>
<updated>2011-12-26T02:19:12Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2011-12-24T18:52:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bb189220a323e3140198161234ed54bf98175469'/>
<id>urn:sha1:bb189220a323e3140198161234ed54bf98175469</id>
<content type='text'>
This wraps all of the complex MIME part handling in a single, simple
function that gets part N from *any* MIME object, so traversing a MIME
part tree becomes a two-line for loop.  Furthermore, the MIME node
structure provides easy access to envelopes for message parts as well
as cryptographic information.

This code is directly derived from the current show_message_body code
(much of it is identical), but the control relation is inverted:
instead of show_message_body controlling the traversal of the MIME
structure and invoking callbacks, the caller controls the traversal of
the MIME structure.
</content>
</entry>
<entry>
<title>show: Pass notmuch_message_t instead of path to show_message_body.</title>
<updated>2011-12-26T02:17:27Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2011-12-24T18:52:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=36f7fe5a1c83f3f0dd8fc883db558ab058b974f3'/>
<id>urn:sha1:36f7fe5a1c83f3f0dd8fc883db558ab058b974f3</id>
<content type='text'>
In addition to simplifying the code, we'll need the notmuch_message_t*
in show_message_body shortly.
</content>
</entry>
</feed>
