unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Render a buffer or string to a simpler string?
Date: Sun, 26 May 2013 07:38:30 +0400	[thread overview]
Message-ID: <87y5b2tnpl.fsf@yandex.ru> (raw)
In-Reply-To: <83a9niqwsa.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 May 2013 05:50:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
> We lack such a feature currently.  Display rendering is a C-level
> operation, whose result is not a string, but an array of structures
> called "glyphs" which are passed to the terminal back end for drawing
> on the screen.  So you need primitives (which don't exist) to produce
> Lisp strings out of those glyphs.

That's what I figured, but had to ask anyway. Thanks for the reply.
Anyway, instead of writing a hacky fix + a bunch of new tests, I ended
up finding a better fix instead (and changing existing tests).

>> To put it differently, the goal is to make the buffer look a certain way,
>> so I'd like to be able to check that it does look that way.
>
> That's hard to do automatically, unless you use external software that
> grabs screen portions.  Rendering is just one of the aspects, there's
> also alignment, decorations, remnants from previous redisplay cycles,
> etc.

I think it's a shame, because out of all (?) text editors, Emacs is the
best positioned to enable human-readable UI tests, because of how often
people use text properties to do visuals.

Testing UI look in graphical applications has to involve screen grabs,
at least on some level.

>> (For my current purpose, it would be fine if that render-to-string
>> function disregarded eyecandy text-properties, like `face', but in the
>> general case, being able to compare them, too, would be handy.)
>
> Removing properties from strings is a feature we do have.

Sure. That's not what I was asking. If render-to-string included those
text properties, that would be fine, too.



  reply	other threads:[~2013-05-26  3:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 19:36 Render a buffer or string to a simpler string? Dmitry Gutov
2013-05-25 20:58 ` Eli Zaretskii
2013-05-25 21:46   ` Dmitry Gutov
2013-05-26  2:50     ` Eli Zaretskii
2013-05-26  3:38       ` Dmitry Gutov [this message]
2013-05-26 15:11         ` Eli Zaretskii
2013-05-26 15:40           ` Dmitry Gutov
2013-05-26 16:15             ` Eli Zaretskii
2013-05-26 23:20               ` Dmitry Gutov
     [not found]             ` <mailman.418.1369584930.22516.help-gnu-emacs@gnu.org>
2013-05-26 17:08               ` esabof
2013-05-26 23:36                 ` Dmitry Gutov
2013-05-26 17:16       ` Stefan Monnier
2013-05-26 23:28         ` Dmitry Gutov
     [not found]       ` <mailman.419.1369588606.22516.help-gnu-emacs@gnu.org>
2013-05-26 17:56         ` esabof
2013-05-27  2:47           ` Eli Zaretskii
2013-05-27  2:48           ` Dmitry Gutov
     [not found]           ` <mailman.445.1369622831.22516.help-gnu-emacs@gnu.org>
2013-05-27 11:59             ` esabof
     [not found]           ` <mailman.446.1369622948.22516.help-gnu-emacs@gnu.org>
2013-05-27 12:14             ` esabof
     [not found] <mailman.381.1369510626.22516.help-gnu-emacs@gnu.org>
2013-05-25 20:45 ` Barry Margolin

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=87y5b2tnpl.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).