Fork me on GitHub
#cursive
<
2016-04-21
>
cfleming01:04:08

@lsenta: I see, interesting, thanks - I’ll try to fix that as part of the same change.

wasser16:04:58

I have seen some code, especially "legacy code" written before the Parinfer addition, that gets parinfer-ed into something invalid. It bit me mostly with long strings split across multiple lines. Not a bug, but it took me a minute to catch on.

tbrooke20:04:21

I know this has been said before and I believe that it is on “the list” somewhere but Cursive really needs Boot I can generate the lien project.clj with the boot plugin but it is a pain

cfleming22:04:58

@wasser: Actually, if it breaks code it should be a bug, I think. Can you show an example?

cfleming22:04:39

@tbrooke: Yeah, it is on the list but boot support is very difficult due to the nature of boot.

danielcompton22:04:17

My code was broken by parinfer

danielcompton22:04:12

e.g.

"dev-once" ["with-profile" "+dev-run" "do"
                            ["clean"]
                            ["cljsbuild" "once" "dev"]
                            ["shell" "open" ~dev-url]]
"dev-once" ["with-profile" "+dev-run" "do"]
                            ["clean"]
                            ["cljsbuild" "once" "dev"]
                            ["shell" "open" ~dev-url]

danielcompton22:04:52

in project.clj which unbalances the forms

cfleming22:04:25

Was that by toggling the editing style?

cfleming22:04:35

I’ve fixed a bug for the next release where that would not run the initial paren mode, which would cause things to break.

wasser23:04:40

@cfleming Sure. Give me a bit. (I just plowed on, so now I need to go back and find the original formatting…)