From: Neal Sidhwaney <nealsid@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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:28:14 -0400 [thread overview]
Message-ID: <CAJ4cxaSvkBgkH4sMk6jsTTYs4jVoc-gyyWSps-PqnprNnt1ymQ@mail.gmail.com> (raw)
In-Reply-To: <83mszlsdpr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
Thanks! Sorry, forgot the patch in the first email 🤦♂️
On Mon, Jul 24, 2023 at 8:19 AM Eli Zaretskii <eliz@gnu.org> wrote:
> 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.
>
[-- Attachment #2: Type: text/html, Size: 1523 bytes --]
next prev parent reply other threads:[~2023-07-24 19:28 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
2023-07-24 19:28 ` Neal Sidhwaney [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ4cxaSvkBgkH4sMk6jsTTYs4jVoc-gyyWSps-PqnprNnt1ymQ@mail.gmail.com \
--to=nealsid@gmail.com \
--cc=64824@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.