thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.22_rc0 2015-08-14T16:23:49Z 2015-08-14T16:23:49Z David Bremner david@tethera.net 2015-04-05T22:39:55Z urn:sha1:f76d8f82dd004cf14426a91e8a80dcd2a4b97317 The function notmuch_exit_if_unmatched_db_uuid is split from notmuch_process_shared_options because it needs an open notmuch database. There are two exceptional cases in uuid handling. 1) notmuch config and notmuch setup don't currently open the database, so it doesn't make sense to check the UUID. 2) notmuch compact opens the database inside the library, so we either need to open the database just to check uuid, or change the API. 2015-06-01T05:32:54Z David Bremner david@tethera.net 2015-04-05T13:13:03Z urn:sha1:0018a8d787a98f80c665061daa9b0c73839d3666 Unfortunately it seems trickier to support --config globally The non-trivial changes are in notmuch.c; most of the other changes consists of blindly inserting two lines into every subcommand. 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-03-29T18:12:28Z urn:sha1:4c62d9366a389b7ddca796009d1dfe6a885cfde0 We rely completely on zlib to do the right thing in detecting gzipped input. Since our dump format is chosen to be 7 bit ascii, this should be fine. 2014-03-30T22:23:16Z Jani Nikula jani@nikula.org 2014-03-25T17:48:57Z urn:sha1:3863755f6d9f3e7666c1484822384c036a4426c3 Also expose the dump function to the rest of notmuch. No functional changes, except for slight improvement in error handling. 2014-01-18T18:45:26Z Jani Nikula jani@nikula.org 2014-01-10T21:28:53Z urn:sha1:c7453773064efbd0b2cd17b15ba483edbd28ce1e Apart from the status codes for format mismatches, the non-zero exit status codes have been arbitrary. Make the cli consistently return either EXIT_SUCCESS or EXIT_FAILURE. 2013-03-08T11:54:41Z Jani Nikula jani@nikula.org 2013-03-03T21:55:09Z urn:sha1:4ef2106792439f5ade157b3ba3b8f7fa86fcb3ed This allows specifying config file as a top level argument to notmuch, and generally makes it possible to override config file options in main(), without having to touch the subcommands. If the config file does not exist, one will be created for the notmuch main command and setup and help subcommands. Help is special in this regard; the config is created just to avoid errors about missing config, but it will not be saved. This also makes notmuch config the talloc context for subcommands. 2013-03-07T13:39:12Z Jani Nikula jani@nikula.org 2013-03-03T21:55:08Z urn:sha1:e76f6517de020783d828be59f461f1d4f465c4b4 We now have a notmuch_config_is_new() function to query whether a config was created or not. Change the notmuch_config_open() is_new parameter into boolean create_new to determine whether the function should create a new config if one doesn't exist. This reduces the complexity of the API. 2013-01-07T02:40:32Z Austin Clements amdragon@MIT.EDU 2013-01-06T20:22:41Z urn:sha1:425e2bc81263230df301c67d93c64ff9685ff840 This switches the new batch-tag format away from using a home-grown hex-encoding scheme for message IDs in the dump to simply using Xapian queries with Xapian quoting syntax. This has a variety of advantages beyond presenting a cleaner and more consistent interface. Foremost is that it will dramatically simplify the quoting for batch tagging, which shares the same input format. While the hex-encoding is no better or worse for the simple ID queries used by dump/restore, it becomes onerous for general-purpose queries used in batch tagging. It also better handles strange cases like "id:foo and bar", since this is no longer syntactically valid. 2013-01-07T02:39:23Z Austin Clements amdragon@MIT.EDU 2013-01-06T20:22:37Z urn:sha1:baca1219af0ef1f81985759e868a68e9dd78e0d1 Previously, restore would abort if a message ID in the dump was missing. Furthermore, it would only report this as a warning. This patch makes it distinguish abort-worthy lookup failures like out-of-memory from non-fatal failure to find a message ID. The former is reported as an error and causes restore to abort, while the latter is reported as a warning and does not cause an abort. This restores 0.14's non-fatal handling of missing message IDs in restore (though 0.14 also considered serious errors non-fatal; we retain the new and better handling of serious errors). 2013-01-06T14:04:19Z David Bremner bremner@debian.org 2012-12-26T19:36:33Z urn:sha1:d705a6a45bf691b60101203bd09a459be255dceb This patch corrects several undesirable behaviours: 1) Empty files were not detected, leading to buffer read overrun. 2) An initial blank line cause restore to silently abort 3) Initial comment line caused format detection to fail