This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-23
Channels
- # announcements (3)
- # architecture (10)
- # babashka (37)
- # beginners (69)
- # calva (2)
- # cider (10)
- # clerk (22)
- # clj-kondo (33)
- # cljdoc (44)
- # clojure (45)
- # clojure-conj (4)
- # clojure-denmark (7)
- # clojure-europe (14)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (4)
- # clojurescript (10)
- # clr (19)
- # conjure (1)
- # emacs (28)
- # events (1)
- # fulcro (1)
- # jobs (1)
- # joyride (1)
- # lsp (18)
- # malli (30)
- # membrane (3)
- # off-topic (23)
- # pathom (45)
- # portal (29)
- # proletarian (7)
- # rdf (15)
- # re-frame (21)
- # reagent (2)
- # releases (6)
- # remote-jobs (1)
- # reveal (6)
- # shadow-cljs (36)
- # slack-help (7)
- # sql (5)
- # tools-deps (3)
Maybe I'm having a weird issue, but it seems lsp is not able to complete things that you refer? If I don't use the alias, it doesn't seem to complete it? (with the exception of clojure.core)
Is that your issue? https://github.com/clojure-lsp/clojure-lsp/issues/1440
If so, it's on master/nightly builds already, available on the next release (this week)
Does auto-add-ns-to-new-files?
need to have lsp-mode perform file watching? Cause I don't see any ns being added on new files, so that was my first guess?
that's enabled by default and no, no client extra setting, probably you have misconfigured source-paths
yeah, that explains.
You can check the classpath with lsp-clojure-server-info
as well
ATM yes, we could re-analyze and compute classpath, but would be tricky to not trigger all the time that