That's nice

@benedek Thanks

In the Clojure side of things, which static linter do you prefer? Do you have them all enabled or just one?

@decoursin while not emacsy, I use: lein-cljfmt, lein-how-to-ns, lein-bikeshed

Do you use those integrated within Emacs nonetheless?

Why do you prefer lein-bikeshed over kibit, eastwood, or clojure.typed?

> Do you use those integrated within Emacs nonetheless? (edited) I wrote some code to auto-watch my files and apply the fixes in a fine-grained manner, reusing my main JVM

not easy b/c lein plugins are hardcoded against lein, so I had to copy/paste a bit

> Why do you prefer lein-bikeshed over kibit, eastwood, or clojure.typed? l-b is the one the I use least actually out of my 'stack'. but I use it b/c clojurescript compat

Ah ok thanks!

colleague uses joker a lot for our cljs codebase, well-integrated with emacs apparently

Yeah, I have that setup for CLJS now, it's pretty nice so far!

Based on my survey, Kibit & Eastwood are almost useless integrated within Emacs.

Since they can only run when the source code compiles, they can't actually detect compile errors. (Detecting compile errors can also be done with just a normal stacktrace, but it would be nice to get a red squiggle underneath the errors to quickly find the problem, rather than searching the stacktrace.) Sure they provide some nice static analysis hints and tips, but hardly much that needs to run after every change/save.

As such, cored.typed seems like the only useful linter (of the three) to be integrated within Emacs.

What do you guys think?