At 18:28 -0500 25 Oct 2001, David Champion <[EMAIL PROTECTED]> wrote:
> Except when it's synonymous with "oh, heck, I don't want to deal with
> this now."
>
> That's when I want something to be "old" instead of "new" or "read", and
> to stay "old" between instances of mutt -- but for "unread" messages to
> stay "unread", without becoming "old".
That's pretty much how I use it as well. I've patched mutt so that
the functionality of the standard versions $mark_old is split into two
variables:
- $mark_old, controls if new messages are automatically marked as old
when you leave a folder. Also, this is now a quad-option (this
part was actually done by somebody else, though I'd have to look to
remember who).
- $see_old, determines whether or not messages that are marked as old
should actually be displayed as such.
It's even done in such a way that changing the value of $see_old will
take effect immediately, not just when messages are being parsed.
The patch (and a couple others I've done) is available from my
(currently *very* minimal) mutt page:
http://pug.schrab.com/aaron/mutt/
Current version up there was originally against 1.3.8, but it should
apply cleanly up to 1.3.23. There's a minor issue applying against the
current CVS version, but it's pretty easy to fix. I'll probably put a
new version up sometime over the weekend.
Of course, I haven't done extensive testing of it in a while; I just
know that it works for me with
set mark_old=no see_old=yes
--
Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/
What kind of head of security would I be if I let people like me know
things that I'm not supposed to know? -- Garibaldi
