From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bruno Haible Newsgroups: gmane.emacs.devel Subject: Re: regexp does not work as documented Date: Tue, 6 May 2008 23:35:59 +0200 Message-ID: <200805062335.59206.bruno@clisp.org> References: <87k5i8ukq8.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1210109791 29491 80.91.229.12 (6 May 2008 21:36:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 May 2008 21:36:31 +0000 (UTC) Cc: 192@emacsbugs.donarmstrong.com, emacs-devel@gnu.org To: David Koppelman , Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 06 23:37:06 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 1JtUqL-0000If-01 for ged-emacs-devel@m.gmane.org; Tue, 06 May 2008 23:37:01 +0200 Original-Received: from localhost ([127.0.0.1]:34162 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JtUpd-0007Aj-3S for ged-emacs-devel@m.gmane.org; Tue, 06 May 2008 17:36:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JtUpa-00079X-18 for emacs-devel@gnu.org; Tue, 06 May 2008 17:36:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JtUpX-00078q-Ux for emacs-devel@gnu.org; Tue, 06 May 2008 17:36:13 -0400 Original-Received: from [199.232.76.173] (port=38002 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JtUpX-00078n-Pv for emacs-devel@gnu.org; Tue, 06 May 2008 17:36:11 -0400 Original-Received: from mo-p07-ob.rzone.de ([81.169.146.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JtUpX-0000uG-C8 for emacs-devel@gnu.org; Tue, 06 May 2008 17:36:11 -0400 X-RZG-CLASS-ID: mo07 X-RZG-AUTH: gMysVb8JT2gB+rFDu0PuvnvUUGmhfq1rhHRG5dSek381RH36PlIq8YOI Original-Received: from linuix.haible.de (dslb-084-058-049-074.pools.arcor-ip.net [84.58.49.74]) by post.webmailer.de (mrclete mo25) (RZmta 16.34) with ESMTP id 200896k46K3sKd ; Tue, 6 May 2008 23:36:02 +0200 (MEST) (envelope-from: ) User-Agent: KMail/1.5.4 In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:96616 Archived-At: David Koppelman wrote: > Later in the week I'll look into it and provide either a fix > or document the limitation. Thank you! Chong Yidong wrote: > > OTOH, I don't see what we can do about this problem. Maybe we could add > > a note to the docstring of highlight-regexp saying that multi-line > > regular expressions are problematic? Does anyone have a suggestion? As an end user, for testing the effect of a regexp on a buffer interactively, I would prefer to have a "volatile" coloring (i.e. one that disappears at the next buffer modification) but is correct, rather than a documented-to-be-wrong coloring that updates itself correctly during buffer modifications. Less functionality but implemented correctly. OTOH, third-party packages may prefer the current behaviour if their regexps match only portions of a line. Bruno