notmuch/test/T055-path-config.sh, branch nmweb thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=nmweb 2023-04-02T22:21:37Z lib: add config key INDEX_AS_TEXT 2023-04-02T22:21:37Z David Bremner david@tethera.net 2023-01-06T00:02:04Z urn:sha1:c6733a45c8ff698505ff330d2edce92c90cbc946 Higher level processing as a list of regular expressions and documentation will follow. lib/open: create database path in some cases 2022-09-03T11:24:43Z David Bremner david@tethera.net 2022-07-29T11:31:37Z urn:sha1:84e4e130e2c920b3dee91901582c4ab6276e2630 There is some duplication of code here, but not all of the locations valid to find a database make sense to create. Furthermore we nead two passes, so the control flow in _choose_database_path would get a bit convoluted. test/path-config: set database.mail_root but not database.path 2022-09-03T11:24:43Z David Bremner david@tethera.net 2022-07-26T01:04:21Z urn:sha1:44c9338061ed64797b21b847ce29bcacd7f72886 The failing "create database" test replicates a bug reported by Sean Whitton [1]. The other two failures also look related to the database being (re)created in the wrong place. [1]: id:87y1wqkw13.fsf@athena.silentflame.com. test: add test for creating database in various configurations. 2022-09-03T11:24:43Z David Bremner david@tethera.net 2022-07-26T00:37:41Z urn:sha1:687866111a0e1df1a365d07f629c4768281ec00d The existing database creation (via add_email_corpus) was always done in the traditional configuration. The use of xapian-metadata is just to portably ensure that there is a database created where we expect there to be. tests: remove dead code from T055-path-config.sh 2022-08-06T12:16:13Z David Bremner david@tethera.net 2022-07-29T12:19:56Z urn:sha1:7b27119d8ee4ad612b7a7d48b612d15a58d68976 This case statement does nothing. test: known broken test for top level .notmuch in split configs 2022-07-05T11:09:57Z David Bremner david@tethera.net 2022-01-16T15:25:10Z urn:sha1:15b940d26aacadecf50469d3837ccb660fd5ba42 In split configurations there is no special significance to a top level directory called .notmuch in the mail root. Users should therefore be able to have mail stored underneath it. python-cffi: use config_pairs API in ConfigIterator 2022-02-17T01:57:22Z David Bremner david@tethera.net 2022-02-09T12:28:54Z urn:sha1:9ddd13f75827f4972872c8766320c7cb80b1819b This returns all of the config keys with non-empty values, not just those that happen to be stored in the database. test: known broken test for list(db.config) in python-cffi bindings 2022-02-17T01:55:45Z David Bremner david@tethera.net 2022-02-09T01:01:16Z urn:sha1:e221a4531fa8d317560d568634da695952c65365 As of notmuch 0.34.2 [1], the python-cffi bindings make available the configuration from both a config file and the database when accessing Database.config like a dictionary. It is therefore confusing that the iterator operations only work on the configuration information stored in the database. [1]: d7f95724132bf658fd151630185899737e2ed829 Merge branch 'release' 2021-12-29T18:20:49Z David Bremner david@tethera.net 2021-12-29T18:20:49Z urn:sha1:3eb25c94bd8fe4065d6df6d665ee393cb9a0ad6f lib/open: do not consider .notmuch alone as an existing database. 2021-12-29T18:11:21Z David Bremner david@tethera.net 2021-12-25T21:22:56Z urn:sha1:25e0f5e59293ce961549201fdc74f81a3cc1675c It makes perfect sense for users to want to pre-create .notmuch, e.g. to install hooks, so we should handle the case of a .notmuch directory without an actual xapian database more gracefully.