all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* bug#21821: 25.0.50; invalid byte code in dired-x.elc
@ 2015-11-03 17:53 Daniel McClanahan
  2015-11-04  0:09 ` Glenn Morris
  2015-11-04  8:15 ` Andreas Schwab
  0 siblings, 2 replies; 6+ messages in thread
From: Daniel McClanahan @ 2015-11-03 17:53 UTC (permalink / raw)
  To: 21821

Byte-compiling lisp/dired-x.el generates invalid byte code in
dired-x.elc, which manifests when attempting to use dired-x functions.
Typically I resolve this by opening and manually evaluating
dired-x.el.

To reproduce on emacs -Q built from master:
1. Byte-recompile dired-x.el
2. Open dired-x.elc.
3. Attempt to evaluate the buffer. It should fail at the attempted
evaluation of `dired-x-bind-find-file' with an "invalid byte code"
error.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#21821: 25.0.50; invalid byte code in dired-x.elc
  2015-11-03 17:53 bug#21821: 25.0.50; invalid byte code in dired-x.elc Daniel McClanahan
@ 2015-11-04  0:09 ` Glenn Morris
  2015-11-04  8:15 ` Andreas Schwab
  1 sibling, 0 replies; 6+ messages in thread
From: Glenn Morris @ 2015-11-04  0:09 UTC (permalink / raw)
  To: Daniel McClanahan; +Cc: 21821

Daniel McClanahan wrote:

> Byte-compiling lisp/dired-x.el generates invalid byte code in
> dired-x.elc, which manifests when attempting to use dired-x functions.

I can't reproduce this. You gave no details of platform or anything;
perhaps you need to bootstrap.

> To reproduce on emacs -Q built from master:
> 1. Byte-recompile dired-x.el
> 2. Open dired-x.elc.
> 3. Attempt to evaluate the buffer. It should fail at the attempted
> evaluation of `dired-x-bind-find-file' with an "invalid byte code"
> error.

Did you literally mean what you say, ie visit the .elc file than
evaluate the buffer? I have never thought of doing that with an elc
file, rather than use M-x load-file.






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#21821: 25.0.50; invalid byte code in dired-x.elc
  2015-11-03 17:53 bug#21821: 25.0.50; invalid byte code in dired-x.elc Daniel McClanahan
  2015-11-04  0:09 ` Glenn Morris
@ 2015-11-04  8:15 ` Andreas Schwab
  2015-11-04  9:39   ` Daniel McClanahan
  1 sibling, 1 reply; 6+ messages in thread
From: Andreas Schwab @ 2015-11-04  8:15 UTC (permalink / raw)
  To: Daniel McClanahan; +Cc: 21821

Daniel McClanahan <danieldmcclanahan@gmail.com> writes:

> To reproduce on emacs -Q built from master:
> 1. Byte-recompile dired-x.el
> 2. Open dired-x.elc.
> 3. Attempt to evaluate the buffer.

elc files contain special markers that can only be interpreted correctly
by load.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#21821: 25.0.50; invalid byte code in dired-x.elc
  2015-11-04  8:15 ` Andreas Schwab
@ 2015-11-04  9:39   ` Daniel McClanahan
  2015-11-04 16:16     ` John Wiegley
  0 siblings, 1 reply; 6+ messages in thread
From: Daniel McClanahan @ 2015-11-04  9:39 UTC (permalink / raw)
  To: Andreas Schwab; +Cc: 21821

> elc files contain special markers that can only be interpreted correctly by
> load.

Ok, I wasn't aware of that. I attempted that in the first place because I hit
the same "invalid byte code" error when attempting to use functions defined in
dired-x as they were intended to be used; without evaluating the elc file
manually, within dired, interactively. However, I cannot reproduce those now. I
will update this if I am able to reproduce such an error.

On Wed, Nov 4, 2015 at 2:15 AM, Andreas Schwab <schwab@suse.de> wrote:
> Daniel McClanahan <danieldmcclanahan@gmail.com> writes:
>
>> To reproduce on emacs -Q built from master:
>> 1. Byte-recompile dired-x.el
>> 2. Open dired-x.elc.
>> 3. Attempt to evaluate the buffer.
>
> elc files contain special markers that can only be interpreted correctly
> by load.
>
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#21821: 25.0.50; invalid byte code in dired-x.elc
  2015-11-04  9:39   ` Daniel McClanahan
@ 2015-11-04 16:16     ` John Wiegley
  2015-11-04 17:10       ` Daniel McClanahan
  0 siblings, 1 reply; 6+ messages in thread
From: John Wiegley @ 2015-11-04 16:16 UTC (permalink / raw)
  To: Daniel McClanahan; +Cc: Andreas Schwab, 21821

>>>>> Daniel McClanahan <danieldmcclanahan@gmail.com> writes:

> Ok, I wasn't aware of that. I attempted that in the first place because I
> hit the same "invalid byte code" error when attempting to use functions
> defined in dired-x as they were intended to be used; without evaluating the
> elc file manually, within dired, interactively. However, I cannot reproduce
> those now. I will update this if I am able to reproduce such an error.

Can we close the bug now, and reopen if you find a reproduction?

John





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#21821: 25.0.50; invalid byte code in dired-x.elc
  2015-11-04 16:16     ` John Wiegley
@ 2015-11-04 17:10       ` Daniel McClanahan
  0 siblings, 0 replies; 6+ messages in thread
From: Daniel McClanahan @ 2015-11-04 17:10 UTC (permalink / raw)
  To: John Wiegley; +Cc: Andreas Schwab, 21821

> Can we close the bug now, and reopen if you find a reproduction?

Yes.

On Wed, Nov 4, 2015 at 10:16 AM, John Wiegley <jwiegley@gmail.com> wrote:
>>>>>> Daniel McClanahan <danieldmcclanahan@gmail.com> writes:
>
>> Ok, I wasn't aware of that. I attempted that in the first place because I
>> hit the same "invalid byte code" error when attempting to use functions
>> defined in dired-x as they were intended to be used; without evaluating the
>> elc file manually, within dired, interactively. However, I cannot reproduce
>> those now. I will update this if I am able to reproduce such an error.
>
> Can we close the bug now, and reopen if you find a reproduction?
>
> John





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-11-04 17:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-03 17:53 bug#21821: 25.0.50; invalid byte code in dired-x.elc Daniel McClanahan
2015-11-04  0:09 ` Glenn Morris
2015-11-04  8:15 ` Andreas Schwab
2015-11-04  9:39   ` Daniel McClanahan
2015-11-04 16:16     ` John Wiegley
2015-11-04 17:10       ` Daniel McClanahan

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.