emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] trunk r113568: Make Java try-with-resources statement


From: Alan Mackenzie
Subject: Re: [Emacs-diffs] trunk r113568: Make Java try-with-resources statement parse properly.
Date: Fri, 2 Aug 2013 17:24:56 +0000
User-agent: Mutt/1.5.21 (2010-09-15)

Hi, Juanma.

On Wed, Jul 31, 2013 at 06:35:45PM +0200, Juanma Barranquero wrote:
> On Sat, Jul 27, 2013 at 2:10 PM, Alan Mackenzie <address@hidden> wrote:
> > ------------------------------------------------------------
> > revno: 113568
> > revision-id: address@hidden
> > parent: address@hidden
> > committer: Alan Mackenzie <address@hidden>
> > branch nick: trunk
> > timestamp: Sat 2013-07-27 12:07:43 +0000
> > message:
> >   Make Java try-with-resources statement parse properly.

> This patch causes redisplay errors when visiting C source files:

> Error during redisplay: (jit-lock-function 2096) signaled
> (wrong-type-argument stringp nil)
> Error during redisplay: (jit-lock-function 2643) signaled
> (wrong-type-argument stringp nil)
> Error during redisplay: (jit-lock-function 3144) signaled
> (wrong-type-argument stringp nil)

> Possibly because of this:

> emacs -Q src/alloc.c
> M-: (font-lock-fontify-region (point-min) (point-max)) <RET>

> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   looking-at(nil)
>   #[(match-pos inside-macro) ...] 7](2295 t)
>   c-find-decl-spots(181931 "[[:alpha:]_]" (nil font-lock-type-face
> font-lock-constant-face font-lock-keyword-face) #[(match-pos
> inside-macro) ...] 7])
>   c-font-lock-declarations(181931)
>   font-lock-fontify-keywords-region(1 181931 nil)
>   font-lock-default-fontify-region(1 181931 nil)
>   c-font-lock-fontify-region(1 181931 nil)
>   font-lock-fontify-region(1 181931)
>   eval((font-lock-fontify-region (point-min) (point-max)) nil)
>   eval-expression((font-lock-fontify-region (point-min) (point-max)) nil)
>   call-interactively(eval-expression nil nil)
>   command-execute(eval-expression)

It looks very much like cc-mode.el hasn't been recompiled.  Is that the
case?

The mechanism is that a new "language variable" (i.e. a CC Mode variable
with different values in C Mode, C++ Mode, Java Mode, ....) was defined
in cc-langs.el.  This involves macros which are used in cc-fonts.el,
cc-engine.el and cc-mode.el, so all of these files need recompilation.

The dependency of cc-mode.elc on cc-langs.elc is specified in
.../lisp/Makefile.

If this isn't the cause of the problem, please get back to me.

-- 
Alan Mackenzie (Nuremberg, Germany).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]