[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cperl-mode "fatigue"
From: |
Peter S Galbraith |
Subject: |
Re: cperl-mode "fatigue" |
Date: |
Tue, 29 Oct 2002 08:51:00 -0500 |
Da Witch <heather710101@yahoo.com> wrote:
> In <q5gznsx1vcc.fsf@lucent.com> Klaus Zeitler
> <kzeitler+usenet@sfsw51.lucent.com> writes:
>
> >>>>>> "Da" == Da Witch <heather710101@yahoo.com> writes:
> > Da>
> > Da> I've noticed that sometimes, especially after I have been editing a
> > Da> buffer for a long time, or if I try to use "qw( ... )", cperl-mode
> > Da> begins to show signs of "fatigue" (for lack of a better word). For
> > Da> example, syntax-based highlighting stops, and everything I type
> > Da> appears in the default foreground text color; or else everything
> > Da> appears in the color reserved for quoted strings.
> > Da>
> >I had this problem every once in a while with all emacs 20 versions, but
> >haven't observed it anymore since I switched to emacs 21. I always thought
> >that this is a font-lock problem.
Whenever font-lock stops working in a buffer, it's a very good bet that
a font-lock error occurs. Perhaps the mode uses functions to return
matches and one of them is not behaviour correctly under certain
conditions. Might be hard to track down (I'm not volunteering either).
> > From emacs 21.1 on I've used jit-lock
> >(instead of fast-lock) as font-lock support mode.
>
> Thanks (and to Matt too). Nothing comes up when I type jit-lock into
> Apropos, but I am using v20.7.2. Does jit-lock come standard with
> v21.1? If not, where can I get it?
Yes, it's the default in emacs-21.2:
font-lock-support-mode's value is jit-lock-mode
Peter