<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib/query.cc, branch 0.20.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.20.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.20.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-03-28T23:34:15Z</updated>
<entry>
<title>lib: replace almost all fprintfs in library with _n_d_log</title>
<updated>2015-03-28T23:34:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-12-26T16:25:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=736ac26407914425a9c94e86616225292cf716dd'/>
<id>urn:sha1:736ac26407914425a9c94e86616225292cf716dd</id>
<content type='text'>
This is not supposed to change any functionality from an end user
point of view. Note that it will eliminate some output to stderr. The
query debugging output is left as is; it doesn't really fit with the
current primitive logging model. The remaining "bad" fprintf will need
an internal API change.
</content>
</entry>
<entry>
<title>lib: make notmuch_query_count_messages explicitely exact</title>
<updated>2015-03-13T06:58:55Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-10-14T16:32:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6d44e5ac4743f618513c9a080733d91afa683f16'/>
<id>urn:sha1:6d44e5ac4743f618513c9a080733d91afa683f16</id>
<content type='text'>
The default is actually exact if no checkatleast parameter is
specified. This change makes that explicit, mainly for documentation,
but also to be safe in the unlikely event of a change of default.

[ commit message rewritten by db based on id:87lho0nlkk.fsf@nikula.org
]
</content>
</entry>
<entry>
<title>lib: add new status reporting API for notmuch_query_search_{m,t}</title>
<updated>2015-03-01T07:49:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-01-20T07:53:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7a0fc103678ea1b1da2df561d222c08db04c5af2'/>
<id>urn:sha1:7a0fc103678ea1b1da2df561d222c08db04c5af2</id>
<content type='text'>
This at least allows distinguishing between out of memory and Xapian
exceptions. Adding finer grained status codes would allow different
Xapian exceptions to be preserved.

Adding wrappers allows people to transition gradually to the new API,
at the cost of bloating the library API a bit.
</content>
</entry>
<entry>
<title>lib: make notmuch_threads_valid return FALSE when passed NULL</title>
<updated>2014-01-25T00:20:54Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-01-23T12:24:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=29f125212619ebca8621dd2106b412b22e1b6d22'/>
<id>urn:sha1:29f125212619ebca8621dd2106b412b22e1b6d22</id>
<content type='text'>
Without this patch, the example code in the header docs crashes for certain
invalid queries (see id:871u00oimv.fsf@approx.mit.edu)
</content>
</entry>
<entry>
<title>query: bind queries to database objects</title>
<updated>2013-11-02T13:20:01Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2013-09-30T16:04:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fd733a4f5c41948b895e37daf9bc0912f695ae59'/>
<id>urn:sha1:fd733a4f5c41948b895e37daf9bc0912f695ae59</id>
<content type='text'>
The queries don't really work after a database is closed, and we would
like them to be freed if the database is destroyed.

Acknowledged-by: David Bremner &lt;david@tethera.net&gt;
Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>lib: add NOTMUCH_EXCLUDE_FLAG to notmuch_exclude_t</title>
<updated>2013-06-25T05:53:16Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2013-05-13T15:10:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d29d7e1ee25059c657412d5b045650f1e3e1533f'/>
<id>urn:sha1:d29d7e1ee25059c657412d5b045650f1e3e1533f</id>
<content type='text'>
Add NOTMUCH_EXCLUDE_FLAG to notmuch_exclude_t so that it can
cover all four values of search --exclude in the cli.

Previously the way to avoid any message being marked excluded was to
pass in an empty list of excluded tags: since we now have an explicit
option we might as well honour it.

The enum is in a slightly strange order as the existing FALSE/TRUE
options correspond to the new
NOTMUCH_EXCLUDE_FLAG/NOTMUCH_EXCLUDE_TRUE options so this means we do
not need to bump the version number.

Indeed, an example of this is that the cli count and show still use
FALSE/TRUE and still work.
</content>
</entry>
<entry>
<title>lib: add --exclude=all option</title>
<updated>2013-05-14T00:32:03Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2013-05-11T19:50:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=38698d86596af64fa25c118dafef0249155ca7a4'/>
<id>urn:sha1:38698d86596af64fa25c118dafef0249155ca7a4</id>
<content type='text'>
Adds a exclude all option to the lib which means that excluded
messages are completely ignored (as if they had actually been
deleted).
</content>
</entry>
<entry>
<title>bitmap:improve memory usage using CHAR_BITS and unsigned CHAR</title>
<updated>2013-02-16T00:05:10Z</updated>
<author>
<name>Robert Mast</name>
<email>beheerder@tekenbeetziekten.nl</email>
</author>
<published>2013-02-13T15:32:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c033cb4c0785f88bd9298ede09badddd50c1780f'/>
<id>urn:sha1:c033cb4c0785f88bd9298ede09badddd50c1780f</id>
<content type='text'>
Using char instead of int allows for simpler definitions of the
DOCIDSET macros so the code is easier to understand and consistent with
respect to memory-usage. Estimated reduction of memory-usage for
bitmap about 8 times.
</content>
</entry>
<entry>
<title>lib: change default for notmuch_query_set_omit_excluded</title>
<updated>2012-04-08T01:58:33Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-04-07T16:10:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d6fbef4690968c8d0b8e9dc19a903e693cace316'/>
<id>urn:sha1:d6fbef4690968c8d0b8e9dc19a903e693cace316</id>
<content type='text'>
</content>
</entry>
<entry>
<title>lib: fix an exclude bug</title>
<updated>2012-03-18T12:14:23Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-03-14T12:26:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c695534df5830d0681f451bd213e75758b532e31'/>
<id>urn:sha1:c695534df5830d0681f451bd213e75758b532e31</id>
<content type='text'>
When the exclude tags contain a tag that does not occur anywhere in
the Xapian database the exclusion fails. We modify the way the query
is constructed to `work around' this. (In fact the new code is cleaner
anyway.)

It also seems to fix another exclusion failure bug reported by
jrollins but we have not yet worked out why it helps in that case.
</content>
</entry>
</feed>
