unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16308@debbugs.gnu.org
Subject: bug#16308: 24.3.50; doc of `font-lock-keywords'
Date: Fri, 07 Feb 2014 18:50:06 -0800	[thread overview]
Message-ID: <87iosqb9nl.fsf@building.gnus.org> (raw)
In-Reply-To: <249f7d3a-dc4e-4963-b8ce-1d3f0120609d@default> (Drew Adams's message of "Tue, 31 Dec 2013 09:20:42 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> The description in the Elisp manual, which is our reference, should be
> at least as complete as the doc string.  It is not.  In particular, it
> does not describe the structure of the value correctly.  It does not
> mention the compiled form, with car `t' etc.
>
> The doc string is far more complete.  If anything, it should be the
> other way around.  But preferably, both doc string and manual (node
> `Search-based Fontification', currently) should each be complete and
> correct.

No, I think the information about the compiled form isn't particularly
relevant for people who are composing the keywords, while it is relevant
for people who examine the variable, so it's fine the way it is.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2014-02-08  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 17:20 bug#16308: 24.3.50; doc of `font-lock-keywords' Drew Adams
2014-02-08  2:50 ` Lars Ingebrigtsen [this message]
2014-02-08  3:21   ` Drew Adams
2014-02-08  5:02     ` Stefan Monnier

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=87iosqb9nl.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=16308@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).