unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 19483-done@debbugs.gnu.org
Subject: bug#19483: 25.0.50; out-of-date doc and Commentary in `font-lock' wrt `font-lock-syntactic-keywords'
Date: Fri, 2 Jan 2015 23:59:54 -0800 (PST)	[thread overview]
Message-ID: <10e946e2-cda1-49be-9cb2-d6575f415d14@default> (raw)
In-Reply-To: <jwvsifs7dt3.fsf-monnier+emacsbugs@gnu.org>

> tags 19483 notabug
> thanks
> 
> > `C-h v font-lock-syntactic-keywords' says that the variable is
> > obsolete since 24.1.
> 
> That's right.
> 
> > But in font-lock.el, the code, multiple doc strings, and
> > the Commentary all rely on it.
> 
> No, they just keep supporting it, because it's only "obsolete" and
> not "removed".

The doc and Commentary should reflect the fact that it has been
declared "obsolete".  That's the point.

> Do you really want to advocate we remove features right away when we
> decide they're obsolete?

Strawman, again.  No one suggested that you remove any feature.

Read the bug report.  It's about the doc (including Commentary). 

When you deprecate something, the doc for it should state that it
is deprecated.  Everywhere.

That the doc was not brought up to date about this as soon as
the status changed to deprecated was a doc bug 4 releases ago.
The bug is still there.

Emacs is the self-documenting editor.  It should tell users
about itself accurately.





  reply	other threads:[~2015-01-03  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 22:25 bug#19483: 25.0.50; out-of-date doc and Commentary in `font-lock' wrt `font-lock-syntactic-keywords' Drew Adams
2015-01-03  3:19 ` Stefan Monnier
2015-01-03  7:59   ` Drew Adams [this message]
2015-01-04  2:36     ` Stefan Monnier
2015-01-04  3:00       ` 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=10e946e2-cda1-49be-9cb2-d6575f415d14@default \
    --to=drew.adams@oracle.com \
    --cc=19483-done@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).