cemerick / austin

The ClojureScript browser-REPL rebuilt stronger, faster, easier.
510 stars 31 forks source link

(run) fails with #<SyntaxError: Parse error> from ClojureScript repl #28

Closed aeberts closed 10 years ago

aeberts commented 10 years ago

Hi Chas, I realize that this may be related to the other open clojurescript bug but here's a report anyway.

I get the following when evaluating `(run) from the ClojureScript repl :

nREPL server started on port 62401 on host 127.0.0.1
REPL-y 0.2.1
Clojure 1.5.1
    Docs: (doc function-name-here)
          (find-doc "part-of-name-here")
  Source: (source function-name-here)
 Javadoc: (javadoc java-object-or-class-here)
    Exit: Control+D or (exit) or (quit)
 Results: Stored in vars *1, *2, *3, an exception in *e

user=> (cemerick.austin.repls/exec)
Browser-REPL ready @ http://localhost:62404/8890/repl/start
Type `:cljs/quit` to stop the ClojureScript REPL
nil
cljs.user=> (run)
"Error evaluating:" (run) :as ".run.call(null);\n"
#<SyntaxError: Parse error>
No stacktrace available.
nil
cljs.user=>

my config:

clojure 1.5.1
clojurescript 0.0-2080
lein-cljsbuild 1.0.0
austin 0.1.3
cemerick commented 10 years ago

I'm afraid I can't reproduce. Using the same versions of Austin, Clojure, and ClojureScript, I get a different (more helpful) error:

user=> (cemerick.austin.repls/exec)
Browser-REPL ready @ http://localhost:49857/2615/repl/start
Type `:cljs/quit` to stop the ClojureScript REPL
nil
cljs.user=> (run)
"Error evaluating:" (run) :as "cljs.user.run.call(null);\n"
#<TypeError: 'undefined' is not an object (evaluating 'cljs.user.run.call')>
TypeError: 'undefined' is not an object (evaluating 'cljs.user.run.call')
    at :1
    at :5

What is this run function, anyway?

aeberts commented 10 years ago

I feel so silly. I thought that the (run) function you included in your browser connected repl sample project was actually part of austin. I cloned the austin repo and went through the steps and voila! everything worked like in your explanatory YT video. Sorry for the trouble - problem solved!

cemerick commented 10 years ago

No worries at all, glad you got things worked out. :-)