it's like Thunderbird set the "mark message as read"
machinery rolling, but when the machinery hits the message I've
already moved, so it marks the new one as read.
Huh?
When the timer expires to move the message from UNREAD to READ, he's
on a completely different message. TB doesn't notice this and marks
the wrong message as READ, rather than cancelling the timer for the
last message and starting a new one.
Oh :) Wonder if there is a bug report on this.
For me, the timer is something on the order of 300ms
So I'd like to know how he *knows* the timer didn't get cancelled and
restarted ?
is there an option to set this to the order of seconds ?
--
Michael O'Keefe | [EMAIL PROTECTED]
Live on and Ride a 03 BMW F650GSDakar| [EMAIL PROTECTED] / |
I like less more or less less than |Work:+1 858 845 3514 / |
more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_|
My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'|
blah, yackety yack - don't come back |Fax :+1 858 _/_\|_,
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
