From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jose A Ortega Ruiz Newsgroups: gmane.emacs.devel Subject: Re: Implementing image support for kitty terminal Date: Fri, 09 Sep 2022 16:34:08 +0100 Message-ID: <87tu5gblzj.fsf@mail.jao.io> 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: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30148"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Tomas Hlavaty , EMACS development team To: chad Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 09 17:36:01 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 1oWg2z-0007i2-Bm for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 17:36:01 +0200 Original-Received: from localhost ([::1]:37708 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWg2y-0002Wp-4x for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 11:36:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51516) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWg1E-0001p2-0Q for emacs-devel@gnu.org; Fri, 09 Sep 2022 11:34:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51068) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWg1D-00062O-I2; Fri, 09 Sep 2022 11:34:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=xDv7TbETyDRKcG1nohKFw2DzVcRqww7+4ih8oG3KV9s=; b=gGQXf91bMf08VQetpEsd v72O3sZ1kkF8VnVghaFbHLRETUCLbEDfsuky28s0mmDgVGV14DG1U9oxf9/UPWv/EwGEg84rYBWaw t+tVG1TBPR+gz6bzFuVuzfw2coQnST3YEIGs2Qahl7EdN+74zdO0oZkhgOmhHzR0yRuHfdeF6x2UW 8HSKr+KqVCLENEVU68Drtyd1xdRgHeMqfA+gLiX8oeKk8qEYFcYmnaTLh3L5/zUC5qDswW2CUIsT2 0Zz0Q99eXBbkXGW1zRv7sk2dtVoBRgn2aiWjnRcGUAFKITycOpo0challXdkf92G/v1TLKriNWPqA 5wEhhEhx5snHlQ==; Original-Received: from cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net ([92.233.85.247]:49832 helo=rivendell.localdomain) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWg1C-0002Bj-Kr; Fri, 09 Sep 2022 11:34:10 -0400 Original-Received: from localhost (rivendell.localdomain [local]) by rivendell.localdomain (OpenSMTPD) with ESMTPA id d1dfb762; Fri, 9 Sep 2022 15:34:08 +0000 (UTC) In-Reply-To: X-Attribution: jao X-Clacks-Overhead: GNU Terry Pratchett X-URL: 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:295079 Archived-At: On Fri, Sep 09 2022, chad wrote: > 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?". well, i simply wouldn't. text alongside images in a window wouldn't be allowed, and it would appear below the image (that's actually how eww behaves with images, even in graphical terminals, at least in some cases). i don't want to convert term emacs in a graphical wyswig editor, just to display images every now and then. perfect enemy of the better and all that :) [...] > 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? i've never used emacs-framebuffer, but i don't think so. i want, for instance, to run emacs in a wayland or x11 term, possibly interacting with other applications there (e.g., i want to watch videos, or, every now and then, open complex webpages in firefox). cheers, jao -- Spend the afternoon. You can't take it with you. -Annie Dillard, author (b. 1945)