GNU bug report logs - #57434
28.1.91; Terminal Emacs Mac OS flickering.

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: kuragin <at> google.com, 57434 <at> debbugs.gnu.org
Subject: bug#57434: 28.1.91; Terminal Emacs Mac OS flickering.
Date: Thu, 01 Sep 2022 09:11:58 +0300

> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Cc: Dmitrii Kuragin <kuragin <at> google.com>,  57434 <at> debbugs.gnu.org
> Date: Thu, 01 Sep 2022 07:44:52 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Given our inability to pinpoint the root cause of the problem, and the
> > unsolved mystery why on some macOS systems the problem is much more
> > prominent than on other macOS systems, I tend to introduce a variable
> > that users could set from Lisp to tell Emacs not to use the optimized
> > insert/delete-lines algorithm in scroll.c.  Unless some significant
> > new ideas or facts emerge in the next day or two, that is.
> 
> I guess I've found these facts today, while rummaging in alacritty's
> Github project.

Thanks.

So we have 2 alternatives:

  . declare that flickering on alacritty is currently a known problem,
    and wait till Someone comes up with the proper solution for Emacs;
  . add that variable I mentioned above, and let users try to fix the
    problem with alacritty by flipping it.

TBH, given your description, I'm no longer sure a simple boolean
variable that disables insert/delete-line optimization will do, since
the issue seems to be a much more general one.  How sure are we that
some other scenario of redrawing a TTY frame won't cause similar
flickering regardless of the insert/delete-line feature?  So maybe
just document the issue in PROBLEMS and advise against using
alacritty?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.