These are dependent on what tool(s) you are using to build a classpath. Calva will use the appropriate command line arguments to start up these tools on your behalf, look in the relevant file for aliases, and possibly apply additional configuration or run some init code. E.g. For deps.edn (aka tools.deps) based connect sequences, Calva will look for aliases in deps.edn and start a repl with a command built on clojure -M. While for Leinengen based connect sequences, Calva looks for aliases in project.clj and builds a start up command from lein repl. You can also create a https://calva.io/connect-sequences/ with an entry in you VS Code`settings.json`.

This is specifically about connecting to a running repl, iiuc. And, not in project. Hmm, I’ll have to check the code to see why we need to know the type. What’s the language, @UJEK1RGJ0 ? Is it a LISP?

@U0ETXRFEW https://github.com/nooga/let-go

here I just used Generic to connect

I think I'll fork Calva and add support for let-go, it's most similar to Joker I think

Majorily cool! What's the main reason you think a fork is needed? Looks like Calva is handling it pretty well?

oh I just wanted to add file associations and the lang specific stuff to menus like the one I shown, let-go is still pretty nascent so I don't want to pollute the upstream

I think we can add it pretty cleanly. But yeah, start with a fork sounds good.

I'd PR all of this stuff back when let-go matures a bit

There are some recent issues on Calva about the Connect Sequences as API.

Maybe a way to do this is to create the API needed in Calva and then make an extension that depends on Calva. Or if #C03DPCLCV9N is enough, do it that way.

will look into this!

btw I'm having a total blast solving AoC in let-go using calva repl today 😄

That's awesome! 🎉