From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#57434: 28.1.91; Terminal Emacs Mac OS flickering. Date: Thu, 08 Sep 2022 09:25:06 +0300 Message-ID: <83r10mfkn1.fsf@gnu.org> References: <8335dcu0sg.fsf@gnu.org> <83mtbks7mo.fsf@gnu.org> <837d2mqm98.fsf@gnu.org> <8335daqlsa.fsf@gnu.org> <83k06komhi.fsf@gnu.org> <83pmgcmmf1.fsf@gnu.org> <83leqvgib2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17408"; mail-complaints-to="usenet@ciao.gmane.io" Cc: kuragin@google.com, 57434@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 08 08:29:00 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWB23-0004Ml-PW for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 08:28:59 +0200 Original-Received: from localhost ([::1]:40762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWB22-0001BG-Fs for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 02:28:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53146) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWAzC-0007k0-PX for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:26:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40095) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oWAzC-00088q-FF for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oWAzC-0003Ab-49 for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 08 Sep 2022 06:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57434 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 57434-submit@debbugs.gnu.org id=B57434.166261835012165 (code B ref 57434); Thu, 08 Sep 2022 06:26:02 +0000 Original-Received: (at 57434) by debbugs.gnu.org; 8 Sep 2022 06:25:50 +0000 Original-Received: from localhost ([127.0.0.1]:57027 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWAyz-0003A8-Oj for submit@debbugs.gnu.org; Thu, 08 Sep 2022 02:25:50 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:32794) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWAyy-00039v-8X for 57434@debbugs.gnu.org; Thu, 08 Sep 2022 02:25:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41082) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWAys-00086v-RA; Thu, 08 Sep 2022 02:25:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=zQRQdvSXPkCuD0HIJhlqmkWM9VTaVznmawefuEckjOM=; b=ivcYtDfa4LVLrb85fCdh 9vKbhLCRDZ/qW4VF4fX+ayi3aZi9jtO4gtqV4xqZ7WUfkQ2XliVKY2+dDfwTXwN+8y0d7CPR4bPJj 4neDB5328JDAf2+Di7XsIz4VxJ3D34WceFFHZkdxDseV30RwsZCuyCsrObXyHRlahi/4dmO07oeks BQfZ0owy3GQU6RgwfQbenASpArz63TBz4IkoEF0JQx59Wx59INtXzrclcOSki41iYLlsK+5WzV9Zu BDsggL72+sw789EOYrX7vcavAQTEx2Hnon2UbJVtLHFQ9ZOz1g/ELUqX9ivaNPG1aX48pBuehgp7M r2SEhLzS6TOYBw==; Original-Received: from [87.69.77.57] (port=1505 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWAyW-0000ME-Jf; Thu, 08 Sep 2022 02:25:36 -0400 In-Reply-To: (message from Gerd =?UTF-8?Q?M=C3=B6llmann?= on Thu, 08 Sep 2022 07:31:17 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:241829 Archived-At: > From: Gerd Möllmann > Cc: Dmitrii Kuragin , 57434@debbugs.gnu.org > Date: Thu, 08 Sep 2022 07:31:17 +0200 > > > So now the next question is: on what should we base the activation of > > these hooks? There are several alternatives: > > > > . if alacritty produces a distinct value from tty-type, we could use > > that, or > > . if alacritty has a distinct terminfo capability that other > > terminals don't, we could use that, or > > . expose a variable to Lisp that users could set in order to turn > > this on and off, and tell users to turn it on if they see the > > issue > > > > Any other ideas? > > I'd like to emphasize that this is not a problem limited to Alacritty. > There are a number of terminal emulators with GPU accelleration, which > all share the same cpmceptual problem. Alacritty is just the one with > the best marketing, riding the Rust wave. > > AFAICT, we have the following situation: > > - We have two proposals P1 and P2 (that we know of). Alacritty > implements P1 only, says Dmitrii, and P2 has a table of emulators > implementing P2, which may or may not implement P1. > > - Neither P1 nor P2 are detectable as a terminfo capability, so one has > to match TERM or use a boolean switch. I don't know if all emulators > use a discernable TERM, or if they use standard TERM names. So you are saying at this point only my last alternative, i.e. a variable exposed to Lisp, is a reasonable way ahead? Until, that is, those emulators get their act together and agree on some standard way of detecting the need for synchronized updates? > >> BTW, tmux uses the sync update for their own TUI and they check "Sync" terminal capability. Do we need to > >> do the same or we can just send the escapes and hope the unsupported terminal would just recover? > > > > What is that Sync capability, what is its value for tmux, and how is > > it supposed to be used? Is there any documentation I could read about > > that? > > I know Sync as an xterm extension, although I don't remember what it is > for. It's a non-standard terminfo capability which is only shown with > infocmp -x. > > Neither P1 nor P2 mention Sync in any way. Does terminfo return the Sync capability on those terminals, as it returns the standard ones? That is, can we test for it inside init_tty?