unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs <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: Mon, 9 May 2022 14:41:02 +0800	[thread overview]
Message-ID: <CAGP6POLmmNaVsRs7gpWqrq7uDBT6x8fsZJ4y0a05L958CuBKDg@mail.gmail.com> (raw)
In-Reply-To: <8735hjjog2.fsf@web.de>

On Mon, May 9, 2022 at 12:55 PM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > I tried the above commands one-by-one, and the Emacs responsiveness is
> > still sluggish when drag the scrollbar to browser the different part
> > of the buffer or the lower right corner of the window to zoom in/out,
> > as indicated in the attached file.
>
> But near the beginning of the buffer (and only there) it's ok?  That's
> what I experience.

Basically, as soon as I drag the scroll bar or zoom the window, the
problem occurs.

> Michael.

HZ



  reply	other threads:[~2022-05-09  6:41 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
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 [this message]
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=CAGP6POLmmNaVsRs7gpWqrq7uDBT6x8fsZJ4y0a05L958CuBKDg@mail.gmail.com \
    --to=hongyi.zhao@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).