Hello Kevin,
That makes sense, I completely misunderstood those few lines of code.
What really should happen then is that all messages in every thread
should be checked and if a !old message is found, then the thread it
belongs to should be uncollapsed.
I'm also interested in hearing what other d
Yoshiki Vazquez Baeza wrote:
> I think I found the reason why this happens, there's a block of code
> that uncollapses *all* the threads in the current mailbox when it is
> reopened. The comments around that block of code seem to indicate that
> only new emails should be uncollapsed, so I've added
Hello Everyone,
I think I found the reason why this happens, there's a block of code
that uncollapses *all* the threads in the current mailbox when it is
reopened. The comments around that block of code seem to indicate that
only new emails should be uncollapsed, so I've added an if statement
(see
Hey Mutters,
I've encountered a strange behaviour that uncollapses all the threads in
the current mailbox after I get the message "Mailbox was externally
modified. Flags may be wrong.". I tried to track down the problem in
curs_main.c but had no luck.
I have the following folder-hook to collapse
