From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.cc-mode.general,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 14:05:38 -0500 Message-ID: <877j7xojcc.fsf-monnier+emacs@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 X-Trace: sea.gmane.org 1139943968 20637 80.91.229.2 (14 Feb 2006 19:06:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Feb 2006 19:06:08 +0000 (UTC) Cc: rms@gnu.org, bug-cc-mode@gnu.org, emacs-devel@gnu.org Original-X-From: cc-mode-help-admin@lists.sourceforge.net Tue Feb 14 20:06:05 2006 Return-path: Envelope-to: sf-cc-mode-help@m.gmane.org Original-Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F95Uy-0004Zt-T3 for sf-cc-mode-help@m.gmane.org; Tue, 14 Feb 2006 20:06:05 +0100 Original-Received: from sc8-sf-list1-b.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7]) by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id 226701227D; Tue, 14 Feb 2006 11:06:04 -0800 (PST) Original-Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1F95Ui-0004Xa-8b for cc-mode-help@lists.sourceforge.net; Tue, 14 Feb 2006 11:05:48 -0800 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by mail.sourceforge.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.44) id 1F95Ug-0004AX-UK for cc-mode-help@lists.sourceforge.net; Tue, 14 Feb 2006 11:05:48 -0800 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1F95Uc-0008F5-QH for bug-cc-mode@gnu.org; Tue, 14 Feb 2006 14:05:42 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.52) id 1F95ZJ-0005cn-A6 for bug-cc-mode@gnu.org; Tue, 14 Feb 2006 14:10:36 -0500 Original-Received: from [209.226.175.25] (helo=tomts5-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F95ZJ-0005cY-15; Tue, 14 Feb 2006 14:10:33 -0500 Original-Received: from alfajor ([70.48.81.214]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060214190538.DLVO18394.tomts5-srv.bellnexxia.net@alfajor>; Tue, 14 Feb 2006 14:05:38 -0500 Original-Received: by alfajor (Postfix, from userid 1000) id 3AF02D7339; Tue, 14 Feb 2006 14:05:38 -0500 (EST) Original-To: Ralf Angeli In-Reply-To: (Ralf Angeli's message of "Tue, 14 Feb 2006 09:49:46 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 Original-Sender: cc-mode-help-admin@lists.sourceforge.net Errors-To: cc-mode-help-admin@lists.sourceforge.net X-BeenThere: cc-mode-help@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: , List-Id: Bug reports, feature requests, and general talk about CC Mode. List-Post: List-Help: List-Subscribe: , List-Archive: X-Original-Date: Tue, 14 Feb 2006 14:05:38 -0500 Xref: news.gmane.org gmane.emacs.cc-mode.general:2991 gmane.emacs.devel:50527 Archived-At: >> I.e. equivalent to "<<\\(.\\|\n\\)*?\\(>>\\)?". > The function actually used in AUCTeX does a bit more. For example it > checks if a face for verbatim content is present and does not set a > match in such a case. Sure. Also it's more efficient than the above regexp. >> it's specific to jit-lock, tho. > Hm, I would not like leaving people who disabled jit-lock out in the > cold. So the hook is probably a better alternative. But thanks for > that hint anyway. jit-lock is already needed for correct refontification of multi-line comments and strings, so I wouldn't worry too much about the effect it would have of foncitifcation of other multiline constructs. >> that I'd want it to be in font-lock-default-fontify-region. I.e. it should >> then be possible to remove mention of font-lock-multiline from >> font-lock-default-fontify-region by moving it to this new hook (which we >> could call font-lock-fontify-extend-region-functions). > Hm, how would it be possible to detect closing tags in this case? > Maybe with an initial search for these tags across the region to be > fontified. Or on a case by case basis for every closing tag which is > encountered during fontication of the region? This would be rather > inefficient compared to using a hook to be called before > `font-lock-after-change-function'. But maybe you are thinking about > something completely different. Huh? I must be missing something: I don't see what's different between font-lock-after-change-function and font-lock-default-fontify-region, other than the fact that they're called at different moments. Stefan ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642