This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-07
Channels
- # announcements (2)
- # bangalore-clj (1)
- # beginners (88)
- # calva (1)
- # cljdoc (1)
- # cljs-dev (1)
- # cljsrn (2)
- # clojure (88)
- # clojure-berlin (2)
- # clojure-europe (2)
- # clojure-india (1)
- # clojure-spec (3)
- # clojure-uk (3)
- # clojurescript (9)
- # clojureverse-ops (4)
- # clojutre (2)
- # cursive (3)
- # data-science (1)
- # emacs (3)
- # fulcro (12)
- # pathom (4)
- # reitit (1)
- # rum (10)
- # shadow-cljs (9)
- # spacemacs (11)
- # sql (7)
- # tools-deps (16)
- # vim (14)
- # xtdb (3)
- # yada (1)
For those using vim-parinfer
, how have you dealt with parinfer’s automatic reformatting of existing files that are not indented in a way that parinfer expects?
An easy example is the clojure-koan
files; in some cases it’s been completely impossible to indent to the desired level of paren nesting.
it's not always doable, depending on the dynamics of your team. some people might find it annoying to have their code reformatted
i usually give the old "i can't help it, parinfer reformats my code automatically ¯\(ツ)/¯" excuse
so far i haven't really run into any resistance on my team. i don't think they care all that much about formatting
one place it can get a little weird is if you open a file where somebody has commented out the final expression in a form, and they wanted it to be easy to comment/uncomment it, so they did something like this:
(...
(foo 1 2 3)
(bar 2 3 4)
;; (baz 3 4 5)
)
(note the trailing paren on its own line)which works fine for parinfer users, but a non-parinfer user will end up with mismatched parens when they uncomment that line