mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
emacs: notmuch-tree: mark the initial message at point as read
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.
This commit is contained in:
parent
bed62eb8be
commit
b649b0c871
1 changed files with 2 additions and 1 deletions
|
@ -954,7 +954,8 @@ unchanged ADDRESS if parsing fails."
|
|||
(goto-char (point-max))
|
||||
(forward-line -1)
|
||||
(when notmuch-tree-open-target
|
||||
(notmuch-tree-show-message-in)))))
|
||||
(notmuch-tree-show-message-in)
|
||||
(notmuch-tree-command-hook)))))
|
||||
|
||||
(defun notmuch-tree-insert-tree (tree depth tree-status first last)
|
||||
"Insert the message tree TREE at depth DEPTH in the current thread.
|
||||
|
|
Loading…
Reference in a new issue