This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-08
Channels
- # announcements (42)
- # aws (2)
- # babashka (69)
- # beginners (38)
- # calva (18)
- # cider (39)
- # circleci (1)
- # clj-commons (10)
- # cljs-dev (2)
- # clojure (36)
- # clojure-australia (14)
- # clojure-europe (25)
- # clojure-gamedev (40)
- # clojure-losangeles (4)
- # clojure-nl (5)
- # clojure-sweden (1)
- # clojure-uk (5)
- # clojurescript (133)
- # core-logic (24)
- # cursive (7)
- # datalevin (4)
- # datascript (3)
- # figwheel-main (1)
- # fulcro (45)
- # honeysql (1)
- # integrant (43)
- # introduce-yourself (1)
- # jobs (4)
- # leiningen (3)
- # lsp (32)
- # nextjournal (9)
- # pathom (18)
- # polylith (21)
- # portal (65)
- # re-frame (6)
- # releases (1)
- # remote-jobs (1)
- # reveal (12)
- # rewrite-clj (1)
- # sci (84)
- # tools-deps (22)
I’m having that semantic token highlighting error now. (After a “git stash save -> get rebase master -> git stash pop”). It’s visible in the screenshots in two ways. The db is a local variable, but highlighted as a global definition. :config has funny dual coloring. The second screenshot is from the same file, in another form where the db variable looks OK. The semantic markup looks OK. Still not sure if the issue is with #lsp , VS Code, or Calva’s lsp client setup. CC: @ericdallo
we currently ignore the didChangeWatchedFiles notifications of type change because last time I added support for that it reduced the performance, then I removed and left to fix it later
feel free to create an issue on clojure-lsp side about analysis outdated when changing files outside the editor
I have also seen something that is maybe the same bug when using live share. Sometimes (not sure when) highlighting is broken, and re-joining the live share session then fixes it. I think closing all files and then reopening them fixes it as well, but I’m not 100% sure about that one.
I’m starting to think that parinfer is coming to Calva. https://twitter.com/pappapez/status/1457646855802740737?s=21
Please consider installing the vsix from that PR (in the start of the Twitter thread). I'd especially like to know whether it works as before with the defaults (parinfer off).
Dear Calva friends. I need help testing the Parinfer VSIX. I’d like to know that it won’t cause too much troubles for people not enabling the experimental features, so even if you are not interested in Parinfer, I’d appreciate your help. Here’s the VSIX: https://15890-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.223-pez-253-parinfer-experiments-ad2037dd.vsix And here’s a demo. And here are docs: https://github.com/BetterThanTomorrow/calva/blob/pez/253-parinfer-experiments/docs/site/parinfer.md
I’ve installed it and will use it while working with the experimental features disabled.
1New VSIX. Now autoclosing brackets in Paredit strict mode again. https://15869-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.223-pez-253-parinfer-experiments-81f3ef63.vsix
Release Candidate 2: https://15879-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.223-pez-253-parinfer-experiments-ebe6772d.vsix (TS updated too).
Parinfer is a required feature for me to be happy and this times up well with us testing calva for the engineering team writ large
RC3: https://15890-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.223-pez-253-parinfer-experiments-ad2037dd.vsix Fixing an issue with misplaced cursor after some edits. I think I am doing something wrong since I need this fix, I’ve reached out in #parinfer about it.
