I think I requested that feature. I'd definitely want to have it update in the background for similar reasons as Dave. But there's no reason why the app couldn't wait a bit to make sure the repository has settled down before doing the actual refresh. Just like FSEvents does it, one could coalesce certain changes. I also have a UKPushbackMessenger class for coalescing stuff in my UliKit on Github, I think. That might help.
It's OK if it takes a second after I make a change to update this, but it sucks to constantly have to bring the window to front and wait for lengthy scanning to finish, like some SVN clients do it. And of course it would only need to be on when one is actually on the "commit" pane, not when I'm in the "history" pane (though of course it'd also be neat if the history pane checked with the server and let me know when the remote repository changes -- SmartSVN does that, and it's very convenient). Cheers, -- Uli
