all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Testing redisplay code in batch
Date: Tue, 22 Sep 2020 23:56:33 -0400	[thread overview]
Message-ID: <jwv1ritw5mo.fsf-monnier+emacs@gnu.org> (raw)

I have a test for the Bug#43519 which I'd like to add to our test suite,
but it requires the redisplay to do its job, and in batch mode it seems
that Mr. Redisplay gets quite sloppy.

Does someone have experience with batch-tests of redisplay code?

So far I've only use the "let-bind execute-kbd-macro to t" trick in
order to convince minibuffer functions to actually use a minibuffer
and process events from `unread-command-events`, but here I need to go
further because I the "dummy windows" used in batch mode aren't
good enough.

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`.

If that can't be done without major surgery to the C code, has someone
already setup some way to run interactive tests in some virtual
interactive session (I guess using something like a detached `screen` or
`tmux`)?


        Stefan




             reply	other threads:[~2020-09-23  3:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  3:56 Stefan Monnier [this message]
2020-09-23 10:34 ` Testing redisplay code in batch 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv1ritw5mo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.