From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#45898: 27.1; wedged in redisplay again Date: Thu, 09 Jun 2022 12:30:07 +0200 Message-ID: <87leu686z4.fsf@gnus.org> References: <46b65e3f-cf3d-a3f2-9a9a-100e58274ff6@jovi.net> <87h74wh9x7.fsf@gnus.org> <83bkv47evy.fsf@gnu.org> <87k09rbcmn.fsf@gnus.org> <83a6an5jt3.fsf@gnu.org> <8335gf5er3.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="9999"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Emacs-hacker2018@jovi.net, 45898@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 09 15:03:46 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 1nzHpB-0002Nu-Rk for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Jun 2022 15:03:45 +0200 Original-Received: from localhost ([::1]:58342 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nzHpA-0002Ws-Kd for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Jun 2022 09:03:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60060) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nzFRO-0001fr-2S for bug-gnu-emacs@gnu.org; Thu, 09 Jun 2022 06:31:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51184) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nzFRN-0002Vn-OJ for bug-gnu-emacs@gnu.org; Thu, 09 Jun 2022 06:31:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nzFRN-0001tJ-Kk for bug-gnu-emacs@gnu.org; Thu, 09 Jun 2022 06:31:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 09 Jun 2022 10:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45898 X-GNU-PR-Package: emacs Original-Received: via spool by 45898-submit@debbugs.gnu.org id=B45898.16547706237202 (code B ref 45898); Thu, 09 Jun 2022 10:31:01 +0000 Original-Received: (at 45898) by debbugs.gnu.org; 9 Jun 2022 10:30:23 +0000 Original-Received: from localhost ([127.0.0.1]:45081 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nzFQk-0001s5-LE for submit@debbugs.gnu.org; Thu, 09 Jun 2022 06:30:22 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:47626) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nzFQf-0001rj-G2 for 45898@debbugs.gnu.org; Thu, 09 Jun 2022 06:30:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=kxdd9c1K017mpCiYHTI4Z4oZgZrKRwLAAqxrOtN2qvg=; b=U+BKuYfyN1TJOZFw+dBzE9+3jO MaMUpEPvpCWNoU04o4XkLp/m8DjnCeJPieo0ZSNmgIu1t0xYJlf+VUpNc+jxy5yW+W9yzI4p1uZ5F 8VkJcRmvGCgz5/h+iw+FDUaE6eIS3LLRziBKn0Wmdsxlg/LtxUkVjqBCbTU1o7anuGOA=; Original-Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzFQV-0006O2-Te; Thu, 09 Jun 2022 12:30:10 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAG1BMVEX22Cb20Q7Xszs0 LjguWqbi0qSjSzv69t7///9X/eT6AAAAAWJLR0QIht6VegAAAAd0SU1FB+YGCQoZLrTAyRQAAAGz SURBVDjLddLBjpswEAZguhLtFbNK7piFB+gQvwBEvQOO72Hj3Lsi8/qdsQ2YZGspQfKnGfyPSZIf QoiM/rI3aDpeLfAvEcvKKvDS0mMHIwCsMEUwNK0rea54a5vONfsOSDRtfnatSo7WHpWFQqQMHaAZ CDqCSR0nYPBn0vchVHgQC3Rq4BwM1EpZIX4G6AhaUInIayllLouPAOcJWmAQpZ2gBLWBAg9C5CLP 5doKFDRxjnSD/RC1XoDTb7PKtB7/B/gtUCuc/dQpIOwrnDhQMQx/EHH0N6sgrugIcH6FURsWniFE cNDjmfdxolNZGYNuHIDSuj/uwHWa4YRz/x6D28eHg/IVBlBGy2mDPHSyAJWMIdO+E8FVSniBC12n 2kHioSawNgI3Q1cBBPUGaYC/DsoVEhPyIe3Z6wr05jU4WFlMAfhEM5kLDlVfQIAUHdTGTYRH6CEz M4nBx9WDLBdAv2Z70wPc+hUOASgdxbv1tX2GC4OurQyn+oWbcLyrLHfAJ7iAsrZYhhgBXZOtCk7I YNZW9In8NthLWT+9gypOyOA/n3SDL7jTDGT1Ag+4azS66uEfmeES2gHEP+0AAAAldEVYdGRhdGU6 Y3JlYXRlADIwMjItMDYtMDlUMTA6MjU6NDYrMDA6MDCmuwKMAAAAJXRFWHRkYXRlOm1vZGlmeQAy MDIyLTA2LTA5VDEwOjI1OjQ2KzAwOjAw1+a6MAAAAABJRU5ErkJggg== X-Now-Playing: The Cure's _Wild Mood Swings_: "Want" In-Reply-To: <8335gf5er3.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Jun 2022 18:58:08 +0300") 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:234044 Archived-At: Eli Zaretskii writes: > So one challenge is to detect the "during redisplay" situation, > including the fact that it's "still the same redisplay cycle". Yes. This reminds me of something else I was thinking about a while back -- if we had something that could tell us "this redisplay cycle has lasted X seconds", then we could possibly have something to react to that. I.e., if the redisplay cycle has gone on for more than 10 seconds, then switch on so-long-mode and see whether that helps... > As for the C-g idea, I think a better and cleaner idea would be to use > atimers to detect signs of potentially a very long redisplay cycle, > and then do...something. Not unlike what we already do with the > hourglass-cursor feature. Ah, yes, that's true -- we already almost have something here via the hourglass thing. Hm... So we could call something from an atimer... but do we have a way to (safely) signal to redisplay that it should stop what it's doing? > Other clever ideas are welcome. Indeed. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no