From: Alan Mackenzie <acm@muc.de>
To: martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 52297@debbugs.gnu.org
Subject: bug#52297: 29.0.50; Error in c-force-redisplay timer
Date: Wed, 9 Feb 2022 16:53:33 +0000 [thread overview]
Message-ID: <YgPxjWKsDQ1NOnBj@ACM> (raw)
In-Reply-To: <fad77d20-7cbd-5ed2-38cb-2fe7b14f8072@gmx.at>
Hello, Martin.
On Wed, Feb 09, 2022 at 09:45:16 +0100, martin rudalics wrote:
> reopen 52297
> quit
> > 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).
> With emacs -Q pulled from master and built today (2022-02-09) I load a
> file containing the following text
[ .... ]
Thanks. With that file, I can reproduce the bug. I'll set about fixing
it.
> With debugging turned on this gets me
> Debugger entered--Lisp error: (error "Font-lock trying to use keywords before setting th...")
> signal(error ("Font-lock trying to use keywords before setting th..."))
> error("Font-lock trying to use keywords before setting th...")
> font-lock-compile-keywords(nil)
> font-lock-fontify-keywords-region(1 112 nil)
> font-lock-default-fontify-region(1523 1532 nil)
> c-font-lock-fontify-region(1523 1532)
> c-force-redisplay(1523 1532)
> apply(c-force-redisplay (1523 1532))
> timer-event-handler([t 25091 29205 916629 nil c-force-redisplay (1523 1532) nil 777000 nil])
> martin
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-02-09 16:53 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
2022-02-08 19:00 ` Eli Zaretskii
2022-02-09 8:45 ` martin rudalics
2022-02-09 16:53 ` Alan Mackenzie [this message]
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=YgPxjWKsDQ1NOnBj@ACM \
--to=acm@muc.de \
--cc=52297@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
/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).