notmuch/test/T610-message-property.sh, branch 0.32

Fix typos

2020-08-10T00:14:36Z

test: sort the output of the "prefix" test in T610-message-property

2020-04-24T00:31:37Z

This test extracts values from a (key,value) map where multiple entries can have the same key, and the entries are sorted by key, but not by value. The test incorrectly assumes that the values will be sorted as well, so sort the output.

lib/string_map: fix return type of string_cmp

2019-03-06T01:46:41Z

I can't figure out how checking the sign of a bool ever worked. The following program demonstrates the problem (i.e. for me it prints 1). #include #include int main(int argc, char **argv) { bool x; x = -1; printf("x = %d\n", x); } This seems to be mandated by the C99 standard 6.3.1.2.

lib: Add known broken test for string_map binary search.

2019-03-06T01:46:41Z

Because the string_map functions are not exported, we test via message properties.

test: tests for python bindings get_property / get_properties

2018-05-02T23:30:51Z

These roughly replicate the equivalent C tests, although they rely on the database state created by the former tests, since the python bindings currently provide read-only access to properties.

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.

cli/dump: don't include tags when not asked for

2017-06-01T10:07:32Z

Add in the analogous test for tags that is given for properties a few lines below.

test: add known broken test --include=properties

2017-06-01T10:03:06Z

Reported in [1], --include=properties currently implies --include=tags, but it should not. [1] id:87y3u8vjbo.fsf@tethera.net

add property: query prefix to search for specific properties

2016-09-21T21:14:25Z

We want to be able to query the properties directly, like: notmuch count property:foo=bar which should return a count of messages where the property with key "foo" has value equal to "bar".

cli: optionally restore message properties from dump file

2016-09-21T21:14:25Z

This somewhat mimics the config line parsing, except there can be arbitrarily many key value pairs, so one more level of looping is required.