Clojurians Log v2

@mauricio.szabo How close to parity with Chlorine is your VS Code plugin? Does it have the new sci-based cljs configuration/extension stuff?

@seancorfield not yet. I need to figure out how to add these on VSCode. In theory, it should work. The problem is mostly that VSCode does not allow me to add commands "on the fly" - they all have to be defined on package.json file. Calva adds a dropdown menu with "additonal commands", but then you can't use keymaps to evaluate code (as far as I know - still checking if there's a way). It's also not playing nice with Clojure indentation yet 😞.

But... I was able to add docstrings on Autocomplete! 🙂

There's an API that allows Atom to get these informations lazily, so it'll not slow down autocomplete as I was fearing 🙂

That's awesome! Thank you!

Re: Clover/VS Code -- if you figure out how to a) add new commands from the cljs file and b) bind them to keys, I might well switch from Atom to VS Code. There are just enough annoying differences between key bindings on Atom/macOS and Atom/Windows that I'm frustrated when switching between my laptop and my desktop -- VS Code seems better in that small respect.

I think we can find a way for chlorine to use Calva's formatter code, if we think about it together some. Of course you can just copy it, but I think we can do something a bit smarter.

@mauricio.szabo Watching all those commits for 0.7.3 -- looking forward to updating to that version and trying it out! 🙂

Just published! 🙂

Also, I forgot to mention on the README and docs (need to update then) - p/let is now being used to "wait for promises" instead of let

Ah, that explains why nothing works for me 🙂 Will update...

(I hope I did not break anything in the process 😄)

Everything works locally with that change. And getNamespace() works anywhere in the file now -- THANK YOU!

Updated and pushed my atom-chlorine-setup repo.

Wow, great! Now I have lots of thing to document 😄