This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-05
Channels
- # asami (13)
- # aws (7)
- # babashka (4)
- # beginners (16)
- # biff (7)
- # cljdoc (10)
- # clojure (32)
- # clojure-europe (27)
- # clojure-nl (14)
- # clojure-norway (7)
- # clojure-uk (3)
- # clojurescript (2)
- # conjure (2)
- # core-async (13)
- # datalevin (4)
- # datomic (3)
- # holy-lambda (7)
- # kaocha (3)
- # lsp (23)
- # off-topic (39)
- # pedestal (10)
- # portal (5)
- # practicalli (2)
- # rdf (10)
- # releases (1)
- # shadow-cljs (66)
- # tools-deps (146)
- # uncomplicate (1)
- # xtdb (10)
lsp warns me about unused namespaced keywords in a project while I'm on a certain namespace, which is quite nice.
Is there a way to just see them all? carve
would be a good candidate for that, but either that or clj-kondo itself don't seem to report them.
Emacs yeah
ah nice that's good but I'd just like to run it from the cli
so it can run in CI
ah cool thanks
We use at nubank's CI, it's pretty useful, you could use lein-clojure-lsp as well if using a lein project
does it find more stuff than clj-kondo?
you would still use both I guess?
Yep, there is clj-depend integration + unused-public-var linter, also you could use clojure-lsp clean-ns
and format
cool, we have carve and clj-kondo atm
maybe I can drop carve if this is as configurable
I'll see what it returns anyway
it support all configurations from clj-kondo and all those integrations are pretty configurable as well, LMK if need any help or if there is anything missing on documentation
interestingly redirecting the output of clojure-lsp diagnostics to file I got a file that kind of crashed Emacs
only 251 lines and not very long lines, weird
maybe the color escaping thing
ah all the analyzing project files
also went to stdout