On Wed, 2007-07-04 at 09:23 -0600, Robin Laing wrote: > But the issue is when Evolution does it's tasks. They should be done > immediately, not when Evolution closes. This brings up the question > of how it handles crashes, just as mine did this morning? Badly... I can see some reason for not doing things instantly, for the sake of efficiency. But leaving everything until the last moment has it's problems, as well. And won't work for those who leave an application running nearly permanently. I don't think it does that, though. I think it saves changes periodically. I know that when it's crashed on me, messages that I've just read come back as being unread (painful), messages that I've read a while ago are marked as being read (as they should be). -- (This box runs FC5, my others run FC4 & FC6, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
