This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-12
Channels
- # beginners (40)
- # boot (2)
- # cider (16)
- # clara (2)
- # cljs-experience (2)
- # clojure (100)
- # clojure-italy (11)
- # clojure-russia (2)
- # clojure-spec (9)
- # clojure-uk (34)
- # clojurescript (36)
- # community-development (3)
- # core-async (4)
- # cursive (4)
- # datascript (1)
- # datomic (20)
- # duct (10)
- # emacs (1)
- # fulcro (2)
- # off-topic (40)
- # onyx (12)
- # overtone (8)
- # portkey (6)
- # quil (1)
- # re-frame (7)
- # ring-swagger (2)
- # shadow-cljs (2)
- # spacemacs (2)
- # test200 (10)
- # tools-deps (16)
- # unrepl (1)
- # vim (24)
https://github.com/clojure-emacs/nREPL/pull/23 looks mostly good, but the ns
styling is somewhat unusual.
It’s more or less a fork of the abandoned slamhound
that’s party of refactor-nrepl
. That’s the type of functionality I think we should have straight in orchard
, btw.
Yeah I largely agree with that, would also kinda like orchard to eat cljfmt and for it to be a lot more opinionated.
been thinking about how to use the clojure.spec specs for core to drive a formatter on and off for a while now
Eg. CIDER’s format specification language is honestly inadequate, as is cljfmt’s, you need something like spec which gives you full parse capabilities.
> Eg. CIDER’s format specification language is honestly inadequate, as is cljfmt’s, you need something like spec which gives you full parse capabilities. Why so? I think cljfmt’s main problem is that it doesn’t do proper parsing, so there’s some potential for false positives. Overall I agree there’s always room for improvement. CIDER format spec and cljfmt improved vastly on the voidness that preceded them. 😄
It’s a pity we never really ported the format spec to cljfmt. I prefer this way more to some global config file.
Oh absolutely 😉 just thinking we now have a full, agreed upon pattern language to hand and leveraging it would lead to some better understanding - eg the ability to specify how you want let binding forms indented no matter what macro they occur in because it’s just the same spec.
So, regarding the dynapath upgrade… did we try a require
to https://github.com/tobias/dynapath/blob/master/src/dynapath/defaults.clj ?