From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jrm@ftfl.ca, 32523@debbugs.gnu.org
Subject: bug#32523: 27.0.50; Emacs hangs when killing rectangle
Date: Fri, 21 Aug 2020 07:06:29 -0700 [thread overview]
Message-ID: <CADwFkmkYTPUQjcJrWuS_DBHJxv0PN4Q29mAyPqQRaPh-MPidtw@mail.gmail.com> (raw)
In-Reply-To: <83eeo0azfb.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> > The rectangle does eventually get cut for me as well. Ignoring speed,
>> > the problem is that Emacs is unusable afterwards. For example, if I go
>> > away for an hour or so, then return, the Emacs process will still be
>> > using something close to 100% CPU and trying to doing something simple,
>> > like moving the point forward, may take minutes.
>>
>> Are you still seeing this behaviour?
>
> I bet he does. the problem with the slow responses after cutting the
> rectangle is that Emacs performs redisplay each type the user types
> some character. The redisplay can be very small and optimized, but it
> can also be much more thorough; for example, typing "M-x" typically
> triggers a thorough redisplay. Each time we need to perform a
> non-trivial redisplay, the same problem with long lines hits again.
Ah, so you interpret what he writes to mean that he leaves Emacs _in the
same buffer_ and then sees these results? Yes, that makes sense. I
somehow assumed he meant that this was persistent even after closing the
problematic buffer, but he didn't say that explicitly.
Asking the same questions here as in another bug report:
Is there anything more we can/should do in this case short of rewriting
the display engine? Does it make sense to track this limitation in a
bug report?
etc/PROBLEMS says:
*** Editing files with very long lines is slow.
For example, simply moving through a file that contains hundreds of
thousands of characters per line is slow, and consumes a lot of CPU.
This is a known limitation of Emacs with no solution at this time.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-21 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 0:59 bug#32523: 27.0.50; Emacs hangs when killing rectangle Joseph Mingrone
2018-08-25 8:11 ` Eli Zaretskii
2018-08-25 11:40 ` Joseph Mingrone
2020-08-21 11:51 ` Stefan Kangas
2020-08-21 13:42 ` Eli Zaretskii
2020-08-21 14:06 ` Stefan Kangas [this message]
2020-08-21 14:28 ` Eli Zaretskii
2020-08-24 18:44 ` Joseph Mingrone
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=CADwFkmkYTPUQjcJrWuS_DBHJxv0PN4Q29mAyPqQRaPh-MPidtw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=32523@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jrm@ftfl.ca \
/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).