<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-config.c, branch 0.29.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.29.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.29.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2019-05-25T09:56:16Z</updated>
<entry>
<title>cli/config: check syntax of user configured field names</title>
<updated>2019-05-25T09:56:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-27T10:13:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4b9c03efc6e4cd4b083c18c98416218059d1b8d7'/>
<id>urn:sha1:4b9c03efc6e4cd4b083c18c98416218059d1b8d7</id>
<content type='text'>
These restrictions are meant to prevent incompatibilities with the
Xapian query parser (which will split at non-word characters) and
clashes with future notmuch builtin fields.
</content>
</entry>
<entry>
<title>cli/config: support user header index config</title>
<updated>2019-05-25T09:56:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-11-17T14:08:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7981bd050e79b07d583de3b310b503eb8439219b'/>
<id>urn:sha1:7981bd050e79b07d583de3b310b503eb8439219b</id>
<content type='text'>
We don't do anything with this configuration information information
yet, but nonetheless add a couple of regression tests to make sure we
don't break standard functionality when we do use the configuration
information.
</content>
</entry>
<entry>
<title>cli/config: refactor _stored_in_db</title>
<updated>2019-05-25T09:54:47Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-11-17T14:08:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c1889aa331c4581094facffa0d826db62947eda4'/>
<id>urn:sha1:c1889aa331c4581094facffa0d826db62947eda4</id>
<content type='text'>
This will make it easier to add other prefixes that are stored in the
database, compared to special casing each one as "query." was. This
commit also adds the ability to validate keys with a given
prefix. This ability will be used in a future commit.
</content>
</entry>
<entry>
<title>gmime-cleanup: remove obsolete gpg_path configuration option and crypto contexts</title>
<updated>2019-05-03T09:55:04Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-02T13:19:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=096d45a878ba9606f1677f66d346b14c3c274fa5'/>
<id>urn:sha1:096d45a878ba9606f1677f66d346b14c3c274fa5</id>
<content type='text'>
Note that we do keep ignoring the gpg_path configuration option,
though, to avoid breakage of existing installations.  It is ignored
like any other unknown configuration option, but we at least document
that it is ignored so that people who find it in their legacy configs
can know that it's safe to drop.

signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>notmuch: Database paths without a leading / are relative to $HOME</title>
<updated>2018-09-08T23:19:24Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2018-09-08T11:49:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=95a9c73c72ff61d5514010a1b9bc11f94cbe988c'/>
<id>urn:sha1:95a9c73c72ff61d5514010a1b9bc11f94cbe988c</id>
<content type='text'>
If the database path specified in the configuration file does *not*
start with a /, presume that it is relative to $HOME and modify the
path used to open the database accordingly.
</content>
</entry>
<entry>
<title>indexing: Change from try_decrypt to decrypt</title>
<updated>2017-12-08T12:05:53Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T06:23:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d3964e81ac98825a025a6120c488ebd73de2a281'/>
<id>urn:sha1:d3964e81ac98825a025a6120c488ebd73de2a281</id>
<content type='text'>
the command-line interface for indexing (reindex, new, insert) used
--try-decrypt; and the configuration records used index.try_decrypt.
But by comparison with "show" and "reply", there doesn't seem to be
any reason for the "try" prefix.

This changeset adjusts the command-line interface and the
configuration interface.

For the moment, i've left indexopts_{set,get}_try_decrypt alone.  The
subsequent changeset will address those.
</content>
</entry>
<entry>
<title>config: define new option index.try_decrypt</title>
<updated>2017-10-21T22:54:33Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-21T02:25:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d0da7a0a1c24b937eb754e8f73e5cf7e3857f24a'/>
<id>urn:sha1:d0da7a0a1c24b937eb754e8f73e5cf7e3857f24a</id>
<content type='text'>
By default, notmuch won't try to decrypt on indexing.  With this
patch, we make it possible to indicate a per-database preference using
the config variable "index.try_decrypt", which by default will be
false.

At indexing time, the database needs some way to know its internal
defaults for how to index encrypted parts.  It shouldn't be contingent
on an external config file (since that can't be retrieved from the
database object itself), so we store it in the database.

This behaves similarly to the query.* configurations, which are also
stored in the database itself, so we're not introducing any new
dependencies by requiring that it be stored in the database.
</content>
</entry>
<entry>
<title>config: test whether an item is stored in the database by name</title>
<updated>2017-10-21T22:54:24Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-21T02:25:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=886c0b1666478548485682fbcaa667bb3cc0f138'/>
<id>urn:sha1:886c0b1666478548485682fbcaa667bb3cc0f138</id>
<content type='text'>
QUERY_STRING was only used in two places, both to test whether a
variable should be stored in (or retrieved from) the database.

Since other configuration variables might be stored in the database in
the future, consolidate that test into a single function.

We also document that these configuration options should not be placed
in the config file.
</content>
</entry>
<entry>
<title>cli: convert notmuch_bool_t to stdbool</title>
<updated>2017-10-10T01:24:02Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-10-07T08:44:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0f314c0c99befea599a68bea51d759b4133efef6'/>
<id>urn:sha1:0f314c0c99befea599a68bea51d759b4133efef6</id>
<content type='text'>
C99 stdbool turned 18 this year. There really is no reason to use our
own, except in the library interface for backward
compatibility. Convert the cli and test binaries to stdbool.
</content>
</entry>
<entry>
<title>config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0</title>
<updated>2017-07-15T00:23:52Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-07-14T13:12:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e142de643d3bb4354f70e1490a97b491d1116e95'/>
<id>urn:sha1:e142de643d3bb4354f70e1490a97b491d1116e95</id>
<content type='text'>
gmime 3.0 no longer offers a means to set the path for gpg.

Users can set $PATH anyway if they want to pick a
differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't
much of a reduction in functionality.

The one main difference is for people who have tried to use "gpg2" to
make use of gpg 2.1, but that isn't usefully co-installable anyway.
</content>
</entry>
</feed>
