<<< Date Index >>>     <<< Thread Index >>>

[Mutt] #3376: Previously tagged messages keep the associated background color until message is again displayed



#3376: Previously tagged messages keep the associated background color until
message is again displayed
------------------------------+---------------------------------------------
 Reporter:  antonio@â         |       Owner:  mutt-dev
     Type:  defect            |      Status:  new     
 Priority:  trivial           |   Milestone:          
Component:  header cache      |     Version:  1.5.20  
 Keywords:  patch             |  
------------------------------+---------------------------------------------
 Forwarding from http://bugs.debian.org/545316
 ----

 {{{
 I tend to mark as read many messages by selecting them all with
 T then ~N and then using ;WN.

 During that processe all tagged messages are rightfully changed to have a
 green background color (or whatever color you configured). However when I
 exit mutt and come back, the background color is kept even if the messages
 are no more tagged.

 It should stop displaying them with a green background color, and indeed
 when I open a message with a green background color, that color goes away.

 Note that refreshing the view with CTRL+L doesn't help. I use the cache
 feature for mailboxes (set header_cache=~/.mutt_cache), it might be
 related to that.
 }}}

 This bug is not reproducible without the header cache so it seems an
 header cache problem.

 Another user did more debugging and found out that:

 {{{
 I've been investigating this bug for about 3 hours now.  It appears that
 sometime the header cache stores the "pair" value in the HEADER struct.
 So
 when the cache is reloaded, it fills it in and trusts it, even if that's
 not
 the colour its supposed to be.

 I don't know what's causing the records to be written out like that, but
 it's
 not right.  I've attached a trivial patch that prevents the problem from
 occuring, but it doesn't get at the root of the issue.  I don't know mutt
 well
 enough to figure that out, so it'll have to go upstream or something.
 Note,
 this patch isn't well tested, but it compiles and doesn't break anything
 obvious.

 As a workaround, you can delete the header cache for the mailbox in
 question
 (if you're using header cache folders).
 }}}

 The patch is a workaround, I hope you could get to the root of the
 problem, in any case it's most likely that we will ship it until the
 problem is solved; patch is attached.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3376>
Mutt <http://www.mutt.org/>
The Mutt mail user agent