From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitrii Kuragin via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#57434: 28.1.91; Terminal Emacs Mac OS flickering. Date: Thu, 8 Sep 2022 08:59:32 -0700 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> <83illyffan.fsf@gnu.org> <83a67afcq0.fsf@gnu.org> Reply-To: Dmitrii Kuragin Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008b817905e82c8410" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10121"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 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 18:01:33 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 1oWJy9-0002QH-OL for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 18:01:33 +0200 Original-Received: from localhost ([::1]:47158 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWJy8-0000DS-NO for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 08 Sep 2022 12:01:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57168) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWJwh-0008T9-SA for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 12:00:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43016) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oWJwh-0003uQ-GI for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 12:00:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oWJwg-0007BM-TR for bug-gnu-emacs@gnu.org; Thu, 08 Sep 2022 12:00:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitrii Kuragin Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 08 Sep 2022 16:00: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.166265279127562 (code B ref 57434); Thu, 08 Sep 2022 16:00:02 +0000 Original-Received: (at 57434) by debbugs.gnu.org; 8 Sep 2022 15:59:51 +0000 Original-Received: from localhost ([127.0.0.1]:59948 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWJwV-0007AU-3A for submit@debbugs.gnu.org; Thu, 08 Sep 2022 11:59:51 -0400 Original-Received: from mail-yw1-f173.google.com ([209.85.128.173]:36561) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oWJwT-0007AG-98 for 57434@debbugs.gnu.org; Thu, 08 Sep 2022 11:59:49 -0400 Original-Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-348b1838c2bso14990617b3.3 for <57434@debbugs.gnu.org>; Thu, 08 Sep 2022 08:59:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=HP+UHXMaAMYSJUnLf530UiZVyQq3eBgEmOZw/Ea2hzc=; b=FMn3w/r7cUO+YvLvCsZgKrf1uWv1IVbi/fgzGbR36NaKWG5nT010nMoFsEnvs5qYi6 Y03SA7TSvGJm2UeZXIQYOFwaz9+c0YRQLjemVT5l34W84Rlvgt1fiUbqsvPZ7vAreZiA 2mfbaPzpOnFufzG3cvSVxj3wiN9+mi/scMEP+Yghan9ojS7HM2kwo46/q9ke2q0+Seuj yW8ktUIGSztrsI5TunUh8COGXGOrzX1aKaJ52TFLKy077m3cXNRoHuHTkIEeDN6g7aT1 MYx3Gq12BknAaZUibviQxKDPmR/YIXBQ/6TvVCCZXbsmq2fKYauVei/0eZzLJb7TXipn TOrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=HP+UHXMaAMYSJUnLf530UiZVyQq3eBgEmOZw/Ea2hzc=; b=I8iaLW2AHDlWMQp7whATuZD7I/VNY3ncsRp8zNMb72SGuytHJB6fq+1vCDJ5itvppn 6vvfKZiw4dNlhM5Cs+TTRDeAx7bQzacWWqsgoGyQTiBZIG4igOf8skuK2w1Z1M4a/5Em MRio4hC9JTN/oAZeRf1+FI6ucjnjynQDkzx3yc9PWKWdqI4mW3twfFLYSYQjNZzwW3/J 7MP12Lm0vP+4eRon5cyIazAxIpFC9tL0mezsZREH42QnpxiaRpvxiCSPMrv7qVmrcHS2 tSwE3kle9Jyd47Ukvm2r5j0n52Psbl85fx7Cu02hkYerVB4auwaXtgGJ78ge1wXMSYR1 VD6A== X-Gm-Message-State: ACgBeo2thstAyI8k/eOvhyn4zLkV24PBiCoYToNGAT8ibAm7Umo251Ks Xy+67/56I/Uw8PsLbW+1+TZ1zI7HsuEOs9ellOIsLQ== X-Google-Smtp-Source: AA6agR5VgOp6gcZOUTAejtUjzVVc4Pgu+YroPfjvVgHqAnIonn1L87otmckMYZl/upi/Jrs88YoYiDRLIyl0/eq5GZE= X-Received: by 2002:a0d:fb87:0:b0:335:db8b:416a with SMTP id l129-20020a0dfb87000000b00335db8b416amr8189529ywf.263.1662652783459; Thu, 08 Sep 2022 08:59:43 -0700 (PDT) In-Reply-To: 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:241923 Archived-At: --0000000000008b817905e82c8410 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I agree with Gerd on the discoveries. Here's some code how tmux works with that [1], we can probably avoid it by providing a frame-local flag which enables the functionality, so that multiple emacs clients might be connected from potentially different terminals. We can improve the default value of the flag based on terminal capabilities later once we have confidence in the way it works and probably extend it to support different specifications of syncing. [1]: https://github.com/tmux/tmux/blob/9c34aad21c0837123a51a5a4233a016805d3e526/= tty-features.c#L474 On Thu, Sep 8, 2022 at 2:35 AM Gerd M=C3=B6llmann wrote: > Eli Zaretskii writes: > > > I guess by P1 you mean these two sequences: > > > > BSU: ESC P =3D 1 s ESC \ > > ESU: ESC P =3D 2 s ESC \ > > > > whereas by P2 you mean these: > > > > DECRQM: ESC [ ? 2026 $ p > > DECRPM: ESC [ ? 2026 ; n $ y (with n =3D 0..4, and 0 or 4 means "no > support") > > BSU: ESC [ ? 2026 h > > ESU: ESC [ ? 2026 l > > Yes, that looks like them. > > > > >> > Do you happen to know where is the definitive documentation of Sync? > >> > >> Sorry, I don't know a definitive documentation. > > > > And any documentation at all? > > Not even that. I tried to find something today, but nothing useful > turned up. > > > > > Anyway, given the problems usually related to querying terminals about > > potentially unsupported features, and the general mess in this field, > > I think our best bet is to have a function that could switch the > > frame-update hooks between these 3 states: > > > > . unused > > . used with P1 BSU/ESU sequences > > . used with P2 BSU/ESU sequences > > > > WDYT? > > Yes, something like that, I guess. > --=20 *If you get an email from me outside of the 9-5 it is *not* because I'm always on or expect an immediate response from you; it is because of work flexibility . Evening and weekend emails are a sign I allocated some regular working hours for other things (such as family, gym, friends,...). And I encourage you to feel free to do the same. --0000000000008b817905e82c8410 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I agree with Gerd on the discoveries.

