[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Prickliness of the "invalid byte code" stuff
From: |
Richard Stallman |
Subject: |
Re: Prickliness of the "invalid byte code" stuff |
Date: |
Sat, 15 Jun 2019 22:40:45 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > url-http-parse-headers: Invalid byte code in
/home/larsi/src/emacs/trunk/lisp/emacs-lisp/cl-seq.elc [8 times]
> >
> > And it's almost always with this "invalid byte code" stuff.
> >
> > What does it mean, really?
> emacs-lisp/cl-seq.elc was modified after being loaded. You need to
> reload it.
I wonder if we could modify that error message so as to inform users
better about the likely cause.
The code which reports that error could check the date of the file,
determine whether the problem is due to changing the file, and
if so say so clearly.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
- Prickliness of the "invalid byte code" stuff, Lars Ingebrigtsen, 2019/06/15
- Re: Prickliness of the "invalid byte code" stuff, Andreas Schwab, 2019/06/15
- Re: Prickliness of the "invalid byte code" stuff,
Richard Stallman <=
- Re: Prickliness of the "invalid byte code" stuff, T.V Raman, 2019/06/16
- Re: Prickliness of the "invalid byte code" stuff, Stefan Monnier, 2019/06/16
- Re: Prickliness of the "invalid byte code" stuff, T.V Raman, 2019/06/16
- Re: Prickliness of the "invalid byte code" stuff, Stefan Monnier, 2019/06/17
- Re: Prickliness of the "invalid byte code" stuff, Richard Stallman, 2019/06/17
- Re: Prickliness of the "invalid byte code" stuff, Stefan Monnier, 2019/06/17
- Re: Prickliness of the "invalid byte code" stuff, Paul Eggert, 2019/06/17
- Re: Prickliness of the "invalid byte code" stuff, Stefan Monnier, 2019/06/17