From: liu shukui <liushukuicn1771@gmail.com>
To: Alan Mackenzie <acm@muc.de>,
emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Cc: 3330@emacsbugs.donarmstrong.com
Subject: Re: bug#3330: Is this a bug? (Emacs 23.0.93)
Date: Wed, 20 May 2009 11:25:32 +0800 [thread overview]
Message-ID: <86ddccb30905192025o3d9f8be4obed4eee32999ef4@mail.gmail.com> (raw)
In-Reply-To: <20090519111147.GB1317@muc.de>
On Tue, May 19, 2009 at 7:11 PM, Alan Mackenzie <acm@muc.de> wrote:
> 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).
>
I use the color-theme package, maybe this is the causation. I will
disable it to test emacs next few days.
prev parent reply other threads:[~2009-05-20 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 5:38 Is this a bug? (Emacs 23.0.93) liu shukui
2009-05-19 11:11 ` bug#3330: " Alan Mackenzie
2009-05-20 3:25 ` liu shukui [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ddccb30905192025o3d9f8be4obed4eee32999ef4@mail.gmail.com \
--to=liushukuicn1771@gmail.com \
--cc=3330@emacsbugs.donarmstrong.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).