@U0ETXRFEW Is there a way to configure this, maybe in VS Code? The only way I know how to do this off-hand is to modify Calva’s package.json and run it from source in the development host.

@U9A1RLFNV thanks for the tip Will go the development host route for now

What kind of files are you trying to use slurp and barf in? The paredit commands are made to work in Clojure code, but might work on some other lisp-like language.

@U9A1RLFNV hmmm.. I'm going to use it for clojure code too ahem.. ClojureDart to be precise 😅 I just need to enable the same commands for the extension .cljd

Might be something we should do in Calva.

For my purposes, this looks like it would be fine I think being able to change the file extensions Calva works on from the VScode extension settings would be a good thing to have though

It makes me happy (for reasons unclear to me) that you are running the development host, @U0154QR3DC7 😃 You can also change the language association manually via the setting File: Association, or at-will with the command Change Language Mode.

Please file an issue about adding ClojureDart. Then a PR fixing it. 😃

Haha damn I hadn't realized I could just Change Language Mode. That works 😅

Maybe will wait until Clojuredart is public? It's currently under closed beta

We should probably also add *.bb. I notice I have that in my settings, so haven't realized it is lacking from Calva.

I think it is fine to add it even while in closed beta. It will also make it easier for us to get early warnings if we need to update something in our Clojure lexer.

okey

Done • Issue: https://github.com/BetterThanTomorrow/calva/issues/1617 • PR: https://github.com/BetterThanTomorrow/calva/pull/1618 (funny that currently the issue and PR counts are so close to each other)

So awesome. 🙏

Now merged to dev. Note to self (and a little bit to you, @U0154QR3DC7 😃 ) the commit message did not reference the issue with Fixes #1617 syntax so it will not be auto-close by the commit. We'll need to close it manually after release.

ahhh.. I did not know that I needed to have the issue number in the commit message I'm not really familiar with using issue numbers 😅 I assumed mentioning the issue from the PR would partly do it Thanks for letting me know

It was such a small change and since things built and tests passed, I decided to not stress the protocol we are using for PRs. 😃

I think another problem with these extensions is LSP. If I remember correctly LSP asks the client for watches on some extensions, cljd and bb aren’t among them. @UKFSJSM38 should we add those to LSP?

What you mean with "watches on some extensions"?

@UKFSJSM38 When initializing the LSP server we register file watchers on the client with “workspace/didChangeWatchedFiles” which are currently set to “/*.{clj,cljs,cljc,edn}“. If I understand this bit of LSP correctly, it tells the client to tell the server any(only?) changes to those files. So currently LSP would not notice any changes to .bb files, right?

Right

is it common to have .bb files? I was not aware, I thought the recomendation of bb was to have it as .clj

I don’t use it and not sure how common it is, but I’m guessing that at least cljd for ClojureDart is mandatory?

I use it here and there and have seen it in some professional projects I've had access to.

Just an anecdote, but yeah I've seen .bb files in professional projects too

I use it when I write a script that only works in Babashka. I don't quite like to have a .clj file that Clojure can't handle. 😃

Ok, feel free to open a issue or PR adding .bb files