From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Bryan Gilbert <bryan@bryan.sh>, 28695@debbugs.gnu.org
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Thu, 5 Oct 2017 10:02:21 -0400 [thread overview]
Message-ID: <CAM-tV-_TL-WNPpfn0_iTEa_KhAjfzOSxZbNY1icChAeZQbkUaA@mail.gmail.com> (raw)
In-Reply-To: <1931afeb-51cb-89c9-72ff-c8a062fecba7@yandex.ru>
On Thu, Oct 5, 2017 at 9:36 AM, Dmitry Gutov <dgutov@yandex.ru> wrote:
> I wasn't able to compare with the revision before double buffering, though:
> after checking out c29071587c64efb30792bd72248d3c791abd9337^, ./autogen.sh
> says:
> Running 'autoreconf -fi -I m4' ...
> /usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No such
> file or directory
Try 'rm aclocal.m4' (this is mentioned in INSTALL.REPO as of last May)
next prev parent reply other threads:[~2017-10-05 14:02 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
2017-10-05 14:02 ` Noam Postavsky [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-_TL-WNPpfn0_iTEa_KhAjfzOSxZbNY1icChAeZQbkUaA@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.