notmuch/test/T050-new.sh, branch 0.32 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.32 2021-03-18T10:57:38Z test: add known broken test for long directory bug 2021-03-18T10:57:38Z David Bremner david@tethera.net 2021-03-18T01:20:35Z urn:sha1:dcd4df2cc01e0628ea6f407687ae6e9eb07bf8fd In [1] Gregor Zattler explained the results of his hard work tracking down a bug in notmuch with long directories. This test duplicates the bug. [1]: id:20210317194728.GB5561@no.workgroup test: clean up some extra whitespace. 2021-03-12T11:19:14Z David Bremner david@tethera.net 2021-01-16T01:29:17Z urn:sha1:97fadd0645e908ff8322577a983dc710bfda33d6 The extra space is mainly just untidy. cli/new: convert to new config framework 2021-02-06T23:52:11Z David Bremner david@tethera.net 2021-01-02T17:10:39Z urn:sha1:0d3bef312dd624225825e6fe175ea8830c1c9e39 In addition to the same type of changes as converting other subcommands, add the possibility of creating a database at the top level. It would probably make sense to use this for insert as well. test: drop use of db_ending 2020-08-01T23:27:30Z David Bremner david@tethera.net 2020-07-30T00:01:30Z urn:sha1:99a7aac8f2af6f3adb8f816be46ee33eb1d57515 This will allow the dropping of the test for the default ending from configure. test: fix hardcoded paths in T050-new.sh 2018-05-26T23:46:44Z David Bremner david@tethera.net 2018-05-26T23:46:44Z urn:sha1:46cf1a98f3616f1a503f7b04c0f6980930aedaf2 The previous paths will fail almost everywhere. test: use --full-scan in T050-new.sh 2018-05-22T16:29:59Z David Bremner david@tethera.net 2018-04-29T23:19:42Z urn:sha1:84b29637261adc3c647e078ad320258b371bd36b Wherever the test relies on directories being scanned, this option should be used to avoid skipping them due to mtimes on directories matching the database. test: add tests for notmuch new --full-scan 2018-05-22T16:29:48Z David Bremner david@tethera.net 2018-04-29T23:19:41Z urn:sha1:d1acff615306a732054b3cc2bec502a419ed861a Most of these just check that adding the flag does not break existing functionality. The one test that does check the full-scan functionality had to be rewritten to output debugging info. lib: choose oldest message when breaking reference loops 2018-04-24T02:00:20Z David Bremner david@tethera.net 2018-04-20T14:59:48Z urn:sha1:491b1f4b4082bee18418942846ec6508856be7b4 This preserves a sensible thread order test: add known broken test for thread ordering from a loop 2018-04-24T02:00:20Z David Bremner david@tethera.net 2018-04-14T01:46:09Z urn:sha1:4e085b6d92909b8f6d4a4b18ccd97fac8b7df620 The previous loop handling code chooses the last message in the message list, which turns out to be the last in date order. See the comment in _notmuch_thread_create. lib: break reference loop by choosing arbitrary top level msg 2018-04-20T14:23:31Z David Bremner david@tethera.net 2018-04-14T01:08:05Z urn:sha1:9293d6da27494d7b607c945c6678bc890749b94f Other parts of notmuch (e.g. notmuch show) expect each thread to contain at least one top level message, and crash if this expectation is not met.