This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-29
Channels
- # announcements (2)
- # babashka (18)
- # beginners (42)
- # calva (56)
- # chlorine-clover (35)
- # clara (9)
- # clj-http (1)
- # clj-kondo (19)
- # cljs-dev (8)
- # clojure (14)
- # clojure-europe (23)
- # clojure-france (7)
- # clojure-norway (6)
- # clojure-uk (3)
- # clojurescript (37)
- # community-development (3)
- # cursive (29)
- # datomic (3)
- # emacs (10)
- # events (2)
- # fulcro (77)
- # hyperfiddle (2)
- # introduce-yourself (4)
- # joker (1)
- # lsp (40)
- # malli (52)
- # meander (7)
- # missionary (16)
- # off-topic (3)
- # pedestal (1)
- # re-frame (5)
- # reitit (38)
- # releases (1)
- # shadow-cljs (4)
- # tools-build (18)
- # tools-deps (1)
- # xtdb (8)
How can I control which aliases are set for clojure-lsp
? I am seeing an error when I open .clj
file in my project:
Maybe .source-alises
does the job? https://clojure-lsp.io/settings/#all-settings
Actually, doesn’t seem like setting it in ~/.lsp/config.edn
works either, still fails with the same error
Does it say that it is using the alias in the error message, or does it stay exactly the same?
So if you run that command in the vscode terminal with and without the deps
alias, you get different results? I thought -Spath
only calculated the classpath…
@U0ETXRFEW running that command without deps
alias in terminal also fails
something like this should work:
.lsp/config.edn
{:source-aliases #{"deps" "dev" "test"}
:project-specs [{:project-path "deps.edn"
:classpath-cmd ["clojure" "-A:deps:dev:test" "-Spath"]}]}
@UKFSJSM38 yeah, just tried it, it’s working! Thanks!
nice, I want to make project-specs
consider source-aliases
automatically in the future, but it seems to couple a little bit the settings
Hello everyone, Anyone else having issues with highlighting and warnings in calva? It seems it won't run correctly when editing and saving a file. In some cases it works again though.
Looks like clojure-lsp semantic tokens are not being applied properly. Try disabling that to see if that could be the issue. https://clojure-lsp.io/settings/ (`:semantic-tokens?`)
I've added a file; '.lsp/config.edn' with {:semantic-tokens? false}
restarted vscode and now the highlighting seems to be working correct, but the red/orange wavy underlines are slow to update and/or shown incorrectly.
FYI: Highlighting is now not using semantic tokens. Those are pretty great to have enabled. They break for me sometimes as well, but not often enough for me to disable them. Maybe there is some clue there with the linting messages being slow/inaccurate as well. Consider filing an issue on clojure-lsp.
I have little understanding of how this all works. I decided to install an older version of calva which fixed it for me. Will try to update to the latest in the future see if the problem is fixed by then, if not I will stick with this older version. Thanks anyways
For those interested: up to v2.0.205 it works fine for me from v2.0.206 it starts acting weird
FYI, at 206 https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.206 we started to use latest clojure-lsp by default, rather than a hardcoded version. So what you are toggling there is rather some ancient version of clojure-lsp vs the latest release. You can, if you like, upgrade to latest Calva and pin the clojure-lsp version in via Calva settings.
At 206 the red wavy line is shown incorrectly/not updating when i move code around or when fixing the issue.
I set the clojure-lsp version to 2021.07.12-12.30.59, it now works fine with latest version of Calva! thanks :)
Do you know what this could be about, @UKFSJSM38?
I think this was a issue I fixed on master already regarding custom-async-lint?
Setting, could you try the master clojure-lsp?
Just clone the repo and run make
anyone seen this one earlier it is on a fresh install of calva with a cloned re-frame project
We should try get a better error message there. @UKFSJSM38 how about including the underlying error? Not sure what it would have been in this case, but maybe something like command not found: npx
which would guide the user better, I think.
I thought we were alreadying including, but it looks we aren't, I'll make the changes for that
Made a commit on clojure-lsp master improving that behavior @U0ETXRFEW, it should print the cause on that popup now
I want to say huge thanks! to all Calva reviewers. Today we received our 54th review and 54th five-star review. ❤️ 🙏 That makes Calva rank #3 on the marketplace, programming languages by rating. https://marketplace.visualstudio.com/search?target=VSCode&category=Programming%20Languages&sortBy=Rating