thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.13 2012-05-15T21:18:45Z 2012-05-15T21:18:45Z David Bremner bremner@debian.org 2012-05-15T21:18:45Z urn:sha1:3fb08bc1259f9a9d80617542da64443e7e63a6c4 2012-05-08T17:49:08Z David Bremner bremner@debian.org 2012-05-08T17:49:08Z urn:sha1:a4b10675bfe6ee90d84b9880b59c4f5ff15eed3a 2012-04-28T13:47:27Z Peter Wang novalazy@gmail.com 2012-04-14T01:41:06Z urn:sha1:0ff54ab712c24263a1dd66ffd2b4266371f24830 Document the 'config list' command and its output. 2012-04-08T02:05:56Z Mark Walters markwalters1009@gmail.com 2012-04-07T16:10:06Z urn:sha1:903327279c38d6750e8347eba23262fa487c6951 This moves notmuch show to the --exclude=(true|false) naming scheme. When exclude=false show returns all threads that match including those that only match in an excluded message. The excluded messages are flagged. When exclude=true the behaviour depends on whether --entire-thread is set. If it is not set then show only returns the messages which match and are not excluded. If it is set then show returns all messages in the threads that match in a non-excluded message, flagging the excluded messages in these threads. The rationale is that it is awkward to use a thread with some missing messages. 2012-04-08T02:05:41Z Mark Walters markwalters1009@gmail.com 2012-04-07T16:10:05Z urn:sha1:fd62a25f91c6ecdd6d60c86b4439321b8e84b309 This commit replaces the --no-exclude option with a --exclude=(true|false|flag) option. The default is to omit the excluded messages. The flag option only makes sense if output=summary (as otherwise there is nowhere to print the flag). In summary output exclude=false and exclude=flag give almost identical output: they differ in that with the exclude=flag option the match count (i.e., the x in [x/n] in the output) is the number of matching non-excluded messages rather than the number of matching messages. Note this changes the default for output=summary when no --exclude= option is given: it used to default to flag and now defaults to true (i.e. omit excluded messages). This is neccesary to keep the cli output uncluttered and for speed reasons. 2012-04-08T02:05:18Z Mark Walters markwalters1009@gmail.com 2012-04-07T16:10:04Z urn:sha1:785c1e497f05cb89365669fea33cfbf9078a4b12 Move the option --no-exclude to the --exclude= scheme. Since there is no way to flag messages only true and false are implemented. Note that, for consistency with other commands, this is implemented as a keyword option rather than a boolean option. 2012-03-20T01:48:24Z David Bremner bremner@debian.org 2012-03-20T01:48:24Z urn:sha1:2ee1d8e1c70ce20728bc3faada389a4802636352 Conflicts: NEWS Conflicts resolved by hand for date of 0.12 release. 2012-03-20T01:28:17Z David Bremner bremner@debian.org 2012-03-20T01:28:17Z urn:sha1:c302bfa2f63fc1e59df6f842fe65d4d6ea258a33 There may be a few NEWS changes after this, but no code (hopefully). 2012-03-20T00:58:20Z Adam Wolfe Gordon awg+notmuch@xvx.ca 2012-03-18T16:32:39Z urn:sha1:92b48c8c98e29ee54ce603931b3abf4c7b521840 2012-03-20T00:57:25Z Adam Wolfe Gordon awg+notmuch@xvx.ca 2012-03-18T16:32:38Z urn:sha1:71855b72f702e8751c35f71c787a00d64a77b663