This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-07
Channels
- # announcements (1)
- # babashka (31)
- # beginners (54)
- # biff (3)
- # calva (22)
- # cider (13)
- # circleci (1)
- # clj-kondo (6)
- # cljsrn (2)
- # clojure (113)
- # clojure-europe (58)
- # clojure-mexico (5)
- # clojure-nl (3)
- # clojure-uk (7)
- # clojurescript (81)
- # cursive (20)
- # datomic (33)
- # events (3)
- # fulcro (29)
- # introduce-yourself (1)
- # meander (78)
- # off-topic (60)
- # om-next (2)
- # podcasts-discuss (1)
- # re-frame (8)
- # reagent (5)
- # reitit (20)
- # remote-jobs (1)
- # shadow-cljs (24)
- # spacemacs (10)
- # sql (8)
- # tools-deps (22)
- # xtdb (16)
tbf it's not insane to think that there might be some sort of subscription mechanism in there
Yeah I agree. I wasn’t trying to point out it was an unreasonable expectation but it’s just not the way it works. Each incoming message essentially creates the transport back from where it came
I'm back to clojure after many months away. I can't remember how to do static syntax checking inside cider. I recall there was an emacs package with a funny name. can someone remind me??? I seem to remember turning it off because of too many false errors.
found it. I was looking for clj-kondo
@U010VP3UY9X if you're experiencing too many false errors, let us know at #clj-kondo, we would wanna know how to make it better 🙂 cc @U04V15CAJ
I think Jim’s errors were related to in-ns back then and there is still an issue open for this
Also I make heavy use of macros, and since kondo doesn't evaluate macros, I found it very distracting.
do I remember correctly though that macro usage cannot be conifigured along with the macro definition? It has been a long time since I looked at this.
@U010VP3UY9X Macro config cannot be configured with the macro, but it can be packaged along with the library, so when others use your library, then the config is automatically picked up
this is an insanely awesome feature of clj-kondo, the ability to extend it to lint macro usages correctly (very precisely!) and then distribute that config along with the library that supplies the macro
without that feature it would be distinctly less useful for us