unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ravine Var <ravine.var@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 45248@debbugs.gnu.org
Subject: bug#45248: 28.0.50; Emacs freezes with big C functions
Date: Wed, 23 Dec 2020 08:48:26 +0530	[thread overview]
Message-ID: <87mty5rxsz.fsf@gmail.com> (raw)
In-Reply-To: <X+JZqNjn329wSMf/@ACM>

Alan Mackenzie <acm@muc.de> writes:
> Sorry it's taken a little while to reply.  I've been preoccupied with
> another bug in the meantime.

No problem.

> By "scrolling becomes slower", do you mean (1) that the time for an
> isolated single full screen scroll becomes longer, the further you are
> through that struct?  Or do you mean (2) that on auto-repeat of the C-v
> or PageDown key, the scrolling becomes slower?

The second behavior. Opening the file and scrolling from the
the beginning with C-v becomes progressively slower.

> If you mean (2), from emacs -Q without enabling
> fast-but-imprecise-scrolling, then you are just seeing the normal
> expected, but unfortunate behaviour of Emacs: Emacs will not redisplay a
> screen as long as there is keyboard input unprocessed, but Emacs is
> spending its time fontifying the intermediate screens (which are not
> about to be displayed) as part of processing that input.  30 characters
> per second is faster than CC Mode can paint a single screen.

Ok.

> For problem (2) I recommend, again, enabling
> fast-but-imprecise-scrolling.

Without the patch in message 11, scrolling is bad
even when fast-but-imprecise-scrolling is enabled.

With the patch, things are much better and there
is no lockup, once fast-but-imprecise-scrolling is enabled.

I think this is enough for this bug - thanks for
looking into this issue.





  reply	other threads:[~2020-12-23  3:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15  3:59 bug#45248: 28.0.50; Emacs freezes with big C functions Ravine Var
2020-12-15 16:05 ` Eli Zaretskii
2020-12-17 15:08 ` Alan Mackenzie
2020-12-18 11:17   ` Ravine Var
2020-12-18 17:29     ` Alan Mackenzie
2020-12-19  4:28       ` Ravine Var
2020-12-22 20:40         ` Alan Mackenzie
2020-12-23  3:18           ` Ravine Var [this message]
2020-12-24 11:50             ` Alan Mackenzie

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=87mty5rxsz.fsf@gmail.com \
    --to=ravine.var@gmail.com \
    --cc=45248@debbugs.gnu.org \
    --cc=acm@muc.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.
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).