[Top][All Lists]

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

Re: Prickliness of the "invalid byte code" stuff

From: Lars Ingebrigtsen
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Sun, 16 Jun 2019 14:41:52 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Richard Stallman <address@hidden> writes:

> 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.

Yes, that would be nice.

I just did a very simple test: I deleted all the .elc files and then
said `C-x v g' on a file and got the familiar "invalid byte code"
message.  At least in this instance it would be more helpful to say that
the .elc file no longer exists...  or perhaps not backtrace at all, but
just load .el file?

Debugger entered--Lisp error: (error "Invalid byte code in 
  #f(compiled-function (arg1 &rest rest) #<bytecode 0x1563e82520e1>)((>= 
(point) bol))
  (cl-assert (>= (point) bol))
  (let ((bol (point)) (date (vc-call-backend vc-annotate-backend 
'annotate-time)) (inhibit-read-only t)) (cl-assert (>= (point) bol)) 
(put-text-property bol (point) 'invisible 'vc-annotate-annotation) date)
  (setq date (vc-annotate-get-time-set-line-props))

(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

reply via email to

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