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.devel Subject: Re: Implementing image support for kitty terminal Date: Thu, 08 Sep 2022 19:04:59 +0300 Message-ID: <83leqtetsk.fsf@gnu.org> References: <83v8pydl9a.fsf@gnu.org> <221cc6e0-ac45-cf03-6b17-c8c3798eebe3@gmail.com> <81f8b155-bc03-187d-2df1-9664374e890a@gmail.com> 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="1347"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org, jao@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 08 18:14:51 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oWKAz-00004y-Dt for ged-emacs-devel@m.gmane-mx.org; Thu, 08 Sep 2022 18:14:49 +0200 Original-Received: from localhost ([::1]:55358 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWKAy-0007zC-El for ged-emacs-devel@m.gmane-mx.org; Thu, 08 Sep 2022 12:14:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54250) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWK20-00024i-CU for emacs-devel@gnu.org; Thu, 08 Sep 2022 12:05:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52308) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWK1y-00051x-8T; Thu, 08 Sep 2022 12:05:31 -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=Mt5N8Ebm53sqc9ma5bemFrDgUTcutbZiAmoW47NcJtw=; b=NkRNmipgiJMjoR3UVvCd JuP5BBDQD8LWPzBBkwqGlzlEDyd/lX7IT13zl/11ebnV5Co80jNmh2SvPEGJCvTSjX4Vxl9v7Usca mOs8cZBcWuxxxeYJM3lA7RmqSO8BV8eic53a5YVoyF28RVeQRelWBpgEx92pN0+eBUbbEv/bxxhfN 2worxYm3aYZ6uicGuKn2O11mtG8IsFlegBDGfrxJciaxjScGUVlSnA+LuwwNx1mNPa3yciVVePXHG R2tlfbAOJfcdnSR3gZvgrp2MZRWNsE4Fl7YQFVRvQjHIt0gUqcvHa5Gn4x507L2ZDKgJ0KVEcnSt1 NraQVwdiIXvsDw==; Original-Received: from [87.69.77.57] (port=1278 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 1oWK1m-00029x-UH; Thu, 08 Sep 2022 12:05:28 -0400 In-Reply-To: <81f8b155-bc03-187d-2df1-9664374e890a@gmail.com> (message from Gerd =?utf-8?Q?M=C3=B6llmann?= on Thu, 8 Sep 2022 16:24:33 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:294986 Archived-At: > Date: Thu, 8 Sep 2022 16:24:33 +0200 > From: Gerd Möllmann > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org, jao@gnu.org > > On 22-09-08 16:03 , Gerd Möllmann wrote: > > On 22-09-08 15:54 , Eli Zaretskii wrote: > >>> Date: Thu, 8 Sep 2022 14:47:48 +0200 > >>> Cc: eliz@gnu.org, emacs-devel@gnu.org, jao@gnu.org > >>> From: Gerd Möllmann > >>> > >>> And I'd leave the "normal" terminal code out of this. > >> > >> Including frame-based redisplay in update_frame? > > > > Yes, I'd leave that as-is.  The frame-based updates used to be quite > > important for relatively dumb and slow terminals because it increases > > the possibility of reusing parts of the display that are alreay > > displayed on the terminal. > > > > I guess terminal emulators allowing images and such are less likely to > > benefit from that. > > Or even, do we still have terminals connected with, don't know, say 1200 > baud or some such? I don't think so, but we do have slow net links and ssh logins. > If not, or not many, maybe such a new backend that is not > frame-based could replace the frame-based one eventually? That's possible. Someone should take measurements and present the results.