thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.16 2013-03-08T11:54:41Z 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 2012-12-31T01:12:11Z David Bremner bremner@debian.org 2012-12-17T03:14:42Z urn:sha1:e40bb1561a6036fcc6a8ff3510dc5061a0ea31e8 This gives line numbers for better debugging. 2012-12-23T03:19:43Z David Bremner bremner@debian.org 2012-12-16T20:05:58Z urn:sha1:0919ea4c553bde840a0f37c6076712f345bcac7d This lets the high level code in notmuch restore be ignorant about what the lower level code is doing as far as allocating memory. 2012-12-23T03:13:15Z David Bremner bremner@debian.org 2012-12-16T19:58:15Z urn:sha1:ba4e8565294fc0a197b4c08082ad912c31888008 The memory usage discipline of tag_op_list_t is never to free the internal array of tag operations before freeing the whole list, so it makes sense to take advantage of hierarchical de-allocation by talloc. By not relying on the context passed into tag_parse_line, we can allow tag_op_list_t structures to live longer than that context. 2012-12-23T03:11:47Z David Bremner bremner@debian.org 2012-12-16T20:04:21Z urn:sha1:77b4ec70ecb9fdcbf9afd31f3663bd0135806bda Previously notmuch_restore_command returned 0 if tag_message returned a non-zero (failure) value. This is wrong, since non-zero status indicates something mysterious went wrong with retrieving the message, or applying it. There was also a failure to check or propagate the return value from tag_op_list_apply in tag_message. 2012-12-09T17:33:34Z David Bremner bremner@debian.org 2012-12-08T21:57:10Z urn:sha1:ea85725450de3e65f1db35112fd621c11dd1cab9 In English, (unlike German) one does not capitalize the first word after a colon.