mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
82e1279790
In [1] Ian observed that notmuch setup was inconsistent with notmuch config set when adding single items, namely adding an unneeded semi-colon at the end. This test replicates that bug. [1]: id:6O3LTUhoXlrnkPWCtPJCP4cagU7mFVEdyTpcC_37BoSzStlARXDBa7oczy6hB0jyjGjBQvgj_jFV58cw0aNx-jUg1h1O-FQ7820k68C0X4M=@protonmail.com
47 lines
1.6 KiB
Bash
Executable file
47 lines
1.6 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
|
|
test_description='"notmuch setup"'
|
|
. $(dirname "$0")/test-lib.sh || exit 1
|
|
|
|
test_begin_subtest "Notmuch new without a config suggests notmuch setup"
|
|
output=$(notmuch --config=new-notmuch-config new 2>&1)
|
|
test_expect_equal "$output" "\
|
|
Error: cannot load config file.
|
|
Try running 'notmuch setup' to create a configuration."
|
|
|
|
test_begin_subtest "Create a new config interactively"
|
|
notmuch --config=new-notmuch-config > log.${test_count} <<EOF
|
|
Test Suite
|
|
test.suite@example.com
|
|
another.suite@example.com
|
|
|
|
/path/to/maildir
|
|
foo bar
|
|
baz
|
|
EOF
|
|
|
|
expected_dir=$NOTMUCH_SRCDIR/test/setup.expected-output
|
|
test_expect_equal_file ${expected_dir}/config-with-comments new-notmuch-config
|
|
|
|
test_begin_subtest "setup consistent with config-set for single items"
|
|
test_subtest_known_broken
|
|
# note this relies on the config state from the previous test.
|
|
notmuch --config=new-notmuch-config config list > list.setup
|
|
notmuch --config=new-notmuch-config config set search.exclude_tags baz
|
|
notmuch --config=new-notmuch-config config list > list.config
|
|
test_expect_equal_file list.setup list.config
|
|
|
|
test_begin_subtest "notmuch with a config but without a database suggests notmuch new"
|
|
notmuch 2>&1 | notmuch_dir_sanitize > OUTPUT
|
|
cat <<EOF > EXPECTED
|
|
Notmuch is configured, but no database was found.
|
|
You probably want to run "notmuch new" now to create a database.
|
|
|
|
Note that the first run of "notmuch new" can take a very long time
|
|
and that the resulting database will use roughly the same amount of
|
|
storage space as the email being indexed.
|
|
|
|
EOF
|
|
test_expect_equal_file EXPECTED OUTPUT
|
|
|
|
test_done
|