This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-12
Channels
- # announcements (1)
- # aws (1)
- # babashka (63)
- # beginners (108)
- # calva (12)
- # cider (6)
- # cljdoc (2)
- # cljsrn (33)
- # clojure (150)
- # clojure-europe (28)
- # clojure-nl (13)
- # clojure-spain (1)
- # clojure-spec (8)
- # clojure-uk (25)
- # clojurescript (16)
- # conjure (7)
- # cursive (7)
- # datomic (15)
- # duct (2)
- # eastwood (2)
- # figwheel (1)
- # figwheel-main (1)
- # fulcro (6)
- # graalvm (1)
- # graalvm-mobile (1)
- # helix (6)
- # honeysql (23)
- # integrant (6)
- # introduce-yourself (4)
- # jobs (10)
- # lsp (132)
- # malli (4)
- # meander (1)
- # membrane (1)
- # off-topic (223)
- # pathom (23)
- # pedestal (3)
- # re-frame (18)
- # reagent (13)
- # releases (1)
- # remote-jobs (2)
- # shadow-cljs (68)
- # tools-deps (217)
- # vim (19)
- # xtdb (79)
After updating Neovim (nightly), I noticed an obvious change in the way my Clojure source files are syntax highlighted. This is a shot in the dark, but I think treesitter syntax highlighting for Clojure may be enabled by default now? Very interesting. (I haven't changed anything in my vimrc to enable anything treesitter related.)
My initial impression is that the syntax highlighting provides an overwhelming amount of information now, and I kind of hate it! I'm going to give it some time, though. I think I might just be too accustomed to the sparse syntax highlighting that I've had for years, and the change is a bit jarring.
It's also possible that I'm just very used to my color scheme, and now everything is a different color than what I'm used to.
Clojure lsp now provides semantic information, which I know coc.nvim picks up and uses. I don't know about other lsp plug-ins or methods
@dave definitely not enabled by default, there's extra steps. Maybe you got runtime file updates?
If you do use coc.nvim and you want to disable this, look at :help CocSem
which will lead you to let g:coc_default_semantic_highlight_groups = 0
in your .vimrc or init.vim
i want to like it and hope to use it in the future, but right now I have manually changed some things to better fit my mental model/workflow that the semantic highlighting isn’t doing. for example, i highlight all built-in/core functions in a different color than “normal” functions, and losing that is annoying enough
I like the idea of semantic highlighting. But I'm so used to my existing highlighting at this point, the change is just jarring.
yeah that’s super cool