unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled.
Date: Sat, 07 May 2022 15:15:23 +0300	[thread overview]
Message-ID: <83v8uhy1wk.fsf@gnu.org> (raw)
In-Reply-To: <875ymhbmis.fsf@t14.reltub.ca> (message from Leo Butler on Sat, 7 May 2022 11:38:36 +0000)

> From: Leo Butler <Leo.Butler@umanitoba.ca>
> CC: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> Date: Sat, 7 May 2022 11:38:36 +0000
> 
> On Sat, May 07 2022, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >> BTW, I opened it in vscode. The experience is very smooth and there
> >> are no such problems.
> >
> > Then you should post this to the VSCode forum instead.
> 
> Eli (and Emmanuel), your answers are *unsatisfactory*.

I didn't answer any questions in what I wrote above, so I don't think
I understand what you are alluding to here.

> The bug Hongyi is reporting has afflicted emacs as long as I can
> remember (15-20 years). It has nothing to do with vscode per se: to
> confirm, I opened my .newsrc.eld file, generated by
> gnus. Incremental search caused emacs to crash.
> 
> Are your answers to this problem: don't use gnus, it makes no sense; or,
> use vi?

If some command crashes Emacs, please submit a bug report using "M-x
report-emacs-bug RET", per the documentation.

The OP described slow responses, not a crash.  The problem with
extremely slow redisplay when lines are long is well known, and
patches to fix it are welcome, if someone knows how to do that.  Over
the years, I had my share of fixes in that area, which improved
things, but evidently not enough.



  reply	other threads:[~2022-05-07 12:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 23:45 Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled Hongyi Zhao
2022-05-07  2:45 ` Emanuel Berg
2022-05-07  7:05   ` Daniel Fleischer
2022-05-07 14:46     ` Emanuel Berg
2022-05-07  6:19 ` Eli Zaretskii
2022-05-07  6:23   ` Hongyi Zhao
2022-05-07  7:09     ` Eli Zaretskii
2022-05-07  7:33       ` Hongyi Zhao
2022-05-07  7:36         ` Hongyi Zhao
2022-05-07  7:43           ` Eli Zaretskii
2022-05-07  8:12             ` Hongyi Zhao
2022-05-07 11:38             ` Leo Butler
2022-05-07 12:15               ` Eli Zaretskii [this message]
2022-05-08  3:42               ` Michael Heerdegen
2022-05-07 12:42 ` 황병희
2022-05-07 23:35 ` Michael Heerdegen
2022-05-08  0:10   ` Hongyi Zhao
2022-05-08  0:49     ` Michael Heerdegen
2022-05-08  2:54       ` Hongyi Zhao
2022-05-08  3:31         ` Michael Heerdegen
2022-05-08  3:58           ` Hongyi Zhao
2022-05-08  4:11             ` Michael Heerdegen
2022-05-08  4:18               ` Hongyi Zhao
2022-05-08  4:38                 ` Michael Heerdegen
2022-05-08  4:56                   ` Michael Heerdegen
2022-05-08  5:35                     ` Michael Heerdegen
2022-05-08  5:47                       ` Hongyi Zhao
2022-05-09  4:53                         ` Michael Heerdegen
2022-05-09  6:48                           ` Hongyi Zhao
2022-05-08  5:31     ` Eli Zaretskii
2022-05-08  5:38       ` Hongyi Zhao
2022-05-08  5:53         ` Eli Zaretskii
2022-05-08  7:29           ` Hongyi Zhao
2022-05-09  4:54             ` Michael Heerdegen
2022-05-09  6:41               ` Hongyi Zhao
2022-05-10  2:07                 ` Michael Heerdegen
2022-05-10  2:26                   ` Hongyi Zhao
2022-05-09  9:48           ` Manuel Giraud
2022-05-11  6:33           ` Michael Heerdegen
2022-05-11  8:21             ` Manuel Giraud
2022-05-11 11:27             ` 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

  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=83v8uhy1wk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).