thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.13 2012-05-05T13:11:57Z 2012-05-05T13:11:57Z Austin Clements amdragon@MIT.EDU 2012-04-30T16:25:33Z urn:sha1:5fddc07dc31481453c1af186bf7da241c00cdbf1 It has been a long-standing issue that notmuch_database_open doesn't return any indication of why it failed. This patch changes its prototype to return a notmuch_status_t and set an out-argument to the database itself, like other functions that return both a status and an object. In the interest of atomicity, this also updates every use in the CLI so that notmuch still compiles. Since this patch does not update the bindings, the Python bindings test fails. 2012-04-28T12:27:33Z Justus Winter 4winter@informatik.uni-hamburg.de 2012-04-22T12:07:53Z urn:sha1:6f7469f54744656f90ce215f365d5731e16acd3c Adapt the notmuch binaries source to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de> 2012-04-15T12:42:15Z Austin Clements amdragon@MIT.EDU 2012-04-08T00:57:50Z urn:sha1:2886af551eaefb0ddc841753c11de6973e4baff0 Setting these to NULL is equivalent to the empty string now. 2012-04-15T12:42:15Z Austin Clements amdragon@MIT.EDU 2012-04-08T00:57:49Z urn:sha1:67da35222c73672d61050c0561757c0b739e9195 Many formats don't need these, so it's more convenient if they don't have to set them at all. 2012-04-15T12:42:15Z Austin Clements amdragon@MIT.EDU 2012-04-08T00:57:46Z urn:sha1:b92f15d014604452c148e75b5b8bd38b3f382f20 show_message used to have a compatibility path for old-style formatters. This removes that. 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-03-31T11:17:20Z Austin Clements amdragon@MIT.EDU 2012-03-27T21:59:50Z urn:sha1:ea4fd50f45b0bc0888070125c632ea2326eb18f7 Previously, show and reply had separate implementations of decoding and printing text parts. Now both use show's implementation, which was more complete. Show's implementation has been extended with an option to add reply quoting to the extracted part (this is implemented as a named flag to avoid naked booleans, even though it's the only flag it can take). 2012-03-20T00:53:53Z Adam Wolfe Gordon awg+notmuch@xvx.ca 2012-03-18T16:32:36Z urn:sha1:1904b01b96c1b731afb9649e7b5bceffce901b88 This new JSON format for replies includes headers generated for a reply message as well as the headers of the original message. Using this data, a client can intelligently create a reply. For example, the emacs client will be able to create replies with quoted HTML parts by parsing the HTML parts. 2012-03-18T12:14:22Z Austin Clements amdragon@MIT.EDU 2012-03-06T18:48:43Z urn:sha1:b1130bc71c02efb504ad723b56f86618fd186a67 This is fully compatible for root and leaf parts, but now has proper support for interior parts. This requires some design decisions that were guided by what I would want if I were to save a part. Specifically: - Leaf parts are printed without headers and with transfer decoding. This is what makes sense for saving attachments. (Furthermore, the transfer decoding is necessary since, without the headers, the caller would not be able to interpret non-transfer-decoded output.) - Message parts are printed with their message headers, but without enclosing part headers. This is what makes sense for saving a message as a whole (which is a message part) and for saving attached messages. This is symmetric for whole messages and for attached messages, though we special-case the whole message for performance reasons (and corner-case correctness reasons: given malformed input, GMime may not be able to reproduce it from the parsed representation). - Multipart parts are printed with their headers and all child parts. It's not clear what the best thing to do for multipart is, but this was the most natural to implement and can be justified because such parts can't be interpreted without their headers. As an added benefit, we can move the special-case code for part 0 into the raw formatter. 2012-03-18T12:14:21Z Austin Clements amdragon@MIT.EDU 2012-03-06T18:48:42Z urn:sha1:7e1742a82c4b52f5337d8db53347d547a4ac67b4 Just code motion.