From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#15120: 24.3.50; (elisp) `Search-based Fontification': unspecified MATCHER cases Date: Sun, 9 Feb 2014 16:02:56 -0800 (PST) Message-ID: <4d6326cc-875a-4581-8ed9-c084dffdda08@default> References: <4e841492-80d7-45a1-b874-afc15d2701c6@default> <87a9e242im.fsf@building.gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1391990659 10556 80.91.229.3 (10 Feb 2014 00:04:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Feb 2014 00:04:19 +0000 (UTC) Cc: 15120@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 10 01:04:26 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WCeMJ-0000ND-PG for geb-bug-gnu-emacs@m.gmane.org; Mon, 10 Feb 2014 01:04:23 +0100 Original-Received: from localhost ([::1]:52562 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WCeMJ-0004Td-4L for geb-bug-gnu-emacs@m.gmane.org; Sun, 09 Feb 2014 19:04:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WCeM7-0004SI-Hg for bug-gnu-emacs@gnu.org; Sun, 09 Feb 2014 19:04:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WCeLy-0005P6-VJ for bug-gnu-emacs@gnu.org; Sun, 09 Feb 2014 19:04:11 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:47015) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WCeLy-0005P2-RU for bug-gnu-emacs@gnu.org; Sun, 09 Feb 2014 19:04:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WCeLy-0002cX-7J for bug-gnu-emacs@gnu.org; Sun, 09 Feb 2014 19:04:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 10 Feb 2014 00:04:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15120 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 15120-submit@debbugs.gnu.org id=B15120.13919905859981 (code B ref 15120); Mon, 10 Feb 2014 00:04:02 +0000 Original-Received: (at 15120) by debbugs.gnu.org; 10 Feb 2014 00:03:05 +0000 Original-Received: from localhost ([127.0.0.1]:32793 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WCeL2-0002av-SJ for submit@debbugs.gnu.org; Sun, 09 Feb 2014 19:03:05 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:30068) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WCeL0-0002aX-FF for 15120@debbugs.gnu.org; Sun, 09 Feb 2014 19:03:04 -0500 Original-Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s1A02xRr031248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Feb 2014 00:03:00 GMT Original-Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s1A02wlt000131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Feb 2014 00:02:59 GMT Original-Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s1A02w59000124; Mon, 10 Feb 2014 00:02:58 GMT In-Reply-To: <87a9e242im.fsf@building.gnus.org> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.8 (707110) [OL 12.0.6680.5000 (x86)] X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:85111 Archived-At: > > 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. >=20 > I see what you mean,=20 No, I don't think you do. > but if you read the page from the start to finish, I certainly did that. Did you? > you see that it explains what all meta-syntactical are once. Not at all. > It says what MATCHER is the first time it talks about it, and then it > just describes what each new element is. So I think the page is OK as > is. You are just not reading. What it says, at the place where you apparently think that it introduces MATCHER for the entire page, is this: "In this kind of element, MATCHER is..." ^^^^^^^^^^^^^^^^^^^^^^^ IN THIS KIND OF ELEMENT! Why on Earth does it say that? It is specifying what MATCHER means in the form `(MATCHER . SUBEXP)', where SUBEXP must be... And by taking the pains to specify explicitly that this applies to this kind of element, the suggestion is that it does NOT necessarily apply to the other kinds of element shown on the page. Otherwise, why say that? That's the point: each of these kinds of "element" is specified separately, and it says so explicitly. If you want to make the current description of MATCHER apply to the whole page, then it needs to be introduced at the outset as applying to the whole page. And the text certainly should NOT then say that the description applies to some particular kind of element. IOW, remove that "In this kind of element...", as well. Again, please _read_ the bug report. Among other things, it says that the doc string gets it right. Use it, if it helps, as your inspiration for actually _fixing_ this bug.