thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.33 2021-08-22T14:12:03Z 2021-08-22T14:12:03Z David Bremner david@tethera.net 2021-08-22T03:51:07Z urn:sha1:8c4f38092a8668d9f3290f114fa1be491c7069f6 This is just a regular character in docstrings (as it is fairly often used in lisp identifiers and buffer names) but is the start of emphasis in rst. This change is needed to quell a noisy warning when including notmuch-tree.rsti 2021-08-22T14:05:13Z David Bremner david@tethera.net 2021-08-22T00:00:11Z urn:sha1:731697d671749a13634a2a4b843ce62f2927f64f This is a bit of a cheat, since the format does not actually change. On the other hand it is fairly common to do something like this to shared libary SONAMEs when the ABI changes in some subtle way. It does rely on the format-version argument being early enough on the command line to generate a sensible error message. 2021-08-22T02:53:42Z jao jao@gnu.org 2021-08-22T00:50:49Z urn:sha1:357dd488caf0262f8a36ea4fd23b9d017cc93440 This new command for notmuch-tree-mode is analogous to notmuch-search-filter-by-tag, bound to "t" in notmuch-search-mode; it gets therefore the same "t" keybinding in notmuch-tree-mode (replacing the current assignment to notmuch-search-by-tag). 2021-08-22T02:48:13Z jao jao@gnu.org 2021-08-22T00:50:48Z urn:sha1:785745783345d3ed56f0b435fcea44515aae8bea This command is analogous to notmuch-filter, but is defined on tree mode buffers. 2021-08-05T11:58:30Z Protesilaos Stavrou info@protesilaos.com 2021-07-17T08:30:18Z urn:sha1:c37c99126d4bf6909399d84455063e0ff0ee9b59 The intent of the 'notmuch-jump-key' face is to allow users/themes to differentiate the text of the minibuffer prompt from the keys that are associated with jump actions. Commit 5cc106b0 correctly introduced the 'notmuch-jump-key' face for keys, but mistakenly applied it to the prompt as well. 2021-08-04T01:55:52Z jao jao@gnu.org 2021-08-04T00:02:41Z urn:sha1:c1f542d68ae843eedc2f5686203aa41dbb6a38e7 When mm-text-html-renderer is set to 'w3m, the variable playing the role of a regular expression for blocked images is w3m-ignored-image-url-regexp. We bind it when the renderer is not 'shr. 2021-07-25T18:15:33Z Jonas Bernoulli jonas@bernoul.li 2021-02-16T00:01:38Z urn:sha1:b649b0c871e7fbfcd15a24d51b071bad2680e5d2 When moving between message in a tree or show buffer, the message at point is marked as read. Likewise when creating such a buffer, then the message that is initially at point is supposed to be marked as read as well. The latter worked for `notmuch-show' but not for `notmuch-tree'. Press "RET" or "M-RET" in a search buffer to observe these behaviors. In both cases the marking is supposed to be done by the function `notmuch-show-command-hook'. In the case of `notmuch-show' that function is added directly to `post-command-hook'. `notmuch-tree' instead adds the function `notmuch-tree-command-hook' to `post-command-hook' and that calls `notmuch-show-command-hook', in the respective show buffer, but of course only if that exists. Because the tree buffer is created asynchronously, the show buffer doesn't exist yet by the time the `post-command-hook' is run, so we have to explicitly run `notmuch-tree-command-hook' once the show buffer exists. The show buffer is created when `notmuch-tree-goto-and-insert-msg' calls `notmuch-tree-show-message-in'. `notmuch-tree-process-filter' is what finally brings us here. 2021-07-19T11:32:49Z David Bremner david@tethera.net 2021-07-07T01:51:08Z urn:sha1:bed62eb8bee4aeca1fabfa5e302b515849f50b31 A let binding without a value is just an obfuscated way of saying nil, especially if you are not going to mutate the variable. 2021-07-13T12:55:00Z David Bremner david@tethera.net 2021-07-07T01:35:30Z urn:sha1:d8a5fba4fe1efd7d0d652ead6d55371bc4078a9d This fixes an a warning from the byte-compiler. The commit 74ab62a34018b38a40db4d363fff3faae964b47a changed the function signature but did not update the declaration. 2021-07-07T01:25:57Z David Bremner david@tethera.net 2021-07-07T01:25:57Z urn:sha1:04f378e673852ade100c54318124ff8c22f857b6 This error crept in during my style rewrite of dkg's proposed change.