From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: Tokenizing Date: Mon, 22 Sep 2014 09:05:51 -0500 Message-ID: <85r3z3kaww.fsf@stephe-leake.org> References: <85d2apdm1h.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1411394831 8144 80.91.229.3 (22 Sep 2014 14:07:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Sep 2014 14:07:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 22 16:07:04 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XW4Gb-0006nw-2W for ged-emacs-devel@m.gmane.org; Mon, 22 Sep 2014 16:07:01 +0200 Original-Received: from localhost ([::1]:46837 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XW4GY-0002BJ-FB for ged-emacs-devel@m.gmane.org; Mon, 22 Sep 2014 10:06:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XW4Fj-0000kM-BX for emacs-devel@gnu.org; Mon, 22 Sep 2014 10:06:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XW4Fb-0000KO-Ly for emacs-devel@gnu.org; Mon, 22 Sep 2014 10:06:07 -0400 Original-Received: from dnvrco-outbound-snat.email.rr.com ([107.14.73.229]:38577 helo=dnvrco-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XW4Fb-0000Hm-Gm for emacs-devel@gnu.org; Mon, 22 Sep 2014 10:05:59 -0400 Original-Received: from [70.94.38.149] ([70.94.38.149:50509] helo=TAKVER) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 97/09-08316-1CC20245; Mon, 22 Sep 2014 14:05:53 +0000 In-Reply-To: (Stefan Monnier's message of "Sun, 21 Sep 2014 12:43:54 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=ReIeCjdv c=1 sm=1 tr=0 a=AppmJ/7ZOOFWL/q6u6u93g==:117 a=AppmJ/7ZOOFWL/q6u6u93g==:17 a=ayC55rCoAAAA:8 a=9XSUBuVRJI8A:10 a=o_R75loqY_IA:10 a=9i_RQKNPAAAA:8 a=l9VjFuPoFlZN5jXtkq0A:9 X-Cloudmark-Score: 0 X-detected-operating-system: by eggs.gnu.org: BaiduSpider X-Received-From: 107.14.73.229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:174646 Archived-At: Stefan Monnier writes: >>>> - it should be possible to completely replace the font-lock-mode with >>>> this mode, given a concrete language tokenizer; >>> The intention for font-lock highlighting is to show >>> syntactic structure. In many cases, we end up limited to lexical >>> highlighting, but that's a problem. >> syntax-propertize provides hooks to let modes add to that; > > Maybe you use it for that, but it's definitely not its intention: > `syntax-propertize' is not meant for highlighting at all. Sorry, I meant "font-lock-add-keywords"; you can add arbitrary functions that use the parser results to choose a face. The parser does rely on syntax-propertize. -- -- Stephe