unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: nealsid@gmail.com
Cc: 64824@debbugs.gnu.org
Subject: bug#64824: 30.0.50; define-error not fontified in font-lock mode
Date: Mon, 24 Jul 2023 15:20:32 +0300	[thread overview]
Message-ID: <83mszlsdpr.fsf@gnu.org> (raw)
In-Reply-To: <874jlugqbr.fsf@archlinux.mail-host-address-is-not-set> (nealsid@gmail.com)

merge 64824 64823
thanks

> From: nealsid@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.





  reply	other threads:[~2023-07-24 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 23:28 bug#64824: 30.0.50; define-error not fontified in font-lock mode nealsid
2023-07-24 12:20 ` Eli Zaretskii [this message]
2023-07-24 19:28   ` Neal Sidhwaney
2023-07-25  0:57 ` bug#64824: v2 of patch nealsid
2023-07-26 14:25   ` bug#64824: 30.0.50; define-error not fontified in font-lock mode Eli Zaretskii
     [not found] ` <handler.64824.D64824.16903814767160.notifdone@debbugs.gnu.org>
2023-07-27  4:49   ` bug#64824: closed (Re: bug#64824: 30.0.50; define-error not fontified in font-lock mode) Neal Sidhwaney

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=83mszlsdpr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64824@debbugs.gnu.org \
    --cc=nealsid@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 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).