From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Robert Pluim <rpluim@gmail.com>, Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
71469@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#71469: font-lock does not apply standard faces and their descendants
Date: Tue, 08 Oct 2024 16:25:32 +0300 [thread overview]
Message-ID: <5882b135ea4b67309fb329fcb95fd06c50211b3a.camel@yandex.ru> (raw)
In-Reply-To: <87v7y2zr97.fsf@gmail.com>
On Tue, 2024-10-08 at 14:57 +0200, Robert Pluim wrote:
> > > > > > On Sat, 05 Oct 2024 09:06:24 -0400, Stefan Monnier via "Bug
> > > > > > reports for GNU Emacs, the Swiss army knife of text
> > > > > > editors" <bug-gnu-emacs@gnu.org> said:
>
> >> We have occasionally declared things obsolete with the
> understanding
> >> that they'll be deleted much later than the normal "10 years,
> give or
> >> take". See the comment in `interactive-p', for example.
> >>
> >> The patch below gives me 64 warnings in our tree. I'm not
> sure if it's
> >> worth installing or not.
>
> Stefan> FWIW, it's a +1 from me (assuming we then silence the
> resulting
> Stefan> warnings, of course).
>
> emacs-lisp/lisp-mode.el:311:18: Warning: ‘font-lock-warning-face’ is
> an obsolete variable (as of 31.1); use ’font-lock-warning-face
> instead.
>
> sounds like a great way to cause confusion. How about:
>
> "use value 'font-lock-comment-face directly instead"
Maybe "pass font-lock-comment-face as a symbol instead"? To understand
what "directly" means one would have to notice the lone singular quote,
which I didn't when I read the suggestion, so I imagine I'd feel
confused had I not know what the warning is about.
next prev parent reply other threads:[~2024-10-08 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 11:59 bug#71469: font-lock does not apply standard faces and their descendants Konstantin Kharlamov
2024-06-10 12:55 ` Eli Zaretskii
2024-06-10 13:41 ` bug#71469: [PATCH] " Konstantin Kharlamov
2024-06-10 15:17 ` Eli Zaretskii
2024-06-10 17:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-05 1:39 ` Stefan Kangas
2024-10-05 13:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-08 12:57 ` Robert Pluim
2024-10-08 13:25 ` Konstantin Kharlamov [this message]
2024-10-09 8:43 ` Robert Pluim
2024-10-09 8:58 ` Konstantin Kharlamov
2024-10-09 12:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:20 ` Robert Pluim
2024-10-09 14:04 ` Konstantin Kharlamov
2024-10-09 14:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=5882b135ea4b67309fb329fcb95fd06c50211b3a.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=71469@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
--cc=stefankangas@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).