<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Oct. 10, 2016, at 8:46 am, Allan Odgaard <<a href="mailto:mailinglist@textmate.org" class="">mailinglist@textmate.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><span style="font-family: sans-serif;" class="">But completely suppressing updates might be too pessimistic, so I’ll look into having it update e.g. 3 seconds after last change. I want to do similar for SCM, where we also suppress updates when TextMate is in the background, but that does bother me a bit </span></blockquote><br class=""></div><div>That sounds quite reasonable.</div><div><br class=""></div><div>I’m currently trying an approach that uses the 'application.did-activate’ callback to check for updates and insert them. (There isn’t a “document.did-activate”, is there?) When a doc that isn’t frontmost gets an update, I switch away from TextMate and then back again, triggering the callback. The momentary interruption isn’t too bad; sometimes it isn’t even noticeable, although it seems that keystrokes can get mixed up if I’m in the middle of typing quickly.</div><div><br class=""></div>I was trying to think of a way to use the new auto-refreshing, but there would have to be a way to trigger it, e.g.<div class=""> mate --uuid $doc --event foobar</div><div class="">that would set $TM_REFRESH to “foobar” and run any commands accordingly.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">-David</div><div class=""><br class=""><div class=""><br class=""></div></div></body></html>