This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-02
Channels
- # announcements (11)
- # aws (2)
- # babashka (42)
- # beginners (26)
- # calva (17)
- # cider (1)
- # clara (2)
- # clj-kondo (44)
- # clojars (30)
- # clojure (43)
- # clojure-australia (6)
- # clojure-europe (29)
- # clojure-gamedev (4)
- # clojure-greece (1)
- # clojure-nl (4)
- # clojure-spec (4)
- # clojure-uk (6)
- # clojurescript (28)
- # cursive (16)
- # data-science (1)
- # datahike (4)
- # datomic (26)
- # emacs (6)
- # events (3)
- # fulcro (11)
- # graalvm (7)
- # holy-lambda (118)
- # java (9)
- # jobs (1)
- # leiningen (3)
- # lsp (21)
- # luminus (2)
- # malli (13)
- # membrane-term (1)
- # music (1)
- # nrepl (3)
- # off-topic (38)
- # pedestal (2)
- # polylith (39)
- # re-frame (33)
- # reagent (7)
- # releases (1)
- # remote-jobs (4)
- # rewrite-clj (28)
- # ring (21)
- # sql (2)
- # tools-deps (23)
- # vim (4)
- # xtdb (15)
Here’s a demo of the new hover with Clojuredocs and that To Rich Comment button: https://www.youtube.com/watch?v=a4sm_B_mqhs Please like and subscribe! 🙏
Can you render arbitrary HTML in these blocks, or is it pre-defined?
It’s Markdown. A somewhat limited markdown even. And it sanitizes html. I have tried using details/summary tags there, but it didn’t work.
I knew it was too good to be true...
@mauricio.szabo I'm trying to troubleshoot an apparent issue with Clover 0.2.6 and semantic token coloring (Calva/LSP)...
I think the difference between 0.2.5 (?) and 0.2.6 is that you removed the grammar stuff?
Yes, I removed the grammar file on 0.2.6
What's exactly happening?
With 0.2.6, I lose a lot of syntax coloring -- comments and strings -- and I just installed 0.2.5 and everything is fine.
So something in 0.2.6 is still, somehow, interfering with Calva/LSP and semantic token coloring.
I just copied Calva's grammar file into the Clover 0.2.6 installation and now it all works.
Let me try something - I just published 0.2.7 version removing some config parameters that may conflict with Calva
@mauricio.szabo Removing grammars
from package.json
solved the issue! Thank you!
Wonderful! I don't plan to mess with semantic things for now, but if I do in the future, I'll keep a config option to toggle it 🙂