From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52297@debbugs.gnu.org
Subject: bug#52297: 29.0.50; Error in c-force-redisplay timer
Date: Tue, 8 Feb 2022 18:36:56 +0000 [thread overview]
Message-ID: <YgK4SKjnDWpDb6XI@ACM> (raw)
In-Reply-To: <874k59r7ef.fsf@gnus.org>
Hello, Lars.
On Tue, Feb 08, 2022 at 11:15:36 +0100, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> >> emacs -Q
> >> C-x C-f some-C-file.c RET
> >> and then press "M-x". Observe the following error message in the echo
> >> area, displayed after "M-x":
> >> Error running timer ‘c-force-redisplay’: (error "Font-lock trying to use keywords before setting them up")
> > OK, I'll look at it.
> Alan, this was nine weeks ago. Have you made any progress here? (I
> don't see the issue myself, but it's apparently stopping Martin from
> using recent Emacs builds.)
Sorry, I lost this one. I've just configured a build on GNU with:
$ CFLAGS='-O0 -g3' ./configure --enable-checking=yes,glyphs --with-gpm
, and built it. When I do
$ emacs -Q
C-x C-f src/xdisp.c
M-x end-of-buffer RET
, I don't see the bug at all.
Eli or Martin, is this bug still showing itself? If so, would it be
possible to give a more exact recipe to reproduce it (though I'm aware
the answer to this question is probably no).
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-02-08 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 7:27 bug#52297: 29.0.50; Error in c-force-redisplay timer Eli Zaretskii
2021-12-06 20:26 ` Alan Mackenzie
2022-02-08 10:15 ` Lars Ingebrigtsen
2022-02-08 18:36 ` Alan Mackenzie [this message]
2022-02-08 19:00 ` Eli Zaretskii
2022-02-09 8:45 ` martin rudalics
2022-02-09 16:53 ` Alan Mackenzie
2022-02-09 18:21 ` martin rudalics
2022-02-09 20:06 ` Alan Mackenzie
2022-02-10 8:26 ` martin rudalics
2022-02-10 17:15 ` bug#52709: [ was: bug#52297: 29.0.50; Error in c-force-redisplay timer ] 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=YgK4SKjnDWpDb6XI@ACM \
--to=acm@muc.de \
--cc=52297@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).