@kenny: you don't really connect to boot cljs repl. You connect to boot's clj repl and then run (adzerk.boot-cljs-repl/start-repl) from there and it switches the current repl to talk to the browser.

(things defined/refered from build.boot are visible from boot.user namespace boot cljs repl starts in, so you can define a convenience function that calls that and/or refer that var)

Minor annoyance: I keep getting a reflection warning for printStackTrace whenever I print a stacktrace

It would also be ideal if, when cursor is positioned at the end of a hyphenated name-like-this, Cntl Backspace removed the whole thing in one go. Similar to the turtling issue (now fixed but only with key re-binding).

@rauh: why not just use the pst function?

https://clojuredocs.org/clojure.repl/pst

@cjmurphy: do you get a message when there is a new version of cursive ?

@roelof I get nagged about new versions of IDEA. I'm not exactly sure what happens with plugins. I'm still on 14.1.5 of IDEA.

oke, I work on 15.0.1

I ask because you said that one of these days a new version of cursive will come out and I hope my template problem is solved

@alexmiller: It's when I use Cursive's own Print last exception function that I get the reflection warning.

I did once try to get a REPL from within Cursive but gave up after an out of memory error. I can get a lein repl going from a windows console easily enough. On my 'to do list' is to have a REPL that comes up and is already in a particular namespace (where I do the 4 Clojure Koans). Items in my 'to do list' are sometimes represented as SO questions: http://stackoverflow.com/questions/33982533/clojure-boot-repl-in-a-particular-namespace

@rauh: gotcha, thx!

@jaen: I run cljs-repl and then boot repl -c and (start-repl) in the REPL. When I open the REPL pane in IntelliJ it is still Clojure. I can tell this by executing (+ 1 "1"). This would work in cljs and show a warning but in Clojure I just get a ClassCastException.

Hm, interesting, I'll have to re-check, but I'm pretty sure Cursive was smart enough to change to cljs repl automatically

Is there some sort of configuration setting I need to set?

None that I know of

It Just Worked™ for me

Where are you running boot repl?

(deftask dev []

  (comp
    (watch)
    ...
    (bcr/cljs-repl)
    (bc/cljs ...)
    ...)

(defn cljs-repl! []
  (bcr/start-repl))

Are the relevant parts of my build.boot

Then I just boot dev from a terminal.

@roelof: I think IntelliJ checks in the backgrounds for updates to plugins

And I have a remote REPL type run config added

With Use Leiningen nREPL port selected

I run that

It connects to the boot running in console

I type (cljs-repl!) there

And it just works

Cursive recognizes it as a cljs REPL type automagically.

Just make sure it does connect

And you have a browser tab open on your cljs application

Clojure 1.7.0
(cljs-repl!)
<< started Weasel server on ws://127.0.0.1:37381 >>
<< waiting for client to connect ... Connection is ws://localhost:37381
Writing boot_cljs_repl.cljs...
 connected! >>
To quit, type: :cljs/quit
=> nil

Is how the Cursive REPL pane should look after connecting.

You run the remote REPL first?

If I run it first I just get

Error connecting to 127.0.0.1:37478 - class java.net.ConnectException: Connection refused

Yes, I run it first.

Hm, interesting.

Nothing is running - no boot repl, or cljs build.

One thing off the top of my head that might cause it is you have a wrong .nrepl-port file generated.

Are you sure you are running only one REPL server?

Errors like those happened to me if I ran something that overwrote the file

Currently only java process is IntelliJ

Hm, interesting. Can you pastebin your build.boot and printscreen your run configurations?

I'm 100% positive this should work.

build.boot http://pastebin.com/g0pfqBtH

Run configs: http://imgur.com/MrsH16j

I can do this: boot dev, boot repl -c, (cljs-repl) and I get a cljs-repl in the console but not in the REPL pane.

Hm, honestly stumped, this looks good : |

Another thing I remembered about such errors.

Are you 100% positively sure you are running the same project in Intellij and in the terminal?

Yes. I am using the terminal inside IntelliJ

Hmpfh. Can you try a normal terminal just to be sure?

Sure

I've never tried the one inside Intellij, so not sure if that may influence something.

What URL do I connect to in the browser? When running boot dev it does not serve my project.

Ah, right, then do copy over your serve task into the comp.

I glossed over that, sorry.

Stuck at:

started Weasel server on  >>
<< waiting for client to connect ... Connection is 
Writing boot_cljs_repl.cljs...

Try reloading the tab

That usually helps if it doesn't connect right away

I can get the cljs repl in the console but it just wont connect in the REPL panel.

Well, I suppose that's something to bring up in #C053K90BR; what I described always worked for me with boot+Cursive.

I think boot hanging at Writing boot_cljs_repl.cljs... meant something, but can't remember what it was.

Here is a screencast of what is happening: https://youtu.be/5rA_wP7PZEI

@kenny: but it looks like it's working

What's the problem?

It is not a cljs repl in the cursive REPL panel.

Ah

But you're not doing

(start-repl) in Cursive REPL pane as well

Only in the terminal

Righttt

Yeah that did it. Thank you! There should be better documentation on that

Hah, I suppose there could be. I don't remember it being that much of a problem to get it working for me, but I agree you have to figure it out looking at a few separate things, which is less than ideal.

@kenny: by the by, I suggest you add

[org.clojure/clojure "1.7.0" :scope "provided"] ; or whichever version you're using
[org.clojure/clojurescript "1.7.170"]

I remember this might cause some problems

Definitely got rid of some of them

Most of those are from clojurescript compiler; not sure about those that you have left, but it's usually a good idea to be clean of those if possible. I've had some code break due to that once.

Anyway, glad the issue with REPL is solved.

Same! They are all warnings and I haven't had a problem with them yet. Probably worth investing some time to figure them out though.