thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23.4 2016-06-05T11:32:17Z 2016-06-05T11:32:17Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-06-02T16:26:14Z urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb Many of the external links found in the notmuch source can be resolved using https instead of http. This changeset addresses as many as i could find, without touching the e-mail corpus or expected outputs found in tests. 2015-11-19T11:50:58Z Daniel Schoepe daniel@schoepe.org 2015-08-11T07:46:37Z urn:sha1:8b5644e63d49a8841d32130d67c465da0623db74 This patch removes the restriction on notmuch-tag that disallows using both --remove-all and --batch. Combining the two options removes tags on all messages affected by each query before applying the new tags. 2015-09-23T11:03:34Z David Bremner david@tethera.net 2015-09-06T13:15:47Z urn:sha1:6cdd34a4c762c954426f586d514a3e041c1db3b0 I think it would be no real problem to cut and paste the gdb based error message test from count to the other clients modified here, but I'm not currently convinced it's worth the trouble since the code path being tested is almost the the same, and the tests are relatively heavyweight. 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. 2015-05-31T17:14:42Z J. Lewis Muir jlmuir@imca-cat.org 2015-05-27T17:53:52Z urn:sha1:d08af93c65310c2d5ec8033040854f8ff4e5550f The word "setup" is a noun, not a verb. Change occurrences of "setup" where used as a verb to "set up". 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-06-29T17:36:07Z Peter Wang novalazy@gmail.com 2013-06-23T04:23:54Z urn:sha1:e8efa11da90fa47adcbc489638320d61ac98391a Move an error condition specific to the 'tag' command out of parse_tag_command_line so that parse_tag_command_line can be used for the forthcoming 'insert' command. 2013-03-30T22:33:59Z Jani Nikula jani@nikula.org 2013-03-09T14:56:49Z urn:sha1:268666a071db33c5ce6a01b052d9a19c184e10f6 Add --remove-all option to "notmuch tag" to remove all tags from the messages matching query before applying the tag changes. This allows removal of all tags and unconditional setting of the tags of a message: $ notmuch tag --remove-all id:foo@example.com $ notmuch tag --remove-all +foo +bar id:foo@example.com without having to resort to the complicated (and still quoting broken): $ notmuch tag $(notmuch search --output=tags '*' | sed 's/^/-/') \ id:foo@example.com $ notmuch tag $(notmuch search --output=tags '*' | sed 's/^/-/') \ +foo +bar id:foo@example.com 2013-03-30T22:33:40Z Jani Nikula jani@nikula.org 2013-03-09T14:56:48Z urn:sha1:a6822eccaca773aa03473bca490618e30dac24ca