thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=master 2024-08-06T09:50:33Z 2024-08-06T09:50:33Z David Bremner david@tethera.net 2023-12-21T17:04:00Z urn:sha1:a691d54280b574035d38f3827d5caca9d0a6ae5b This limitation seems somewhat hard to fix, but at least try to warn users when combining crypto operations with mbox output format. Because the default is --decrypt=auto, the warning is omitted if --decrypt=auto is specified. While this is not great, it seems more wrong to always warn, or to change the default because of this. 2024-06-15T17:46:12Z David Bremner david@tethera.net 2024-05-26T12:52:32Z urn:sha1:0d2a964ea3d0c466d6284dd0b693285941c28440 In [1], Jakub Wilk observes that the current behaviour is confusing since it looks like there are two mailboxes in From, while in fact there is only one. It seems to me that notmuch should at least quote the display-name part of a mailbox if it has "funny" characters in it, and perhaps always quote it. Either way will require changing the indexing code, since the structure is lost when writing the headers to the database. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021614 2023-07-21T09:58:16Z David Bremner david@tethera.net 2023-04-09T14:26:23Z urn:sha1:dfa43a19218ed46f677034ab7bf8b8907a327935 When running the test suite without building first, it is desirable to have the tests consider these variables being undefined as equivalent to the feature not being present, and in particular for the tests not to generate errors. 2022-07-30T11:41:50Z David Bremner david@tethera.net 2022-07-01T21:45:44Z urn:sha1:4612f3eb3dbf16bf98ccbadef77d7a6f6361e692 This introduces a new mandatory key for message structures, namely "duplicate". Per convention in devel/schemata this does _not_ increase the format version. This means that clients are responsible for checking that it exists, and not crashing if it does not. The main functional change is teaching mime_node_open to understand a 'duplicate' argument. Support for --duplicate in notmuch-reply would make sense, but we defer it to a later commit. 2021-09-05T00:07:19Z David Bremner david@tethera.net 2021-08-24T15:17:43Z urn:sha1:2944d5913319056dfec5c23065932fd1c87a96f6 The change in each case is to call notmuch_query_create_with_syntax, relying on the already inherited shared options. As a bonus we get improved error handling from the new query creation API. The remaining subcommand is 'tag', which is a bit trickier. 2021-07-03T23:27:39Z jao jao@gnu.org 2021-07-02T20:44:21Z urn:sha1:13d49b8e16cfbe9ea473754a3f59861cd68549e1 New unit tests for notmuch show --sort, covering the basic use cases. 2017-10-20T22:52:49Z Jani Nikula jani@nikula.org 2017-09-25T20:38:19Z urn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa Don't assume the tests are always run from within the source tree. 2015-08-07T19:56:39Z Tomi Ollila tomi.ollila@iki.fi 2015-08-06T09:13:36Z urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741 The files (test) scripts source (with builtin command `.`) provides information which the scripts depend, and without the `source` to succeed allowing script to continue may lead to dangerous situations (e.g. rm -rf "${undefined_variable}"/*). At the end of all source (.) lines construct ' || exit 1' was added; In our case the script script will exit if it cannot find (or read) the file to be sourced. Additionally script would also exits if the last command of the sourced file exited nonzero. 2014-01-25T00:24:11Z David Bremner david@tethera.net 2014-01-23T12:24:01Z urn:sha1:ecbb29e8cea404faab2ef55b06431942ee329941 We want to return an error status, not 0 or (worse) segfault. 2014-01-25T00:19:50Z David Bremner david@tethera.net 2014-01-23T12:23:59Z urn:sha1:5c526d1737212dd736b1c3fedc6bf5b3493ce436 This test catches a segfault on a syntactically invalid query. It also catches a problem with my initial fix, which still returned 0.