unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: acm@muc.de, 52298@debbugs.gnu.org
Subject: bug#52298: 29.0.50; Frequent redisplay cycles induced by c-type-finder-timer-func timer in CC Mode
Date: Mon, 13 Dec 2021 14:25:20 +0000	[thread overview]
Message-ID: <YbdX0AYXgqsO8AWf@ACM> (raw)
In-Reply-To: <m1pmq1wgbp.fsf@yahoo.es>

Hello, Daniel.

On Mon, Dec 13, 2021 at 00:31:38 +0100, Daniel Martín wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > This particular feature simply hasn't worked out well.  If the
> > background scanning were to complete in a few seconds, it wouldn't
> > be too bad.  But nearly two minutes on a modern (well, 4½ yo)
> > machine for just one buffer, with the annoyance of the "stuttering",
> > is not worth the gain.

> If you want another data point, on my 2017 MacBook Pro visiting xdisp.c
> took 1:30 min of background work (using 25% of the CPU).

Thanks, that's helpful.  It confirms that the slow background
fontification check is real, not just an artifact of my current set up.

> Is it possible to make the feature optional, even for the default
> font-lock decoration level in CC mode?  So only the people that want
> more accurate highlighting of types pay the cost of this background
> work.

It would be possible, but I don't think it would be a good idea.  People
generally tend to stay unaware of this sort of option (how many people
know about stealth fontification, for example?), and the cost of
maintaining it is fairly high.

I still think the best thing to do is to rip it out.  It was a
worthwhile experiment, but one which didn't deliver the desired result.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2021-12-13 14:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  7:46 bug#52298: 29.0.50; Frequent redisplay cycles induced by c-type-finder-timer-func timer in CC Mode Eli Zaretskii
2021-12-06 20:53 ` Alan Mackenzie
2021-12-07 12:58   ` Eli Zaretskii
2021-12-07 19:58     ` Alan Mackenzie
2021-12-07 20:16       ` Eli Zaretskii
2021-12-08 20:15 ` Alan Mackenzie
2021-12-09  7:08   ` Eli Zaretskii
2021-12-09 20:11     ` Alan Mackenzie
2021-12-09 20:38       ` Eli Zaretskii
2021-12-10 18:16         ` Alan Mackenzie
2021-12-10 18:51           ` Eli Zaretskii
2021-12-10 22:52             ` Alan Mackenzie
2021-12-11  7:59               ` Eli Zaretskii
2021-12-11 14:52                 ` Alan Mackenzie
2021-12-11 15:38                   ` Eli Zaretskii
2021-12-11 17:04                     ` Alan Mackenzie
2021-12-11 18:21                       ` Eli Zaretskii
2021-12-12  8:58                         ` Alan Mackenzie
2021-12-12  9:15                           ` Eli Zaretskii
2021-12-12 19:05                             ` Alan Mackenzie
2021-12-12 19:21                               ` Eli Zaretskii
2021-12-13 14:19                                 ` Alan Mackenzie
2021-12-12 23:31                               ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-13 14:25                                 ` Alan Mackenzie [this message]
2021-12-19 14:38                               ` 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=YbdX0AYXgqsO8AWf@ACM \
    --to=acm@muc.de \
    --cc=52298@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    /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).