all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sujith Manoharan <sujith.wall@gmail.com>, 59530@debbugs.gnu.org
Subject: bug#59530: 29.0.50; Fontification hangs with C header file
Date: Sat, 26 Nov 2022 14:11:28 +0000	[thread overview]
Message-ID: <Y4IekIFP0ItbxRed@ACM> (raw)
In-Reply-To: <83a64et1v5.fsf@gnu.org>

Hello, Eli.

On Sat, Nov 26, 2022 at 13:02:38 +0200, Eli Zaretskii wrote:
> > From: Sujith Manoharan <sujith.wall@gmail.com>
> > Date: Thu, 24 Nov 2022 09:32:03 +0530

> > Opening this header file with lots of macros makes Emacs
> > very slow.

> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/include/asic_reg/dce/dce_12_0_sh_mask.h

> > Same behavior is seen with other header files inside asic_reg.
> > Fontification/scrolling hangs Emacs and it becomes unusable.

> > Bug #25706 suggested the workaround 'fast-but-imprecise-scrolling',
> > but enabling it doesn't seem to improve things now.

> Alan, did you see this bug report?

I hadn't, no, but I think it's already been fixed by the following
commit:

commit 3208a42c47c4f98cb03c4b15164ca83113244b40
Author: Alan Mackenzie <acm@muc.de>
Date:   Thu Nov 24 10:51:03 2022 +0000

    CC Mode: Make it scroll fast over buffers with only #define's

The OP's test file was around 6 MB big.  When I scrolled all the way
through it, it took around 32 seconds.

I'll look into this more carefully, and get in touch with the OP.

Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-11-26 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  4:02 bug#59530: 29.0.50; Fontification hangs with C header file Sujith Manoharan
2022-11-26 11:02 ` Eli Zaretskii
2022-11-26 14:11   ` Alan Mackenzie [this message]
2022-11-26 15:09 ` Alan Mackenzie
2022-11-27  8:45   ` Sujith Manoharan
2022-11-28 19:46     ` 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

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

  git send-email \
    --in-reply-to=Y4IekIFP0ItbxRed@ACM \
    --to=acm@muc.de \
    --cc=59530@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=sujith.wall@gmail.com \
    /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.