From: Alan Mackenzie <acm@muc.de>
To: AC <achirvasub@gmail.com>
Cc: 43037@debbugs.gnu.org, larsi@gnus.org
Subject: bug#43037: Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’
Date: Fri, 16 Oct 2020 16:04:06 +0000 [thread overview]
Message-ID: <20201016160406.GB7085@ACM> (raw)
In-Reply-To: <AF72E40C-D208-47B8-B112-C1252CD662AE@gmail.com>
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@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).
next prev parent reply other threads:[~2020-10-16 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 12:37 bug#43037: Eval error in the ‘c-lang-defvar’ or ‘c-lang-setvar’ AC
2020-10-16 8:29 ` Lars Ingebrigtsen
2020-10-16 10:14 ` AC
2020-10-16 10:45 ` Eli Zaretskii
2020-10-16 13:35 ` AC
2020-10-16 14:43 ` Alan Mackenzie
2020-10-16 15:38 ` AC
2020-10-16 16:04 ` Alan Mackenzie [this message]
2020-10-16 16:08 ` AC
2020-10-16 20:04 ` Alan Mackenzie
2020-10-16 15:45 ` Eli Zaretskii
2020-10-16 16:32 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201016160406.GB7085@ACM \
--to=acm@muc.de \
--cc=43037@debbugs.gnu.org \
--cc=achirvasub@gmail.com \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.