all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 15120@debbugs.gnu.org
Subject: bug#15120: 24.3.50; (elisp) `Search-based Fontification': unspecified MATCHER cases
Date: Sat, 17 Aug 2013 10:33:13 -0700 (PDT)	[thread overview]
Message-ID: <4e841492-80d7-45a1-b874-afc15d2701c6@default> (raw)

The doc string is good in this regard, but the Elisp manual is not.

The manual says that an element can be FUNCTION.  OK.

And it says, for (MATCHER . SUBEXP), that MATCHER can be a function.  OK.

But it does not say that for all of the other (MATCHER . *) patterns
MATCHER can also be a function.  In fact, for the others MATCHER is left
unspecified.

And for (MATCHER . SUBEXP-HIGHLIGHTER) the doc actually refers to a
"SUBEXP in MATCHER", which suggests, but does not specify, that MATCHER
in this case can be or perhaps even *must be* a REGEXP.

Follow the example of the doc string, or state somewhere that MATCHER,
in all that follows, can be either a regexp or a function...

IOW, make clear just what MATCHER can be, in general or in each of the
cases.



In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-08-07 on ODIEONE
Bzr revision: 113750 lekktu@gmail.com-20130808011911-0jzpc9xuncegg6x9
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 CFLAGS=-O0 -g3 LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'





             reply	other threads:[~2013-08-17 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 17:33 Drew Adams [this message]
2014-02-08  5:06 ` bug#15120: 24.3.50; (elisp) `Search-based Fontification': unspecified MATCHER cases Lars Ingebrigtsen
2014-02-10  0:02   ` Drew Adams
2014-02-10  8:03     ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4e841492-80d7-45a1-b874-afc15d2701c6@default \
    --to=drew.adams@oracle.com \
    --cc=15120@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.