From: Akib Azmain Turja <akib@disroot.org>
To: Jose A Ortega Ruiz <jao@gnu.org>
Cc: Tomas Hlavaty <tom@logand.com>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Implementing image support for kitty terminal
Date: Thu, 08 Sep 2022 17:13:18 +0600 [thread overview]
Message-ID: <871qsmazld.fsf@disroot.org> (raw)
In-Reply-To: <87a67bymys.fsf@mail.jao.io> (Jose A. Ortega Ruiz's message of "Wed, 07 Sep 2022 20:59:55 +0100")
[-- Attachment #1: Type: text/plain, Size: 3130 bytes --]
Jose A Ortega Ruiz <jao@gnu.org> writes:
> On Wed, Sep 07 2022, Tomas Hlavaty wrote:
>
>> On Wed 07 Sep 2022 at 21:11, Eli Zaretskii <eliz@gnu.org> wrote:
>>> In particular, the current model of image display
>>> in the Emacs display engine is that an image is basically considered a
>>> single very large character, from the screen layout POV.
>>
>> Are you talking about GUI emacs?
>> Is that not different in tty emacs?
>> I thought that the tty emacs has no concept of image (so far?).
>>
>>> I guess
>>> that's not what you have in mind for the above, so IMO it's important
>>> to come up with an alternative model that would somehow fit with the
>>> current display code with only minor changes, if we want this not to
>>> be too complex.
>>
>> For example, the tty based w3m web browser optionally supports images.
>> It reserves space w*h chars on the tty and then uses external program
>> to draw the image in the right place.
>>
>> I guess tty emacs would also need to reserve a w*h chars rectangle on
>> the tty and then send the right escape code to fill that gap with the
>> image.
>>
>> First, tty emacs would need to understand images instead of throwing
>> error. At least their dimensions. Maybe using some library or even in
>> elisp, for example like this
>> https://logand.com/sw/emacs-framebuffer/file/emacs-framebuffer.el.html#l286
>> I have not figured out, how to actually plug it into upstream emacs, as
>> this seems to require a lot of changes to C code.
>
> fwiw, in the kitty case, image libraries are going to be almost for sure
> available, it being an x11/wayland application. so an emacs compiled
> with image support (but not necessarily linking against any x libs)
> doesn't seem like a strong requirement. in that scenario, determining
> the size of an image wouldn't needed a lot of C code, would it? and, if
> those libraries are not available, a call to "file foo.png" is (at least
> in my system) telling me the size of foo.png... kind of hacky, of
> course, but as a first step maybe good enough.
>
>> Second, tty emacs would need to somehow reserve rectangle for the image.
>> This might be lots of work I guess.
>
> i was hoping this wouldn't be the case... at least when running inside
> terminal emulators, emacs nox seems pretty dexterous lying out windows
> and filly them with content, and i reckoned it must have a pretty good
> idea of their sizes. but maybe i'm too optimistic :)
>
>> Third, there would have to be a piece of code which actually draws the
>> image. In case of kitty terminal, the image path and coordinates would
>> be sent to the tty using the kitty terminal protocol.
>
> (as an aside, this would also work for other terminals like konsole or
> wayst, which support the protocol).
>
> cheers,
> jao
What? You need to send the path of the image? How would this work for
a SSH session?
--
Akib Azmain Turja
Find me on Mastodon at @akib@hostux.social.
This message is signed by me with my GnuPG key. Its fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-09-08 11:13 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 15:50 Implementing image support for kitty terminal Jose Antonio Ortega Ruiz
2022-09-07 17:10 ` Tomas Hlavaty
2022-09-07 18:11 ` Eli Zaretskii
2022-09-07 18:49 ` Jose A Ortega Ruiz
2022-09-07 19:41 ` Eli Zaretskii
2022-09-07 20:09 ` Jose A Ortega Ruiz
2022-09-08 6:51 ` Eli Zaretskii
2022-09-07 20:11 ` Stefan Monnier
2022-09-08 5:30 ` Eli Zaretskii
2022-09-08 12:47 ` Gerd Möllmann
2022-09-08 13:54 ` Eli Zaretskii
2022-09-08 14:03 ` Gerd Möllmann
2022-09-08 14:24 ` Gerd Möllmann
2022-09-08 16:04 ` Eli Zaretskii
2022-09-09 4:59 ` Gerd Möllmann
2022-09-09 12:19 ` Stefan Monnier
2022-09-09 12:53 ` Eli Zaretskii
2022-09-09 12:59 ` Gerd Möllmann
2022-09-09 13:17 ` tomas
2022-09-09 14:10 ` Gerd Möllmann
2022-09-09 14:20 ` Eli Zaretskii
2022-09-09 14:27 ` Gerd Möllmann
2022-09-09 15:12 ` Stefan Monnier
2022-09-10 7:52 ` Gerd Möllmann
2022-09-10 14:13 ` Optimizing tty display update (was: Implementing image support for kitty terminal) Stefan Monnier
2022-09-10 14:17 ` Gerd Möllmann
2022-09-10 14:25 ` Eli Zaretskii
2022-09-10 14:29 ` Gerd Möllmann
2022-09-10 15:14 ` Optimizing tty display update Stefan Monnier
2022-09-11 10:21 ` Gerd Möllmann
2022-09-11 1:09 ` Po Lu
2022-09-11 4:44 ` Gerd Möllmann
2022-09-11 5:32 ` VCS forensics (was: Optimizing tty display update) Eli Zaretskii
2022-09-11 5:51 ` VCS forensics Gerd Möllmann
2022-09-10 16:54 ` Optimizing tty display update Lars Ingebrigtsen
2022-09-10 8:06 ` Implementing image support for kitty terminal Kyaw Thu Soe
2022-09-09 13:27 ` Stefan Monnier
2022-09-08 16:00 ` Eli Zaretskii
2022-09-09 4:58 ` Gerd Möllmann
2022-09-07 18:56 ` Tomas Hlavaty
2022-09-07 19:51 ` Eli Zaretskii
2022-09-08 18:30 ` Tomas Hlavaty
2022-09-08 18:45 ` Eli Zaretskii
2022-09-08 19:45 ` Tomas Hlavaty
2022-09-08 20:33 ` Jose A Ortega Ruiz
2022-09-08 20:29 ` Jose A Ortega Ruiz
2022-09-08 20:52 ` Tomas Hlavaty
2022-09-08 21:47 ` Jose A Ortega Ruiz
2022-09-08 22:21 ` Óscar Fuentes
2022-09-08 22:46 ` Tomas Hlavaty
2022-09-09 5:48 ` Jose A Ortega Ruiz
2022-09-08 22:43 ` Tomas Hlavaty
2022-09-08 23:32 ` Jose A Ortega Ruiz
2022-09-09 1:43 ` Po Lu
2022-09-09 5:52 ` Jose A Ortega Ruiz
2022-09-09 7:25 ` Po Lu
2022-09-09 6:06 ` Eli Zaretskii
2022-09-09 6:21 ` Jose A Ortega Ruiz
2022-09-09 6:43 ` Eli Zaretskii
2022-09-09 14:56 ` Jose A Ortega Ruiz
2022-09-09 15:20 ` chad
2022-09-09 15:34 ` Jose A Ortega Ruiz
2022-09-10 2:56 ` Tomas Hlavaty
2022-09-10 3:35 ` Visuwesh
2022-09-10 6:01 ` Tomas Hlavaty
2022-09-10 6:51 ` Po Lu
2022-09-10 19:52 ` Tomas Hlavaty
2022-09-09 15:25 ` Stefan Monnier
2022-09-09 16:15 ` Eli Zaretskii
2022-09-10 0:45 ` Jose A Ortega Ruiz
2022-09-10 6:15 ` Eli Zaretskii
2022-09-09 1:41 ` Po Lu
2022-09-09 5:53 ` Jose A Ortega Ruiz
2022-09-22 17:31 ` Memory problems update (was: Implementing image support for kitty terminal) Jose Antonio Ortega Ruiz
2022-09-23 0:29 ` Memory problems update Po Lu
2022-09-23 1:11 ` Jose A Ortega Ruiz
2022-09-23 6:08 ` Eli Zaretskii
2022-09-23 21:46 ` Jose A Ortega Ruiz
2022-09-23 21:57 ` Jose A Ortega Ruiz
2022-09-23 23:32 ` Jose A Ortega Ruiz
2022-09-24 0:20 ` Po Lu
2022-09-24 12:59 ` Jose A Ortega Ruiz
2022-09-23 5:33 ` Memory problems update (was: Implementing image support for kitty terminal) Eli Zaretskii
2022-09-23 22:01 ` Jose A Ortega Ruiz
2022-09-24 6:25 ` Eli Zaretskii
2022-09-24 6:33 ` Memory problems update Po Lu
2022-09-24 12:53 ` Jose A Ortega Ruiz
2022-09-09 1:40 ` Implementing image support for kitty terminal Po Lu
2022-09-09 5:56 ` Jose A Ortega Ruiz
2022-09-07 19:59 ` Jose A Ortega Ruiz
2022-09-08 11:13 ` Akib Azmain Turja [this message]
2022-09-08 13:25 ` Jose A Ortega Ruiz
2022-09-08 19:26 ` Tomas Hlavaty
2022-09-08 19:15 ` Tomas Hlavaty
2022-09-08 19:30 ` Eli Zaretskii
2022-09-08 20:03 ` Tomas Hlavaty
2022-09-09 5:43 ` Eli Zaretskii
2022-09-10 3:02 ` Tomas Hlavaty
2022-09-08 10:59 ` Akib Azmain Turja
2022-09-08 13:44 ` Eli Zaretskii
2022-09-08 9:13 ` Akib Azmain Turja
2022-09-08 19:31 ` Tomas Hlavaty
-- strict thread matches above, loose matches on Subject: below --
2022-09-10 10:15 xenodasein--- via Emacs development discussions.
2022-09-10 10:38 ` Eli Zaretskii
2022-09-10 11:06 ` xenodasein--- via Emacs development discussions.
2022-09-10 11:13 ` Akib Azmain Turja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qsmazld.fsf@disroot.org \
--to=akib@disroot.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jao@gnu.org \
--cc=tom@logand.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.