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:13:44 +0000 (GMT) Message-ID: References: <43F18C90.4050205@gmx.at> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: sea.gmane.org 1140037113 10763 80.91.229.2 (15 Feb 2006 20:58:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 15 Feb 2006 20:58:33 +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:31 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 1F9Tj0-0004Jh-GJ for sf-cc-mode-help@m.gmane.org; Wed, 15 Feb 2006 21:58:11 +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 C648232256; Wed, 15 Feb 2006 12:58:07 -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 1F9Tim-0007Pf-FY for cc-mode-help@lists.sourceforge.net; Wed, 15 Feb 2006 12:57:56 -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 1F9Til-0004Oy-7Y for cc-mode-help@lists.sourceforge.net; Wed, 15 Feb 2006 12:57:56 -0800 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1F9Tih-0007AJ-1u for bug-cc-mode@gnu.org; Wed, 15 Feb 2006 15:57:51 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.52) id 1F9Tnc-0005Z0-NG for bug-cc-mode@gnu.org; Wed, 15 Feb 2006 16:02:59 -0500 Original-Received: from [193.149.49.134] (helo=acm.acm) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9TnY-0005Ya-4D; Wed, 15 Feb 2006 16:02:53 -0500 Original-Received: from localhost (root@localhost) by acm.acm (8.8.8/8.8.8) with SMTP id UAA00953; Wed, 15 Feb 2006 20:13:45 GMT X-Sender: root@acm.acm Original-To: martin rudalics In-Reply-To: <43F18C90.4050205@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:13:44 +0000 (GMT) Xref: news.gmane.org gmane.emacs.cc-mode.general:3010 gmane.emacs.devel:50581 Archived-At: Hi, Martin! On Tue, 14 Feb 2006, martin rudalics wrote: > >>With the matcher function above text in quotation marks won't be > >>fontified when I start typing stuff like "< >>no closing quotation mark. Now if the closing quotation mark is > >>entered a few lines below the line containing the opening quotation > >>mark, font locking won't see the opening quotation mark and the > >>multiline quotation won't be fontified. > > Indeed. You can use contextual refontification, tho: > > (if jit-lock-context-unfontify-pos > > (setq jit-lock-context-unfontify-pos > > (min jit-lock-context-unfontify-pos > > (re-search-backward "<<" limit t)))) > > it's specific to jit-lock, tho. >Provided the "<<" is still after window-start, though. >In any case, it's completely inappropriate to search tags in the hook. [ Small linguistic point: "search" = "durchsuchen"; "search for" = "suchen".] >The hook should trigger an idle timed function that would do the search. >And you could calmly replace the 1000 characters limit by something more >useful. I disagree profoundly. This would interact with other idly timed functions, some of which might well already be fontifying up to the bits being searched. The font locking code is already very complicated, and this extra complication would make it very difficult indeed to debug. I think the function should be run from the after-change hook, brute force fashion. Should it prove too slow[*], then would be the time to implement a more sophisticated strategy. [*] I have a 166 MHz PC, available for testing for "too slow". -- Alan Mackenzie (Munich, Germany) ------------------------------------------------------- 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