all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: jrm@ftfl.ca, 32523@debbugs.gnu.org
Subject: bug#32523: 27.0.50; Emacs hangs when killing rectangle
Date: Fri, 21 Aug 2020 16:42:00 +0300	[thread overview]
Message-ID: <83eeo0azfb.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=VNeYPTHPLtnk6JaN8dHcPN6pm4yCM4fyPPxcCQjCdTw@mail.gmail.com> (message from Stefan Kangas on Fri, 21 Aug 2020 04:51:37 -0700)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 21 Aug 2020 04:51:37 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 32523@debbugs.gnu.org
> 
> > 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.





  reply	other threads:[~2020-08-21 13:42 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 [this message]
2020-08-21 14:06         ` Stefan Kangas
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83eeo0azfb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32523@debbugs.gnu.org \
    --cc=jrm@ftfl.ca \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.