From: Chris Hecker <checker@d6.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 59038@debbugs.gnu.org, "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
acm@muc.de
Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sat, 5 Nov 2022 08:01:33 -0700 [thread overview]
Message-ID: <CAOdMLc2OSe8_vLHq7_dV959ahT320dJsSX1Ciae3RPCOqnV=Lg@mail.gmail.com> (raw)
In-Reply-To: <87tu3dabbw.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
>> (instantly, it’s 27kb)
> Which is a lot, even in this day and age.
I don't even know what to say to this. Literally every other editor I
tried including the immense pile that is visual studio opened this file
instantly, including ones that do syntax highlighting.
I love emacs but holy cow you need to renormalize what you think a modern
computer is capable of so your performance expectations for emacs are more
realistic.
Anyway, I’m glad it’s fixed in 29.
Chris
On Sat, Nov 5, 2022 at 04:29 Po Lu <luangruo@yahoo.com> wrote:
> Chris Hecker <checker@d6.com> writes:
>
> > Yeah? This isn’t 1970.
>
> Emacs becoming unusable due to long lines has been fixed in Emacs 29.
>
> > I have 32gb of ram and a 12 core cpu.
>
> Physical memory and the number of processors installed does not really
> matter here, unfortunately, as Emacs only uses one processor to process
> your (27kb) file.
>
> > (instantly, it’s 27kb)
>
> Which is a lot, even in this day and age.
>
> > or it should at least stop after a few ms and tell me it’s lame and
> > needs me to switch manually to another mode.
>
> A few ms is shorter than a roundtrip to and fro the X server over my
> current connection. But:
>
> > I mean, given the 28.2 user experience, there is no opportunity to
> > switch to fundamental mode because emacs was hosed. I don’t even
> > think ctrl-g worked for me.
>
> All of this is no longer a problem in Emacs 29, and even if you somehow
> still cause redisplay to become wedged, you can set max-redisplay-ticks
> to a suitable value.
>
[-- Attachment #2: Type: text/html, Size: 2309 bytes --]
next prev parent reply other threads:[~2022-11-05 15:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 2:48 bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely Chris Hecker
2022-11-05 5:12 ` Gerd Möllmann
2022-11-05 7:01 ` Eli Zaretskii
2022-11-05 7:50 ` Gerd Möllmann
2022-11-05 8:21 ` Chris Hecker
2022-11-05 8:45 ` Gerd Möllmann
2022-11-05 9:30 ` Eli Zaretskii
2022-11-05 10:39 ` bug#59038: Re[2]: " Chris Hecker
2022-11-05 11:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 15:01 ` Chris Hecker [this message]
2022-11-06 5:17 ` Gerd Möllmann
2022-11-05 22:03 ` Alan Mackenzie
2022-11-06 6:00 ` Eli Zaretskii
2022-11-05 9:28 ` Eli Zaretskii
2022-11-06 5:18 ` Gerd Möllmann
2022-11-05 22:27 ` Gregory Heytings
2022-11-05 23:41 ` Gregory Heytings
2022-11-06 3:58 ` Phil Sainty
2022-11-06 5:20 ` Gerd Möllmann
2022-11-06 13:54 ` Alan Mackenzie
2022-11-06 9:18 ` Gregory Heytings
2022-11-06 13:52 ` Eli Zaretskii
2022-11-06 16:34 ` Alan Mackenzie
2022-11-07 7:55 ` Gerd Möllmann
[not found] ` <Y2fiMTlfuNqae7zp@acm>
2022-11-06 19:46 ` bug#59038: Re[2]: " Chris Hecker
2022-11-07 12:25 ` Alan Mackenzie
2022-11-05 6:52 ` Eli Zaretskii
2022-11-05 10:45 ` Phil Sainty
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOdMLc2OSe8_vLHq7_dV959ahT320dJsSX1Ciae3RPCOqnV=Lg@mail.gmail.com' \
--to=checker@d6.com \
--cc=59038@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).