Fork me on GitHub
#cursive
<
2021-03-06
>
AJ Jaro12:03:15

Wow! Great! Thanks for the affirmation!! It's not fancy but it does the job

👍 3
raspasov06:03:26

For sure does :)

robert-stuttaford07:03:53

hi @cfleming 😄 finally trying Cursive out in anger. wondering if there's a way to prevent the formatter from indenting map values that begin on the next line? we have a large mature codebase, and this is causing whitespace wars and frustration in our team 😅

;; what I want
{:long-key-over-here
 (let [something :worth-its-own-line]
   something)}

;; what I get
{:long-key-over-here
                     (let [something :worth-its-own-line]
                       something)}

raspasov07:03:41

Settings→Editor→Code Style→Clojure

raspasov07:03:26

Actually… perhaps I don’t have it configured to get what you want, when I have multiple keys in the map; I am not sure 🙂 sorry

raspasov07:03:24

Try under Settings→Editor→Code Style→Clojure-&gt; General remove checkbox “Align map values”

cfleming08:03:46

@U0509NKGK Ugh, no, currently not I’m afraid. I’ve been meaning to fix this for the longest time, I’ll try to get it in the next EAP. As raspasov says, disabling the alignment altogether might fix it too - depends whether you want the alignment for other entries or not.

cfleming09:03:24

@U0509NKGK If you’re still having problems with that or anything else, let me know

mikejcusack12:03:26

I'm confused by this because in my editor I get what you want

mikejcusack12:03:08

Turning off "align map values" indeed works

mikejcusack12:03:09

In general I have Align reader conditional values and One space list indent enabled

robert-stuttaford12:03:24

thanks @U01NYKKE69G - i'm literally in the first couple days, so still exploring!

👍 3
cfleming21:03:06

Yeah, the only case that won’t work at the moment is if you generally want map entries aligned, but don’t want that to happen when there’s a newline between the key and the value. If you don’t want any of them aligned then you’re good to go.