From: joakim@verona.se
To: Eli Zaretskii <eliz@gnu.org>
Cc: clement.pit@gmail.com, emacs-devel@gnu.org
Subject: Re: Take a screenshot from within Emacs
Date: Fri, 08 Jul 2016 10:29:04 +0200 [thread overview]
Message-ID: <m360sgh6sv.fsf@exodia.verona.se> (raw)
In-Reply-To: <83bn28k6e8.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Jul 2016 09:09:35 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: joakim@verona.se
>> Date: Thu, 07 Jul 2016 21:57:41 +0200
>> Cc: Emacs developers <emacs-devel@gnu.org>
>>
>> I don't think Emacs has the capability to access its internal rendering
>> data out of the box.
>
> Actually, it does, sort of. Take a look at the dump-glyph-matrix
> function and the subroutines it calls. There are also
> dump-frame-glyph-matrix (for TTY frames) and dump-tool-bar-row. They
> describe the data structures Emacs uses to draw its windows and
> frames. We could use them to provide some initial testing capability
> for the display engine. The disadvantages of using these functions
> are that (a) they currently need Emacs build with GLYPH_DEBUG defined,
> and (b) they don't test the terminal-specific parts of the display
> engine (in xterm.c, w32term.c, nsterm.m, etc.) that actually write to
> the glass.
Yes you are right of course. I even used those routines while working
on the xwidget branch, but forgot.
--
Joakim Verona
next prev parent reply other threads:[~2016-07-08 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 19:44 Take a screenshot from within Emacs Clément Pit--Claudel
2016-07-07 19:57 ` joakim
2016-07-08 6:09 ` Eli Zaretskii
2016-07-08 8:29 ` joakim [this message]
2016-07-08 9:13 ` psachin
2016-07-08 9:27 ` Eli Zaretskii
2016-07-08 16:10 ` Clément Pit--Claudel
2016-07-07 20:53 ` Andrey Tykhonov
2016-07-08 16:13 ` Clément Pit--Claudel
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=m360sgh6sv.fsf@exodia.verona.se \
--to=joakim@verona.se \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.