unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: bryan@bryan.sh, 28695@debbugs.gnu.org
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Thu, 05 Oct 2017 17:01:25 +0300	[thread overview]
Message-ID: <83mv55wv62.fsf@gnu.org> (raw)
In-Reply-To: <1931afeb-51cb-89c9-72ff-c8a062fecba7@yandex.ru> (message from Dmitry Gutov on Thu, 5 Oct 2017 16:36:53 +0300)

> Cc: 28695@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 5 Oct 2017 16:36:53 +0300
> 
> Eli, perhaps it would be wise to ask the reporter if he'd like it to be 
> turned off by default, if this problem can't be fixed in time.

I kinda did, by proposing the recipe to turn it off, and waiting for a
response ;-)

> Personally, I can stand a few minor glitches, given that double 
> buffering saves me from flickering, which has been an annoyance for years.

I know that you are very happy with this feature, which is why it
puzzles me how come you (and others who like it) don't see these
problems.

> I wasn't able to compare with the revision before double buffering, 
> though: after checking out c29071587c64efb30792bd72248d3c791abd9337^, 
> ./autogen.sh says:

It should be easier to use a previous release of Emacs, if you have it
or can install it.

Btw, the hardships of building an old enough checkout are the reason
why I keep old binaries around, and insist on not doing a bootstrap
(which nukes them).  I find this a much easier way of "bisecting", or
at least of having a good start point for looking for a change that
causes some bug.





  reply	other threads:[~2017-10-05 14:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  3:10 bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2017-10-04  7:53 ` Eli Zaretskii
2017-10-04  9:04 ` martin rudalics
2017-10-04  9:32   ` Eli Zaretskii
2017-10-04 11:21     ` Bryan Gilbert
2017-10-04 11:36       ` Eli Zaretskii
2017-10-04 12:02         ` Bryan Gilbert
2017-10-04 12:31           ` Eli Zaretskii
2017-10-05 13:36       ` Dmitry Gutov
2017-10-05 14:01         ` Eli Zaretskii [this message]
2017-10-05 14:02         ` Noam Postavsky
2017-10-07  7:53           ` Dmitry Gutov
2017-10-07  8:14             ` Eli Zaretskii
2017-10-09 13:53               ` Dmitry Gutov
2017-10-09 14:03                 ` Eli Zaretskii
2017-10-15 22:55                   ` Dmitry Gutov
2017-10-16  2:30                     ` Eli Zaretskii
2017-10-26 23:19                       ` Dmitry Gutov
2017-10-28  9:33                         ` Eli Zaretskii
2017-10-28 21:47                         ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on GNU/Linux Richard Stallman
2017-10-05 14:26         ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2022-04-23 13:46 ` Lars Ingebrigtsen
2022-05-22 11:28   ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mv55wv62.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28695@debbugs.gnu.org \
    --cc=bryan@bryan.sh \
    --cc=dgutov@yandex.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).