It matters because if you read messages yarn marks them as read. THen when
you exit it has to update the X-Status. To update the X-Status it seems to
(for some reason) scan the entire folder-- hence the delay.
Those are my non-scientific observations anyhow. And if you hit Insert to
"unread" them before exiting yarn seems to have a flag somewhere that says
there was a "change" made.. and so scans the whole folder on exiting anyhow.
Wheee. A slight annoyance... but a situation I can live with.
--
..,.,.,,..,...,.,.,.,.,.,.,,,,.,.,.,...,.,.,..,.,,.,..,..,.,..,.,,.,.
Tim Muddleton =-=- when sense makes no sense -=-= as544@torfree.net
-=-=- Animal Farm by George Orwell wouldn't take long to read -=-=-
``'`''`'`'''`'```'`'`'`'`''`'``'`'`'`'`'`''`'`'`''```'`'`'`''`''``'`'
Yarn/2 Bells & Whistles Page: http://www.io.org/~tm/bells2.html