Re: Fontification Problems with alltt

Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:

> * Jan T. Kim (2005-03-07) writes:
> 
> > Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:
> >
> >> * Jan T. Kim (2005-03-06) writes:
> 
> [fontification bleeding out of alltt environment]
> 
> >> There was a similar report a few days ago.  It is likely Emacs not
> >> updating the font locking correctly.  Do you still see the problem
> >> with a development version of Emacs?
> >
> > I've just installed emacs-21.4a, dated 17-Feb-2005 on
> > http://ftp.gnu.org/pub/gnu/emacs/ , hope that's sufficiently "bleeding
> > edge"...
> 
> There haven't been any changes to the font locking code in this
> release compared to Emacs 21.3.  So I'd say no.  It would have to be a
> CVS snapshot or checkout.  But of course installing and using such a
> snapshot is not everybody's cup of tea.

Ok -- I have compiled Emacs 22.0.50.1 from CVS. Thus far, I have not
been able to trigger the bug again, but this may not mean much, as I
don't know a reliable way to trigger it. Here are some potentially
relevant observations, though. The fontification does get inversed
(i.e. it's not just "bleeding out of the alltt environment",
everything is brown outside and content inside alltt is multicoloured,
depending on commands) if

    *  the alltt environment is empty

    * \begin{alltt} is followed by a backslash and a newline.

Both these effects also occur with the 21.3 version, although sometimes
very slowly (which is why I haven't noticed this pattern before -- the
CVS version seems to be substantially faster) and are usually reversed
upon adding stuff.

Now, assuming for the moment that upgrading to 22.0.50.1 fixes the
problem: Does that mean that this upgrade is the only way to get
AUCTeX working correctly? Can you give me any recommendations on how
to work this? Any recommendations?

Best regards & thanks in advance, Jan