Bug 1253231 - mutt: unread, collapsed thread does not change color to read when marked with <read-thread>
mutt: unread, collapsed thread does not change color to read when marked with...
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: mutt (Show other bugs)
22
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Matej Mužila
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-13 05:23 EDT by Stefan Assmann
Modified: 2016-07-19 15:55 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 15:55:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stefan Assmann 2015-08-13 05:23:33 EDT
Description of problem:
I have the following in my .muttrc
color index red default "~O"
color index red default "~N"

When moving to an unread thread, which is collapsed, and calling <read-thread> the thread is marked as read but the color is still red. It should be black now, because it is read.
After un-collapsing and re-collapsing the thread is properly colored in black.

Version-Release number of selected component (if applicable):
mutt-1.5.23-9.fc22.x86_64

How reproducible:
always

Steps to Reproduce:
1. set color for unread mails
2. select an unread collapsed thread
3. call read-thread

Actual results:
thread stays in color of unread mail

Expected results:
thread should be in color of read mail
Comment 1 Matej Mužila 2015-08-13 08:49:40 EDT
Hi,

I'm not able to reproduce it. Could you please send me your .muttrc (without your login information)?
Comment 3 Fedora End Of Life 2016-07-19 15:55:18 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.