This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-19
Channels
- # beginners (59)
- # calva (20)
- # cider (25)
- # clj-kondo (12)
- # cljdoc (3)
- # cljsrn (15)
- # clojure (104)
- # clojure-europe (4)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-spec (14)
- # clojure-uk (13)
- # clojurescript (33)
- # code-reviews (26)
- # core-async (1)
- # cursive (5)
- # data-science (3)
- # datomic (8)
- # emacs (3)
- # fulcro (5)
- # graphql (3)
- # hoplon (1)
- # jobs-discuss (4)
- # kaocha (14)
- # nyc (1)
- # off-topic (33)
- # pathom (4)
- # pedestal (2)
- # quil (1)
- # re-frame (5)
- # reagent (10)
- # reitit (6)
- # rewrite-clj (3)
- # shadow-cljs (173)
- # specter (7)
- # sql (4)
- # vim (58)
- # yada (3)
@regen In the next release (coming this week hopefully) I will turn on the cache option by default, unless it's set to false. So a PR to ALE won't be needed anymore
An idea I had is that clj-kondo could emit calls an LSP-server that collects information about defn locations, arities etc, which could then be used for editor tooling.
Is the cache being disabled what's causing ALE to not highlight the *info* messages? I thought it intentionally ignored them?
before clj-kondo would only activate the cache if you said --cache true. ALE didn't pass that option
the info thing: I don't know, but you can tweak the config, so that's not a big issue
ok, I think you might be mixing me up with someone else, as I haven't encountered the ALE cache issue.
@regen oh I see. you only mentioned ALE, but you didn't have that issue. but I still don't think the cache works in vim right now with ale, does it?
I'm discontinuing the snap package. https://github.com/borkdude/clj-kondo/issues/424#issuecomment-522733274