run-guile and run-racket error on Emacs launch #2

jaor commented 2016年06月03日 00:32:41 +02:00 (Migrated from gitlab.com)

Created by: fice-t

If I use either run-guile or run-racket (or run-gracket) before loading Geiser, then Emacs flashes white (never seen that before), and then I get one of these messages:

geiser-impl--load-impl: Required feature geiser-guile' was not providedgeiser-impl--load-impl: Required feature geiser-racket' was not provided

The REPL then does not load (and refuses to load afterwards). I noticed that it also tries to load my init file for some reason (nothing of use to Geiser is currently in there).

All of the other Geiser run- variants work fine.

*Created by: fice-t* If I use either `run-guile` or `run-racket` (or `run-gracket`) before loading Geiser, then Emacs flashes white (never seen that before), and then I get one of these messages: `geiser-impl--load-impl: Required feature `geiser-guile' was not provided` `geiser-impl--load-impl: Required feature `geiser-racket' was not provided` The REPL then does not load (and refuses to load afterwards). I noticed that it also tries to load my init file for some reason (nothing of use to Geiser is currently in there). All of the other Geiser `run-` variants work fine.

jaor commented 2016年06月03日 00:52:27 +02:00 (Migrated from gitlab.com)

Created by: fice-t

Here's a backtrace in emacs -Q evaluating (progn (package-initialize) (run-guile)):

 require(geiser-guile "/home/alex/.emacs.d/init.el" t)
 geiser-impl--load-impl(guile)
 mapc(geiser-impl--load-impl (guile racket chicken))
 byte-code("301円302円!210円303円304円\"207円" [geiser-active-implementations provide geiser-repl mapc geiser-impl--load-impl] 3)
 require(geiser-repl)
 byte-code("300円301円302円303円304円$210円305円306円!210円305円307円!207円" [geiser-impl--define "/home/alex/.emacs.d/init.el" guile nil ((binary geiser-guile--binary) (arglist geiser-guile--parameters) (version-command geiser-guile--version) (minimum-version geiser-guile-minimum-version) (repl-startup geiser-guile--startup) (prompt-regexp geiser-guile--prompt-regexp) (debugger-prompt-regexp geiser-guile--debugger-prompt-regexp) (enter-debugger geiser-guile--enter-debugger) (marshall-procedure geiser-guile--geiser-procedure) (find-module geiser-guile--get-module) (enter-command geiser-guile--enter-command) (exit-command geiser-guile--exit-command) (import-command geiser-guile--import-command) (find-symbol-begin geiser-guile--symbol-begin) (display-error geiser-guile--display-error) (external-help guile--manual-look-up) (check-buffer geiser-guile--guess) (keywords geiser-guile--keywords) (case-sensitive geiser-guile-case-sensitive-p)) require geiser-repl geiser-menu] 5)
 (run-guile)
 (progn (package-initialize) (run-guile))
 eval((progn (package-initialize) (run-guile)) nil)
 eval-expression((progn (package-initialize) (run-guile)) nil)
 call-interactively(eval-expression nil nil)
 command-execute(eval-expression)```

I forgot to mention that I'm using the latest MELPA installation.

*Created by: fice-t* Here's a backtrace in `emacs -Q` evaluating `(progn (package-initialize) (run-guile))`: `````` require(geiser-guile "/home/alex/.emacs.d/init.el" t) geiser-impl--load-impl(guile) mapc(geiser-impl--load-impl (guile racket chicken)) byte-code("301円302円!210円303円304円\"207円" [geiser-active-implementations provide geiser-repl mapc geiser-impl--load-impl] 3) require(geiser-repl) byte-code("300円301円302円303円304円$210円305円306円!210円305円307円!207円" [geiser-impl--define "/home/alex/.emacs.d/init.el" guile nil ((binary geiser-guile--binary) (arglist geiser-guile--parameters) (version-command geiser-guile--version) (minimum-version geiser-guile-minimum-version) (repl-startup geiser-guile--startup) (prompt-regexp geiser-guile--prompt-regexp) (debugger-prompt-regexp geiser-guile--debugger-prompt-regexp) (enter-debugger geiser-guile--enter-debugger) (marshall-procedure geiser-guile--geiser-procedure) (find-module geiser-guile--get-module) (enter-command geiser-guile--enter-command) (exit-command geiser-guile--exit-command) (import-command geiser-guile--import-command) (find-symbol-begin geiser-guile--symbol-begin) (display-error geiser-guile--display-error) (external-help guile--manual-look-up) (check-buffer geiser-guile--guess) (keywords geiser-guile--keywords) (case-sensitive geiser-guile-case-sensitive-p)) require geiser-repl geiser-menu] 5) (run-guile) (progn (package-initialize) (run-guile)) eval((progn (package-initialize) (run-guile)) nil) eval-expression((progn (package-initialize) (run-guile)) nil) call-interactively(eval-expression nil nil) command-execute(eval-expression)``` `````` I forgot to mention that I'm using the latest MELPA installation.

