GNU bug report logs -
#43037
Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’
Previous Next
Reported by: AC <achirvasub <at> gmail.com>
Date: Tue, 25 Aug 2020 12:38:02 UTC
Severity: normal
Tags: moreinfo
Done: Alan Mackenzie <acm <at> muc.de>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 43037 in the body.
You can then email your comments to 43037 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Tue, 25 Aug 2020 12:38:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
AC <achirvasub <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 25 Aug 2020 12:38:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I compile emacs off the emacs-27 branch. On those machines, opening certain file types results in the above error.
For .js files for instance, the full error is
Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for ‘font-lock-comment-end-skip’ (fallback source eval - js-mode compiled with CC Mode 5.34 but loaded with 5.34.1): (error "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode (might be a cyclic reference)")
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 08:30:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 43037 <at> debbugs.gnu.org (full text, mbox):
AC <achirvasub <at> gmail.com> writes:
> I compile emacs off the emacs-27 branch. On those machines, opening
> certain file types results in the above error.
>
> For .js files for instance, the full error is
>
> Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for
> ‘font-lock-comment-end-skip’ (fallback source eval - js-mode compiled
> with CC Mode 5.34 but loaded with 5.34.1): (error
> "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode (might
> be a cyclic reference)")
(This bug report unfortunately got no attention at the time.)
I'm unable to reproduce this bug in Emacs 27 or Emacs 28. Do you have a
recipe for reproducing this bug, starting from "emacs -Q"?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 16 Oct 2020 08:30:04 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 10:15:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 43037 <at> debbugs.gnu.org (full text, mbox):
On October 16, 2020 4:29:18 AM EDT, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
>AC <achirvasub <at> gmail.com> writes:
>
>> I compile emacs off the emacs-27 branch. On those machines, opening
>> certain file types results in the above error.
>>
>> For .js files for instance, the full error is
>>
>> Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for
>> ‘font-lock-comment-end-skip’ (fallback source eval - js-mode compiled
>> with CC Mode 5.34 but loaded with 5.34.1): (error
>> "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode
>(might
>> be a cyclic reference)")
>
>(This bug report unfortunately got no attention at the time.)
>
>I'm unable to reproduce this bug in Emacs 27 or Emacs 28. Do you have
>a
>recipe for reproducing this bug, starting from "emacs -Q"?
>
Yes.
Literally seconds ago I compiled emacs-27, started it up with 'emacs -Q' and then visited the blank file '~/new.js'. That error popped up.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 10:46:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 43037 <at> debbugs.gnu.org (full text, mbox):
> Date: Fri, 16 Oct 2020 06:14:17 -0400
> From: AC <achirvasub <at> gmail.com>
> Cc: 43037 <at> debbugs.gnu.org
>
> Literally seconds ago I compiled emacs-27, started it up with 'emacs -Q' and then visited the blank file '~/new.js'. That error popped up.
I cannot reproduce this with stock Emacs 27.1, but I can reproduce
with the current emacs-27 branch. The more detailed error message is
this:
Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for ‘font-lock-comment-end-skip’ (fallback source eval - js-mode compiled with CC Mode 5.34 but loaded with 5.34.1): (error "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode (might be a cyclic reference)")
Alan, can you take a look, please?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 13:37:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 43037 <at> debbugs.gnu.org (full text, mbox):
Thank you for confirming it happens!
Some additional info: I can reproduce this consistently on 3 machines, all running Ubuntu (20.04 and 18.04); the procedure is the same on all of them (compile the current emacs-27 branch from the repo). I don't know if this (the Ubuntu base) matters..
On the other hand, the "standard" Emacs 27.1 that comes with Arch Linux does not exhibit this.
On October 16, 2020 6:45:34 AM EDT, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Fri, 16 Oct 2020 06:14:17 -0400
>> From: AC <achirvasub <at> gmail.com>
>> Cc: 43037 <at> debbugs.gnu.org
>>
>> Literally seconds ago I compiled emacs-27, started it up with 'emacs
>-Q' and then visited the blank file '~/new.js'. That error popped up.
>
>I cannot reproduce this with stock Emacs 27.1, but I can reproduce
>with the current emacs-27 branch. The more detailed error message is
>this:
>
>Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for
>‘font-lock-comment-end-skip’ (fallback source eval - js-mode compiled
>with CC Mode 5.34 but loaded with 5.34.1): (error
>"‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode (might
>be a cyclic reference)")
>
>Alan, can you take a look, please?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 14:45:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 43037 <at> debbugs.gnu.org (full text, mbox):
Hello, Eli and AC.
On Fri, Oct 16, 2020 at 13:45:34 +0300, Eli Zaretskii wrote:
> > Date: Fri, 16 Oct 2020 06:14:17 -0400
> > From: AC <achirvasub <at> gmail.com>
> > Cc: 43037 <at> debbugs.gnu.org
> > Literally seconds ago I compiled emacs-27, started it up with 'emacs
> > -Q' and then visited the blank file '~/new.js'. That error popped
> > up.
> I cannot reproduce this with stock Emacs 27.1, but I can reproduce
> with the current emacs-27 branch. The more detailed error message is
> this:
> Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for
> ‘font-lock-comment-end-skip’ (fallback source eval - js-mode
> compiled with CC Mode 5.34 but loaded with 5.34.1): (error
> "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode
> (might be a cyclic reference)")
> Alan, can you take a look, please?
Yes, I think the problem is precisely what the error message said.
js-mode.el was compiled (quite a long time ago) when c-version was still
5.34, but since then c-version has become 5.34.1. So their is a clash
between what js-mode.el was compiled with and the CC Mode current in the
Emacs version.
To resolve this, I think deleting lisp/progmodes/js-mode.elc and
compiling lisp/progmodes/js-mode.el again should sort out the problem.
This problem has happened more than once. I think the solution should
be in the Makefile to add a dependency of js-mode.elc on cc-defs.el.
--
Alan Mackenzie (Nuremberg, Germany).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 15:39:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 43037 <at> debbugs.gnu.org (full text, mbox):
Thank you!
Quick request for clarification:
On October 16, 2020 10:43:53 AM EDT, Alan Mackenzie <acm <at> muc.de> wrote:
>Hello, Eli and AC.
>
>On Fri, Oct 16, 2020 at 13:45:34 +0300, Eli
>Yes, I think the problem is precisely what the error message said.
>js-mode.el was compiled (quite a long time ago) when c-version was
>still
>5.34, but since then c-version has become 5.34.1. So their is a clash
>between what js-mode.el was compiled with and the CC Mode current in
>the
>Emacs version.
>
>To resolve this, I think deleting lisp/progmodes/js-mode.elc and
>compiling lisp/progmodes/js-mode.el again should sort out the problem.
>
Were all instances of 'js-mode' in the above-quoted message meant to be 'js' instead?
I have js.{el,elc} in my clone of the repo, but no js-mode* at all (anywhere in my homedir, for that matter).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 15:46:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 43037 <at> debbugs.gnu.org (full text, mbox):
> Date: Fri, 16 Oct 2020 14:43:53 +0000
> Cc: AC <achirvasub <at> gmail.com>, larsi <at> gnus.org, 43037 <at> debbugs.gnu.org
> From: Alan Mackenzie <acm <at> muc.de>
>
> > Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ for
> > ‘font-lock-comment-end-skip’ (fallback source eval - js-mode
> > compiled with CC Mode 5.34 but loaded with 5.34.1): (error
> > "‘c-font-lock-comment-end-skip’ got no (prior) value in js-mode
> > (might be a cyclic reference)")
>
> > Alan, can you take a look, please?
>
> Yes, I think the problem is precisely what the error message said.
> js-mode.el was compiled (quite a long time ago) when c-version was still
> 5.34, but since then c-version has become 5.34.1. So their is a clash
> between what js-mode.el was compiled with and the CC Mode current in the
> Emacs version.
>
> To resolve this, I think deleting lisp/progmodes/js-mode.elc and
> compiling lisp/progmodes/js-mode.el again should sort out the problem.
You are right.
> This problem has happened more than once. I think the solution should
> be in the Makefile to add a dependency of js-mode.elc on cc-defs.el.
Yes, please. On the emacs-27 branch, please.
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 16:05:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 43037 <at> debbugs.gnu.org (full text, mbox):
Hello, AC.
On Fri, Oct 16, 2020 at 11:38:28 -0400, AC wrote:
> Thank you!
> Quick request for clarification:
> On October 16, 2020 10:43:53 AM EDT, Alan Mackenzie <acm <at> muc.de> wrote:
> >Hello, Eli and AC.
> >On Fri, Oct 16, 2020 at 13:45:34 +0300, Eli
> >Yes, I think the problem is precisely what the error message said.
> >js-mode.el was compiled (quite a long time ago) when c-version was
> >still
> >5.34, but since then c-version has become 5.34.1. So their is a clash
> >between what js-mode.el was compiled with and the CC Mode current in
> >the
> >Emacs version.
> >To resolve this, I think deleting lisp/progmodes/js-mode.elc and
> >compiling lisp/progmodes/js-mode.el again should sort out the problem.
> Were all instances of 'js-mode' in the above-quoted message meant to be 'js' instead?
Apologies. js-mode should indeed have been js, as in js.el and js.elc.
> I have js.{el,elc} in my clone of the repo, but no js-mode* at all (anywhere in my homedir, for that matter).
--
Alan Mackenzie (Nuremberg, Germany).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 16:09:01 GMT)
Full text and
rfc822 format available.
Message #34 received at 43037 <at> debbugs.gnu.org (full text, mbox):
On October 16, 2020 12:04:06 PM EDT, Alan Mackenzie <acm <at> muc.de> wrote:
>
>> Were all instances of 'js-mode' in the above-quoted message meant to
>be 'js' instead?
>
>Apologies. js-mode should indeed have been js, as in js.el and js.elc.
>
Thank you!
I can confirm your suggestion works fine: simply touching lisp/progmodes/js.el to change its timestamp induced the build system to recompile it, and now the error's gone.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#43037
; Package
emacs
.
(Fri, 16 Oct 2020 16:34:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 43037 <at> debbugs.gnu.org (full text, mbox):
Hello, Eli.
On Fri, Oct 16, 2020 at 18:45:43 +0300, Eli Zaretskii wrote:
> > Date: Fri, 16 Oct 2020 14:43:53 +0000
> > Cc: AC <achirvasub <at> gmail.com>, larsi <at> gnus.org, 43037 <at> debbugs.gnu.org
> > From: Alan Mackenzie <acm <at> muc.de>
[ .... ]
> > To resolve this, I think deleting lisp/progmodes/js-mode.elc and
> > compiling lisp/progmodes/js-mode.el again should sort out the problem.
> You are right.
> > This problem has happened more than once. I think the solution should
> > be in the Makefile to add a dependency of js-mode.elc on cc-defs.el.
> Yes, please. On the emacs-27 branch, please.
DONE.
> Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
Reply sent
to
Alan Mackenzie <acm <at> muc.de>
:
You have taken responsibility.
(Fri, 16 Oct 2020 20:05:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
AC <achirvasub <at> gmail.com>
:
bug acknowledged by developer.
(Fri, 16 Oct 2020 20:05:01 GMT)
Full text and
rfc822 format available.
Message #42 received at 43037-done <at> debbugs.gnu.org (full text, mbox):
Hello, AC.
On Fri, Oct 16, 2020 at 12:08:28 -0400, AC wrote:
> On October 16, 2020 12:04:06 PM EDT, Alan Mackenzie <acm <at> muc.de> wrote:
> >> Were all instances of 'js-mode' in the above-quoted message meant
> >> to be 'js' instead?
> >Apologies. js-mode should indeed have been js, as in js.el and js.elc.
> Thank you!
> I can confirm your suggestion works fine: simply touching
> lisp/progmodes/js.el to change its timestamp induced the build system
> to recompile it, and now the error's gone.
That's great! I've put the amendment into the emacs-27 branch
Makefile.in, as discussed with Eli, so I'm closing the bug with this
post.
--
Alan Mackenzie (Nuremberg, Germany).
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 14 Nov 2020 12:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 42 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.