thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.36-1 2022-02-17T01:57:22Z 2022-02-17T01:57:22Z David Bremner david@tethera.net 2022-02-09T12:28:54Z urn:sha1:9ddd13f75827f4972872c8766320c7cb80b1819b This returns all of the config keys with non-empty values, not just those that happen to be stored in the database. 2022-01-15T19:59:39Z David Bremner david@tethera.net 2021-12-25T13:33:05Z urn:sha1:fad2e7540bf9309bfb335650ded753e9ed085eff If we know the configuration is split, but there is no mail root defined, this indicates a (lack of) configuration error. Currently this can only arise in XDG configurations. 2022-01-09T23:34:58Z David Bremner david@tethera.net 2022-01-09T23:34:58Z urn:sha1:63d3b2b5cf8702b5fecea77392ce46f8a8249175 notmuch 0.34.3 release 2022-01-09T19:16:51Z David Bremner david@tethera.net 2022-01-08T21:21:43Z urn:sha1:8b737af28bc377db3e661a5744f3b7479b7ce485 The previous (pre-0.34.2) constructor searched for a config file but only if the database path was not specified, and only to retrieve database.path. Neither of the available options (CONFIG.SEARCH or CONFIG.NONE) matches this semantics exactly, but CONFIG.SEARCH causes less breakage for people who relied on the old behaviour to set their database.path [1]. Since it also seems like the friendlier option in the long run, this commit switches to CONFIG.SEARCH as default. This requires a certain amount of updating the pytest tests, but most users will actually have a config file, unlike the test environment. [1]: id:87fsqijx7u.fsf@metapensiero.it 2022-01-09T13:20:56Z David Bremner david@tethera.net 2022-01-09T13:20:56Z urn:sha1:22e04ed01acc115b7fb25b60231014f585f11c4a 2022-01-08T20:29:41Z David Bremner david@tethera.net 2022-01-08T14:03:16Z urn:sha1:9e7ea628e6bddbd7345d053a3daf14af74896cc2 If we return regular Message objects, python will try to destroy them, and the underlying notmuch object, causing e.g. the crash [1]. [1]: id:87sfu6utxg.fsf@tethera.net 2022-01-01T15:48:40Z David Bremner david@tethera.net 2022-01-01T14:36:43Z urn:sha1:9cc026f3daaa7731527787f8c7e729c0a08c456c Existing users of the legacy python bindings use message.get_flags(Message.FLAG.MATCH) to determine which messages in a thread matched. Since the bindings don't provide get_flags anymore, they should provide a property analogous to the existing "excluded" property. 2021-12-05T13:08:48Z David Bremner david@tethera.net 2021-10-31T10:03:54Z urn:sha1:f17d75b83c90ae4ea75f79377f3acb873b9e564e The main idea is to replace the hack of copying version.txt into the bindings source with a generated _notmuch_config.py file. This will mean that the bindings only build after configuring and building notmuch itself. Given those constraints, "pip install ." should work. 2021-12-05T12:53:39Z Floris Bruynooghe flub@devork.be 2021-11-06T11:02:37Z urn:sha1:ca4e1d885b0d9dcdeb45ad6f2829f88dafc7949c The python exception class was incorrectly loading the error message which resulted in unprintable exception objects. 2021-12-04T12:42:31Z David Bremner david@tethera.net 2021-10-30T16:22:35Z urn:sha1:d7f95724132bf658fd151630185899737e2ed829 Since release 0.32, libnotmuch provides searching for database and configuration paths. This commit changes the python module notmuch2 to use those facilities. This fixes the bug reported in [1], along with a couple of the deprecation warnings in the python bindings. Database.default_path is deprecated, since it no longer faithfully reflects what libnotmuch is doing, and it is also no longer used in the bindings themselves. This commit choose the default of config=CONFIG.EMPTY (equivalent to passing "" to notmuch_database_open_with_config). This makes the change upward compatible API-wise (at least as far as the test suite verifies), but changing the default to CONFIG.SEARCH would probably be more convenient for bindings users. [1]: id:87h7d4wp6b.fsf@tethera.net