notmuch/test/T055-path-config.sh, branch 0.38.3thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.38.32023-12-06T11:33:05Zlib: clear error message on success in _choose_database_path2023-12-06T11:33:05ZDavid Bremnerdavid@tethera.net2023-12-03T18:56:44Zurn:sha1:b97cd90040a8353e6f94c317af2020f3d6e67a2e
Previously we both found a database and returned a message saying that
the database could not be found (along with a success code). This
change should prevent spurious error output.
test: add known broken test for incorrect error message2023-12-06T11:33:05ZDavid Bremnerdavid@tethera.net2023-12-03T15:41:11Zurn:sha1:5a582e8ed9b9bfd88e63149fb671510bc2b2e9f8
Duplicate bug reported in id:87wmtvcor5.fsf@alyssa.is
The error message is nonsense, because notmuch config list actually
includes the database in those two cases.
lib: add config key INDEX_AS_TEXT2023-04-02T22:21:37ZDavid Bremnerdavid@tethera.net2023-01-06T00:02:04Zurn:sha1:c6733a45c8ff698505ff330d2edce92c90cbc946
Higher level processing as a list of regular expressions and
documentation will follow.
lib/open: create database path in some cases2022-09-03T11:24:43ZDavid Bremnerdavid@tethera.net2022-07-29T11:31:37Zurn: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.path2022-09-03T11:24:43ZDavid Bremnerdavid@tethera.net2022-07-26T01:04:21Zurn: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:43ZDavid Bremnerdavid@tethera.net2022-07-26T00:37:41Zurn: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.sh2022-08-06T12:16:13ZDavid Bremnerdavid@tethera.net2022-07-29T12:19:56Zurn:sha1:7b27119d8ee4ad612b7a7d48b612d15a58d68976
This case statement does nothing.
test: known broken test for top level .notmuch in split configs2022-07-05T11:09:57ZDavid Bremnerdavid@tethera.net2022-01-16T15:25:10Zurn: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 ConfigIterator2022-02-17T01:57:22ZDavid Bremnerdavid@tethera.net2022-02-09T12:28:54Zurn: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 bindings2022-02-17T01:55:45ZDavid Bremnerdavid@tethera.net2022-02-09T01:01:16Zurn: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