From: Amos Bird <amosbird@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: unpleasant flickering in terminal emacs
Date: Fri, 27 Apr 2018 20:23:07 +0800 [thread overview]
Message-ID: <87o9i47s9g.fsf@gmail.com> (raw)
In-Reply-To: <CAHa53uzG8miF8Bq14GZDC780F6m9CwWboZgYg4qXEgNKuGOV7A@mail.gmail.com>
Thanks. But it's emacs in the terminal which flickers, not in the
GUI. I'm not
sure if the double buffering mechanism has anything to do with
terminals.
regards,
Tim Visher <tim.visher@gmail.com> writes:
> I don't have an informed idea about whether you're suffering
> from this (I
> never have) but your question tickled my memory.
>
> https://www.facebook.com/notes/daniel-colascione/buttery-smooth-emacs/10155313440066102/
>
> On Fri, Apr 27, 2018 at 7:58 AM, Amos Bird <amosbird@gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm using emacs master branch in terminal (alacritty). When
>> moving
>> cursor with relative line number enabled or scrolling up/down,
>> I get
>> unpleasant screen flickering. However, frame switch works fine,
>> which
>> I suppose uses full rendering updates. It seems partial
>> rendering
>> update doesn't work well. The author of alacritty mentioned one
>> possible cause : "flickering is typically caused by a program
>> not
>> writing full updates to the pty. We drain all available bytes
>> up to
>> like 64k before yielding for a render. It may be that we should
>> add
>> some heuristic around time to prevent flickering from poorly
>> behaved
>> terminal applications." So my question is, can I enable full
>> updates
>> for every redisplay? Thanks!
>>
>> Here is a screencast of flickering.
>>
>> https://youtu.be/wv4QINKHDUY
>>
>> regards,
>>
>> --
>> Amos Bird
>> amosbird@gmail.com
>>
>>
--
Amos Bird
amosbird@gmail.com
next prev parent reply other threads:[~2018-04-27 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 11:58 unpleasant flickering in terminal emacs Amos Bird
2018-04-27 12:04 ` Tim Visher
2018-04-27 12:23 ` Amos Bird [this message]
2018-04-27 12:51 ` Eli Zaretskii
2018-04-27 12:50 ` Eli Zaretskii
2018-04-27 15:05 ` Amos Bird
2018-04-27 15:51 ` Eli Zaretskii
2018-04-27 16:45 ` Amos Bird
2018-04-27 18:27 ` Eli Zaretskii
2018-04-28 3:36 ` Amos Bird
2018-04-28 6:40 ` Eli Zaretskii
[not found] ` <mailman.13046.1524853658.27995.help-gnu-emacs@gnu.org>
2018-04-27 20:38 ` Emanuel Berg
2018-04-28 6:27 ` Eli Zaretskii
[not found] ` <mailman.13064.1524896893.27995.help-gnu-emacs@gnu.org>
2018-04-28 11:05 ` Emanuel Berg
[not found] <mailman.13019.1524830349.27995.help-gnu-emacs@gnu.org>
2018-04-27 15:14 ` Emanuel Berg
2018-04-27 16:47 ` Amos Bird
[not found] ` <mailman.13042.1524847634.27995.help-gnu-emacs@gnu.org>
2018-04-27 16:58 ` Emanuel Berg
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=87o9i47s9g.fsf@gmail.com \
--to=amosbird@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tim.visher@gmail.com \
/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.