<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib/notmuch-private.h, branch 0.31.4</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.31.4</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.31.4'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2021-02-15T20:43:50Z</updated>
<entry>
<title>fix build failure with glib 2.67</title>
<updated>2021-02-15T20:43:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-02-15T20:43:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6db8b422d91a75b7c16f013f10f41d1109ce5866'/>
<id>urn:sha1:6db8b422d91a75b7c16f013f10f41d1109ce5866</id>
<content type='text'>
Based on a patch from Michael J Gruber [1].  As of glib 2.67 (more
specifically [2]), including "gmime-extra.h" inside an extern "C"
block causes build failures, because glib is using C++ features.

Observing that "gmime-extra.h" is no longer needed in
notmuch-private.h, which can simply delete that include, but
we have to correspondingly move the includes which might include
it (in particular crypto.h) out of the extern "C" block also.

This seems less fragile than only moving gmime-extra, and relying on
preprocessor sentinels to keep the deeper includes from happening.

Move to the include to the outside of the extern block.

[1]: id:aee618a3d41f7889a7449aa16893e992325a909a.1613055071.git.git@grubix.eu
[2]: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1715
</content>
</entry>
<entry>
<title>lib: encapsulate the use of notmuch_database_t field 'mode'</title>
<updated>2020-07-28T11:47:58Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-07-26T23:31:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d7d4c729ab3b74eaaebe64cb8c7383b0ea06cec0'/>
<id>urn:sha1:d7d4c729ab3b74eaaebe64cb8c7383b0ea06cec0</id>
<content type='text'>
The plan is to change the underlying representation.
</content>
</entry>
<entry>
<title>lib: rename _n_d_create to _n_d_find_or_create</title>
<updated>2020-07-22T22:52:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-07-19T10:36:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ce360ce4c99597946949317aa40892536c9ebc05'/>
<id>urn:sha1:ce360ce4c99597946949317aa40892536c9ebc05</id>
<content type='text'>
The error message and name were confusing when called in some "read
only" context.
</content>
</entry>
<entry>
<title>repair: set up codebase for repair functionality</title>
<updated>2019-09-01T11:20:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-08-29T15:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1b29822cf55eb53e1d45a71c2a3e4a2c2a4574d1'/>
<id>urn:sha1:1b29822cf55eb53e1d45a71c2a3e4a2c2a4574d1</id>
<content type='text'>
This adds no functionality directly, but is a useful starting point
for adding new repair functionality.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>lib: run uncrustify</title>
<updated>2019-06-14T10:41:27Z</updated>
<author>
<name>uncrustify</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-13T10:55:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2b62ca2e3b786beca8d89fa737bda0b49faa638d'/>
<id>urn:sha1:2b62ca2e3b786beca8d89fa737bda0b49faa638d</id>
<content type='text'>
This is the result of running

     $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc

in the lib directory
</content>
</entry>
<entry>
<title>indexing: record protected subject when indexing cleartext</title>
<updated>2019-05-29T11:14:44Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-27T22:40:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5c3a44681f2fffbd3a7d76e424c134a82470ddd2'/>
<id>urn:sha1:5c3a44681f2fffbd3a7d76e424c134a82470ddd2</id>
<content type='text'>
When indexing the cleartext of an encrypted message, record any
protected subject in the database, which should make it findable and
visible in search.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>lib/database: index user headers.</title>
<updated>2019-05-25T10:21:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-02-26T02:10:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=adb53b073791f710b93a8fc755b6b7b606bf7fd1'/>
<id>urn:sha1:adb53b073791f710b93a8fc755b6b7b606bf7fd1</id>
<content type='text'>
This essentially involves calling _notmuch_message_gen_terms once for
each user defined header.
</content>
</entry>
<entry>
<title>lib: support user prefix names in term generation</title>
<updated>2019-05-25T10:17:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-02-26T01:57:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=75bdce79527571c12c5de0c630747d6262b73fbd'/>
<id>urn:sha1:75bdce79527571c12c5de0c630747d6262b73fbd</id>
<content type='text'>
This should not change the indexing process yet as nothing calls
_notmuch_message_gen_terms with a user prefix name. On the other hand,
it should not break anything either.

_notmuch_database_prefix does a linear walk of the list of (built-in)
prefixes, followed by a logarithmic time search of the list of user
prefixes. The latter is probably not really noticable.
</content>
</entry>
<entry>
<title>lib: cache user prefixes in database object</title>
<updated>2019-05-25T10:08:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-11-17T14:09:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b52cda90f0b05ce5055fb840e6d9dd88c09f1f83'/>
<id>urn:sha1:b52cda90f0b05ce5055fb840e6d9dd88c09f1f83</id>
<content type='text'>
This will be used to avoid needing a database access to resolve a db
prefix from the corresponding UI prefix (e.g. when indexing). Arguably
the setup of the separate header map does not belong here, since it is
about indexing rather than querying, but we currently don't have any
other indexing setup to do.
</content>
</entry>
<entry>
<title>lib: setup user headers in query parser</title>
<updated>2019-05-25T09:56:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-11-17T14:08:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=575493e78534f8fd241d663b8690a22d6885e0b1'/>
<id>urn:sha1:575493e78534f8fd241d663b8690a22d6885e0b1</id>
<content type='text'>
These tests will need to be updated if the Xapian
query print/debug format changes.
</content>
</entry>
</feed>
