Clojurians Log v2

Just published some small fixes on version 0.2.1. Probably the ClojureScript bug is fixed. I still want to make more tests (specially with the :browser target) 🙂

When I enter something bad directly into REPL being used by Chlorine, I get the sort of error shown here, which includes some useful information like "Unable to resolve classname". Doing an eval from chlorine, though, shows a clojure.lang.Compiler$CompilerException with a generic syntax error message and line/column number (didn't paste it here, as Slack mangled the formatting). New to chlorine, so not sure if that's something with the new version or if it has always been that way.

This can happen if you’re in a CLJS namespace and your preferences are set to evaluate CLJ or vice versa.

I assume that is the "Should we evaluate Clojure or ClojureScript" setting? It was set to prefer-clj, I put it as clj, same behavior.

@dave.dixon I'll open an issue, I'm seeing this behavior too.

Weird one: several times now, after typing a colon, atom will crash. I think it's happening when the colon is entered in front of some other text. Haven't found a consistent repro case. The window goes white and I get a popup with the options to restart or exit. Are there error logs for the package written someplace? Since it seems to be related to clojure keywords, perhaps it's something do with completion?

Probably... I'll look at this issue too (I already have a fix for the other one). I keep forgetting that Atom's autocomplete is kinda aggressive and it'll try to autocomplete on every keyword (I use a keymap to trigger autocomplete).

Are you having this issue on Clojure files, or on ClojureScript?

Clojure

Okay, I just found that if I type L and delete it, it'll trigger this problem 😞

Atom allows Autocomplete with "0" characters to trigger it, so that's one of the issues (I probably didn't check this)

Ah, that explains something very weird that happened to me the other day (it's happened exactly once and I pressed space too fast to even see the popup!).

Yes, I've just tested here and indeed the error exists. I'll push a fix right now 🙂

Awesome, thank you!

You rock @mauricio.szabo!

Oh, thanks a lot 🙂

Nice!