Re: How to let mutt always mark mbox as new if it contains new
On 2009-05-08, Patrick Shanahan <ptilopteri@xxxxxxxxx> wrote:
> * Wu, Yue <vanopen@xxxxxxxxx> [05-08-09 18:26]:
> >
> > Do you me I should fix it manually?
>
> :^), yes
>
> > >From the manpage of muttrc, it says mark_old is for:
> >
> > > Controls whether or not mutt marks new unread messages as old if you
> > > exit a mailbox without reading them.
> >
> > So it's for message, not for mbox. My issue is that when I enter into
> > mbox then change to others, then the mbox's new mark will gone, no
> > matter if the mbox contains new messages or not.
>
> Mutt inserts a "flag" into each message header according to your
> configuration. If you examine the header of a message flagged as
> "old" you will see "Status: O" near the last header line.
>
> Since you had previously used mutt configured to "mark_old" and mutt
> did as it was told, you must those messages which have already been
> flagged. To do this:
>
> T~O;N
>
> Enter the above characters and the entire visible listing will have
> the "old" flagged messages changed to "new".
>
> > Maybe I didn't describe myself clearly, so make you misunderstand?
> > Sorry for my bad English.
>
> Yes, you have made your problem clear. But once the "new" messages
> have been marked/flagged as "old" changing the configuration will not
> automagically change them back to "new". The key sequence I displayed
> above "T~O;N" will change the entire current mbox file.
>
> And since you have set "mark_old" to "off" or "unset", you will not
> see this happen any more.
>
> I hope I have made this clear for you. :^)
I don't think this is Wu Yue's problem, Patrick. I could be wrong,
but as I understand him, he is opening a mailbox, leaving some of
the messages unread, then changing to another mailbox, then checking
to see which mailboxes contain new mail (perhaps with the y
command), and sees that the first mailbox has no N in front of it,
indicating that it contains no new messages, although in fact it
does.
If that is the problem, then I see that problem with my
installation, too. I don't have a solution other than to quit and
restart mutt.
HTH,
Gary