From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Elena Newsgroups: gmane.emacs.help Subject: Re: Best way to detect font-lock mode is on? Date: Wed, 5 Jan 2011 06:52:14 -0800 (PST) Organization: http://groups.google.com Message-ID: <7cb5b66f-02fb-47b7-a4a8-ba571c19f3ac@t8g2000prh.googlegroups.com> References: <87ei8uvgws.fsf@puma.rapttech.com.au> <8762u6v7sd.fsf@puma.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1294242045 14009 80.91.229.12 (5 Jan 2011 15:40:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 5 Jan 2011 15:40:45 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 05 16:40:41 2011 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PaVTd-0003KH-JZ for geh-help-gnu-emacs@m.gmane.org; Wed, 05 Jan 2011 16:40:41 +0100 Original-Received: from localhost ([127.0.0.1]:45441 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PaVTc-0007ED-TZ for geh-help-gnu-emacs@m.gmane.org; Wed, 05 Jan 2011 10:40:40 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!news2.glorb.com!postnews.google.com!t8g2000prh.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 18 Original-NNTP-Posting-Host: 89.96.190.244 Original-X-Trace: posting.google.com 1294239134 13754 127.0.0.1 (5 Jan 2011 14:52:14 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 5 Jan 2011 14:52:14 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: t8g2000prh.googlegroups.com; posting-host=89.96.190.244; posting-account=AFCLjAoAAABJAOf_HjgEEEi3ty-lG5m2 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:184016 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:78214 Archived-At: On Jan 5, 5:50=A0am, Stefan Monnier wrote: > > Yes, that is how I plan to do it if font-lock is not enabled. I'm > > currently experimenting with syntax-ppss and parse-partial-sexp to see > > if the cached version can be used reliably or if the uncaching variant > > is required and if this has too high a penalty. I have found that with > > syntax-ppss, I do get false positives fairly frequently if I don't firs= t > > call syntax-pps-flush-cache, which would seem to defeat its benefits > > over parse-partial-sexp. > > font-lock uses syntax-ppss, so if syntax-ppss is wrong, font-lock should > be wrong as well. syntax-ppss -> Parse-Partial-Sexp State Isn't syntax-ppss Lisp-specific? What about text highlighted by font-lock-add-keywords?