From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Emacs flickers periodically
Date: Sat, 17 Jun 2017 21:21:12 +0300 [thread overview]
Message-ID: <efcfec39-7701-91a3-ec5c-de180d772467@yandex.ru> (raw)
In-Reply-To: <83o9tmzpiw.fsf@gnu.org>
On 6/17/17 4:56 PM, Eli Zaretskii wrote:
>>> Actually, Emacs flickers on a TTY more frequently than in GUI frames,
>>> because certain changes on display require that the entire TTY frame
>>> be redrawn.
>>
>> Couldn't that actually be beneficial?
>
> Beneficial in what sense? Users are generally annoyed by flickering,
> especially when most or all of the display doesn't change.
In the "eliminating bugs" sense, bugs to which you referred later. I
can't say I have a clear idea how, except by eliminating certain
optimizations which you refer to in bug#16621).
And also, terminal emulators might have their own display
synchronization logic. Still, I've never tried the test cases for the
two bugs mentioned below in the terminal. Maybe someone should do that
and report back.
>> As long as it's never redrawn in an inconsistent state.
>
> AFAIK, Emacs never redraws display in inconsistent state (barring
> bugs, of course).
But that's the effect that the double-buffering patch brings: limiting
redrawing to consistent states only.
So maybe those were bugs (like 12363 and 16621), but they went unfixed
until Daniel's patch.
next prev parent reply other threads:[~2017-06-17 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 16:59 Emacs flickers periodically Narendra Joshi
2017-06-17 9:30 ` Emanuel Berg
2017-06-17 14:06 ` Narendra Joshi
2017-06-17 15:01 ` Emanuel Berg
2017-06-17 17:03 ` Narendra Joshi
2017-06-17 9:42 ` Dmitry Gutov
2017-06-17 9:57 ` Emanuel Berg
2017-06-17 10:10 ` Dmitry Gutov
2017-06-17 10:48 ` Eli Zaretskii
2017-06-17 10:51 ` Dmitry Gutov
2017-06-17 11:28 ` Emanuel Berg
2017-06-17 14:04 ` Narendra Joshi
2017-06-17 13:56 ` Eli Zaretskii
2017-06-17 18:21 ` Dmitry Gutov [this message]
2017-06-17 18:35 ` Eli Zaretskii
2017-06-17 19:27 ` Dmitry Gutov
2017-06-17 19:37 ` Eli Zaretskii
2017-06-17 15:21 ` Emanuel Berg
2017-06-17 14:04 ` Narendra Joshi
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=efcfec39-7701-91a3-ec5c-de180d772467@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).