From: frederik@ofb.net
To: "Mattias Engdegård" <mattiase@acm.org>, "Eli Zaretskii" <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, 39658@debbugs.gnu.org
Subject: bug#39658: 26.3; can't edit file with terminal escape sequences
Date: Tue, 18 Feb 2020 08:58:50 -0800 [thread overview]
Message-ID: <20200218165850.GC1035@localhost> (raw)
In-Reply-To: <83v9o3lvxk.fsf@gnu.org> <7F3D1DAD-529E-4CD9-A711-820FEF35A971@acm.org>
Thank you Mattias for figuring that out, and Eli for being more patient than I.
I think I'll let the professionals handle it from here.
On Tue, Feb 18, 2020 at 05:02:29PM +0100, Mattias Engdegård wrote:
>> My guess is that rendering the escape sequences in the problem file is causing some kind of quadratic complexity.
>
>It looks like it's the left square brackets ('['). Take them out and it's fast.
>
On Tue, Feb 18, 2020 at 06:08:55PM +0200, Eli Zaretskii wrote:
>> Date: Tue, 18 Feb 2020 05:48:59 -0800
>> From: frederik@ofb.net
>>
>> To reproduce, open the attached file in Emacs, and type C-x C-n. On my system Emacs uses 100% of CPU, indefinitely.
>
>On my system, visiting this file takes 36 sec of CPU time. Which is
>long, but is not indefinitely.
>
>If someone wants to investigate this case, I'd start with visiting the
>file after "M-x profiler-start". Then look at the hot spot(s).
>
next prev parent reply other threads:[~2020-02-18 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 13:48 bug#39658: 26.3; can't edit file with terminal escape sequences frederik
2020-02-18 13:58 ` Robert Pluim
2020-02-18 14:15 ` frederik
2020-02-18 16:05 ` Eli Zaretskii
2020-02-18 16:02 ` Mattias Engdegård
2020-02-18 16:58 ` frederik [this message]
2020-02-18 22:09 ` Mattias Engdegård
2020-02-19 17:47 ` Eli Zaretskii
2020-02-20 13:36 ` Mattias Engdegård
2020-02-20 14:26 ` Robert Pluim
2020-02-23 4:42 ` Phil Sainty
2020-02-20 14:46 ` Eli Zaretskii
2020-02-18 16:08 ` 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=20200218165850.GC1035@localhost \
--to=frederik@ofb.net \
--cc=39658@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=rpluim@gmail.com \
/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.