From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: subtle problem of font-lock in *compilation* buffer Date: Tue, 12 Sep 2006 18:50:06 -0400 Message-ID: <87fyewpun5.fsf@stupidchicken.com> References: <87ejujxg42.fsf@furball.mit.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1158101336 22496 80.91.229.2 (12 Sep 2006 22:48:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 12 Sep 2006 22:48:56 +0000 (UTC) Cc: emacs-devel@gnu.org, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 13 00:48:54 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 1GNH3Q-000158-SW for ged-emacs-devel@m.gmane.org; Wed, 13 Sep 2006 00:48:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GNH3Q-0004ja-Gy for ged-emacs-devel@m.gmane.org; Tue, 12 Sep 2006 18:48:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GNH3B-0004gS-CZ for emacs-devel@gnu.org; Tue, 12 Sep 2006 18:48:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GNH39-0004fP-Lq for emacs-devel@gnu.org; Tue, 12 Sep 2006 18:48:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GNH39-0004fI-EQ for emacs-devel@gnu.org; Tue, 12 Sep 2006 18:48:15 -0400 Original-Received: from [18.19.1.138] (helo=cyd) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GNH4j-0007lH-9r; Tue, 12 Sep 2006 18:49:53 -0400 Original-Received: by cyd (Postfix, from userid 1000) id 637D54EB5C; Tue, 12 Sep 2006 18:50:06 -0400 (EDT) Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Mon\, 11 Sep 2006 15\:57\:19 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:59748 Archived-At: Richard Stallman writes: > > That is perhaps because of "1:0:1". > > How can the compilation font-lock pattern distinguish this from a > legitimate error message? > > How about by the spaces in the "file name"? It would wrongly reject compilation messages for file names containing spaces. Kenichi Handa writes: > I don't know whqether it's uncommon or not, but if a packages uses > libtool with "-version-info M:N:L" argument, the above line > appears. It may be too ad hoc but we can tell font-lock > that a line matching with the regexp "-version-info [0-9]" > is not an error message (if font-lock accepts such a > request). I don't see a straightforward way of doing this, but I guess it's worth a shot. > Or, more generally, we may be able tell that a line matching with > "^/bin/sh " is not an error message. This would be wrong if you are compiling the file /bin/sh (unlikely as that may seem).