jaor commented 2016年06月13日 04:53:39 +02:00 (Migrated from gitlab.com)

Created by: fice-t

For some reason, after updating I can't reproduce this myself. It definitely wasn't working before.

It seems that define-geiser-implementation somehow expanded when load-file-name was set to my init file, which doesn't make much sense. Now it seems to be expanding properly.

If it comes up again then I'll re-open this.

*Created by: fice-t* For some reason, after updating I can't reproduce this myself. It definitely wasn't working before. It seems that `define-geiser-implementation` somehow expanded when `load-file-name` was set to my init file, which doesn't make much sense. Now it seems to be expanding properly. If it comes up again then I'll re-open this.

jaor commented 2016年06月13日 20:06:11 +02:00 (Migrated from gitlab.com)

Created by: fice-t

Ah, I managed to figure out why I couldn't reproduce last night.

When you install Geiser automatically (as part package.el in your init file), it compiles Geiser such that load-file-name is set to your init file. This doesn't happen when you download/update it manually after the init process is over.

Perhaps define-geiser-implementation should take an explicit file name argument rather than relying on load-file-name being a certain value.

*Created by: fice-t* Ah, I managed to figure out why I couldn't reproduce last night. When you install Geiser automatically (as part `package.el` in your init file), it compiles Geiser such that `load-file-name` is set to your init file. This doesn't happen when you download/update it manually after the init process is over. Perhaps `define-geiser-implementation` should take an explicit file name argument rather than relying on `load-file-name` being a certain value.

jaor commented 2016年08月10日 23:11:06 +02:00 (Migrated from gitlab.com)

Created by: fice-t

@jaor What does the first argument of geiser-impl--define really do? I changed it to be always nil and it seems to still work.

*Created by: fice-t* @jaor What does the first argument of `geiser-impl--define` really do? I changed it to be always `nil` and it seems to still work.

danielsz1 commented 2018年07月01日 04:47:46 +02:00 (Migrated from gitlab.com)

Same problem here. Only in my case it expands to "/home/arch/daniel/.cask/cask-cli.el"

Same problem here. Only in my case it expands to `"/home/arch/daniel/.cask/cask-cli.el"`

bigos commented 2019年04月27日 18:02:34 +02:00 (Migrated from gitlab.com)

I guess I had the same error. I use Emacs with modified https://github.com/bbatsov/prelude .
I have fixed it by modifying

~/.emacs.d/modules/prelude-scheme.el

At the top of the file now I have

;;; Code:
(prelude-require-package 'geiser)
(require 'prelude-lisp)
(require 'geiser)
(require 'geiser-racket)

I have added the last line to fix the problem.

I guess I had the same error. I use Emacs with modified https://github.com/bbatsov/prelude . I have fixed it by modifying > ~/.emacs.d/modules/prelude-scheme.el At the top of the file now I have ``` ;;; Code: (prelude-require-package 'geiser) (require 'prelude-lisp) (require 'geiser) (require 'geiser-racket) ``` I have added the last line to fix the problem.

jaor commented 2020年07月20日 06:59:14 +02:00 (Migrated from gitlab.com)

changed the description

changed the description

jaor commented 2020年07月20日 06:59:14 +02:00 (Migrated from gitlab.com)

moved from jaor/geiser#156

moved from jaor/geiser#156