clojure-lsp Released clojure-lsp https://github.com/clojure-lsp/clojure-lsp/releases/tag/2024.08.03-15.28.27 with housekeeping and minor improvements!
• General
◦ Bump clj-kondo to 2024.08.01 fixing high memory usage issue.
◦ Bump Clojure to 1.11.3
◦ Fix use of :filename-pattern from kondo breaking references.
◦ Add api.dump to the pod namespace so it can be used with babashka.
• Editor
◦ Add clojure.test/deftest option to resolve macro as code action. https://github.com/clojure-lsp/clojure-lsp/issues/1850
◦ Allow starting clojure-lsp without a project root but with limited features. https://github.com/clojure-lsp/clojure-lsp/issues/1815
◦ Add code action "Add require" for namespaced keywords. https://github.com/clojure-lsp/clojure-lsp/pull/1793
brew install clojure-lsp/brew/clojure-lsp-native
clojure-lsp-native 2024.04.22-11.50.26 is already installed but outdated (so it will be upgraded).
==> Fetching clojure-lsp/brew/clojure-lsp-native
==> Downloading
==> Downloading from
###################################################################################################################################################################################################### 100.0%
Error: clojure-lsp-native: SHA256 mismatch
Expected: fc9734132bdc1cc54af9d7272ce0468a9fd2340f09f75d77ca54b2050b8b3d67
Actual: bed83cbbc902cfd554a467da13acc37e4ec963827b212d45d0c8a05187d4191d Am I doing something wrong or installing/updating from brew is not working currently?
there were some complications as mentioned https://clojurians.slack.com/archives/CBE668G4R/p1722869941319609, I'm releasing a new version
Ok, thank you!
it should be fixed on latest release
It worked, thank you!
Hi guys, i've got a (probably) beginner question. I'm trying to get the clojure-lsp to include the clojure.core source code so that i can use the goto definition functionality on them. So i figured out that the core library sits in a .jar file and https://clojure-lsp.io/settings/#source-paths-discovery states that .jar files are ignored by default which makes sense but how do i set the lsp to inclure the clojure core jar file?
Between :dependency-scheme, :source-paths, :source-aliases and more my brain is turning into mush and having never worked with java i'm out of my depth. Does anybody have any pointers?
@wilcov just adding clojure to deps.edn and restarting clojure-lsp should do the trick
I'm working on the Exercism bob exercise which has the following lines in it's project.clj
(defproject bob "0.1.0-SNAPSHOT"
:description "bob exercise."
:url ""
:dependencies [[org.clojure/clojure "1.10.0"]])
and
{:aliases {:test {:extra-paths ["test"]
:extra-deps {io.github.cognitect-labs/test-runner
{:git/url ""
:sha "705ad25bbf0228b1c38d0244a36001c2987d7337"}}
:main-opts ["-m" "cognitect.test-runner"]
:exec-fn cognitect.test-runner.api/test}}}
in it's deps.edn
The settings page of clojure-lsp states that Note that it's possible to have more than one project type at the same time e.g. deps + babashka, clojure-lsp will merge the classpath and everything should work fine.
So presumably it should work?
When i try the goto definition on a function that i defined in the same .clj file it works, but when i try in on a core function i get an error (in neovim) that the index is out of range .
Perhaps it's good to know that the documentation of the function is being loaded properly (so i can see it's signature with the hover functionality)
Also, i'm using neovim 0.10.0 with conjure.
As a final note, when i start a lein repl in my terminal and try i.e. (source re-find) the source code of the re-find function does get shown, but perhaps that's compeletely unrelatednormally it should work, but I don't know anything about neovim
perhaps @ericdallo
or @rahul080327
@wilcov by any chance have you disabled the zipplugin in nvim?
Maybe as part of neovim startup? To reduce boot time
I'm using LazyVim which does disable the zipPlugin in it's example config, so that might be it, i'd have to check my own configs if it's actually disabled
Yeah it’s most likely that. Should work when you change it
That actually fixed it! Thanks to you both for your help
aaaah thanks @rahul080327!