Clojurians Log v2

Hi, is proto-repl-charts still active?

@jamesvickers19515 What specifically are you asking there? A lot of Clojure projects are "finished" and done get a lot of maintenance but they're still fine to rely on.

Neither ProtoREPL itself nor the charts package have been getting a lot of attention lately since Jason has been busy on other stuff -- but they are both pretty solid for daily usage.

I found ProtoREPL worked well but the overall Atom experience was unsurvivable without accurate paren balancing, which is a feature of a combination of other packages that I didn't get working satisfactorily

@phill Did you try parinfer and/or paredit?

I have both installed and find it to be a fairly pleasant experience. Previously with ProtoREPL, now with Chlorine.

I know parinfer can infuriate some people -- it does take a bit of getting used to but it's wonderfully productive once you get used to it.

On my Windows laptop, all I have installed are Chlorine, Ink, Lisp Paredit, and Parinfer. I've got a lot more installed on my work desktop.

I tried parinfer. It made a hash of my code, like, when I changed let to when-let it didn't shove the continuation lines of the binding form over. But it was complicated by a plethora of advice pages about the like 5 packages to set up and the detailed options to give them to make them work together. To give it another try, could you recommend The Correct Instructions?

Parinfer doesn't have any dependencies, as I recall. I'm just looking to see what settings I have for it...

I have Smart Mode, Force Balance, and Warn on opening bad file all checked. Those are the only settings for Parinfer.

And the standard key bindings for it.

If you open a "bad file" and don't let it fix the file, then it turns itself off, I think, and you need to turn it back on (see the status bar settings).

For ex., https://clojurescript.org/tools/atom recommends installing both Paredit and Parinfer because Paredit contributes auto indentation