thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.18 2014-03-26T00:22:03Z 2014-03-26T00:22:03Z Jani Nikula jani@nikula.org 2014-03-19T16:44:50Z urn:sha1:31a6333aa46fc8125d2fe1effd6fddf48e47c14e This makes the from guessing agnostic to header folding by spaces or tabs. 2014-03-09T13:13:17Z Jani Nikula jani@nikula.org 2014-02-03T19:51:42Z urn:sha1:998a8a95c3cd19950b78c50912345669952ba3eb The guess_from_received_header() function had grown quite big. Chop it up into smaller functions. No functional changes. 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-08-27T10:57:36Z John Lenz lenz@math.uic.edu 2013-07-02T00:19:42Z urn:sha1:f735a85c28a3c6b6e38ecaba04029a917c6d6830 For my client, the largest bottleneck for displaying large threads is exporting each html part individually since by default notmuch will not show the json parts. For large threads there can be quite a few parts and each must be exported and decoded one by one. Also, I then have to deal with all the crazy charsets which I can do through a library but is a pain. Therefore, this patch adds an --include-html option that causes the text/html parts to be included as part of the output of show. diff man/man1/notmuch-show.1 2013-08-17T07:06:08Z Austin Clements amdragon@MIT.EDU 2013-08-16T15:35:43Z urn:sha1:dc51bf0ad4ce84414e79d2f30752502f7c0d46c0 Previously, reply's default text format used an odd mix of RFC 2045 MIME encoding for the reply template's body and some made-up RFC 2822-like UTF-8 format for the headers. The intent was to present the headers to the user in a nice, un-encoded format, but this assumed that whatever ultimately sent the email would RFC 2047-encode the headers, while at the same time the body was already RFC 2045 encoded, so it assumed that whatever sent the email would *not* re-encode the body. This can be fixed by either producing a fully decoded UTF-8 reply template, or a fully encoded MIME-compliant RFC 2822 message. This patch does the latter because it is a) Well-defined by RFC 2822 and MIME (while any UTF-8 format would be ad hoc). b) Ready to be piped to sendmail. The point of the text format is to be minimal, so a user should be able to pop up the template in whatever editor they want, edit it, and push it to sendmail. c) Consistent with frontend capabilities. If a frontend has the smarts to RFC 2047 encode the headers before sending the mail, it probably has the smarts to RFC 2047 decode them before presenting the template to a user for editing. Also, as far as I know, nothing automated consumes the reply text format, so changing this should not cause serious problems. (And if anything does still consume this format, it probably gets these encoding issues wrong anyway.) 2013-08-17T07:05:44Z Austin Clements amdragon@MIT.EDU 2013-08-16T15:35:42Z urn:sha1:6cdab6e0b77041791f70345ac729d63d865bae5e Previously, the References header code seemed to assume notmuch_message_get_header would return NULL if the header was not present, but it actually returns "". As a result of this, it was inserting an unnecessary space when concatenating an empty or missing original references header with the new reference. This shows up in only two tests because the text reply format later passes the whole reply template through g_mime_filter_headers, which has the side effect of stripping out this extra space. 2013-08-13T15:44:08Z Austin Clements amdragon@MIT.EDU 2013-08-12T18:40:36Z urn:sha1:013d11c9f7c7f7876faf5035a5acb60924daf3c6 Given how long it took me to figure out why we pass the reply headers through g_mime_filter_headers, it's worth a comment. 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. 2012-12-16T21:21:32Z Austin Clements amdragon@MIT.EDU 2012-12-16T03:17:26Z urn:sha1:f6adf6615c51d878a61b1f37afb4c501ba31e4de