notmuch/test/T040-setup.sh, branch release

test/setup: ignore blank lines in generated config

2023-08-21T22:30:54Z

The presense of the blank lines between sections depends on the version of glib. Strip them before comparison.

CLI/setup: special case single item lists

2022-01-24T13:32:39Z

This matches the heuristic used by "notmuch config set" to decide if something is a list. This change fixes the bug reported at [1]. [1]: id:6O3LTUhoXlrnkPWCtPJCP4cagU7mFVEdyTpcC_37BoSzStlARXDBa7oczy6hB0jyjGjBQvgj_jFV58cw0aNx-jUg1h1O-FQ7820k68C0X4M=@protonmail.com

test/setup: add known broken test for single items

2022-01-24T13:31:00Z

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

CLI+lib: detect missing database in split configurations.

2021-03-27T12:26:14Z

Eventually we want to do all opening of databases in the top level (main function). This means that detection of missing databases needs to move out of subcommands. It also requires updating the library to use the new NO_DATABASE status code.

test/setup: check file output instead of notmuch config list

2021-03-27T12:26:14Z

This allows verification of comments added to new / updated config file.

test/setup: add check for config exists, but no database.

2021-03-18T11:03:19Z

This code path is not currently tested, and will need updating if the location of the xapian database changes.

cli/new: convert to new config framework

2021-02-06T23:52:11Z

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.

gmime-cleanup: remove obsolete gpg_path configuration option and crypto contexts

2019-05-03T09:55:04Z

Note that we do keep ignoring the gpg_path configuration option, though, to avoid breakage of existing installations. It is ignored like any other unknown configuration option, but we at least document that it is ignored so that people who find it in their legacy configs can know that it's safe to drop. signed-off-by: Daniel Kahn Gillmor

test: use $(dirname "$0") for sourcing test-lib.sh

2017-10-20T22:52:49Z

Don't assume the tests are always run from within the source tree.

config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0

2017-07-15T00:23:52Z

gmime 3.0 no longer offers a means to set the path for gpg. Users can set $PATH anyway if they want to pick a differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't much of a reduction in functionality. The one main difference is for people who have tried to use "gpg2" to make use of gpg 2.1, but that isn't usefully co-installable anyway.