From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Last steps for pretesting (font-lock-extend-region-function) Date: Tue, 25 Apr 2006 15:26:46 -0400 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1145993269 20655 80.91.229.2 (25 Apr 2006 19:27:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 Apr 2006 19:27:49 +0000 (UTC) Cc: Ralf Angeli , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 25 21:27:48 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FYTCK-00066P-3B for ged-emacs-devel@m.gmane.org; Tue, 25 Apr 2006 21:27:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYTCJ-0004uS-ET for ged-emacs-devel@m.gmane.org; Tue, 25 Apr 2006 15:27:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FYTBY-0004fP-25 for emacs-devel@gnu.org; Tue, 25 Apr 2006 15:26:56 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FYTBW-0004eY-3e for emacs-devel@gnu.org; Tue, 25 Apr 2006 15:26:55 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYTBV-0004eQ-TT for emacs-devel@gnu.org; Tue, 25 Apr 2006 15:26:53 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FYTE2-0004vM-C5 for emacs-devel@gnu.org; Tue, 25 Apr 2006 15:29:30 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 53D762CF46F; Tue, 25 Apr 2006 15:26:52 -0400 (EDT) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 2618B452A; Tue, 25 Apr 2006 15:26:46 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 1652171500; Tue, 25 Apr 2006 15:26:46 -0400 (EDT) Original-To: Alan Mackenzie In-Reply-To: (Alan Mackenzie's message of "Tue, 25 Apr 2006 10:53:07 +0000 (GMT)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-2.82, requis 5, autolearn=not spam, ALL_TRUSTED -2.82) X-DIRO-MailScanner-From: monnier@iro.umontreal.ca X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:53407 Archived-At: >>> I was talking about programmer work, and I've shown you the code for >>> font-lock-multiline: it's quite a bit shorter and more straightforward than >>> your hack using b-c-f and a-c-f: just match the multiline element, place >>> a font-lock-multiline property on it, and you're set. >> Do you even have to bother with placing font-lock-multiline properties >> manually? In AUCTeX we simply set the font-lock-multiline variable to >> t and font-lock added the property automatically. > Yes, absolutely! There are two separate things here which Stefan is > failing to distinguish: > (i) The matching of keywords which span line breaks; This can only reliably be handled by a hook in font-lock-default-fontify-region. > (ii) Extending a font-lock region to include all text needing > refontification. > If I've understood font-lock-multiline properly, only manually setting > f-l-m can achieve purpose (ii). No, setting the font-lock-multiline variable will (if all goes well) take care of (ii), but won't reliably take care of (i). Setting the font-lock-multiline property by hand will take care of (ii) but not of (i). Stefan