From: Pieter van Oostrum <pieter@vanoostrum.org>
To: Phil Sainty <psainty@orcon.net.nz>, 38407@debbugs.gnu.org
Subject: bug#38407: 27.0.50; infinite loop with display of large file without newlines
Date: Sun, 1 Dec 2019 19:40:14 +0100 [thread overview]
Message-ID: <24036.2318.53069.309311@cochabamba.vanoostrum.org> (raw)
In-Reply-To: <24035.60375.240969.134042@cochabamba.vanoostrum.org>
Pieter van Oostrum wrote:
> Phil Sainty wrote:
>
> > On 1/12/19 8:23 PM, Pieter van Oostrum wrote:
> > > Here it is, compressed. I am loading the uncompressed file,
> > > of course.
> >
> > 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').
> >
> > However, for me, bidi-inhibit-bpa comprehensively deals to that.
> >
> > Is it possible that you didn't recompile or reinstall Emacs in
> > the way you thought you had, after pulling Eli's changes?
> >
> > Can you confirm that C-h v bidi-inhibit-bpa actually shows you
> > documentation about the variable? If it doesn't, then setting
> > it will have no effect whatsoever.
>
> This is what it says.
>
> bidi-inhibit-bpa is a variable defined in ‘C source code’.
> Its value is nil
>
> Calls these functions when changed: (#<subr set-buffer-redisplay>)
>
> Documentation:
> Non-nil means inhibit the Bidirectional Parentheses Algorithm.
> Disabling the BPA makes redisplay faster, but might produce incorrect
> display reordering of bidirectional text with embedded parentheses and
> other bracket characters whose ’paired-bracket’ Unicode property is
> non-nil, see ‘get-char-code-property’.
>
> So yes, it is the right one.
>
> Latest experiment:
>
> Opened this version of Emacs.
> (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 that Emacs was responsive.
> But after opening the frame, Emacs is unresponsive again with 100% CPU usage. After 30 minutes, I killed it.
That was without so-long-mode. I retried with so-long-mode, and now everything 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 compiling the latest master now.
Thanks everybody for all the help.
--
Pieter van Oostrum <pieter@vanoostrum.org>
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
next prev parent reply other threads:[~2019-12-01 18:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 21:52 bug#38407: 27.0.50; infinite loop with display of large file without newlines Pieter van Oostrum
2019-11-27 23:38 ` Phil Sainty
2019-11-28 0:30 ` Phil Sainty
2019-11-28 1:22 ` Phil Sainty
2019-11-28 6:51 ` Pieter van Oostrum
2019-11-28 15:14 ` Eli Zaretskii
2019-11-28 18:30 ` Pieter van Oostrum
2019-11-28 18:53 ` Eli Zaretskii
2019-11-28 22:09 ` Pieter van Oostrum
2019-11-29 7:12 ` Eli Zaretskii
2019-11-29 11:48 ` Phil Sainty
2019-11-29 13:20 ` Eli Zaretskii
2019-11-29 13:48 ` Dmitry Gutov
2019-11-29 14:26 ` Eli Zaretskii
2019-11-29 14:31 ` Dmitry Gutov
2019-11-29 15:03 ` Eli Zaretskii
2019-11-29 16:53 ` Dmitry Gutov
2019-11-29 19:28 ` Eli Zaretskii
2019-11-29 17:24 ` Pieter van Oostrum
2019-11-29 19:30 ` Eli Zaretskii
2019-11-30 8:25 ` Pieter van Oostrum
2019-12-01 7:23 ` Pieter van Oostrum
2019-12-01 10:37 ` Phil Sainty
2019-12-01 16:35 ` Pieter van Oostrum
2019-12-01 18:40 ` Pieter van Oostrum [this message]
2019-12-02 16:23 ` Eli Zaretskii
2019-12-01 17:45 ` Eli Zaretskii
2019-12-02 10:27 ` Robert Pluim
2019-12-03 11:20 ` Robert Pluim
2019-12-03 16:05 ` Eli Zaretskii
2019-12-04 9:15 ` Robert Pluim
2019-12-04 15:45 ` Eli Zaretskii
2019-12-05 7:27 ` Robert Pluim
2019-12-05 15:01 ` Eli Zaretskii
2019-12-05 20:38 ` Phil Sainty
2019-12-06 8:04 ` Eli Zaretskii
2019-12-07 1:28 ` Phil Sainty
2019-12-07 7:56 ` Eli Zaretskii
2019-11-28 15:06 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24036.2318.53069.309311@cochabamba.vanoostrum.org \
--to=pieter@vanoostrum.org \
--cc=38407@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.