GNU bug report logs - #64824
30.0.50; define-error not fontified in font-lock mode

Previous Next

Package: emacs;

Reported by: nealsid <at> gmail.com

Date: Mon, 24 Jul 2023 07:31:03 UTC

Severity: normal

Merged with 64823

Found in version 30.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 64824 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: nealsid <at> gmail.com
Cc: 64824 <at> debbugs.gnu.org
Subject: Re: bug#64824: 30.0.50; define-error not fontified in font-lock mode
Date: Mon, 24 Jul 2023 15:20:32 +0300
merge 64824 64823
thanks

> From: nealsid <at> gmail.com
> Date: Sun, 23 Jul 2023 19:28:56 -0400
> 
> In a buffer with emacs-lisp-mode active, 'define-error' is not fontified
> by font-lock mode.  The keyword should be listed somewhere around line 360 in
> emacs-lisp/lisp-mode.el.
> 
> Recipe:
> 
> - Start emacs
> - Visit a file ending in .el
> - Type: (define-error 'new-error "this is a new error")
> - Wait for fontification to complete and notice it is not highlighted
> 
> In lisp-mode.el, there is a comment about constructs being updated
> automatically from obarray, but I was not able to understand how this
> happens, and thought maybe the comment is referring to symbols created
> with those commands?

Thanks I merged this with your original report, since it's the same
issue.




This bug report was last modified 1 year and 301 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.