unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: font-lock-reference-face no longer defined?
Date: Fri, 16 Sep 2022 19:50:33 +0200	[thread overview]
Message-ID: <m1pmfvtdhy.fsf@yahoo.es> (raw)
In-Reply-To: <p911qsbw7n1.fsf@google.com> (T. V. Raman's message of "Fri, 16 Sep 2022 10:28:50 -0700")

"T.V Raman" <raman@google.com> writes:

> Background:
>
> There are times that I'm  seeing errors from jit-lock re
> font-lock-reference-face not being defined -- have seen it while
> working in elisp files, but dont have a reliable repro case.
>
> Doing  a recursive grep in the Emacs sources @HEAD, I see numerous
> references to font-lock-reference-face but I indeed dont see it
> defined anywhere. Confused ...

It was an obsolete alias since Emacs 20.3 and was removed by this
commit:

commit 107f832577123ea7ebe867cba55601d0142f546f
Author: Stefan Kangas <stefan@marxist.se>
Date:   Sun Jul 31 11:33:42 2022 +0200

    Delete additional items obsolete since 20, 21 and 22
    
    * lisp/font-lock.el (font-lock-reference-face): Delete variable
    alias obsolete since 20.3.
    * lisp/progmodes/cc-cmds.el (c-toggle-auto-state): Delete alias
    obsolete since 22.1.
    * lisp/replace.el (query-replace-regexp-eval): Delete function
    obsolete since 22.1.
    (replace-count, replace-re-search-function): Doc fixes; adjust for
    above deleted function.

Code should use font-lock-constant-face instead.  I'm also confused
because I still see references to the old variable name in the Emacs
codebase.



  reply	other threads:[~2022-09-16 17:50 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 [this message]
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
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

  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=m1pmfvtdhy.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.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).