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: Sat, 10 Sep 2022 09:15:20 +0300 Message-ID: <83fsgzbvrb.fsf@gnu.org> 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> <83wnacbk2o.fsf@gnu.org> <87r10kawfy.fsf@mail.jao.io> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35173"; mail-complaints-to="usenet@ciao.gmane.io" Cc: tom@logand.com, emacs-devel@gnu.org To: Jose A Ortega Ruiz Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 10 08:24:58 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 1oWtvF-0008zi-Di for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Sep 2022 08:24:57 +0200 Original-Received: from localhost ([::1]:44702 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWtvE-0002Zh-3J for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Sep 2022 02:24:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51038) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWtmJ-00081H-1G for emacs-devel@gnu.org; Sat, 10 Sep 2022 02:15:44 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:44018) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWtmH-0003e3-Ve; Sat, 10 Sep 2022 02:15:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=LoeSAhEV9kdc+WVHz0rJGTRXb+E5a0unR+yXd/OTQek=; b=rQfG33RHOSSI y3wUP6o7k9GfpxoKX+y7jSQl38HuRFyNifmFS9iUd/zJG6xKAGDySaYcYjYVoMRD4QJp25ydkD6lR IOlnuKJI8xpWMb9TG+9ymZC1XGS5mNUD48ZyocSaSZXK9MrFQOL/OVYDdCMi8PWFjqHpNK1jHnPq9 5BzyFrCweu6OtGG2ZU846RusrkBtQrqZ4TnMNwKEiV45sQ1cxSmYEutNfmAQzJESOhELBRHEsqNqP tPJeKEOQenSvJLPwoEvMP5kOhnu3dUNv0R+y8nfPVtVi2zNdzgOGGnYXCyFVvmlEIQiLYF64nVtbt Bcpoy8GFPaoSr7RKrWxgmw==; Original-Received: from [87.69.77.57] (port=2496 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 1oWtmH-0006Ta-DV; Sat, 10 Sep 2022 02:15:41 -0400 In-Reply-To: <87r10kawfy.fsf@mail.jao.io> (message from Jose A Ortega Ruiz on Sat, 10 Sep 2022 01:45:53 +0100) 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:295103 Archived-At: > From: Jose A Ortega Ruiz > Cc: tom@logand.com, emacs-devel@gnu.org > Date: Sat, 10 Sep 2022 01:45:53 +0100 > > On Fri, Sep 09 2022, Eli Zaretskii wrote: > > [...] > > > But you do want to support text and images in the same buffer, don't > > you? So the following situation: > > > > tttttttttttttttttttt (1) > > IIIIIII > > IIIIIII > > IIIIIII > > tttt IIIIIII ttttttt (2) > > tttttttttttttttttttt (3) > > > > where "t" is text is "I" is an image, should be supported, yes? > > no, not necessarily. i'd be already pretty happy even if that wouldn't > be possible. for my uses cases, rendering that as > > > tttttttttttttttttttt (1) > > IIIIIII > > IIIIIII > > IIIIIII > > IIIIIII > > tttt ttttttt (2) > > tttttttttttttttttttt (3) > > would be good enough. moreover, there are few cases of images inserted > by even current graphical emacs (at least in my use cases) with text > flowing on the sides (i remember even having to advice eww at some point > to get inline images). You misunderstand what I described, I think. It is a simple case of text mixed with an image, i.e. a line which has both text and images. It is not "text flowing on the sides of the image", which Emacs currently doesn't support even on GUI frames, not unless the image is displayed in slices. Try looking at some URL with images with EWW on a GUI frame, and you will see what I described. You said you did want to be able to have EWW display pages with images. If you do, what I described will be needed. By contrast, what you describe is a line that has only a single image, and no text (not even some whitespace) nor another image near it. Which is possible, but is just a subset of what needs to be supported.