Re: Implementing image support for kitty terminal

[Jose A Ortega Ruiz]

On Fri, Sep 09 2022, chad wrote:

> On Fri, Sep 9, 2022 at 10:57 AM Jose A Ortega Ruiz <jao@gnu.org> 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)