From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#57434: 28.1.91; Terminal Emacs Mac OS flickering. Date: Thu, 08 Sep 2022 08:43:46 +0200 Message-ID: References: <83mtbks7mo.fsf@gnu.org> <837d2mqm98.fsf@gnu.org> <8335daqlsa.fsf@gnu.org> <83k06komhi.fsf@gnu.org> <83pmgcmmf1.fsf@gnu.org> <83leqvgib2.fsf@gnu.org> <83r10mfkn1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10528"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (darwin) Cc: kuragin@google.com, 57434@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 08 08:44:18 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 1oWBGr-0002aO-HU for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 08:44:17 +0200 Original-Received: from localhost ([::1]:43190 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWBGq-0004JQ-AM for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 02:44:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47998) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWBGc-0004JG-Ux for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:44:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40129) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oWBGc-0002OK-KY for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:44:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oWBGc-0003dC-9f for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 02:44:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 08 Sep 2022 06:44: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.166261943713940 (code B ref 57434); Thu, 08 Sep 2022 06:44:02 +0000 Original-Received: (at 57434) by debbugs.gnu.org; 8 Sep 2022 06:43:57 +0000 Original-Received: from localhost ([127.0.0.1]:57061 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWBGW-0003cm-JZ for submit@debbugs.gnu.org; Thu, 08 Sep 2022 02:43:56 -0400 Original-Received: from mail-ej1-f43.google.com ([209.85.218.43]:44779) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWBGU-0003cZ-SM for 57434@debbugs.gnu.org; Thu, 08 Sep 2022 02:43:55 -0400 Original-Received: by mail-ej1-f43.google.com with SMTP id r18so8526100eja.11 for <57434@debbugs.gnu.org>; Wed, 07 Sep 2022 23:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date; bh=oxy6ckKyBHT3YNozz5La8NwzEmMHZnsWCLGHKoDiMds=; b=lFzvimEa6RRLiHxwN0Xrg1eaNFuZgWJVatyqO855udDoljE68GdZE0V/rP37CgTf5Z dluAFmM6zpY12s9+DVsASTTZQHo5Dm4kNrgZRrtIM/qryQFqHpzDXcl2reHoERNxoHnW qQX3eTceAjgtQjGCfVkcJw5DBj/WhTJbOcW7PNod1VkX+IkkAxSI1VidcXZ8PPdkPv2X +uEx7+SAbOIxa6ZHo6+1EqVvCQ46wt0nFtCpYNNlIXftG4kr8+yxzSVremSCQw6ZWDmp F/8aooI0WHVM6Z/IIlVfXORBpm9MwpUxbePrAnqAxgIlUbBL/rWOWdxhldkFmZ3A+Lyg x+cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date; bh=oxy6ckKyBHT3YNozz5La8NwzEmMHZnsWCLGHKoDiMds=; b=6TfPJFnljsOPJmBreHI71yYAbW+t78o7CHvBkUnuANlr0il5Q4bT7JLaLRdZ+Yy9pv qM4YDlM3JFm+pBKM0q3c42oJ70u+ZzxYJLpiy/KfdENbPMmkkJpGi+lXtYmsvURGUEEv cIJs+1ogE8/jDZeiFguh4fmdk+pczFH8o1Hwsrx46E8Cz0FIMRwqDhIF3zY0JTBJR65V 5JgsHvGgYC10PyY5+NZh9zGV1lgpsIOUVzdE6gszmsm6u+0qsmBeKueJy7LvGQWhHGon xGNMnBSg0bWconPdxU/bDpAsi/O+FUb+9aDQWPyuk+vPQbnNISkpFfEO/zsc/rrk+pMK BIFg== X-Gm-Message-State: ACgBeo2wKwUJRJb1So3dUtqwJX0J93ZevG0BnLZr3zrRaX7P0h8WemqM LJb/B9NJ6eii2mrGdBW8IHfhAQj0/xOivQ== X-Google-Smtp-Source: AA6agR75ArqsV+2DUX9knfG0wsegpA2u1CclfH8DTAe0ncYSgTyDmvqhdMHz9xgAX3qFqSi3idPAKA== X-Received: by 2002:a17:906:cc12:b0:741:64ed:125a with SMTP id ml18-20020a170906cc1200b0074164ed125amr4920838ejb.713.1662619428200; Wed, 07 Sep 2022 23:43:48 -0700 (PDT) Original-Received: from Mini.fritz.box (pd9e367ac.dip0.t-ipconnect.de. [217.227.103.172]) by smtp.gmail.com with ESMTPSA id ek24-20020a056402371800b0044f1fcf5ee0sm1922630edb.48.2022.09.07.23.43.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 07 Sep 2022 23:43:47 -0700 (PDT) In-Reply-To: <83r10mfkn1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 08 Sep 2022 09:25:06 +0300") 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:241832 Archived-At: Eli Zaretskii writes: > 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? Yes, I think an option is currently all we can do. And somehow define what to send to the terminal, P1 or P2. I installed iTerm2 just now, which implements P2 at least. iTerm2 has a preference options to switch GPU acceleration on/off. iTerm2 uses TERM=xterm256-color, independent of the GPU setting. So matching TERM wouldn't work with iTerm2. The query control sequence of P2 seems to return if GPU accel is on or off on iTerm2. > >> >> 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? I think so. BTW, iTerm2 doesn't seem to define Sync. Kitty does. It's a mess.