thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.26.2 2016-09-04T11:23:14Z 2016-09-04T11:23:14Z Mark Walters markwalters1009@gmail.com 2016-09-03T22:59:43Z urn:sha1:fce8146a8b738f2317034fee6236cdbd3597849b With all the preparation it is now simple to add the actual insert code. Since insert can fail for many reasons we let the user decide interactively deal with it. We modify test-lib.el to set file fcc, so that all the old tests and emacs_fcc_message from test-lib.sh still work 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. 2016-03-26T12:03:54Z Tomi Ollila tomi.ollila@iki.fi 2016-03-19T15:50:29Z urn:sha1:cc369779abc6599a758ed60dc17d2f3862bdcacf in d27d90875dfb1 (2016-02-20) notmuch-mua-reply-insert-header-p-function was set to notmuch-show-reply-insert-header-p-never as its default was changed to something else. Now that default is set back to *-never so this change done in d27d90875dfb1 is not needed anymore. 2016-02-21T12:37:48Z David Edmondson dme@dme.org 2016-02-20T18:24:40Z urn:sha1:d27d90875dfb16720de624a57387451665882c19 Add a customizable function specifying which parts get a header when replying, and give some sensible possiblities. These are, 1) all parts except multipart/*. (Subparts of a multipart part do receive a header button.) 2) only included text/* parts. 3) Exactly as in the show buffer. 4) None at all. This means the reply contains a mish-mash of all the original message's parts. In the test suite we set the choice to option 4 to match the previous behaviour. 2016-01-29T21:45:46Z David Bremner david@tethera.net 2015-08-16T17:41:12Z urn:sha1:ef30770dfa0fbef4e91ec90d6ce21b5a55b15375 Test the ability of notmuch-mua-mail to send S/MIME signed (and encrypted) messages; this really relies on existing functionality in message-mode. The generated keys and messages will later be useful for testing the notmuch CLI. 2014-09-21T19:23:45Z Austin Clements amdragon@MIT.EDU 2014-04-21T18:37:39Z urn:sha1:f4cdabccd0e75d94d7f6f4d50684afc67bbf7f0d The test of viewing 8bit messages is known-broken. The rest pass, but for very fragile reasons. The next several commits will fix the known-broken test and make our charset handling robust. 2014-09-21T19:12:52Z David Bremner david@tethera.net 2014-09-20T05:41:35Z urn:sha1:b4892677016c7a994dea75b8ea71bbde92ac17cb Previously we did this for a single test, but some other proposed tests ( id:1398105468-14317-3-git-send-email-amdragon@mit.edu ) show similar breakage when switching renderers. 2014-07-13T15:33:53Z David Bremner david@tethera.net 2014-05-09T00:20:07Z urn:sha1:eed6c75556e18d943ac690598edceef0c4ee59d5 The unread/read changes will use the post-command-hook. test_emacs does not call the post-command-hook. This adds a notmuch-test-progn which takes a list of commands as argument and executes them in turn but runs the post-command-hook after each one. The caller can batch operations (ie to stop post-command-hook from being interleaved) by wrapping the batch of operations inside a progn. We also explicitly run the post-command-hook before getting the output from a test; this makes sense as this will be a place the user would be seeing the information. 2014-03-24T22:48:04Z Mark Walters markwalters1009@gmail.com 2014-03-22T11:51:09Z urn:sha1:941e172724188eb0f65bc05035a0a6871a70ba72 This allows (and requires) the original-tags to be passed along with the current-tags to be passed to notmuch-tag-format-tags. This allows the tag formatting to show added and deleted tags.By default a removed tag is displayed with strike-through in red (if strike-through is not available, eg on a terminal, inverse video is used instead) and an added tag is displayed underlined in green. If the caller does not wish to use the new feature it can pass current-tags for both arguments and, at this point, we do exactly that in the three callers of this function. Note, we cannot tidily allow original-tags to be optional because we would need to distinguish nil meaning "we are not specifying original-tags" from nil meaning there were no original-tags (an empty list). We use this in subsequent patches to make it clear when a message was unread when you first loaded a show buffer (previously the unread tag could be removed before a user realised that it had been unread). The code adds into the existing tag formatting code. The user can specify exactly how a tag should be displayed normally, when deleted, or when added. Since the formatting code matches regexps a user can match all deleted tags with a ".*" in notmuch-tag-deleted-formats. For example setting notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show deleted tags at all. All the variables are customizable; however, more complicated cases like changing the face depending on the type of display will require custom lisp. Currently this overrides notmuch-tag-deleted-formats for the tests setting it to '((".*" nil)) so that they get removed from the display and, thus, all tests still pass. 2014-01-12T21:08:14Z David Bremner david@tethera.net 2014-01-11T17:25:39Z urn:sha1:b4f3be53c8789485d63aafde03b5f5a7e5d86592 In some environments (at least Hurd), process-attributes is unimplimented and always returns nil. This ends up causing test failures (see e.g. id:87a9ffofsc.fsf@zancas.localnet). Historically and according to POSIX 1003.1-2001, a signal of 0 can be used to check the validity of a pid. This seems less heinous than parsing the output of ps(1).