When you start the REPL, does it show you a select list of aliases you can enable for Calva to use? It seems like you've selected :build but not :fig?

If :fig has :main-opts, you'll want to do something like copy :fig as :fig-main in your deps.edn file, then remove the :main-opts option from :fig. Then you can select :build and :fig in Calva, and use clojure -A:fig-main:build from the command-line.

omg that's exactly it I am still at the stage where I mostly copy and paste build commands from the internet without understanding what they do. I learned something, thank you!

Follow up: how do I evaluate in line after I start Calva? That's why I wanted it do it in the first place

I don't see the command "Load/Evaluate Current File and its Requires/Dependencies"

Hard to say without a bit more information. Is the repl connected at this point? The word REPL should be highlighted in a different color. Your cursor/focus should be in a Clojure file (`.clj`).

Apparently the correct lauch sequence was to check :fig but not :build. Now it works like a charm!

FWIW, I got frustrated in the middle and tried bootstrapping a shadow-cljs project instead of the figwheel and it was much quicker to get setup than figwheel so I might go with that for my next cljs project (a mobile app)

I believe Calva has better support for shadow than figwheel. I personally like the simplicity of figwheel but shadow is definitely way more popular and seems much more actively maintained because of that...

The tutorial I found for clojurescript used figwheel

There are lots of ClojureScript tutorials out there, all different. Some use the older version of Figwheel (before figwheel-main). The older the tutorial, the less likely it is to still work. There have been lots of changes in the cljs ecosystem and tooling over the years 😐

I used this: https://www.learn-clojurescript.com/

This is the bootstrap command:

clj -X:new :template figwheel-main :name learn-cljs/weather :args '["+deps" "--reagent"]'

That is only a couple of years old so it should be pretty up-to-date, so you should be good with that.

Maybe 9500 is the web-serving port that you're meant to visit with a web browser? In that case, the Clojure REPL port will be different. Its number might be different every time you start a REPL, and might be written to a hidden file in the project directory.

Ohh I thought it was the same one. Thanks! I'll go looking for it

I remember being confused about which port was for what. 😃

However, clj should create an nrepl port file and Calva should find it, so you should have the correct port pre-filled in. Are you starting the repl in the right directory?

Yea, it says it couldn’t find the port file

Strange… Is it a project you can share?

VS Code has a code folding feature. It has no API, so we can’t automatically fold or expand the meta data, but you get that chevron thingy.

Too bad that API doesn't exist!

Manually folding each section still works all right for my use case though, thanks 🙂

Hello again! In this thread I learnt that there is an API for the folding: https://clojurians.slack.com/archives/CBE668G4R/p1687640798948849 It doesn’t look like what I was searching for, but that’s probably because the VS Code team are better at designing API:s than I am. The API is in the form of a https://code.visualstudio.com/api/references/vscode-api#FoldingRangeProvider, and I think that Calva already does most of the work for figuring those out, so shouldn’t be too much work to add support. The folding ranges returned can have a type attached: comment and region. I’m thinking that if we use comment for Rich comments (and possibly line comments too) and region for the attribute map of functions. Then you could use the Fold all Regions command to fold those inline tests. It will make me more willing to go back to using inline tests too, because I find them a bit distracting when they are always visible. I say, even though I find myself doing things like this:

(defn ms->minutes
  "NB: Assumes zero is plural"
  {:rcf (comment [(ms->minutes (* 60 1000))
                  (ms->minutes (* 120 1000))
                  (ms->minutes (* 59 1000))])}
  [ms]
  (let [m (quot ms 60000)]
    (apply tr
           (if (= 1 m)
             [:date-time/minute [m]]
             [:date-time/minutes [m]]))))

@U0ETXRFEW https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_foldingRange indeed a folding request in LSP spec which is not supported by clojure-lsp yet, feel free to open an issue so we can discuss what foldings make sense, I feel like we would like to support folding functions and top-level forms, this meta folding could be something more

Cool! Here’s a feature request: https://github.com/clojure-lsp/clojure-lsp/issues/1602

There isn’t. But we could probably add that option.

Okay, thats something 😀 I run the pushd and popd in the pwsh command, but since it always starts in cmd.exe it wont work

Could you make a PS script and just call that from the command?

Could try that

Will let you know if and how that works out

Yeah thats not working out, it stops printing to console. Thing is that leiningen is a batch file so it always starts in cmd

I guess I don’t quite understand the precise problem here. It is also that Jack-in does have its limitations, and starting the repl yourself and connecting it is always an option. That’s what I do in many projects because I like to be able to reload the VS Code window without killing the app I am working with.

good point, I wanted to log the jackin output window due to long log outputs racing by 🙂 thats all

This works 🙂 pwsh -ExecutionPolicy ByPass -NoExit -Command {pushd path\to\project\folder ; lein update-in :dependencies conj '[nrepl,\"1.0.0\"]' -- update-in :plugins conj '[cider/cider-nrepl,\"0.28.5\"]' -- update-in [:repl-options,:nrepl-middleware] conj '["cider.nrepl/cider-middleware"]' -- with-profile +dev repl :headless | Tee-Object -FilePath ".\.pwsh\output.log" ; popd}

If you start the repl in an integrated terminal you’ll have the same convenience for watching the logs. And can be put in a task for even more convenience.

But they cant be logged?

I don’t know what that means. Can you elaborate?

The output window of the terminal inside VSCode isnt logged to file

I see. Maybe it wasn’t clear to me that some terminal outside VS Code is logged to file. 😃 Maybe you can use some equivalent to tee in powershell to log the repl process output to a file?