thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.18 2014-04-12T10:59:44Z 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-03-29T01:14:51Z urn:sha1:3c13bc0321baaf340663779d6fce2b1f34c1c2c3 The main goal is to support gzipped output for future internal calls (e.g. from notmuch-new) to notmuch_database_dump. The additional dependency is not very heavy since xapian already pulls in zlib. We want the dump to be "atomic", in the sense that after running the dump file is either present and complete, or not present. This avoids certain classes of mishaps involving overwriting a good backup with a bad or partial one. 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-03-30T22:22:21Z Jani Nikula jani@nikula.org 2014-03-25T17:07:49Z urn:sha1:2a79d81211664ca3f0cd1a847795d48bd66b8a3d No functional changes, except for slight improvement in error handling. 2014-01-24T12:52:09Z David Bremner david@tethera.net 2014-01-23T13:02:46Z urn:sha1:f4167e6de86d071cd94721c2acc1397bf291a13c Although we didn't formally deprecate the old format, the new one has been available for a year. 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:40:01Z Austin Clements amdragon@MIT.EDU 2013-01-06T20:22:40Z urn:sha1:d08c714b6a172cf0018bee4f60aff069d5508d4e When we switch to using regular Xapian queries in the dump format, \n will cause problems, so we disallow it. Specially, while Xapian can quote and parse queries containing \n without difficultly, quoted queries containing \n still span multiple lines, which breaks the line-orientedness of the dump format. Strictly speaking, we could still round-trip these, but it would significantly complicate restore as well as scripts that deal with tag dumps. This complexity would come at absolutely no benefit: because of the RFC 2822 unfolding rules, no amount of standards negligence can produce a message with a message ID containing a line break (not even Outlook can do it!). Hence, we simply disallow it. 2012-12-08T14:40:54Z David Bremner bremner@debian.org 2012-06-14T22:08:42Z urn:sha1:bfe66da4321ce63b6fb3693eddf809e2e0532888 sup is the old format, and remains the default, at least until restore is converted to parse this format. Each line of the batch-tag format is modelled on the syntax of notmuch tag: - "notmuch tag" is omitted from the front of the line - The dump format only uses query strings of a single message-id. - Each space seperated tag/message-id is 'hex-encoded' to remove trouble-making characters. - It is permitted (and will be useful) for there to be no tags before the query. In particular this format won't have the same problem with e.g. spaces in message-ids or tags; they will be round-trip-able.