unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Testing redisplay code in batch
Date: Wed, 23 Sep 2020 14:37:50 -0400	[thread overview]
Message-ID: <jwvlfh0tk6v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83tuvovaer.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Sep 2020 17:24:12 +0300")

>> So I'm ideally looking for a way to convince Emacs's internals to
>> perform redisplay as if there were "real" windows.  I don't need to
>> "see/display" the result, OTOH because I only need to test things like
>> `window-start` and `window-end` after calling `redisplay`.
>
> I think it is best to define the capabilities required from such a
> test harness.  What you say about seems to hint that you only intend
> to look at stuff exposed to Lisp.  If that is indeed the case, it
> could be easier to provide, but many aspects of the display engine
> cannot be tested this way, since only a small fraction of that is
> exposed to Lisp.

Indeed.  In the past I was thinking (abstractly) of much more demanding
circumstances, but for this specific test, all I need is to know the
`window-start`, so the corresponding data is already exposed to Lisp.
I don't know if that makes it easy enough to implement it without
significant work.


        Stefan




  reply	other threads:[~2020-09-23 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  3:56 Testing redisplay code in batch Stefan Monnier
2020-09-23 10:34 ` Phil Sainty
2020-09-23 23:16   ` Stefan Monnier
2020-09-24 14:31     ` Eli Zaretskii
2020-09-24 18:31       ` Stefan Monnier
2020-09-24 18:58         ` Eli Zaretskii
2020-09-23 10:50 ` Alan Mackenzie
2020-09-23 13:30   ` Stefan Monnier
2020-09-23 14:24 ` Eli Zaretskii
2020-09-23 18:37   ` Stefan Monnier [this message]
2020-09-23 18:51     ` 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=jwvlfh0tk6v.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).