From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 13915@debbugs.gnu.org
Subject: bug#13915: 24.3.50; `font-lock-syntactic-keywords' - really obsolete?
Date: Mon, 11 Mar 2013 14:04:58 -0700 [thread overview]
Message-ID: <DED20D4D179948DE8B8A15EF7E59992C@us.oracle.com> (raw)
In-Reply-To: <jwva9q9vfc9.fsf-monnier+emacs@gnu.org>
> > No one suggested that you should remove support for it before
> > marking it obsolete! You are right to suppose that I would
> > never have suggested such a thing. So why bring it up as a
> > straw man?
>
> Because the "uses" you seem to see in font-lock.el are just the code
> that *implements* font-lock-syntactic-keywords. None of it *uses* it.
> So removing those "uses" would remove support for it.
I would humbly suggest that most of the occurrences (I did not refer to the
occurrences as "*uses*", so your quotes are inaccurate here) are vestigial, in
doc strings. They do not *implement* `font-lock-syntactic-keywords'.
And I was clear that any occurrences that remain to *implement* the old should
of course remain.
Since a preferred replacement has already been implemented, that (the new, not
the old) is what should be mentioned, above all, in the doc strings. That is
not the case. That is the point about `font-lock.el' occurrences.
But the *important* point is what the bug report is really about:
>> 4. But the 24.3 NEWS is no clearer about this. Both the 24.3
>> Elisp manual and the 24.3 font-lock.el Commentary and doc strings
>> still speak mainly of `font-lock-syntactic-keywords'
>> (`syntax-propertize-function' is barely present in font-lock.el).
>>
>> As before.
>>
>> Users are not helped any more than before wrt converting code
>> that uses `font-lock-syntactic-keywords'.
>>
>> That's what this bug report is about.
If you update the NEWS & the manual & the doc strings, and leave the code as is
to support both old and new, then the bug will be fixed.
The NEWS, in particular, should tell users how to replace the old with the new.
It is no help wrt that, so far. It is clearly not as simple as substituting one
(a function) for the other (a variable).
It's about helping users. If I did not find this unclear myself I would not
have taken the time to file the bug (and reply to your (so far) sarcastic and
unhelpful replies).
next prev parent reply other threads:[~2013-03-11 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 15:26 bug#13915: 24.3.50; `font-lock-syntactic-keywords' - really obsolete? Drew Adams
2013-03-11 1:22 ` Stefan Monnier
2013-03-11 3:47 ` Drew Adams
2013-03-11 20:43 ` Stefan Monnier
2013-03-11 21:04 ` Drew Adams [this message]
2013-03-12 2:49 ` Stefan Monnier
2013-03-12 5:36 ` Drew Adams
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=DED20D4D179948DE8B8A15EF7E59992C@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13915@debbugs.gnu.org \
--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 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).