Here's some code how tmux works with that [1], we can probably av= oid it by providing a frame-local flag which enables the functionality, so = that multiple emacs clients might be connected from potentially different t= erminals.

We can improve the default value of the flag= based on terminal capabilities later once we have confidence in the way it= works and probably extend it to support different specifications of syncin= g.

[1]:=C2=A0https://g= ithub.com/tmux/tmux/blob/9c34aad21c0837123a51a5a4233a016805d3e526/tty-featu= res.c#L474

On Thu, Sep 8, 2022 at 2:35 AM Gerd M=C3=B6llmann <<= a href=3D"mailto:gerd.moellmann@gmail.com">gerd.moellmann@gmail.com>= wrote:
Eli Zare= tskii <eliz@gnu.org> writes:

> I guess by P1 you mean these two sequences:
>
>=C2=A0 =C2=A0BSU: ESC P =3D 1 s ESC \
>=C2=A0 =C2=A0ESU: ESC P =3D 2 s ESC \
>
> whereas by P2 you mean these:
>
>=C2=A0 =C2=A0DECRQM: ESC [ ? 2026 $ p
>=C2=A0 =C2=A0DECRPM: ESC [ ? 2026 ; n $ y=C2=A0 (with n =3D 0..4, and 0= or 4 means "no support")
>=C2=A0 =C2=A0BSU:=C2=A0 =C2=A0 ESC [ ? 2026 h
>=C2=A0 =C2=A0ESU:=C2=A0 =C2=A0 ESC [ ? 2026 l

Yes, that looks like them.

>
>> > Do you happen to know where is the definitive documentation o= f Sync?
>>
>> Sorry, I don't know a definitive documentation.
>
> And any documentation at all?

Not even that.=C2=A0 I tried to find something today, but nothing useful turned up.

>
> Anyway, given the problems usually related to querying terminals about=
> potentially unsupported features, and the general mess in this field,<= br> > I think our best bet is to have a function that could switch the
> frame-update hooks between these 3 states:
>
>=C2=A0 =C2=A0. unused
>=C2=A0 =C2=A0. used with P1 BSU/ESU sequences
>=C2=A0 =C2=A0. used with P2 BSU/ESU sequences
>
> WDYT?

Yes, something like that, I guess.


--
--0000000000008b817905e82c8410--