This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-19
Channels
- # aleph (3)
- # beginners (90)
- # boot (1)
- # cider (1)
- # cljdoc (23)
- # clojars (1)
- # clojure (91)
- # clojure-dev (8)
- # clojure-greece (1)
- # clojure-italy (17)
- # clojure-japan (1)
- # clojure-nl (6)
- # clojure-spec (4)
- # clojure-uk (89)
- # clojurescript (48)
- # core-async (5)
- # cursive (79)
- # datascript (1)
- # datomic (40)
- # duct (1)
- # emacs (7)
- # figwheel-main (2)
- # graphql (7)
- # jobs (5)
- # nyc (5)
- # off-topic (61)
- # other-languages (2)
- # parinfer (6)
- # re-frame (63)
- # reagent (131)
- # ring-swagger (6)
- # shadow-cljs (158)
- # spacemacs (14)
- # tools-deps (15)
daveliepmann14:07:02
Hi folks, I'm a Paredit user helping to onboard a new-to-Clojure dev who uses Parinfer. One merge conflict we are running into is my use of comment
blocks that have the closing-paren on their own line. (This helps me rapidly navigate the code and evaluate the expression inside the comment
. For example:
(comment
(do-stuff!)
)
Apparently Parinfer sees this as a problem to correct, and automatically changes this to
(comment
(do-stuff!))
Is there a simple way to tell Parinfer to chill out in such scenarios, without breaking Parinfer globally?