Jonas Bernoulli writes:
> 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.
Applied to master. Thanks for patiently
David Bremner writes:
> Jonas Bernoulli writes:
>
>>
>> Please merge the proposed fix; IMO it is sound. My follow-up, the reply
>> to Tomi, seems quite confused though. But just because we are uncertain
>> whether there is further room for improvement, that shouldn't keep us
>> from fixing
Jonas Bernoulli writes:
>
> Please merge the proposed fix; IMO it is sound. My follow-up, the reply
> to Tomi, seems quite confused though. But just because we are uncertain
> whether there is further room for improvement, that shouldn't keep us
> from fixing the bug. Maybe in the future we
David Bremner writes:
> Jonas Bernoulli writes:
>
>> Hm, when no tree buffer is involved, then `notmuch-show-command-hook'
>> probably is required. Anyway, there seems to be some undead code and
>> rethinking all this would be a good idea.
>
> I'm not sure I followed the discussion, but I'm
Jonas Bernoulli writes:
> Hm, when no tree buffer is involved, then `notmuch-show-command-hook'
> probably is required. Anyway, there seems to be some undead code and
> rethinking all this would be a good idea.
I'm not sure I followed the discussion, but I'm marking
Hm, when no tree buffer is involved, then `notmuch-show-command-hook'
probably is required. Anyway, there seems to be some undead code and
rethinking all this would be a good idea.
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send
> I try to understand whether adding notmuch-tree-command-hook to
> post-command-hook in notmuch-tree.el (not in this change) actually
> have any effect.
You're right, that's unnecessary, and it gets worse.
`notmuch-tree-command-hook' is unnecessary too and if it weren't,
then it would fail
On Tue, Feb 16 2021, Jonas Bernoulli wrote:
> 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
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"
