notmuch/test/T030-config.sh, branch 0.38 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.38 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/config: use g_key_file_get_string to read config values 2021-12-04T16:17:09Z David Bremner david@tethera.net 2021-09-30T18:59:54Z urn:sha1:18cdd21b8b2ef056062700607eade43909c32cd2 Unlike the previous g_key_file_get_value, this version processes escape codes for whitespace and \. The remaining two broken tests from the last commit are because "notmuch config get" treats every value as a list, and thus the previously introduces stripping of leading whitespace applies. test: known broken tests for escape characters in config files. 2021-12-04T16:16:47Z David Bremner david@tethera.net 2021-09-30T18:28:34Z urn:sha1:482bd3a46de34c5f6c5cae3696fd56ffdadc6299 glib generates the following escape characters with their usual meanings: \n, \t, \r, and \\, along with \s for _leading_ spaces. Currently notmuch fails to unescape these on reading the config files. These tests demonstrate this bug; the one new test that passes is because apparently glib only escapes tabs at the beginning of a key. rename built_with.sexpr_query to built_with.sexp_queries 2021-12-04T00:06:06Z David Bremner david@tethera.net 2021-10-30T18:49:20Z urn:sha1:b264a49be3dccb7d110eae6420019a052f1f665b It is confusing to use two different names (sexp vs sexpr) when compared with the command line option --query=sexp and (furthermore) singular vs plural when compared with the man page title. configure: optional library sfsexp 2021-09-05T00:07:19Z David Bremner david@tethera.net 2021-08-24T15:17:11Z urn:sha1:a83ad52da40b51b8419cae3c9ce1517ac33e547c The configure part is essentially the same as the other checks using pkg-config. Since the optional inclusion of this feature changes what options are available to the user, include it in the "built_with" pseudo-configuration keys. Merge tag 'debian/0.32.3-1' 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] CLI/config: restore "notmuch config get built_with.*" 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'. test/config: add tests for built_with 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. lib/config: add NOTMUCH_CONFIG_AUTOCOMMIT 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. lib/config: canonicalize paths relative to $HOME. 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.