Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(require 'swank-clojure-autoload) after swank-clojure-jar-path has been set #2

Closed
fbreuer opened this issue Jul 12, 2009 · 3 comments
Closed

Comments

@fbreuer
Copy link

fbreuer commented Jul 12, 2009

In clojure-slime-config
(require 'swank-clojure-autoload)
is called before swank-clojure-jar-path is set. This results in the error
"You must specifiy either a swank-clojure-binary or a swank-clojure-jar-path"
if all the used specified was clojure-src-root. Changing the order of (require...) and (setq...) in the definition of clojure-slime-config solves this issue.

@michel-slm
Copy link
Contributor

Consider swank-clojure has now reorganized its files, perhaps rather than modifying clojure-mode to keep track, a better fix is to document that the directory where the swank-clojure .el files are should be added to the load-path before clojure-slime-config is called?

@RickMoynihan
Copy link

Also swank-clojure-autoloads no longer seems to exist in swank-clojure... I get problems saying:

Debugger entered--Lisp error: (file-error "Cannot open load file" "swank-clojure-autoloads")
require(swank-clojure-autoloads)
eval((require (quote swank-clojure-autoloads)))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)

@technomancy
Copy link
Contributor

This is deprecated; swank shouldn't be checked out using elisp any more.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants