This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-25
Channels
- # announcements (6)
- # asami (1)
- # babashka (80)
- # beginners (89)
- # bitcoin (1)
- # calva (30)
- # cider (33)
- # clj-kondo (1)
- # cljsrn (45)
- # clojars (5)
- # clojure (60)
- # clojure-australia (1)
- # clojure-dev (9)
- # clojure-europe (133)
- # clojure-italy (7)
- # clojure-nl (6)
- # clojure-uk (44)
- # clojurescript (11)
- # conjure (1)
- # data-oriented-programming (2)
- # datahike (13)
- # datascript (4)
- # datomic (19)
- # deps-new (29)
- # depstar (5)
- # duct (39)
- # fulcro (8)
- # girouette (1)
- # helix (10)
- # honeysql (17)
- # jobs (5)
- # jobs-discuss (2)
- # leiningen (6)
- # lsp (51)
- # malli (60)
- # meander (37)
- # membrane (8)
- # off-topic (31)
- # overtone (3)
- # pathom (36)
- # re-frame (8)
- # reagent (30)
- # remote-jobs (2)
- # sci (1)
- # sql (32)
- # startup-in-a-month (3)
- # testing (3)
- # tools-deps (7)
- # xtdb (7)
Well... had to revert that release for now š . v2.0.176 has the reversion. There's an issue in the released version of the code with the interop between cljs and js that I need to figure out: https://github.com/BetterThanTomorrow/calva/issues/1044
Just noticed I have Looks like it is only relevant to HTML/XML so that's probably why I added it and I guess without it you have to close tags manually, so I guess I'll keep it.Auto Close Tag
extension installed but can't remember why/when -- thoughts? Keep it, nix it?
Masochist!
Hi! I used Calva for about. week now. Worked fine with refactorings, references search and other Clojure features for somedays, but last few days the message āInitializing clojure language features via clojure-lspā is spinning in the bottom bar, and things like references search donāt work. Iāve tried restarting VS code and my mac. Any ideas?
@pez Didnāt touch the extension config system yet, that was a pleasant experience. Unfortunately no luck, tried 2.0.172 and 2.0.173. I have a pretty new mac, how long does it normally take to initialize? 5 minutes now on 172
I should mention that Iām not using a REPL connection. But worked without it earlier.
I think it might be a question where you can get help in the #lsp channel. Iāll be following the discussion and try to be of help if I can.
@ingesol You can try removing the .lsp/sqlite.db
file and re-open your project. Sometimes helps
It would be nice if clojure-lsp
the binary had some --doctor
option which you could execute from the command line to see what it's doing exactly and what the status of things is.
@ericdallo
That would be quite convenient for situations like this, to see if it's in LSP or if it's in the client side (Calva or lsp-mode)
@pez @borkdude Thanks for helping out! It turned out to be a StupidUserException after all, I suddenly remembered that I never actually got my custom clj-kondo hook to work, and it crashed the whole thing silently
Ah, yes. I had also forgotten about that you were experimenting with kondo hooks. We should probably add a troubleshooting section here: https://calva.io/clojure-lsp/
@borkdude it'd be a good feature, but not sure what to check, most things LSP has that could be checked are received when server is initializing
@pez Right, in the troubleshooting section you could put:
rm -rf .lsp/sqlite.db
rm -rf .clj-kondo/.cache
mv .clj-kondo/config.edn .clj-kondo/config.backup.edn
The last line will disable the existing clj-kondo config (and thus all hooks as well), which sometimes can contain mistakes as well
I think clj-kondo prints an error if could not parse the config.edn correctly (hooks errors also?), if we bind the *out* we could probably log that to clojure-lsp log @borkdude?
Right, so that's probably not being caught as clojure-lsp is a process running in background, that's why we log to a custom file, I'll check if we can catch the *err*
and log to the file instead š
Iām happy and proud to be contributing to open source by providing examples of bad input š @borkdude @pez @ericdallo