This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-23
Channels
- # announcements (2)
- # beginners (150)
- # calva (59)
- # cider (10)
- # clj-kondo (63)
- # cljs-dev (15)
- # cljsrn (34)
- # clojure (127)
- # clojure-dev (16)
- # clojure-europe (12)
- # clojure-italy (18)
- # clojure-nl (6)
- # clojure-russia (3)
- # clojure-uk (23)
- # clojurescript (18)
- # clojutre (15)
- # clr (2)
- # cursive (3)
- # datomic (26)
- # duct (6)
- # fulcro (9)
- # graalvm (3)
- # joker (9)
- # lambdaisland (1)
- # off-topic (12)
- # om (1)
- # pathom (29)
- # re-frame (16)
- # reagent (2)
- # shadow-cljs (57)
- # slack-help (2)
- # spacemacs (45)
- # sql (20)
- # xtdb (3)
- # yada (3)
Emacs is "deleting orphaned package flycheck-clj-kondo" and I don't know why.
I do have that package listed in dotspacemacs-additional-packages
@jumar this is okay, we have simplified the way you add clj-kondo to Spacemacs https://github.com/syl20bnr/spacemacs/tree/develop/layers/+lang/clojure#enable-clj-kondo-linter
You can remove the previous config for this (in additional packages and user-config)
Hm, for some reason it doesn't work at all. This is the only thing I did:
(clojure :variables
clojure-enable-clj-refactor t
clojure-enable-linters 'clj-kondo)
Apart from that I commented out my earlier configuration for clj-kondo.
In .spacemacs there's still this bit in the custom-set-variables
:
'(package-selected-packages
(quote
(flycheck-clj-kondo
Yes, I added it a long time ago in dotspacemacs-configuration-layers
; but the docs (linked above) don't mention that
@jumar you will need develop
branch from at least the start of September 2019 for this new method of clj-kondo to work
did you restart Spacemac? and is clj-kondo on your system PATH?
Unfortunately, that doesn't seem to help (latest develop). Is there any requirement on the Emacs version (I'm on Mac OS X)?
@jumar I usually try flycheck-compile in a buffer when I try to debug flycheck issues. Maybe that helps. My 2 cts, I know 0 about spacemacs.
@jumar I dropped joker as clj-kondo was more than enough coverage for me. Try comment out the joker code in your .spacemacs
file. They should work together, but if you comment out the joker code then its one less potential place for failure.
@borkdude any special areas in which joker
is still better - some particular types of errors it can detect that clj-kondo cannot?
If its helpful, my current .spacemacs file is at https://gist.github.com/ef3086a61a219e4b4d37b354fcdd32b7
@jumar I have a hard time coming up with any as I'm trying to complete with other linters
@jumar suggest you would get more value with clj-kondo running as a flycheck backend (as the Clojure layer option) and then running eastwood/kibit as a one of process before sharing commits or as part of CD/CI pipeline. Although clj-kondo catches 99.9% of things anyway
Finally sort it out - the final piece was removing clojure-lint
layer which I forgot about (searching only for joker
inside the .spacemacs
file)
I was thinking of adding joker as an option to the clojure-enable-linters
but I am unsure if we need both as @borkdude as added so much to clj-kondo
. I've recommended dropping joker in my Spacemacs book and just use clj-kondo
because its so awesome. Thanks
That wouldn’t be too hard to include in kondo. Maybe there’s already an issue for it.
couldn't find the issue, so created one: https://github.com/borkdude/clj-kondo/issues/472
in the meantime, clj-kondo analysis data and tools can report on unused private vars: https://github.com/borkdude/clj-kondo/tree/master/analysis#private-vars
hey @jr0cket have we thanked you for all your spacemacs guides and help yet? (I’m feeling grateful today)
Always nice to get another thank you. Just updating the linter section today 😁. Lots more updates in the next few weeks