<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib/thread.cc, branch 0.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-03-31T20:32:00Z</updated>
<entry>
<title>emacs: Fix the notmuch-search-authors-width variable.</title>
<updated>2010-03-31T20:32:00Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-11T23:04:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b957a1b029d27c6b2ecd352dbacde3d9d164666f'/>
<id>urn:sha1:b957a1b029d27c6b2ecd352dbacde3d9d164666f</id>
<content type='text'>
This variable existed previously, but wasn't actually used for anything.
</content>
</entry>
<entry>
<title>lib: Rename iterator functions to prepare for reverse iteration.</title>
<updated>2010-03-09T17:22:29Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-09T17:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e5d2f22db290a830c0267f34b519c6138af00ed'/>
<id>urn:sha1:4e5d2f22db290a830c0267f34b519c6138af00ed</id>
<content type='text'>
We rename 'has_more' to 'valid' so that it can function whether
iterating in a forward or reverse direction. We also rename
'advance' to 'move_to_next' to setup parallel naming with
the proposed functions 'move_to_first', 'move_to_last', and
'move_to_previous'.
</content>
</entry>
<entry>
<title>correct message flag enum value so that it matches the type</title>
<updated>2009-11-28T04:50:59Z</updated>
<author>
<name>Bart Trojanowski</name>
<email>bart@jukie.net</email>
</author>
<published>2009-11-28T02:20:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6da656657621febf2d5b9e1ba69c8856f9882140'/>
<id>urn:sha1:6da656657621febf2d5b9e1ba69c8856f9882140</id>
<content type='text'>
As per Carl's request, this patch corrects the only value defined under
the notmuch_message_flag_t enum typedef to match the name of the type.

Signed-off-by: Bart Trojanowski &lt;bart@jukie.net&gt;
</content>
</entry>
<entry>
<title>have _notmuch_thread_create mark which messages matched the query</title>
<updated>2009-11-28T01:07:06Z</updated>
<author>
<name>Bart Trojanowski</name>
<email>bart@jukie.net</email>
</author>
<published>2009-11-25T04:54:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bede40987a64b7c2565d771922a3eac0a229ee28'/>
<id>urn:sha1:bede40987a64b7c2565d771922a3eac0a229ee28</id>
<content type='text'>
When _notmuch_thread_create() is given a query string, it can return more
messages than just those matching the query.  To distinguish those that
matched the query expression, the MATCHING_SEARCH flag is set
appropriately.

Signed-off-by: Bart Trojanowski &lt;bart@jukie.net&gt;
</content>
</entry>
<entry>
<title>lib/query: Drop the first and max_messages arguments from search_messages.</title>
<updated>2009-11-24T04:25:13Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-24T04:25:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=94eb9aacd40a8aa133f64bbe5ed71c0138fb5ed9'/>
<id>urn:sha1:94eb9aacd40a8aa133f64bbe5ed71c0138fb5ed9</id>
<content type='text'>
These only existed to support the chunky-searching hack, but that
was recently dropped anyway.
</content>
</entry>
<entry>
<title>Typsos</title>
<updated>2009-11-18T11:21:36Z</updated>
<author>
<name>Ingmar Vanhassel</name>
<email>ingmar@exherbo.org</email>
</author>
<published>2009-11-17T23:23:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2ce25b93a72b4a8d6daa5321f9ef7df0772a789f'/>
<id>urn:sha1:2ce25b93a72b4a8d6daa5321f9ef7df0772a789f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>notmuch search: Change default search order to be newest messages first.</title>
<updated>2009-11-18T04:58:30Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-18T04:52:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=333486572517d2e2084d66208de59085f21d8573'/>
<id>urn:sha1:333486572517d2e2084d66208de59085f21d8573</id>
<content type='text'>
This is what most people want for a _search_ command. It's often
different for actually reading mail in an inbox, (where it makes more
sense to have results displayed in chronological order), but in such a
case, ther user is likely using an interface that can simply pass the
--sort=oldest-first option to "notmuch search".

Here we're also change the sort enum from NOTMUCH_SORT_DATE and
NOTMUCH_SORT_DATE_REVERSE to NOTMUCH_SORT_OLDEST_FIRST and
NOTMUCH_SORT_NEWEST_FIRST. Similarly we replace the --reverse option
to "notmuch search" with two options: --sort=oldest-first and
--sort=newest-first.

Finally, these changes are all tracked in the emacs interface, (which
has no change in its behavior).
</content>
</entry>
<entry>
<title>Fix "too many open files" bug by closing message files when done with them.</title>
<updated>2009-11-18T02:37:13Z</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2009-11-18T02:33:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d025e89ac7ccecc9a6bbea5e867fcc15589f81b5'/>
<id>urn:sha1:d025e89ac7ccecc9a6bbea5e867fcc15589f81b5</id>
<content type='text'>
The message file header parsing code parses only enough of the file to
find the desired header fields, then it leaves the file open until the
next header parsing call or when the message is no longer in use. If a
large number of messages end up being active, this will quickly run
out of file descriptors.

Here, we add support to explicitly close the message file within a
message, (_notmuch_message_close) and call that from thread
construction code.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;

Edited-by: Carl Worth &lt;cworth@cworth.org&gt;:

Many portions of Keith's original patch have since been solved other
ways, (such as the code that changed the handling of the In-Reply-To
header). So the final version is clean enough that I think even Keith
would be happy to have his name on it.
</content>
</entry>
<entry>
<title>get_in_reply_to: Implement via the database, not by opening mail file.</title>
<updated>2009-11-18T01:40:19Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-18T01:40:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=387828c4356416278fdac8446c904fe4c5ad283d'/>
<id>urn:sha1:387828c4356416278fdac8446c904fe4c5ad283d</id>
<content type='text'>
This reduces our reliance on open message_file objects, (so is a step
toward fixing the "too many open files" bug), but more importantly, it
means we don't load a self-referencing in-reply-to header, (since we
weed those out before adding any replyto terms to the database).
</content>
</entry>
<entry>
<title>notmuch show: Implement proper thread ordering/nesting of messages.</title>
<updated>2009-11-16T04:41:45Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-16T04:39:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=933caf814fcbbb7420d03ef42bb37bea6dd90449'/>
<id>urn:sha1:933caf814fcbbb7420d03ef42bb37bea6dd90449</id>
<content type='text'>
We now properly analyze the in-reply-to headers to create a proper
tree representing the actual thread and present the messages in this
correct thread order. Also, there's a new "depth:" value added to the
"message{" header so that clients can format the thread as desired,
(such as by indenting replies).
</content>
</entry>
</feed>
