From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Pieter van Oostrum Newsgroups: gmane.emacs.bugs Subject: bug#38407: 27.0.50; infinite loop with display of large file without newlines Date: Sun, 1 Dec 2019 19:40:14 +0100 Message-ID: <24036.2318.53069.309311@cochabamba.vanoostrum.org> References: <39c498717f8958e7fdc408d4da51d378@webmail.orcon.net.nz> <24031.28277.201123.531348@cochabamba.vanoostrum.org> <83r21sowx1.fsf@gnu.org> <24032.4698.256238.87458@cochabamba.vanoostrum.org> <83k17jq1ch.fsf@gnu.org> <24032.17845.921546.629745@cochabamba.vanoostrum.org> <83fti7p349.fsf@gnu.org> <4B1ABCA7-A69C-4251-8EBD-A11654A92642@vanoostrum.org> <83v9r2o4z9.fsf@gnu.org> <24035.27244.755074.180653@cochabamba.vanoostrum.org> <24035.60375.240969.134042@cochabamba.vanoostrum.org> Reply-To: Pieter van Oostrum Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="72268"; mail-complaints-to="usenet@blaine.gmane.org" To: Phil Sainty , 38407@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Dec 01 19:41:26 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ibU9r-000If7-Qs for geb-bug-gnu-emacs@m.gmane.org; Sun, 01 Dec 2019 19:41:24 +0100 Original-Received: from localhost ([::1]:54326 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibU9q-0007RR-39 for geb-bug-gnu-emacs@m.gmane.org; Sun, 01 Dec 2019 13:41:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58419) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibU9e-0007R7-6a for bug-gnu-emacs@gnu.org; Sun, 01 Dec 2019 13:41:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibU9Z-0007pC-Bg for bug-gnu-emacs@gnu.org; Sun, 01 Dec 2019 13:41:10 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58970) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ibU9W-0007oz-NZ for bug-gnu-emacs@gnu.org; Sun, 01 Dec 2019 13:41:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ibU9W-0003ws-J5 for bug-gnu-emacs@gnu.org; Sun, 01 Dec 2019 13:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pieter van Oostrum Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 01 Dec 2019 18:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38407 X-GNU-PR-Package: emacs Original-Received: via spool by 38407-submit@debbugs.gnu.org id=B38407.157522562615127 (code B ref 38407); Sun, 01 Dec 2019 18:41:02 +0000 Original-Received: (at 38407) by debbugs.gnu.org; 1 Dec 2019 18:40:26 +0000 Original-Received: from localhost ([127.0.0.1]:36710 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ibU8v-0003vv-Me for submit@debbugs.gnu.org; Sun, 01 Dec 2019 13:40:25 -0500 Original-Received: from [145.132.212.31] (port=55390 helo=cochabamba.vanoostrum.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ibU8t-0003vb-P8 for 38407@debbugs.gnu.org; Sun, 01 Dec 2019 13:40:24 -0500 Original-Received: from cochabamba.vanoostrum.org (localhost [IPv6:::1]) by cochabamba.vanoostrum.org (Postfix) with ESMTP id 4CFEA9FD871A; Sun, 1 Dec 2019 19:40:15 +0100 (CET) In-Reply-To: <24035.60375.240969.134042@cochabamba.vanoostrum.org> X-Mailer: VM undefined under 27.0.50 (i686-apple-darwin10.0.0) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:172727 Archived-At: Pieter van Oostrum wrote: > Phil Sainty wrote: >=20 > > On 1/12/19 8:23 PM, Pieter van Oostrum wrote: > > > Here it is, compressed. I am loading the uncompressed file, > > > of course. > >=20 > > Without bidi-inhibit-bpa, visual-line-mode is certainly brutal > > with this file (I've been waiting several minutes for Emacs 27 > > to respond to `end-of-buffer'). > >=20 > > However, for me, bidi-inhibit-bpa comprehensively deals to that. > >=20 > > Is it possible that you didn't recompile or reinstall Emacs in > > the way you thought you had, after pulling Eli's changes=3F > >=20 > > Can you confirm that C-h v bidi-inhibit-bpa actually shows you > > documentation about the variable=3F If it doesn't, then setting > > it will have no effect whatsoever. >=20 > This is what it says. >=20 > bidi-inhibit-bpa is a variable defined in =E2=80=98C source code=E2=80= =99. > Its value is nil >=20 > Calls these functions when changed: (#)= >=20 > Documentation: > Non-nil means inhibit the Bidirectional Parentheses Algorithm. > Disabling the BPA makes redisplay faster, but might produce incorrec= t > display reordering of bidirectional text with embedded parentheses a= nd > other bracket characters whose =E2=80=99paired-bracket=E2=80=99 Unic= ode property is > non-nil, see =E2=80=98get-char-code-property=E2=80=99. >=20 > So yes, it is the right one. >=20 > Latest experiment: >=20 > Opened this version of Emacs.=20 > (setq bidi-inhibit-bpa t) > open the file extensions.json (i.e. without visual-line-mode) > go to the end of the buffer. > Emacs gets responsive again after about one minute. > Then I open a new frame (Cmd-N), the frame appears, so this proves t= hat Emacs was responsive. > But after opening the frame, Emacs is unresponsive again with 100% C= PU usage. After 30 minutes, I killed it. That was without so-long-mode. I retried with so-long-mode, and now eve= rything works as it should. Even in grep-mode when the culprit file has= a hit, it appears in the grep buffer and I can scroll over it. As soon= as I set bidi-inhibit-bpa to nil again, it fails. I saw that bidi-inhibit-bpa is now part of so-long-mode, so I am compil= ing the latest master now. Thanks everybody for all the help. --=20 Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]