From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Koppelman Newsgroups: gmane.emacs.devel Subject: Re: regexp does not work as documented Date: Sat, 10 May 2008 15:13:37 -0500 Message-ID: References: <87k5i8ukq8.fsf@stupidchicken.com> <200805061335.11379.bruno@clisp.org> <48204B3D.6000500@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1210450436 30829 80.91.229.12 (10 May 2008 20:13:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 May 2008 20:13:56 +0000 (UTC) Cc: Chong Yidong , 192@emacsbugs.donarmstrong.com, Bruno Haible , emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 10 22:14:32 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JuvSe-0005ZS-M5 for ged-emacs-devel@m.gmane.org; Sat, 10 May 2008 22:14:28 +0200 Original-Received: from localhost ([127.0.0.1]:57887 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuvRw-0002Rb-16 for ged-emacs-devel@m.gmane.org; Sat, 10 May 2008 16:13:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuvRs-0002QW-7e for emacs-devel@gnu.org; Sat, 10 May 2008 16:13:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuvRq-0002P4-OV for emacs-devel@gnu.org; Sat, 10 May 2008 16:13:39 -0400 Original-Received: from [199.232.76.173] (port=45443 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuvRq-0002Ou-ID for emacs-devel@gnu.org; Sat, 10 May 2008 16:13:38 -0400 Original-Received: from ecelsrv1.ece.lsu.edu ([130.39.223.98]:47698) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JuvRq-0007j3-9X for emacs-devel@gnu.org; Sat, 10 May 2008 16:13:38 -0400 Original-Received: from localhost (unknown [127.0.0.1]) by ecelsrv1.ece.lsu.edu (Postfix) with ESMTP id B7D0E2839E; Sat, 10 May 2008 20:13:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at ece.lsu.edu Original-Received: from ecelsrv1.ece.lsu.edu ([127.0.0.1]) by localhost (ecelsrv1.ece.lsu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fh7l+otWzISs; Sat, 10 May 2008 15:13:37 -0500 (CDT) Original-Received: from nested.ece.lsu.edu (nested.ece.lsu.edu [130.39.222.143]) by ecelsrv1.ece.lsu.edu (Postfix) with ESMTP id 186F728018; Sat, 10 May 2008 15:13:37 -0500 (CDT) In-Reply-To: (David Koppelman's message of "Sat, 10 May 2008 14:18:59 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:96943 Archived-At: I *am* able to reproduce the font-lock-multiline limitation martin described if the buffer is in text mode. I had tried to reproduce it in emacs-lisp mode. First I'll work on the hi-lock warning as I described below, then I'll see about detecting and doing something helpful for additional situations where multi-line won't work. David Koppelman writes: > I was able to reproduce the problem with Bruno Haible's testcase and > font-lock-multiline t does "fix" it. However martin rudalics warns that > font-lock-multiline won't work for all cases and provides an example > idea (below). I can't get that to fail. That is, with > font-lock-multiline t the text was correctly fontified (though after a > pause). My realization of the example was to remove and then add the > first quotation mark from one of the interior lines below (also > tried with more quoted lines): > > msgstr "" > "Project-Id-Version: GNU gettext-tools 0.16.2-pre5\n" > "Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n" > "POT-Creation-Date: 2007-11-02 03:23+0100\n" > "PO-Revision-Date: 2007-10-27 13:35+0200\n" > "Last-Translator: Christophe Combelles \n" > "Last-Translator: Christophe Combelles \n" > x > > The fix I'm contemplating would be to warn the user when a multi-line > regexp was added interactively and font-lock-multiline was nil, and then > perhaps to offer to set font-lock-multiline to t (or to not set it, or > to stop asking).