<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/query.cc, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2009-11-10T00:24:03Z</updated>
<entry>
<title>libify: Move library sources down into lib directory.</title>
<updated>2009-11-10T00:24:03Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-10T00:12:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=146549321044615d9aef2b30cedccda9c49f3f38'/>
<id>urn:sha1:146549321044615d9aef2b30cedccda9c49f3f38</id>
<content type='text'>
A "make" invocation still works from the top-level, but not from
down inside the lib directory yet.
</content>
</entry>
<entry>
<title>Rename message_results/thread_results to messages/threads.</title>
<updated>2009-10-31T23:32:30Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-31T23:32:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c96021a47705bdb2ac189d52825a8edc033d35dd'/>
<id>urn:sha1:c96021a47705bdb2ac189d52825a8edc033d35dd</id>
<content type='text'>
Shorter naming without being any less clear. A definite win.
</content>
</entry>
<entry>
<title>notmuch search: Add (relative) date to search output</title>
<updated>2009-10-30T00:31:07Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-30T00:31:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c771eaf362edb021888d114989d38d8fb2b4cfb3'/>
<id>urn:sha1:c771eaf362edb021888d114989d38d8fb2b4cfb3</id>
<content type='text'>
The new function for formatting relative dates is nice enough that
we need to start using it more places. Here's one of them.
</content>
</entry>
<entry>
<title>notmuch show: Initial implementation (headers only)</title>
<updated>2009-10-29T15:51:12Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-29T15:51:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bf78a89196b251c2465f6cefa8198f22c87ff23d'/>
<id>urn:sha1:bf78a89196b251c2465f6cefa8198f22c87ff23d</id>
<content type='text'>
We're using a delimiter syntax that Keith is optimistic about
being able to easily parse in emacs. Note: We're not escaping
any occurrence of the delimiters in the message yet, so we'll
need to fix that.
</content>
</entry>
<entry>
<title>Add public notmuch_thread_get_subject</title>
<updated>2009-10-27T00:35:31Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-27T00:35:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c12823648ee84b4748e0e9f0cd97f7264911b589'/>
<id>urn:sha1:c12823648ee84b4748e0e9f0cd97f7264911b589</id>
<content type='text'>
And use this in "notmuch search" to display subject line as well as
thread ID.
</content>
</entry>
<entry>
<title>Add notmuch_thread_get_tags</title>
<updated>2009-10-26T21:46:14Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-26T21:46:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=94f01d9de914b609e1f02385092b82fd61ca73b5'/>
<id>urn:sha1:94f01d9de914b609e1f02385092b82fd61ca73b5</id>
<content type='text'>
And augment "notmuch search" to print tag values as well as thread ID
values. This tool is almost usable now.
</content>
</entry>
<entry>
<title>Fix memory leak in notmuch_thread_results_t</title>
<updated>2009-10-26T21:02:58Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-26T21:02:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1726c5c814aecd924849a0b91c82d420af945827'/>
<id>urn:sha1:1726c5c814aecd924849a0b91c82d420af945827</id>
<content type='text'>
If we were using a talloc-based resizing array then this wouldn't
have happened. Of course, thanks to valgrind for catching this.
</content>
</entry>
<entry>
<title>results_get: Fix to return NULL if past the end of the results</title>
<updated>2009-10-26T12:14:51Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-26T12:14:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b42c4418a401d6192f9c6e8584bc780bb3ff9960'/>
<id>urn:sha1:b42c4418a401d6192f9c6e8584bc780bb3ff9960</id>
<content type='text'>
We had documented both notmuch_thread_results_get and
notmuch_message_results_get to return NULL if (! has_more)
but we hadn't actually implemented that. Fix.
</content>
</entry>
<entry>
<title>Add an initial implementation of a notmuch_thread_t object.</title>
<updated>2009-10-26T06:12:20Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-26T06:12:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1ba3d46fab12d616b2085f5794543444cc4bc750'/>
<id>urn:sha1:1ba3d46fab12d616b2085f5794543444cc4bc750</id>
<content type='text'>
We've now got a new notmuch_query_search_threads and a
notmuch_threads_result_t iterator. The thread object itself
doesn't do much yet, (just allows one to get the thread_id),
but that's at least enough to see that "notmuch search" is
actually doing something now, (since it has been converted
to print thread IDs instead of message IDs).

And maybe that's all we need. Getting the messages belonging
to a thread is as simple as a notmuch_query_search_messages
with a string of "thread:&lt;thread-id&gt;".

Though it would be convenient to add notmuch_thread_get_messages
which could use the existing notmuch_message_results_t iterator.

Now we just need an implementation of "notmuch show" and we'll
have something somewhat usable.
</content>
</entry>
<entry>
<title>Rename notmuch_query_search to notmuch_query_search_messages</title>
<updated>2009-10-26T05:22:07Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-10-26T05:11:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cd467cafb5eee180661ebc14e0fb71426e67c855'/>
<id>urn:sha1:cd467cafb5eee180661ebc14e0fb71426e67c855</id>
<content type='text'>
Along with renaming notmuch_results_t to notmuch_message_results_t.
The new type is quite a mouthful, but I don't expect it to be
used much other than the for-loop idiom in the documentation,
(which does at least fit nicely within 80 columns).

This is all in preparation for the addition of a new
notmuch_query_search_threads of course.
</content>
</entry>
</feed>
