On Nov 22, 2013, at 3:18 AM, Mark van Atten <vanattenm...@gmail.com> wrote:
> Well, I wrote `the current sources', but that was wrong: I just > checked bitbucket again and saw your commits of the last few hours. So > I pulled the updates and rebuilt. To my surprise, the phenomena remain > exactly the same. This time I got a message though: rio flickers natively, you just have to be on a really slow machine to see it. Or in this case a slow cpu server (virtualbox) or a slow network connection to the cpu server (wifi to a remote site in my case). The recent drawterm-cocoa changes clean up full screen changes. > objc[3785]: Object 0x7fb261297930 of class NSConcreteMapTable > autoreleased with no pool in place - just leaking - break on > objc_autoreleaseNoPool() to debug This morning’s push you get rid of that autoreleasepool warning.
