From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: XKCD/541 compliance, anyone? Date: Fri, 02 Jan 2015 20:49:30 -0500 Message-ID: References: <8761drazec.fsf@wmi.amu.edu.pl> <87k318npmf.fsf@wmi.amu.edu.pl> <87ppaxmel3.fsf@wmi.amu.edu.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1420249827 26659 80.91.229.3 (3 Jan 2015 01:50:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Jan 2015 01:50:27 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jan 03 02:50:19 2015 Return-path: Envelope-to: geh-help-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 1Y7Dr9-00046D-7T for geh-help-gnu-emacs@m.gmane.org; Sat, 03 Jan 2015 02:50:19 +0100 Original-Received: from localhost ([::1]:53258 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7Dr8-0006aN-Ov for geh-help-gnu-emacs@m.gmane.org; Fri, 02 Jan 2015 20:50:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47394) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7Dqx-0006Y3-MH for help-gnu-emacs@gnu.org; Fri, 02 Jan 2015 20:50:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y7Dqu-0008R7-Gu for help-gnu-emacs@gnu.org; Fri, 02 Jan 2015 20:50:07 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:51307) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7Dqu-0008QO-9Y for help-gnu-emacs@gnu.org; Fri, 02 Jan 2015 20:50:04 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y7Dqt-00042z-Ed for help-gnu-emacs@gnu.org; Sat, 03 Jan 2015 02:50:03 +0100 Original-Received: from 69-165-141-1.dsl.teksavvy.com ([69.165.141.1]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Jan 2015 02:50:03 +0100 Original-Received: from monnier by 69-165-141-1.dsl.teksavvy.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Jan 2015 02:50:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 25 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 69-165-141-1.dsl.teksavvy.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Cancel-Lock: sha1:dBmVr2ccxJNuL0hBgFJu45MBdb4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:101846 Archived-At: > Do I get it correctly that it "outputs" a function, so that I can > write > (setq syntax-propertize-function (syntax-propertize-rules (...))) > ? That's right. > I have global font lock mode, so font locking is on everywhere. Nope: global-font-lock-mode only enabled font-lock in those modes where there are font-lock keywords defined. >>> but then again, not in message mode, for instance. >> Probably because font-lock-keywords-only is set to t, so font-lock >> doesn't end up calling syntax-ppss. > Now that is strange: it seems that font-lock-keywords-only is set to t > in mu4e-message mode (where I'm now), but grepping through mu4e sources > didn't give any results (nor did isearching message.el). I'll have to > look into this further (check other modes etc.) That's because font-lock-keywords-only is set indirectly via the 2nd element of `font-lock-defaults'. Stefan