parinfer

daveliepmann 2018-07-19T14:18:02.000371Z

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?

dominicm 2018-07-19T14:35:41.000369Z

You can do some stuff like #__ in the tail as a hack

daveliepmann 2018-07-19T14:36:58.000167Z

that's the direction we were looking too 😕

snoe 2018-07-19T14:37:01.000059Z

cursive at least also considers (do-stuff) a top level form (ignores the comment)

👍 1
daveliepmann 2018-07-19T14:54:53.000339Z

OK thanks folks—looks like #__ is the winner

cfleming 2018-07-19T21:22:45.000003Z

@daveliepmann I’m pretty sure CIDER also considers forms inside comment blocks to be top-level for sending to REPL purposes - I added that after someone missed it from Emacs.