From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Werner LEMBERG Newsgroups: gmane.emacs.devel Subject: Re: [sigra@home.se: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows] Date: Tue, 14 Feb 2006 09:18:00 +0100 (CET) Message-ID: <20060214.091800.102630091.wl@gnu.org> References: <87fymod0dt.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1139943729 19714 80.91.229.2 (14 Feb 2006 19:02:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Feb 2006 19:02:09 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 14 20:02:07 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 1F95Qn-0003Y0-Cm for ged-emacs-devel@m.gmane.org; Tue, 14 Feb 2006 20:01:46 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F95Qm-0003TF-Or for ged-emacs-devel@m.gmane.org; Tue, 14 Feb 2006 14:01:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F90o8-0005Gk-5l for emacs-devel@gnu.org; Tue, 14 Feb 2006 09:05:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F90N0-00078N-Sp for emacs-devel@gnu.org; Tue, 14 Feb 2006 08:37:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F90Ej-0005us-Ho for emacs-devel@gnu.org; Tue, 14 Feb 2006 08:28:58 -0500 Original-Received: from [212.227.126.186] (helo=moutng.kundenserver.de) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F90JO-0001Ay-54 for emacs-devel@gnu.org; Tue, 14 Feb 2006 08:33:47 -0500 Original-Received: from [84.175.195.202] (helo=rigel.site) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1F90E61eDi-00070Z; Tue, 14 Feb 2006 14:28:38 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by rigel.site (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k1E8I0T5006741; Tue, 14 Feb 2006 09:18:00 +0100 Original-To: monnier@iro.umontreal.ca In-Reply-To: X-Mailer: Mew version 4.2.54 on Emacs 22.0.50.1 / Mule 5.0 (SAKAKI) X-Provags-ID: kundenserver.de abuse@kundenserver.de login:2dc398bc694a1e60948148ba0a42c0da 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:50525 Archived-At: > > Currently a function is used as matcher in `font-lock-keywords' for > > this functionality. It basically operates like this: > > I.e. equivalent to "<<\\(.\\|\n\\)*?\\(>>\\)?". It might be a good idea to add the above regexp to the emacs info file as an example how to write a regexp which spans more than a single line. Werner