From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Emacs freezes again when I try to open a file including only one very long line. Date: Thu, 30 Jun 2022 16:56:44 +0300 Message-ID: <83zghu45lv.fsf@gnu.org> References: <83mtdy8j3y.fsf@gnu.org> <83tu856ny2.fsf@gnu.org> <83leth6iga.fsf@gnu.org> <83k0907ty3.fsf@gnu.org> <83h7447pjc.fsf@gnu.org> <83a69w6vsd.fsf@gnu.org> <838rpf7m9t.fsf@gnu.org> <834k037lac.fsf@gnu.org> <8335fn7e64.fsf@gnu.org> <831qv778ye.fsf@gnu.org> <87sfnmcnyx.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17975"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 30 15:58:17 2022 Return-path: Envelope-to: geh-help-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 1o6ugT-0004X9-2R for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 30 Jun 2022 15:58:17 +0200 Original-Received: from localhost ([::1]:53352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6ugR-000439-Nq for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 30 Jun 2022 09:58:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55738) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6uer-0003b9-3h for help-gnu-emacs@gnu.org; Thu, 30 Jun 2022 09:56:38 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50208) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6ueq-0007nN-RY for help-gnu-emacs@gnu.org; Thu, 30 Jun 2022 09:56:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=WQvM6kHiW8xyinzhJeAwSeE5LtyDRN9U8OGMK+B1f4Q=; b=OUyvRj6fUxaM N1/sYAAGUut51//C1uzZhzohWWHPkbAxZgF3wVpCQvzYMy2EqnmCikxW17tyaUUGJCOGUJwLlzaUE Rye2X31X1ttV5IZxcPvkpKT5Qwu//SIR9U8QOpLYxIqJBe4esGhfvjPSklZETgf0S9ByZNKHfJLv8 q9D2DvFSUlOdjFcwqgB8FytoxeNMwkFzRyLJDlaqFIrrLG+nfECunI785Rniw26RXpbd9xPdoMqBi tt+UJn1+hP+Su5453yINRxfPsdlhEv7kLHOcgdSyMj4MZcjLrc2W+UoQHiGJZqWtgiXFajyXvzDNT 1QcsFoptgU/lYKfipYa5jw==; Original-Received: from [87.69.77.57] (port=3943 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6ueq-000150-37 for help-gnu-emacs@gnu.org; Thu, 30 Jun 2022 09:56:36 -0400 In-Reply-To: <87sfnmcnyx.fsf@web.de> (message from Michael Heerdegen on Thu, 30 Jun 2022 14:52:54 +0200) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:138229 Archived-At: > From: Michael Heerdegen > Date: Thu, 30 Jun 2022 14:52:54 +0200 > > Would it be more sensible to do something different than showing the > partially redisplayed window with a non-blinking cursor? I'd need more specific proposals to say anything intelligent. To your general question, my only answer is: this is what avoiding redisplay of a window looks like in Emacs. (Perhaps you didn't realize, but blinking the cursor on a GUI frame requires a redisplay cycle each time the cursor is turned on or off -- that's why it stops blinking in the window whose buffer is marked "not for redisplay".) > Even if Emacs successfully aborted redisplay and everything is good, > people might think Emacs is still frozen because it looks > frozen. That's what happened to me: I thought the feature wouldn't > work with my config for some reason, until I tried to select a > different window and then - ah! - that actually works! But it took > some time... I think it's a one-time "eureka!" thing -- once you realize that this is what happens, it will no longer be a surprise. (Note that the warning popping up was a last-minute improvement: the original implementation just silently stopped updating the window, because we cannot signal an error from redisplay in a way that causes an error message to appear in the echo-area.) Again, practical proposals for something you think is better are welcome.