From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Markus Triska Newsgroups: gmane.emacs.bugs Subject: bug#53798: 27.1; OSX: (redisplay) does not reliably redisplay Date: Sat, 05 Feb 2022 19:55:31 +0100 Message-ID: <875yptb0t8.fsf@metalevel.at> References: <83leyp1mte.fsf@gnu.org> <87tuddxlwb.fsf@metalevel.at> <83ee4h196x.fsf@gnu.org> <87h79duq77.fsf@metalevel.at> <83a6f517mw.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="309"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: 53798@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 05 19:56:58 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1nGQEy-000APC-BB for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Feb 2022 19:56:56 +0100 Original-Received: from localhost ([::1]:33782 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nGQEw-0004ME-UN for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Feb 2022 13:56:54 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60840) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nGQE7-0004Jb-81 for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 13:56:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41701) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nGQE6-00008F-9c for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 13:56:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nGQE6-0004Us-8F for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 13:56:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Markus Triska Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Feb 2022 18:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53798 X-GNU-PR-Package: emacs Original-Received: via spool by 53798-submit@debbugs.gnu.org id=B53798.164408733417220 (code B ref 53798); Sat, 05 Feb 2022 18:56:02 +0000 Original-Received: (at 53798) by debbugs.gnu.org; 5 Feb 2022 18:55:34 +0000 Original-Received: from localhost ([127.0.0.1]:35592 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nGQDe-0004Tg-Gy for submit@debbugs.gnu.org; Sat, 05 Feb 2022 13:55:34 -0500 Original-Received: from [78.47.144.35] (port=46242 helo=metalevel.at) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nGQDc-0004TX-Gv for 53798@debbugs.gnu.org; Sat, 05 Feb 2022 13:55:32 -0500 Original-Received: by metalevel.at (Postfix, from userid 1000) id 175179C755; Sat, 5 Feb 2022 19:55:31 +0100 (CET) In-Reply-To: <83a6f517mw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Feb 2022 20:38:15 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:226087 Archived-At: Eli Zaretskii writes: > If you want Emacs to do something, why do you care about redisplay and > its rate? Redisplay cannot affect what Emacs does, it just reflects > the snapshot of the state. In many such cases, I would like to get an expression about how far along Emacs has already come, and also to see whether the actions I automated contain obvious errors which would become immediately apparent from seeing a sequence of intermediary steps which are displayed like a movie. In addition, also in cases where I do know that everything works correctly, I would often like to show these steps to others so that they get an impression about what is going on internally. Seeing only a stalled Emacs prevents a truly impressive and enjoyable presentation. In addition, I would like to automate everything reliably in the sense that it runs in the same way irrespective of what else is going on, such as whether a key is accidentally pressed, the mouse is moved etc. > I don't understand why you care. Why not leave Emacs to its devices, > so it performs redisplay when it finishes whatever it is that you want > it to do? In this concrete case, I looked at the documentation of `redisplay', and it reads, at the start: Perform redisplay. Since I see no redisplay, I wondered whether the documentation is in fact correct. This is what led me to reporting this issue, in the hope that someone cares sufficiently about Emacs to align the functionality of redisplay with its documentation. > I think Alan or someone else who can look into this stuff on macOS > should chime in, because it sounds like its macOS specific. I also > notice that the redisplay architecture on macOS have changed > dramatically since Emacs 27.1, so maybe the current code base no > longer behaves like what you see. Thank you a lot! If there are any questions, please let me know. All the best, Markus