unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Chris Hecker" <checker@d6.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, 59038@debbugs.gnu.org, acm@muc.de
Subject: bug#59038: Re[2]: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sat, 05 Nov 2022 10:39:49 +0000	[thread overview]
Message-ID: <emeaf9b5ac-237a-4e5b-86c4-f06b7d5d225d@checker-blade15> (raw)
In-Reply-To: <83a6554ujx.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]


I mentioned the actual length of the line FTR, not as an excuse for
unbearably slow display.

Ah, ok, sorry, I thought you were disagreeing that the line was not that 
long.  :)

It's nice to have that fixed, if it isn't too complex, but in general
visiting such a file as C file is not a reasonable thing to do.

Right, but I didn't know this was what ?format=TEXT downloaded from 
googlesource.com, so if I'd had unsaved buffers I would have been 
screwed.  Luckily I didn't lose work (except having to reopen a bunch of 
files to get back to where I was).

Like I said, try Emacs 29, where this should be fixed.

I just upgraded to 28 from 26, which took a while!  :)   Anyway, I'll 
give it a shot sometime, but it sounds like you and Gerd are having 
different experiences with this file?

Chris





------ Original Message ------
From: "Eli Zaretskii" <eliz@gnu.org>
To: "Chris Hecker" <checker@d6.com>
Cc: gerd.moellmann@gmail.com; 59038@debbugs.gnu.org; acm@muc.de
Sent: 2022-11-05 02:30:58
Subject: Re: bug#59038: loading this base64 file makes emacs -Q 28.2 peg 
a core infinitely

>>  From: Chris Hecker <checker@d6.com>
>>  Date: Sat, 5 Nov 2022 01:21:34 -0700
>>  Cc: 59038@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, acm@muc.de
>>
>>  > It's a single 21,728-character line.
>>
>>  Yeah?  This isn’t 1970.  I have 32gb of ram and a 12 core cpu.   It’s a bug.  It should either parse the file
>>  (instantly, it’s 27kb) 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.  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.
>
>Like I said, try Emacs 29, where this should be fixed.
>
>I mentioned the actual length of the line FTR, not as an excuse for
>unbearably slow display.

[-- Attachment #2: Type: text/html, Size: 4547 bytes --]

  reply	other threads:[~2022-11-05 10:39 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           ` Chris Hecker [this message]
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
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=emeaf9b5ac-237a-4e5b-86c4-f06b7d5d225d@checker-blade15 \
    --to=checker@d6.com \
    --cc=59038@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@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 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).