Michael O'Keefe wrote:
crypticreign wrote:
Todd Walton wrote:
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.
--
crypticreign
San Diego, CA
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
