Clojurians Log v2

@bozhidar Hey. I released #nbb v0.0.82.

nbb nrepl-server :port 1337

$ lein repl :connect 1337
Connecting to nREPL at 127.0.0.1:1337
Could not resolve symbol: nrepl.core/versionniluser=>
nil
user=> (require '["fs" :as fs])
nil
user=> (fs/existsSync "README.md")
false
user=> (js/process.cwd)
"/private/tmp"

But unfortunately it doesn't work with CIDER yet.

Great progress! Thanks for letting me know.

@bozhidar somehow when I cider-connect to the server, I get: It also seems to try System/getProperty which isn't available. Should I try something else?

I can try cider-connect-cljs custom

I guessing that's for the welcome prompt.

Let me check.

Ah, no. That's for the classpath. I guess we should make this conditional or something, as I doubt the classpath makes sense in nodejs.

nbb does have a classpath but it's more like CLJS (without the JVM, let's say self-hosted) than anything else

did lumo support nREPL?

it doesn't seem so but the use case would be similar

(@viesti had you tested your work with CIDER?)

I think I did, made some hacks to please it a bit 🙂

something like this: https://github.com/viesti/nrepl-cljs-sci/commit/f172d5f7898be844d7434b2972cfb063a116cf33#diff-6d49d64b8894e5627407513f159ee5dd92efd3897361dc0a673e567540c27a03

ooooh uuugh ;)

yeah 🙂

trying out different nrepl clients, they spew interesting things at the server 😄

like reply, which is in leinigen, sends the completion functionality on connect

yeah, but it does work after that

yup

just that you get some amount of errors

I think CIDER tries to see what kind of environment it deals with using System

that "lisp expression" probably cause by cider sending stuff to eval which then throws

trench worked pretty well so far btw

and cider not too prepared that something goes wrong

yup, trench more "friendly" to non-java nrepl servers 🙂

don't actually know if there should be (maybe should bad word) a kind of "handshake"

server: "Hi, server here, I'm on JVM" client: "Oh nice, let me check your classpath"

well, nbb has a classpath too, just not the System stuff

and probably also a different API around it

I pushed nbb v0.0.83 with a small fix: noticed (require 'cljs.core) was done which it failed on, this should work now

hmm, crap that particular one doesn't. just a minute

oh wau now just realised that this discussion is on #nrepl channel 😄

well, the topic is nrepl isn't it? ;)

hope bozhidar didn't get angry on the hacks I did 😄

yeah, just typed away

anyway, neat things

I think he is used to greater hack to make nrepl work... is my guess :)

yup 🙂

We can go into a thread however about #nbb and nrepl. 🧵

I don't remember how I checked babashka nrepl server

just had cider connection to it a minute ago, cider seems not to panick with it

We need similar code in CIDER for nbb:

(defun cider--babashka-version ()
  "Retrieve the underlying connection's Babashka version."
  (with-current-buffer (cider-current-repl)
    (when nrepl-versions
      (nrepl-dict-get nrepl-versions "babashka"))))

(defun cider--babashka-nrepl-version ()
  "Retrieve the underlying connection's babashka.nrepl version."
  (with-current-buffer (cider-current-repl)
    (when nrepl-versions
      (nrepl-dict-get nrepl-versions "babashka.nrepl"))))

(defun cider-runtime ()
  "Return the runtime of the nREPl server."
  (cond
   ((cider--clojure-version) 'clojure)
   ((cider--babashka-version) 'babashka)
   (t 'generic)))

Should be relatively simple IMO.

aah, neat!

now I feel dumb not asking this earlier 😄

I found out that evaluation for #nbb works fine in a .clj buffer but just not in a .cljs buffer

Actually both for #calva and CIDER/emacs

To get things rolling, I posted an issue here: https://github.com/clojure-emacs/cider/issues/3061