On Wed, Sep 14, 2022 at 12:23:44PM +0800, Kevin J. McCarthy wrote:
For that case, Mutt is uncollapsing every thread, passing in the parent
message of each thread.
But surely it is not intended to uncollapse every thread, just because I
accidentally happen to reopen the mailbox because I saved a copy of an
outgoing message in the current mailbox?
And if it is indeed intended behaviour, how would you solve the problem?
- I reply to an email in an uncollapsed thread
- Mutt saves a copy of the reply via _record_ option
- I manually collapse the thread
- I sync my mailbox
- Now mutt uncollapses the thread again?!?
Surely you would agree, that the last step is unexpected behaviour from
mutt.
Above you gave the following definition for that option:
The intent of the option is uncollapsing for newly *received* messages
in the thread, not new as pertaining to message flags.
The thing is that even according to your definition, mutt is behaving
incorrectly: The outgoing message saved via "record" is **not** a newly
received message.
Could you point me in the right direction how to best solve this
problem? Maybe we would need to track messages that we save via
"record", but maybe there is an easier fix.
