From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie 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: Wed, 15 Feb 2006 20:56:25 +0000 (GMT) Message-ID: References: <43F239E3.2020707@gmx.at> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: sea.gmane.org 1140037120 10777 80.91.229.2 (15 Feb 2006 20:58:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 15 Feb 2006 20:58:40 +0000 (UTC) Cc: Stefan Monnier , bug-cc-mode@gnu.org, Ralf Angeli , rms@gnu.org, emacs-devel@gnu.org Original-X-From: cc-mode-help-admin@lists.sourceforge.net Wed Feb 15 21:58:34 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 1F9Tiw-0004IU-En for sf-cc-mode-help@m.gmane.org; Wed, 15 Feb 2006 21:58:06 +0100 Original-Received: from sc8-sf-list1-b.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7]) by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP id 1488833FE3; Wed, 15 Feb 2006 12:58:05 -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 1F9TiT-0007OW-FT for cc-mode-help@lists.sourceforge.net; Wed, 15 Feb 2006 12:57:37 -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 1F9TiT-0004M9-7I for cc-mode-help@lists.sourceforge.net; Wed, 15 Feb 2006 12:57:37 -0800 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1F9TiO-00079S-Mp for bug-cc-mode@gnu.org; Wed, 15 Feb 2006 15:57:32 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.52) id 1F9TnK-0005Xj-AN for bug-cc-mode@gnu.org; Wed, 15 Feb 2006 16:02:41 -0500 Original-Received: from [193.149.49.134] (helo=acm.acm) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9TnD-0005X5-P7; Wed, 15 Feb 2006 16:02:32 -0500 Original-Received: from localhost (root@localhost) by acm.acm (8.8.8/8.8.8) with SMTP id UAA00973; Wed, 15 Feb 2006 20:56:25 GMT X-Sender: root@acm.acm Original-To: martin rudalics In-Reply-To: <43F239E3.2020707@gmx.at> X-Spam-Score: 1.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 1.0 FORGED_RCVD_HELO Received: contains a forged HELO 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: Wed, 15 Feb 2006 20:56:25 +0000 (GMT) Xref: news.gmane.org gmane.emacs.cc-mode.general:3011 gmane.emacs.devel:50582 Archived-At: Hi, Martin! On Tue, 14 Feb 2006, martin rudalics wrote: > > Huh? Why would window-start matter? >Because fontification triggered by redisplay will fontify the displayed >area first. `jit-lock-context-fontify' would reset the fontified >property for everything after the "<<". Redisplay now would trigger >refontification below window-start. It won't care about the "<<". > > I'm not sure which hook you're talking about. The code I wrote above is > > meant to be used on font-lock-keywords when finding a ">>". >The hook that would trigger searching for the "<<" after a buffer >change, `before-font-lock-after-change-function' or whatever it will be >called. I simply believe that searching some 1000 characters every time >you type one single character may slow down editing noticeably. But >maybe I didn't understand the scenario correctly. Surely it would be possible to arrange for this searching to be done only when one of these delimiters is inserted or deleted? In a before-change function, you check whether or not a change is happening around a ">>", ">", "<" or "<<", and record this in some variables. In the after-change you see if a delimiter has actually been inserted or deleted. Only then need you search. Since this searching will be done only rarely, you probably don't need to worry about searching even the entire buffer. -- Alan. ------------------------------------------------------- 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