Clojurians Log v2

I just installed clojure with scoop. Anyone know how I add it to my emacs exec-path? I've tried the sccop/modules/ directory which contains the ClojureTools powershell script and jar. I'm not knowledgeable of powershell.

@jjttjj It's at C:\Users\<account>\scoop\apps for me

(at least, clojure is -- not sure where clj ended up?)

is it correct that you want to be using clojure and not clj for emacs anyway?

yup

tnx

i thought clj was some powershell-specific thing and not an executable on windows -- i'll take a look

i don't see an exe for clojure either -- doing powershell -command clojure seems to work, fwiw

isn't it a clojure.cmd thingie that scoop produces?

There's a shims folder too on my PATH -- but I am fuzzy as to how cmd and PS map a command name to a filename...

i see a cmd-clojure.exe in the shims folder

(I start my REPL tooling explicitly and use a Socket REPL so the whole CIDER/jack-in thing isn't applicable to my workflow)

spartan workflow ftw

(reference to a podcast with Stuart Halloway)

lol, i do something similar but don't find it spartan 🙂

well, at least you avoid the fighting with tooling, which is kind of the point of it

Yeah, I want an editor setup that works with local and remote processes identically, therefore requires "no dependencies" and the bare minimum over-the-wire machinery.

Someone asked why babashka didn't show a REPL, but did have a socket repl server. The reason is, personally I don't type a lot in console REPLS

(sorry off topic)

what does it mean to not show a REPL?

when you type clj, you get a REPL in the console

ah that, tnx

Atom's Chlorine has a readonly panel where it displays results -- but there's no "input": you cannot type into Chlorine's REPL. I like that because it encourages a "better" workflow (or at least discourages/prevents a "bad" workflow).

if one had support for a repl like this, could the socket part be something that could be an external program that just forwards between bb and something else?

Btw, I just bought Parallels Desktop, it was a Black Friday deal, so I can now properly run Windows on my Mac again. VirtualBox was crashing my Mac so hard, it wasn't possible for me for a while.

dunno

I guess most of the code can be reused somehow

just thinking one could drop the built in socket repl to simplify the code living in bb

just like clojure itself does it

although i guess there would be a problem of getting an external tool to work on multiple platforms

ah, looking forward to more windows testing? 😉

The code in babashka.impl.socket_repl contains both code for the socket REPL (start-repl!) and the REPL code that you would also use for the console REPL (repl)

it's just mirroring what clojure itself does, only it was made a little more graalvm-friendly

don't want to miss out on all the fun

ha ha ha

I didn't understand the recent posts on a .dll. Wasn't this problem solved with 19.3.0 ?

this one: https://github.com/oracle/graal/issues/1762#issuecomment-560527509

or was this only about JDK 11?

guys, I added very recently cmd-clojure and cmd-clj if shims are required, for example to be able to run from cmd.exe

I see @sogaiu already figured that out 🙂

thanks for adding them 🙂

Ah, this was what I needed for emacs, thanks!

Thanks for your work on scoop-clojure stuff too. I set up dev environments on both windows and linux recently, and for the first time windows was easier! It was always considerably harder in the past. This is my first time using scoop and it seems pretty great