thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.33 2021-08-19T04:46:42Z 2021-08-19T04:46:42Z David Bremner david@tethera.net 2021-08-19T04:46:42Z urn:sha1:3df2281746d57abbb45790ecb432ef40533c30bc notmuch release 0.32.3-1 for unstable (sid) [dgit] [dgit distro=debian no-split --quilt=linear] 2021-08-18T00:09:56Z David Bremner david@tethera.net 2021-07-18T17:58:22Z urn:sha1:686230712f3865ac0d0250084113d6d859cc2519 We need to special case the config section "built_with" because it is not (currently) handled by the library. This seems consist with the other sub-sub-commands 'list' and 'set'. 2021-08-18T00:09:38Z David Bremner david@tethera.net 2021-07-18T17:58:21Z urn:sha1:202dde04e1057d0ab06a4e11f059f9ed2c6a717f The "get" test is known broken because this functionality was dropped during the 0.32 config rewrite. 2021-06-27T16:59:42Z David Bremner david@tethera.net 2021-05-21T15:54:10Z urn:sha1:2f608d2a9400f666ec0aca1f76b59f6640104e4e This will be used to control how often atomic transactions are committed. 2021-05-10T14:08:18Z David Bremner david@tethera.net 2021-05-07T00:16:38Z urn:sha1:31098c4ae40511ffda9788a6654adbf898063d7f Prior to 0.32, notmuch had the (undocumented) behaviour that it expanded a relative value of database.path with respect to $HOME. In 0.32 this was special cased for database.path but broken for database.mail_root, which causes problems for at least notmuch-new when database.path is set to a relative path. The change in T030-config.sh reflects a user visible, but hopefully harmless behaviour change; the expanded form of the paths will now be printed by notmuch config. 2021-03-27T12:26:14Z David Bremner david@tethera.net 2021-02-19T12:41:36Z urn:sha1:dd9112e7d8e89e8566b90379f5f3b1461a2d2845 Previously the fact that some configuration options were only stored in the database (and thus editing the config file had no effect) was a source of user confusion. This was fixed with the series ending at d9af0af1646. On the other hand, the underlying partition of config options into those stored by default in the database and those stored in the config file remained. This is also confusing, since now some invocations of "notmuch config set" modify the config file, and others silently modify the database instead. With this commit, it is up to the user to decide which configuration to modify. A new "--database" option is provided for notmuch config to enable modifying the configuration information in the database; otherwise the default is to update an external config file. 2021-03-27T12:26:14Z David Bremner david@tethera.net 2021-02-14T13:32:41Z urn:sha1:b76da87d29b6c9714e3d62fd8d459733df084f92 notmuch_config_open will be preserved in the medium term for use by the commands that are manipulating the config file directly (config and setup) 2021-03-27T12:26:14Z David Bremner david@tethera.net 2021-02-14T11:54:22Z urn:sha1:3787fe6c84ae223ba8c34920c3a2495c71abfe6c Use the database opened at the top level rather than opening another notmuch_database_t. Test output changes because keys are now listed in alphabetical order, and because a missing database is no longer an error. 2021-03-27T12:26:14Z David Bremner david@tethera.net 2021-02-13T13:01:50Z urn:sha1:ecb91d056c1d99373316ccf7aff748bc91e90ef4 This commit starts the conversion of notmuch-config.c functionality (as opposed to just interface) to the new config framework. The change to T030-config is because of the move of the canonicalization database paths from the notmuch_config_t accessor to the internal function _choose_database_path. 2021-03-20T10:24:59Z David Bremner david@tethera.net 2021-03-04T13:31:13Z urn:sha1:cba540d6f5cbbad282a3046ed00a7966238fa14d Make checks more uniform between creating new databases and opening existing ones.