From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Testing redisplay code in batch Date: Wed, 23 Sep 2020 14:37:50 -0400 Message-ID: References: <83tuvovaer.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="717"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 23 20:52:17 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kL9sG-000AdC-Tc for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Sep 2020 20:52:16 +0200 Original-Received: from localhost ([::1]:43780 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kL9sF-0001wt-W5 for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Sep 2020 14:52:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57004) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kL9eO-0004kI-Rl for emacs-devel@gnu.org; Wed, 23 Sep 2020 14:37:56 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:33158) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kL9eM-0001hB-TK; Wed, 23 Sep 2020 14:37:56 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 5FB104406E4; Wed, 23 Sep 2020 14:37:53 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C6EA1440703; Wed, 23 Sep 2020 14:37:51 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1600886271; bh=ZzeOdSjdpZk9W+30nlsy996FxzSX+O67lzfbN/9Tjfo=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=aKWEvTrMeYuFy1exK3IJ07rEm6Xtqsj3bOWe5ftdPn4Mz+2uOqWAQyChoFFPkUYrW 81IPwoQmqXj6QzwONY1eEtUO4beH3/sQullUP8wp05B+HxXqbDXwcYYSDTne92AO4v YRiTuLhqV4vQvlpuF4JhmTS713Pc8xLAognjkrUuxlsdE6bV+JBeQWebqvlaxb67a5 CggA3VJiDnI7+IjzA4IFMgME/dvNjq8INSWqJEDhv3zby5hDVO1lZkT9yGY2pymrPi zAuIVpWPxkzz6Ck0tPrGE/EO2NKh1ePsikvcRRMup3AnVvzr+NElEeivjrkMARWAVX sXwzx9P0VnWoQ== Original-Received: from alfajor (unknown [45.72.232.131]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 9DE5C120778; Wed, 23 Sep 2020 14:37:51 -0400 (EDT) In-Reply-To: <83tuvovaer.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Sep 2020 17:24:12 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/23 14:35:04 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:256375 Archived-At: >> 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