diff options
author | Jason Cox <me@jasoncarloscox.com> | 2024-01-04 23:00:38 -0500 |
---|---|---|
committer | Robin Jarry <robin@jarry.cc> | 2024-01-07 11:43:42 +0100 |
commit | ef4b7dc5d46b7d40c79131d812a6296d1bb9668c (patch) | |
tree | 4b7230a5596eb060d5aaf7644c0e9864db5f2b4d /worker/jmap | |
parent | e2c1bafafe06b87a8a7e9639ff427949f4adbf61 (diff) | |
download | aerc-ef4b7dc5d46b7d40c79131d812a6296d1bb9668c.tar.gz |
notmuch: keep track of all siblings in thread
Consider a thread with a root message and three child messages, each of
which has a single child message, like so:
root
child 1
grandchild 1a
child 2
grandchild 2a
child 3
grandchild 3a
With the previous implementation, if child 2 (or child 3) is not shown
by the current query, then grandchild 2a (or grandchild 3a) will not be
shown either. Ensure that this bug does not occur; that is, ensure that
children of non-queried non-first-child messages are shown in threads.
A more complex implementation is possible that maintains only a single
loop over the messages, but thinking about it made my head hurt. Use a
second (at times redundant) loop instead for simplicity's sake.
Changelog-fixed: Don't lose child messages of non-queried parents in
notmuch threads
Signed-off-by: Jason Cox <me@jasoncarloscox.com>
Acked-by: Robin Jarry <robin@jarry.cc>
Tested-by: Inwit <inwit@sindominio.net>
Diffstat (limited to 'worker/jmap')
0 files changed, 0 insertions, 0 deletions