This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-18
Channels
- # beginners (84)
- # boot (21)
- # cider (12)
- # cljs-dev (13)
- # cljsrn (3)
- # clojure (169)
- # clojure-dusseldorf (2)
- # clojure-gamedev (6)
- # clojure-germany (1)
- # clojure-russia (15)
- # clojure-serbia (4)
- # clojure-spec (16)
- # clojure-uk (4)
- # clojurescript (51)
- # core-async (1)
- # datomic (23)
- # emacs (16)
- # figwheel (1)
- # fulcro (60)
- # hoplon (8)
- # lein-figwheel (3)
- # leiningen (1)
- # luminus (4)
- # lumo (43)
- # off-topic (4)
- # re-frame (17)
- # rum (37)
- # shadow-cljs (21)
- # test-check (13)
- # vim (14)
@dominicm I'd take a look at refactor-nrepl. They likely have something like this that you may be able to adapt.
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?
Kibit can be run on piped in code, it's a limitation of squiggly clojure that it does not provide the buffer to kibit
@decoursin I put in a lot of effort getting it to work with https://github.com/SevereOverfl0w/clojure-check/
@decoursin https://github.com/SevereOverfl0w/clojure-check/blob/master/main.go#L121 kibit can take a StringReader as input
Here was my attempt at adding dump-jump-go
to work with right mouse click: https://github.com/decoursin/emacs.d/blob/master/init.el#L337.