News for hackers. Stuff that matters.
Re:Buttery Smooth Emacs by dom0 on Sunday October 30, 2016 @12:09PM (#12830531)
Perhaps using a compositing desktop manager mitigates it, since those are almost always vsync'd and double buffered.

Edit: Hm, no there is no synchronization between the WM and emacs in any way. So this can't be it.

Re:Buttery Smooth Emacs by to3m on Sunday October 30, 2016 @12:23PM (#12830611)
It definitely flickers a bit when running in XQuartz.

(I hope this change doesn't make it run crappily in XQuartz! X-Windows programs that do double buffering draw to an offscreen buffer often perform really poorly, poorly enough that I'd definitely rather have the flicker, not least because I don't mind the flicker too much anyway.

(I assume a lot of them have a client-side pixmap that's written to manually, and then has to be sent over the network link. )

Re:Buttery Smooth Emacs by quotemstr on Sunday October 30, 2016 @01:49PM (#12831115)
One of the advantages of using the X double buffer extension or XRender or something like that is you don't need to send raster image data over the network. You're still sending ordinary drawing commands, and it's the server that accumulates the results into a pixmap somewhere.

If it is slow for you, you can turn off the new stuff:

    (modify-frame-parameters nil '((inhibit-double-buffering . t)))
Re:Buttery Smooth Emacs by rurban on Sunday October 30, 2016 @07:19PM (#12833122)
But why inhibit-double-buffering and not just the simple no-double-buffering?
Re:Buttery Smooth Emacs by to3m on Sunday October 30, 2016 @08:19PM (#12833399)
There are only 3 variables with a "no-" prefix, but 30+ starting with "inhibit-"...
Re:Buttery Smooth Emacs by digi_owl on Sunday October 30, 2016 @03:28PM (#12831726)
Would not surprise me one bit if the compositing is the cause rather than the "solution".