This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-30
Channels
- # announcements (2)
- # babashka (3)
- # beginners (31)
- # biff (3)
- # calva (40)
- # chlorine-clover (2)
- # clerk (5)
- # clj-kondo (10)
- # clojure (13)
- # clojure-art (1)
- # clojure-denver (16)
- # clojure-europe (44)
- # clojure-nl (1)
- # clojure-norway (27)
- # clojure-sweden (3)
- # clojure-uk (1)
- # clojurescript (49)
- # clr (6)
- # community-development (2)
- # datalevin (10)
- # datomic (63)
- # events (2)
- # fulcro (9)
- # holy-lambda (15)
- # honeysql (8)
- # hoplon (6)
- # hyperfiddle (9)
- # introduce-yourself (1)
- # kaocha (1)
- # london-clojurians (2)
- # matrix (1)
- # nbb (7)
- # off-topic (38)
- # polylith (6)
- # re-frame (4)
- # reagent (2)
- # releases (3)
- # sci (13)
- # scittle (5)
- # shadow-cljs (6)
- # sql (5)
- # tools-deps (4)
- # vim (33)
- # web-security (8)
- # xtdb (2)
In VSCode/Linux, I'm getting 'Cannot run program "boot" ... no such file or directory' when Calva starts. If I run "boot show --fake-classpath" from the terminal in VSCode, it runs correctly. Any ideas how to troubleshoot this?
When VSCode opens a Clojure project, Calva runs boot
if there's a build.boot
. I have no idea how it does it. I've been through all of the Calva settings and can't find a path or anything. I launched code
via a bash
shell and all the things are already on the path anyway.
I had no idea Calva did that. Are you sure it isn’t something else that does it? Some other Clojure extension, maybe?
Yeah, but you get some errors when it’s run in VS Code. Was thinking it could fool clojure-lsp…. Could it be different java versions in the shell outside VS Code and the terminal inside it?
Unless the Java LSP server will automagically download a JRE, I don't see how it's possible to have more than one Java.
I'm on a Steam Deck and the only place I can install anything is under $HOME or via Flatpak.
So both Java and code
are manually installed. code
is under ~/bin
and OpenJDK 11 by Scala's coursier
tool and accessed via PATH
.
Same paths inside and outside code
, which makes sense since I launched code
from bash
.
Launching code from bash is otherwise what I advice people to do in situations like this. 😃
Cool that you run Calva on a Steam Deck. I’ll have to borrow my son’s device and try that.
It's a shockingly decent development platform--especially hooked up to an external display+keyboard+mouse.
One just has to be aware that there's no swap by default, so if you run out of RAM, you crash.
Jack-in is a bit of a funny name, which I regret using a bit. But if you start the REPL with boot, and make sure you have nrepl and cider-nrepl running there with the versions that Calva want, then you can connect the Calva to the REPL and things should work fine.
Unless we find a solution for that lsp classpath problem you won’t have all the nice clojure-lsp things, but Calva compensates pretty nicely with what the REPL offers.
> Unless we find a solution for that lsp classpath problem you won’t have all the nice clojure-lsp things Any ideas for how to troubleshoot this? Might Joyride help?