unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 52418@debbugs.gnu.org
Subject: bug#52418: 27.2; Regression in doc of `font-lock-defaults' since Emacs 25
Date: Fri, 10 Dec 2021 22:39:31 +0000	[thread overview]
Message-ID: <SJ0PR10MB54880B389EF3D96D57561ABCF3719@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)

Prior to Emacs 25, the doc (string and Elisp manual) for
`font-lock-defaults' correctly said this:

 Defaults should be of the form:

  (KEYWORDS [KEYWORDS-ONLY [CASE-FOLD [SYNTAX-ALIST
                                        [SYNTAX-BEGIN ...]]]])

And it specified that:

 If SYNTAX-BEGIN is non-nil, it should be a function with no args used
 to move backwards outside any enclosing syntactic block, for syntactic
 fontification.  Typical values are `beginning-of-line'...

This was replaced starting with Emacs 25 by just this:

 (KEYWORDS [KEYWORDS-ONLY [CASE-FOLD [SYNTAX-ALIST ...]]])

And a statement that the `...' is a possibly empty list of conses of
this form: (VARIABLE . VALUE).

It may be that such conses are acceptable now.  But the previous
description, which is now lacking, also still applies.  The value
for Dired mode, for example is this:

 (dired-font-lock-keywords t nil nil beginning-of-line)

That value fits ONLY the old description.  It does NOT fit the new
description, which is, at best, incomplete.

Please fix the doc for this, whatever the complete truth might be.
Clearly, the doc is wrong (or else values such as that for Dired are
wrong, and that value still works).

In GNU Emacs 27.2 (build 1, x86_64-w64-mingw32)
 of 2021-03-26 built on CIRROCUMULUS
Repository revision: deef5efafb70f4b171265b896505b92b6eef24e6
Repository branch: HEAD
Windowing system distributor 'Microsoft Corp.', version 10.0.19042
System Description: Microsoft Windows 10 Pro (v10.0.2009.19042.1348)






                 reply	other threads:[~2021-12-10 22:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=SJ0PR10MB54880B389EF3D96D57561ABCF3719@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=52418@debbugs.gnu.org \
    /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).