Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2018-07-19

Channels

#parinfer
<
2018-07-19
>
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?

dominicm14:07:41

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

daveliepmann14:07:58

that's the direction we were looking too 😕

snoe14:07:01

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

👍 1
daveliepmann14:07:53

OK thanks folks—looks like #__ is the winner

cfleming21:07:45

@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.