thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.30 2020-06-06T10:55:58Z 2020-06-06T10:55:58Z Tomi Ollila tomi.ollila@iki.fi 2020-05-24T19:17:56Z urn:sha1:ed40579ad3882e6f9bbe9b1ba5e707ab289ca203 Fixed emacs docstrings to be consistent. No functional change. - removed some (accidental) indentation - removed some trailing newlines - added trailing periods where missing (some exclusions) 2020-04-27T10:36:10Z Jonas Bernoulli jonas@bernoul.li 2020-04-25T20:18:07Z urn:sha1:11ac932a4503872c19987b843d58513c4b9ef76f Starting with Emacs 27 the old `cl' implementation is finally considered obsolete. Previously its use was strongly discouraged at run-time but one was still allowed to use it at compile-time. For the most part the transition is very simple and boils down to adding the "cl-" prefix to some symbols. A few replacements do not follow that simple pattern; e.g. `first' is replaced with `car', even though the alias `cl-first' exists, because the latter is not idiomatic emacs-lisp. In a few cases we start using `pcase-let' or `pcase-lambda' instead of renaming e.g. `first' to `car'. That way we can remind the reader of the meaning of the various parts of the data that is being deconstructed. An obsolete `lexical-let' and a `lexical-let*' are replaced with their regular variants `let' and `let*' even though we do not at the same time enable `lexical-binding' for that file. That is the right thing to do because it does not actually make a difference in those cases whether lexical bindings are used or not, and because this should be enabled in a separate commit. We need to explicitly depend on the `cl-lib' package because Emacs 24.1 and 24.2 lack that library. When using these releases we end up using the backport from GNU Elpa. We need to explicitly require the `pcase' library because `pcase-dolist' was not autoloaded until Emacs 25.1. 2019-03-31T16:20:32Z Léo Gaspard leo@gaspard.io 2018-10-22T14:44:54Z urn:sha1:8e584392dce53d322b9403306991944c5578b1f0 This changes the meaning of `e` for non-drafts to make it behave similarly to new messages, which here means add the `FCC` header. 2016-11-13T17:15:31Z David Bremner david@tethera.net 2016-11-13T14:08:50Z urn:sha1:2dd96d6bd642c3b32ce1997528f69665019b7497 Provide functionality to resume editing a message previously saved with notmuch-draft-save, including decoding the X-Notmuch-Emacs-Secure header. Resume gets the raw file from notmuch and using the emacs function mime-to-mml reconstructs the message (including attachments). 'e' is bound to resume a draft from show or tree mode. 2016-11-13T17:15:31Z David Bremner david@tethera.net 2016-11-13T14:08:49Z urn:sha1:90248f862b1860cc80c8afd06636311372e95fe4 In general the user may not want to save plaintext copies of messages that they are sending encrypted, so give them a chance to abort. 2016-11-13T16:55:24Z Mark Walters markwalters1009@gmail.com 2016-11-13T14:08:48Z urn:sha1:d820b97477f5705640aa8dcf9dcf311e37508def This provides initial support for postponing in the emacs frontend; resuming will follow in a later commit. On saving/postponing it uses notmuch insert to put the message in the notmuch database Current bindings are C-x C-s to save a draft, C-c C-p to postpone a draft (save and exit compose buffer). Previous drafts get tagged deleted on subsequent saves, or on the message being sent. Each draft gets its own message-id, and we use the namespace draft-.... for draft message ids (so, at least for most people, drafts are easily distinguisable).