thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.21_rc2 2015-10-17T12:07:36Z 2015-10-17T12:07:36Z Mark Walters markwalters1009@gmail.com 2015-10-15T18:53:09Z urn:sha1:ff1fb5027c03dee80d59f54e5c0d9b62d7bd66c9 Currently notmuch-show-max-text-part-size is 10000 which means some relatively normal messages have all parts hidden by default. Increase this to 100000 by default. The setting was introduced to alleviate problems with notmuch being very slow on large threads. Users hitting these problems may wish to customize this variable to something smaller (like 10000). 2015-10-17T12:07:16Z Mark Walters markwalters1009@gmail.com 2015-10-15T18:46:34Z urn:sha1:3d38baf35280b9fe2d94a104bb2148e82164996b Formerly replying to an encrypted message in tree-view did not work: the message was not decrypted. This commit makes notmuch-tree respect the setting of notmuch-crypto-process-mime. In particular, if notmuch-crypto-process-mime is set to t, then replying to encrypted messages in tree mode will now decrypt the reply (as it already did in show mode). 2015-09-07T12:27:09Z Uli Scholler uli@scholler.net 2015-09-06T21:29:05Z urn:sha1:9a5143abbcfbb008f846329b5c50b9322af5322a When filtering the current search further with notmuch-search-filter, wrap the current search in parens (if necessary). This fixes unexpected behavior when the current search is complex (like "(tag:this and date:one_week_ago..) or tag:that"). 2015-08-07T19:33:57Z David Bremner david@tethera.net 2015-08-07T19:33:57Z urn:sha1:d02e4dee71b9fb38919ac5e78ec56d1df79473fb M-x whitespace-cleanup in Emacs. 2015-08-07T19:18:59Z David Bremner david@tethera.net 2015-08-01T09:44:56Z urn:sha1:d0553ad524f241ba42f685cba6745c8a3a9ba20a Previously we globally modified these variables, which tended to cause problems for people using message-mode, but not notmuch-mua-mail, to send mail. User visible changes: - Calling notmuch-fcc-header-setup is no longer optional. OTOH, it seems to do the right thing if notmuch-fcc-dirs is set to nil. - The Fcc header is visible during message composition - The name in the mode line is changed, and no longer matches exactly the menu label. - Previously notmuch-mua-send-and-exit was never called. Either we misunderstood define-mail-user-agent, or it had a bug. So there was no difference if the user called message-send-and-exit directly. Now there will be. - User bindings to C-c C-c and C-c C-s in message-mode-map are overridden. The user can override them in notmuch-message-mode-map, but then they're on their own for Fcc handling. 2015-08-07T19:17:26Z David Bremner david@tethera.net 2015-08-01T09:44:55Z urn:sha1:03aff8499d55614377d01e0296a4f186e0ed8735 This is to provide a clean way of overriding e.g. keybindings when sending mail from notmuch. This is needed in particular to allow somewhere to dynamically bind certain message-mode variables which are not respected when buffer-local. See e.g. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21174 2015-08-04T18:56:38Z Tomi Ollila tomi.ollila@iki.fi 2015-08-02T14:48:14Z urn:sha1:3c1eea5646fcf33d66acb874d82f3518a75c24de Now that we have `notmuch-emacs-version' defined in notmuch emacs MUA use that as a part of User-Agent: header to provide more accurate version information when sending emails. In case some incomplete installation of notmuch emacs MUA is used and `notmuch-emacs-version' is defined as "unknown" then fall back to ask version info from cli (as it used to be before this commit). Requiring notmuch-version[.elc] and if that is missing setting "fallback" notmuch-emacs-version (to "unknown") was moved from notmuch.el to notmuch-lib.el as notmuch-mua.el (which provides User-Agent: information) require's the latter. 2015-08-04T18:56:28Z Tomi Ollila tomi.ollila@iki.fi 2015-08-02T14:48:13Z urn:sha1:0c565fa29fc29f74209d4343e2fc88f3b8008aaa As it asks `notmuch` binary for its version number. 2015-08-04T07:15:23Z Mark Walters markwalters1009@gmail.com 2015-06-13T08:08:09Z urn:sha1:2982d70ac683c74c62e20081b36529c90bccc914 Show the current thread with a different filter (i.e., open messages in the thread matching the new query). Bound to 'l' for "limit". Note that it is not the same as filter in search mode as it replaces the existing query rather than ANDing with it (but it does keep the thread-id part of the query). 2015-08-04T07:15:13Z Mark Walters markwalters1009@gmail.com 2015-06-13T08:08:08Z urn:sha1:d4053be21acf4c3fce0b477e26eec95b42a36bd7 Separate out a notmuch-show-goto-msg-id sub-function from notmuch-show-apply-state. There should be no functional change but the next patch will call the new function.