lsp 2026-09-20

Hello! I've got a question regarding clojure-lsp, emacs lsp-mode, bb.edn, and clj-kondo imports. When I add a bb.edn file to a clojure project, it looks like some clj-kondo configs are imported: • babashka/ffi • babashka/fs • hiccup/hiccup • rewrite-clj/rewrite-clj • taoensso/encore Am I observing this behavior accurately? I'm guessing this is to support bb scripts as these libraries are included in babashka.

If you do a bb --print-deps you'll see all of the above included. Except for encore, but I think it is brought in by timbre.

👍 1

Hello! What are the plans for cutting the next release of clojure-lsp? I'd love to get the newer stuff in clj-kondo (in particular, the inclusion of defspec from test.check included back in https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20260724.

Is using the nightly builds an option? That's what I use with Calva.

Yeah, I intend to do one in a week or so, but use a nightly is probably best

Editors have option to use nightly or download from #C032YH7P0R2

Cheers! I generally try to limit the number of non-standard-released-dependencies (frex, I use homebrew to get my clojure-lsp). But I'll take look.

If there were a new release, it'd be good for me too. I have a handful of PRs out there and I didn't want to merge with myself (being lazy) so I'm avoiding doing another one should they be approved.

@john.t.richardson.dev recently I lost my GH notifications, can you tag me again or send me so I can take a look? Só we can release including those

https://github.com/clojure-lsp/clojure-lsp/pull/2379 - prompt for multi-file refactorings (in Calva, at least) https://github.com/clojure-lsp/clojure-lsp/pull/2386 - when using :refer to resolve namespaces, show the count where missing https://github.com/clojure-lsp/clojure-lsp/pull/2417 - code action to replace a namespace with an alias (using :as) https://github.com/clojure-lsp/clojure-lsp/pull/2430 - just some unit tests for code coverage that I had missed earlier

🙏 1

thank you and sorry for the delay, I will take a look at those

It's fine! Thanks!

@john.t.richardson.dev merged 2 and added comments to the other 2

I think these are addressed now

I used your suggestion - swap namespace with alias. But I can change it to something else if you or others come up with a better name