Clojurians Log v2

@cjmurphy in cursive run configuration, do you have nrepl port hardcoded, or "from nrepl file"? generally, shadow starts on new port every time:

just now, restarted 2 times within a minute:

shadow-cljs - nREPL server started on port 55773
shadow-cljs - nREPL server started on port 55785

and when port is hardcoded:

Could not connect to localhost:50892: Connection refused (Connection refused)

I don't known where to find that screenshot.

The nREPL server is always started on:

:nrepl  {:port 9000}

@cjmurphy Can you send a screenshot of your run config?

I’ve received reports of that exception, but I’ve never managed to reproduce it.

Sent you as a PM. There's nothing special about it and it is the same that others use.

Connecting to Shadow's existing nREPL is a revelation to me. Does it really mean my REPL/JVM will never be hosed?? I'll never have to wait for it coming up again. I should have picked up on this a long time ago.

For the UX one possibility would be to do away with local and remote all together. And have more explanation on the Run Configuration page, making it longer than a page. Also if you detect that there's an nrepl server running at 9000 and the REPL is not connecting to it then that's almost certainly a mis-configuration and the user should be alerted. It could be in red writing on that page.

Maybe make each possible situation that the user might want into a sentence and the user chooses one.

So "Full stack with Shadow-cljs" option might have a status of 'waiting for nREPL server to start listening at port 9000'. There would be a place to enter the port number (9000 only being a default).

@michael819 thanks - but I got that already

@cfleming that's it! perfect! best possible answer! In my defence I don't think that existed last time I read the docs.

^FYI @t.denley