From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Is there something like `on-display-functions'? Date: Thu, 28 Jan 2010 10:14:40 +0000 Message-ID: <20100128101440.GA2285@muc.de> References: <20100127135716.GA3432@muc.de> <4B60EB47.3080208@censorshipresearch.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1264673340 4918 80.91.229.12 (28 Jan 2010 10:09:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 Jan 2010 10:09:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 28 11:08:57 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NaRJ0-0000dP-4I for ged-emacs-devel@m.gmane.org; Thu, 28 Jan 2010 11:08:54 +0100 Original-Received: from localhost ([127.0.0.1]:33308 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NaRIz-00065i-DI for ged-emacs-devel@m.gmane.org; Thu, 28 Jan 2010 05:08:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NaRIA-0005o4-8R for emacs-devel@gnu.org; Thu, 28 Jan 2010 05:08:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NaRI5-0005mW-Lm for emacs-devel@gnu.org; Thu, 28 Jan 2010 05:08:01 -0500 Original-Received: from [199.232.76.173] (port=46466 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NaRI5-0005mL-DC for emacs-devel@gnu.org; Thu, 28 Jan 2010 05:07:57 -0500 Original-Received: from colin.muc.de ([193.149.48.1]:3816 helo=mail.muc.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NaRI4-0004eR-Oz for emacs-devel@gnu.org; Thu, 28 Jan 2010 05:07:57 -0500 Original-Received: (qmail 52319 invoked by uid 3782); 28 Jan 2010 10:07:54 -0000 Original-Received: from acm.muc.de (pD9E225E1.dip.t-dialin.net [217.226.37.225]) by colin2.muc.de (tmda-ofmipd) with ESMTP; Thu, 28 Jan 2010 11:07:53 +0100 Original-Received: (qmail 2901 invoked by uid 1000); 28 Jan 2010 10:14:40 -0000 Content-Disposition: inline In-Reply-To: <4B60EB47.3080208@censorshipresearch.org> User-Agent: Mutt/1.5.9i X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) X-Primary-Address: acm@muc.de X-detected-operating-system: by monty-python.gnu.org: FreeBSD 4.6-4.9 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:120556 Archived-At: Hi, Daniel! On Wed, Jan 27, 2010 at 08:41:27PM -0500, Daniel Colascione wrote: > On 1/27/10 8:57 AM, Alan Mackenzie wrote: > > Is there some hook called each time something's about to be displayed > > on the screen (regardless of whether or not font-lock is enabled)? > > If there is, I could use it to apply the appropriate text properties > > to C++ template delimiters as they're about to be displayed, thus > > potentially speeding up startup for C++ (and like languages). > Wouldn't that do the wrong thing if, say, the first half of a template > argument list is at the bottom of the visible portion of the buffer, > and I want to jump to its end? No. :-) I'm intending to mark the template delimiters ONLY in pairs from now on. This is due to difficulties with the current approach, which is to mark an opening < when it looks like a template opener. It is rarely (?never) necessary to look very far for a matching >, since a <..> pair can never enclose a ;, {, or } [*]. The "never" might happen when you type a < shortly before an infinite number of #define lines. But C++ hackers don't really use #define, do they? ;-) [*] Any rough estimate of how large the gap between < and > gets in real C++ programs would be welcome. -- Alan Mackenzie (Nuremberg, Germany).