This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-25
Channels
- # announcements (3)
- # asami (63)
- # babashka (5)
- # babashka-sci-dev (32)
- # beginners (56)
- # calva (2)
- # cider (28)
- # clj-commons (9)
- # clj-kondo (16)
- # cljdoc (41)
- # cljs-dev (19)
- # clojure (67)
- # clojure-europe (15)
- # clojure-nl (1)
- # clojure-poland (1)
- # clojure-uk (2)
- # clojurescript (27)
- # community-development (10)
- # data-science (2)
- # datascript (8)
- # datomic (21)
- # events (3)
- # fulcro (54)
- # graalvm (18)
- # introduce-yourself (2)
- # juxt (3)
- # lsp (6)
- # music (1)
- # nextjournal (8)
- # off-topic (44)
- # omni-trace (1)
- # reitit (13)
- # releases (3)
- # rewrite-clj (4)
- # shadow-cljs (10)
- # spacemacs (6)
- # sql (12)
- # tools-build (17)
- # tools-deps (3)
- # web-security (1)
clojure-lsp breaks when you open the clojure-lsp repo in calva 🙂 turns out having a settings.json:
{
"calva.clojureLspPath": "./clojure-lsp"
}
before you make for the first time doesn’t work.
I think it’s fine to have it like this, because anyone working on lsp with calva should probably call follow @pez guide, but we should mention the explosion. It took me a few minutes to figure out what was wrong.
Or does anyone have a better idea of how to “fix” this situation?So changing lsp from calva has a few annoyances, mostly on the calva side. I’ll create a ticket later. the one thing that’s kind of on LSPs side is the output. is there anyway to see the output of println? or do you just use log/debug for everything? I guess I should just connect portal to it for debugging/exploration
yeah, i was hoping we could force that into the repl output, but I should just stop being lazy and embrace the logging + connect portal if it’s to much logging. thank you for the help
😅 1