From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: bug#3330: Is this a bug? (Emacs 23.0.93) Date: Tue, 19 May 2009 11:11:47 +0000 Message-ID: <20090519111147.GB1317@muc.de> References: <86ddccb30905182238y1674a8fah36a7ecc5ebe64eb5@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1242731559 15136 80.91.229.12 (19 May 2009 11:12:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 May 2009 11:12:39 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org To: liu shukui , 3330@emacsbugs.donarmstrong.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 19 13:12:32 2009 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.50) id 1M6NFH-0001m8-Em for ged-emacs-devel@m.gmane.org; Tue, 19 May 2009 13:12:32 +0200 Original-Received: from localhost ([127.0.0.1]:42470 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6NFG-00032k-HY for ged-emacs-devel@m.gmane.org; Tue, 19 May 2009 07:12:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M6NE2-0002Xn-Mu for emacs-devel@gnu.org; Tue, 19 May 2009 07:11:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M6NDx-0002Uu-S3 for emacs-devel@gnu.org; Tue, 19 May 2009 07:11:14 -0400 Original-Received: from [199.232.76.173] (port=36591 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6NDx-0002Un-Ou for emacs-devel@gnu.org; Tue, 19 May 2009 07:11:09 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:3366 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 1M6NDx-00027X-9Z for emacs-devel@gnu.org; Tue, 19 May 2009 07:11:09 -0400 Original-Received: (qmail 24391 invoked by uid 3782); 19 May 2009 11:11:07 -0000 Original-Received: from acm.muc.de (pD9E2397A.dip.t-dialin.net [217.226.57.122]) by colin2.muc.de (tmda-ofmipd) with ESMTP; Tue, 19 May 2009 13:11:05 +0200 Original-Received: (qmail 2342 invoked by uid 1000); 19 May 2009 11:11:47 -0000 Content-Disposition: inline In-Reply-To: <86ddccb30905182238y1674a8fah36a7ecc5ebe64eb5@mail.gmail.com> 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:110982 gmane.emacs.pretest.bugs:24471 Archived-At: Hi! On Tue, May 19, 2009 at 01:38:17PM +0800, liu shukui wrote: > Hi all, > I am using Emacs 23.0.93, When I run the "occur" command in the c++ > source file, this problem happens occasionally. Is this a bug that > should be fixed? Maybe. :-) > Error during redisplay: (void-function > font-lock-match-c++-style-declaration-item-and-skip-to-next) [6 times] A grep through the Emacs 23 lisp sources doesn't find this function (even when I remember not to quote the two plus signs ;-). However, it existed in Emacs 21, but was removed from Emacs 22 after the font locking stuff for C++ Mode (etc.) was moved into CC Mode. There still exists the function font-lock-match-c-style-declaration-item-and-skip-to-next ^^ in font-lock.el, which obviously is very like the one you're missing. I don't know why the C one is still there but the C++ isn't. > GNU Emacs 23.0.93.1 (i686-pc-linux-gnu, GTK+ Version 2.12.11) of > 2009-05-04 on tux At a guess, you're somehow using old code, maybe something you byte-compiled when Emacs 21 was in fashion. If that doesn't look like the problem, could you please see if you can reproduce the problem when you start Emacs-23 with "emacs -Q". -- Alan Mackenzie (Nuremberg, Germany).