Clojurians Log v2

Hi everyone, just introducing myself, new to Slack, Clojure and Chlorine. Well not totally new to Clojure, I've dabbled in it a bit before and am just getting more into it now. Been learning the last couple of weeks from Russ Olsen's book Getting Clojure. Now trying to get a Chlorine setup going after seeing Sean Corfield's video of it on Youtube.

Had some problems getting Chlorine up and running, likely due to my lack of experience so would appreciate any help with that. I've made some posts about it on Clojureverse as Clojurenoob and on the Chlorine GitHub issues as SarmBoJim, hope it's not too much of a hassle that I posted stuff there that likely may not be a bug, I'm not very experienced with GitHub either.

Anyway at the moment my main issue is that I cannot connect to a socket REPL with Chlorine

I get this when trying to connect on Windows 10:

And my project.clj options for Leiningen are as follows:

Any help would be great thanks, I tried opening the port in Windows Firewall but that hasn't worked either.

OK I just figured it out and oh my Lord, am I a dumb dumb, I totally forgot to add with-profile +socket when I was invoking lein repl so that's why it wasn't connecting, kinda figured it out after I ran netstat and saw there was nothing running with port 5555 after invoking lein repl, thanks very much for suffering a fool guys, sorry for wasting your time 😄😅😅

@flyingpython Hi, sorry for the wait (it's morning only now 😄). Don't worry about posting here, or opening an issue and also posting here. Glad to know it did work, any trouble don't hesitate to send a message. It'll also help a lot if you send any problems you're having with Chlorine, maybe I can add more tools or simplify things to help 🙂

Hey @flyingpython Great to see you here -- and really glad you've figured out the problem! Sorry I'd gone to bed early before you arrived last night (Pacific time). I guess there's still the puzzle about why the nREPL connection was misbehaving, but at least the Socket REPL connection is working now.

@seancorfield I know why - I've posted on the issue. It's simply because the "default implementation" of hadling exceptions is to print then to STDERR, then send back a simplified #error object (even stacktraces are omitted). I remember seeing the problem when I tested on the past, but brushed away because it's not the current focus of Chlorine. Will re-visit the problem later 🙂

Oh cool! I haven't checked my email or GitHub yet this morning -- just made a coffee and got to my desk 🙂

And in this case its just because the Orchard auto-complete stuff isn't on the classpath? Could Chlorine be "nicer" about that, or is that the fault of nREPL?

Yes, Chlorine can be nicer (like, capturing the exception on require for example and not trying to require for envioronments that it does not support like ClojureCLR). That's probably what I'll implement in the future 😄

(but to be honest I don't like the fact that nREPL will print exceptions by default... seems like the wrong thing to do - if I want to beautify exceptions, for example, I can't because it was already printed 😞)

This messes up source-map support that I recently added for ClojureScript, for example...

Yeah, there's a lot I don't like about nREPL 😐

I believe that as a protocol, it's quite good to be honest; really simple, stream-based, very similar to what was proposed to prepl, a lot better than UNREPL for example. The problems are some design decisions, the "middleware"-based approach for everything. These are quite confusing and I don't see much value on then

(and the decision to use bencode transport by default, that complicates a little bit when reading strings)

@seancorfield By the way... I think I'll probably revert the decision to use let that automatically resolve promises. It's not playing nice with other functions, unfortunately. I'll probably change it to plet or p/let; in the beginning, it seemed like a good idea but when the codes become more complex, the Promise start to leak to other functions, to threading macros, and so on 😞

No problem. I don't mind being on the bleeding edge 🙃 and it did seem a bit "magical"...

OK thanks guys, I'll let you know if I encounter any further issues 😁

Feel free to DM me if you have any Qs about what's in my videos, or REBL in general if you're using that.

Also "good morning" and "cool snake" -- where are you based?

Ok thanks, I'll be looking at getting REBL working with it next probably

Good morning to you too, am based in New Zealand, the snake was from when I lived in Cambodia about 5 years ago

I'd been fascinated by snakes since I was a kid but there aren't any in NZ so I was so happy to get to touch one that day, that is my happy picture I guess 😄

Cool. I love snakes but my partner is absolutely terrified of them 😞 We were supposed to be visiting NZ in August but, coronavirus, so that's not happening 😞

Def. ping me if you need help with REBL (esp. on Windows! 🙂 )

Ha yeah coronavirus, can't wait till can travel again 😄

Yeah will ping if I need help

I'd read on Google somewhere that REBL wasn't working on Windows but I think it may've been an old post

Oh, I use Atom + Chlorine + REBL all the time on Windows, via Powershell (but I don't use Leiningen).

Ah OK cool, confirmation it works 😄

Although that won't matter if you're using my atom-chlorine-setup files -- since those don't care about Leiningen etc.

OK - I would need to learn CLJ though? That is what you are using to build in place of Leiningen?

I use the Clojure CLI / deps.edn on Windows via the Scoop installer -- and my "dot clojure" repo has aliases to start a Socket REPL Server and to start REBL on Windows.

I just can't remember how to tell Leiningen about a third-party JAR that lives on your local filesystem (which is what REBL is).

(I haven't used Leiningen for years)

OK I will need to look into those things or look into leiningen more

I'll have a look later today

Again thanks for the help and have a great day Sean 😉