From: Eli Zaretskii <eliz@gnu.org>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: Emacs canvas support
Date: Wed, 29 Apr 2020 20:38:07 +0300 [thread overview]
Message-ID: <83h7x2xke8.fsf@gnu.org> (raw)
In-Reply-To: <83imhixkva.fsf@gnu.org> (message from Eli Zaretskii on Wed, 29 Apr 2020 20:27:53 +0300)
> Date: Wed, 29 Apr 2020 20:27:53 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> That's not how Emacs controls what's on display. It basically
> represents each window as a 2D array of glyphs, each one of which has
> a certain graphical representation. The representation itself is of
> no concern to the display engine (well, almost); the only thing it
> cares about is the metrics of each glyph, because that's what it needs
> to do layout calculations.
Oh, and one more important aspect: everything that winds up on display
must come from some buffer or some Lisp string. It could be a special
text property or somesuch, but it must be found by walking some buffer
or some known-in-advance Lisp string, because that's what top-level
display functions do: they iterate over these objects, and produce the
glyphs based on what they find there.
next prev parent reply other threads:[~2020-04-29 17:38 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875zdikdge.fsf.ref@yahoo.com>
2020-04-29 6:34 ` Emacs canvas support Po Lu via Emacs development discussions.
2020-04-29 8:24 ` Eli Zaretskii
2020-04-29 9:57 ` Po Lu
2020-04-29 10:10 ` Eli Zaretskii
2020-04-29 10:22 ` Po Lu
2020-04-29 10:27 ` Po Lu via Emacs development discussions.
2020-04-29 11:47 ` Eli Zaretskii
2020-04-29 10:35 ` Eli Zaretskii
2020-04-29 10:41 ` Po Lu
2020-04-29 11:51 ` Eli Zaretskii
2020-04-29 12:12 ` Po Lu
2020-04-29 16:14 ` David Engster
2020-04-29 16:54 ` Eli Zaretskii
2020-04-29 17:16 ` tomas
2020-04-29 17:27 ` Eli Zaretskii
2020-04-29 17:38 ` Eli Zaretskii [this message]
2020-04-30 13:11 ` Arthur Miller
2020-04-30 14:18 ` Eli Zaretskii
2020-04-30 14:58 ` Arthur Miller
2020-04-30 17:30 ` Eli Zaretskii
2020-05-01 14:32 ` Arthur Miller
2020-04-29 18:51 ` tomas
2020-04-29 19:03 ` Eli Zaretskii
2020-04-29 19:08 ` tomas
2020-04-29 19:25 ` Eli Zaretskii
2020-04-29 19:59 ` tomas
2020-04-30 1:19 ` Stefan Monnier
2020-04-30 6:55 ` tomas
2020-04-30 12:03 ` Stefan Monnier
2020-04-30 12:50 ` tomas
2020-04-30 8:04 ` Po Lu
2020-04-30 12:08 ` Stefan Monnier
2020-04-30 13:55 ` Eli Zaretskii
2020-05-01 23:27 ` Po Lu
2020-05-02 6:51 ` Eli Zaretskii
2020-04-30 13:46 ` Eli Zaretskii
2020-04-30 14:37 ` Stefan Monnier
2020-04-30 17:27 ` Eli Zaretskii
2020-04-30 18:22 ` Stefan Monnier
2020-04-30 18:42 ` Eli Zaretskii
2020-04-30 14:27 ` Drew Adams
2020-04-30 13:33 ` Eli Zaretskii
2020-04-30 13:52 ` Arthur Miller
2020-04-29 19:23 ` David Engster
2020-04-30 13:29 ` Eli Zaretskii
2020-04-30 6:52 ` Corwin Brust
2020-04-29 17:08 ` Eli Zaretskii
2020-04-29 20:14 ` David Engster
2020-04-30 13:35 ` Eli Zaretskii
2020-04-29 20:48 ` Juri Linkov
2020-04-30 2:36 ` Eli Zaretskii
2020-04-30 20:20 ` Juri Linkov
2020-05-01 6:01 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h7x2xke8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).