From: "T.V Raman" <raman@google.com>
To: monnier@iro.umontreal.ca
Cc: raman@google.com, mardani29@yahoo.es, emacs-devel@gnu.org, acm@muc.de
Subject: Re: font-lock-reference-face no longer defined?
Date: Fri, 16 Sep 2022 13:46:15 -0700 [thread overview]
Message-ID: <25380.57495.56006.25514@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <jwvwna3rwbt.fsf-monnier+emacs@gnu.org>
thx, apologies for the noise, rgrep didn't tell me those were in
comments, and I was too lazy to check;-)
Stefan Monnier writes:
> > File: lisp/progmodes/cperl-mode.el
> > 6060 8 ;; font-lock-reference-face
> > 6067 8 ;; font-lock-reference-face
>
> Notice: inside a comment (and AFAIK that commented code doesn't actually
> use that face, it just says what to do in case that face shows up).
>
> > File: lisp/progmodes/cc-fonts.el
>
> That's the CC-mode I was referring to.
>
> > File: etc/themes/deeper-blue-theme.el
> > 74 6 `(font-lock-reference-face ((,class (:foreground "LightCoral"))))
> >
> > File: etc/themes/whiteboard-theme.el
> > 54 6 `(font-lock-reference-face ((,class (:foreground "salmon"))))
>
> These two themes just define the face, i.e. say what to do in case some
> third party uses it. Notice how `whiteboard-theme` also defines the
> appearance of `realgud-*` faces, which aren't defined in Emacs.
> We could remove those "references", but I see no urgency.
>
>
> Stefan
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-09-16 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 17:28 font-lock-reference-face no longer defined? T.V Raman
2022-09-16 17:50 ` Daniel Martín
2022-09-16 18:00 ` T.V Raman
2022-09-16 18:26 ` Stefan Monnier
2022-09-16 18:32 ` T.V Raman
2022-09-16 18:51 ` Stefan Monnier
2022-09-16 19:29 ` Stefan Kangas
2022-09-16 20:46 ` T.V Raman [this message]
2022-09-16 19:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25380.57495.56006.25514@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
/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.