From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: chad Newsgroups: gmane.emacs.devel Subject: Re: Implementing image support for kitty terminal Date: Fri, 9 Sep 2022 11:20:03 -0400 Message-ID: References: <87v8pz18wf.fsf@mail.jao.io> <83o7vrgimc.fsf@gnu.org> <87wnafdnee.fsf@logand.com> <835yhzgdyi.fsf@gnu.org> <87k06den1s.fsf@logand.com> <87illxy5ir.fsf@mail.jao.io> <87sfl1d1wi.fsf@logand.com> <87czc5y1wp.fsf@mail.jao.io> <878rmtcwrv.fsf@logand.com> <87a679xx0v.fsf@mail.jao.io> <83zgf9cc9i.fsf@gnu.org> <87zgf9ax01.fsf@mail.jao.io> <83wnadcajk.fsf@gnu.org> <87wnacbnq4.fsf@mail.jao.io> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000003dc15205e840159d" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36302"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Tomas Hlavaty , EMACS development team To: Jose A Ortega Ruiz Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 09 17:21:29 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 1oWfov-0009Ik-Mk for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 17:21:29 +0200 Original-Received: from localhost ([::1]:53132 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWfou-0004V7-4z for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 11:21:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWfnt-0003LR-AY for emacs-devel@gnu.org; Fri, 09 Sep 2022 11:20:28 -0400 Original-Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]:39715) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oWfno-0003um-MZ; Fri, 09 Sep 2022 11:20:22 -0400 Original-Received: by mail-ed1-x52b.google.com with SMTP id z8so3018676edb.6; Fri, 09 Sep 2022 08:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=hq4ysaDEclbcmeq1JBNvSh3nUpD8l8gJ7se6MqpRUa8=; b=fVRg3OYQ6GjofIpyyKVAaLb9IZrDrCgNOyvXqx7uxVGRmMzlW1G00bpwxZZyyKnBZN dm5Pa5zlQivxa0ixCe+r/SruFd7/SIj23JTtV/S3oaff8HLu7doodBOdLBQLosK4nOpd Qz8mKYET8RQzIBVjQmzH+wPpqmVSGpvprVVcHivJyVicXDVJ5kYvKdRrQjVTwuHVbdu/ m5KVSn4JqC/RWB/KtnVff30uizxr6jUzYbJvmOLRKO67uWbl3eiPzmu+Ku6AJdQgH1pJ k7YbpdF36iMCL/TR3FOVMxND3l5tR9ae087B4UKZAoM6maMJaOxgIs3eAnTEsyoO1IV5 ic+g== 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=hq4ysaDEclbcmeq1JBNvSh3nUpD8l8gJ7se6MqpRUa8=; b=t8rUPrH0YOwyBRNKds/mMJPzKtSD+HvJSXaRNu+TQa3I2pwMiVdfqhLCYXX+M8kCIG YqUSufjf+P0PwNMYnstgCEq8aFZx9j+2N+BcoZ6gGq4rVuDGJbLrg+m72BVGe5q1rGTZ xkg+7XzkskMyTGEq4RzbJNXGIbknuHv4TX+RRUyIwbvsLlz5gcG8B2p31eyuJcaCN1Ic Sp2n1mVyM+/ICNh4Jbc3e6fKchhsoaAMEjRDSaprKLuiFV87xqVFjZFHtWUr9vk5+6/V D8Fez5cHSTkfITJ6hBHB5Pv67L0WysZUNwwOgiv5RwQPH+x6b65X9l6ItSu5XTvQUCXk Z/2g== X-Gm-Message-State: ACgBeo2PLLanPKvulrSDOFzgEHW40lYOa68MWLCr7kMQB4xD0CX65pYi Q9v9YssDC8MsasiLtLcptdJCq3dVisrLxrWREFonilse X-Google-Smtp-Source: AA6agR672h2sQQ76I+sK3hiqJPlQKysdNQTeD/YLimc+jKz3JDxfCdy2s+XZD274GEiIpbHpr7EH/lyn3RaCk/+IplU= X-Received: by 2002:a05:6402:ca9:b0:44e:d8f3:3d0e with SMTP id cn9-20020a0564020ca900b0044ed8f33d0emr11686806edb.397.1662736815471; Fri, 09 Sep 2022 08:20:15 -0700 (PDT) In-Reply-To: <87wnacbnq4.fsf@mail.jao.io> Received-SPF: pass client-ip=2a00:1450:4864:20::52b; envelope-from=yandros@gmail.com; helo=mail-ed1-x52b.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:295077 Archived-At: --0000000000003dc15205e840159d Content-Type: text/plain; charset="UTF-8" On Fri, Sep 9, 2022 at 10:57 AM Jose A Ortega Ruiz wrote: > [...] > > > xxxx > xxxx > xxxx How will you handle > xxxx this text? > xxxx Note that users have to reach that text, for example with C-n, including both lines. Also, it needs to wrap between "handle" and "this". This ignores a bunch of other issues like "what happens if the image is sliced into more lines than will fit on the screen at once?". This is a commonly recurring idea. In the 90's, HTML went through these concerns with a model that was mostly (Grail, Amaya, etc.) read-only, and ended up with CSS and the DOM, which are conceptually close to emacs' redisplay engine and glyph matrix. It is certainly possible to forbid/ignore most of the complexity in favor of a simple hack, as people have mentioned already. That doesn't help figure out the issues that would be necessary to make the feature be fully (or even mostly) emacs-capable, and if that's what you want, doesn't emacs-framebuffer already give you that? Hope that helps, ~Chad --0000000000003dc15205e840159d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, Sep 9, 2022 at 10:57 AM Jose A Or= tega Ruiz <jao@gnu.org> wrote:
[...]

=C2=A0
xxxx
xxxx
xxxx=C2=A0 How will you handle
xxxx=C2=A0 this text?
xxxx

Note that users have to reach that text, for example with C-n, incl= uding both lines. Also, it needs to wrap between "handle" and &qu= ot;this". This ignores a bunch of other issues like "what happens= if the image is sliced into more lines than will fit on the screen at once= ?".

This is a commonly recurring idea. In the 90's, HTML went through th= ese concerns with a model that was mostly (Grail, Amaya, etc.) read-only, a= nd ended up with CSS and the DOM, which are conceptually close to emacs'= ; redisplay engine and glyph matrix.

It is certainly possible to forbid/ignore mo= st of the complexity=C2=A0in favor of a simple hack, as people have mention= ed already. That doesn't help figure out the issues that would be neces= sary to make the feature be fully (or even mostly) emacs-capable, and if th= at's what you want, doesn't emacs-framebuffer already give you that= ?

Hope= that helps,
~Chad

--0000000000003dc15205e840159d--