Fork me on GitHub

paredit or parinfer? what to choose.

Jordan Robinson13:02:25

I like parinfer but it's definitely just a preference thing 🙂


My recommendation is paredit all the way.Clojure is my first lisp and my first functional programming language. Back in '14 when I started playing with Clojure and Cursive, it was an absolute heureka moment when I read the Cursive paredit docs. Paredit made it incredibly easy to work with an otherwise unknown language and I totally miss it from every language where it isn't available. slurp, barf, raise, splice, etc are absolutely essential to my toolbox ever since. It makes you understand the AST of your code while being completely decoupled from how you indent/lay out things.

✔️ 3

Personally I use parinfer, since I can also use the paredit commands when they make sense.


Is there a way to get the clj formatter to suck up the trailing closing parens on their own line? I don't see a paren-affecting setting in the code style settings panel


It should do this by default, do you have a case where that’s not working?


Hmm it's definitely not. On any clojure project/file.


It's possible this is user error as this is a long time cursive install, and I might have broke a setting in the past. Is there an option for this?


Is it possible to define custom resolvers for macros? I'd like to use orchestra's defn-spec without all my code being red and squiggly 😅


do you know that if you press alt+enter on a macro form, Idea will ask you to select what kind of syntax to use for it?


Yes, but this one can't be resolved as any of the existing ones


@U016XBH746B Could you add an issue for that and I’ll look at adding support, since orchestra is pretty popular.