Clojurians Log v2

Great, I'll add these too 🙂

@seancorfield just added the missing commands. Please notice that I'm not removing the old commands so far, so if you find any problem ping me (and use the old code) so I can fix it

Are there other Atom plugins or settings people find useful in conjunction with Chlorine?

I use lisp-paredit and parinfer.

When I paste with parinfer on, the pasted test is placed inside the previous form in the file, regardless of the cursor position. Is that just how it works, or is there some setting which controls this?

@dave.dixon That's because parinfer adjusts the structure to match the indentation (of the code being pasted in). So, "that [is] just how it works". You could also turn parinfer off temporarily when pasting -- but then you potentially lose structural integrity of the code.

Thanks. Just a minor difference from how it worked in Cursive.

Yeah, I don't think there's a single "right" choice here, because of the inherent tension between indentation and structure that parinfer usage implies.

With parinfer, sometimes I just toggle for "parens mode" and paste my code, so I don't loose integrity and my code is auto-indented

I think it's the best of both worlds

Nice, great tip!

Just published a new version now 🙂. I just found that, for some reason, exceptions are being duplicated on the console, and I have no idea why I'm not experimenting this behavior on my local development. Anywway, I'll fix it too 🙂

Updating to 0.2.0

https://github.com/mauricioszabo/atom-chlorine/blob/master/docs/extending.md is the URL of the extending doc now BTW

Oh, and it's JS not CoffeeScript 😞

For some reason, my init script is JS, not CoffeeScript. But I just saw here on a blank-slate Atom that the default init script is, indeed, CoffeeScript, so I'll update this documentation to use Coffee

(otherwise people can be really confused...)

My atom-chlorine-setup init.coffee file has been updated for Chlorine 0.2.0 and everything seems to work! Thank you @mauricio.szabo!

https://github.com/seancorfield/atom-chlorine-setup/blob/master/init.coffee#L50-L69

Great! Glad to see that everything is working fine!

Much nicer code too.

I'm just about to push a change to make pkg clearer (`chlorine = pkg.mainModule` and then chlorine.ext...) but it's functionally the same.

(`package` is a reserved word in CS I discovered!)

Removed compliment from my dev dependencies and the new autocomplete all seems really good so kudos there too!

Great! I'll just ask to be cautious with the name chlorine as a var. As I was testing these extension points, I found out that if I define a chlorine variable on the devtools while I'm developing the package, it conflicts with goog.global.chlorine and things break in a bizarre way 😄

This is not a problem with production builds, so maybe we can keep it on the init.coffee file 🙂

Ah, interesting. I nearly used an abbreviation for it. Perhaps I'll update it to do that.

Changed to Cl (the element symbol). Although I wonder if CoffeeScript avoids the potential breakage?

I think it does. Indeed, probably on init script it also avoids the breakage even in Javascript because it doesn't allow you to create global variables. It's just in the devtools that these problems occur