thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23 2016-09-30T10:13:54Z 2016-09-30T10:13:54Z Mark Walters markwalters1009@gmail.com 2016-09-29T13:44:04Z urn:sha1:0b138c268641080c766801b4d74db3b693ca6eaa Since doing the Fcc with notmuch insert could be slow (if the indexing takes some time) add a message saying we are doing it. 2016-09-29T11:07:38Z Mark Walters markwalters1009@gmail.com 2016-09-28T10:03:46Z urn:sha1:4266e76eed0e0b2ab8a720b60f8b3cc515fe0aac This updates the docstring for the variable notmuch-fcc-dirs to match the new insert code. 2016-09-26T16:01:31Z Mark Walters markwalters1009@gmail.com 2016-09-25T07:18:10Z urn:sha1:9966720453c72286b5f36a56323244d70202cb26 This tweaks the keybindings in tree-mode. It make b do bounce/resend matching show-mode. Since b was already bound to scroll message pane back, we now use backspace for that. This means space/backspace scroll the message pane forwards/backwards, and page-up/page-down scrolls the tree pane forwards/backwards. 2016-09-25T10:42:01Z Mark Walters markwalters1009@gmail.com 2016-09-18T10:57:32Z urn:sha1:51d27e08555ac3187bd9d5649a0074ba6a9aabce Commit d25d33ff cleaned up some of the tag face code. However, for the face notmuch-tag-deleted it used the test ((class color) (supports :strike-through)) to decide whether to use red strikethrough or inverse-video (emacs in a terminal typically doesn't support red strikethrough, but in X it does). However, it seems that test often returns true even though red strikethrough is not supported. This breaks the tag update code -- the wrong thing is displayed to the user. Thus we make the test explicitly more specific, changing the test to ((class color) (supports :strike-through "red")) 2016-09-24T13:08:24Z Mark Walters markwalters1009@gmail.com 2016-09-19T09:39:49Z urn:sha1:7b2d7d65126b11ce08079b7cf235e1073fb1c22b j is in the global notmuch keymap bound to notmuch jump. In tree-mode it makes sense to close the message pane first (otherwise the new search runs in the small top pane of tree-mode). 2016-09-18T13:57:27Z Mark Walters markwalters1009@gmail.com 2016-09-13T01:45:58Z urn:sha1:a448879e49fb838a302b4e68d73e63c6b75d9175 This stops the (usually incorrect) sigstatus and encstatus buttons appearing when replying in emacs, and updates the test suite to match. Overriding the status button functions is a little unusual but much less intrusive than passing an argument all the way down the call chain. It also makes it clear exactly what it does. We also hide the application/pgp-encrypted part as it can only contain "Version: 1". We do this in notmuch show, which means it also happens when replying. 2016-09-12T11:12:10Z Matt Armstrong marmstrong@google.com 2016-08-14T22:17:42Z urn:sha1:d25d33ff2d818d5a423e07b7f465add9c970dc75 I believe this moves all "anonymous" face specifications in notmuch code into a configurable defface. 2016-09-12T11:08:45Z Matt Armstrong marmstrong@google.com 2016-08-14T22:13:00Z urn:sha1:3856286e21ab4ef282bbb262b700477282327923 While passing a lambda to mapc is idiomatic elisp, dolist is easier to understand, and there are a few other calls to it in this file. 2016-09-12T11:06:00Z Mark Walters markwalters1009@gmail.com 2016-08-06T15:29:34Z urn:sha1:7b7960ea228ca0449e2711377dfdebc23a791147 Previously if notmuch-wash-wrap-lines-length was set then all messages would be wrapped at this value (or window-width if that is smaller). This was done regardless of the message's depth in a thread -- for example, if the n.w.w.l.l is 80 and the messages depth is 20 (so indented 20 by default) the messages text only got 60 characters of space. This commit changes that so a message always gets the full n.w.w.l.l of width regardless of its indentation (unless that goes over window-width of course). 2016-09-12T11:03:34Z Mark Walters markwalters1009@gmail.com 2016-07-11T07:49:19Z urn:sha1:f94921520778ae4005500f5d1b943e2d4ddd3b2a This allows the user to override the mime-type of a part in the show buffer. This takes the simple option of displaying the part with the specified mime-type in its own buffer (in view mode). This avoids further complicating the part handling code. Bound to ". m" (i.e., m in the part map). Then the user can either enter a mime-type (with completion to all mime types that mailcap (and thus notmuch) knows about, or press return for the default choice of text/plain.