Clojurians Log v2

@jasongilman is here but “away” — I would expect any “todo” to be listed on the GH repo and/or in issues there?

^ @john

ah thanks

Yeah, I was checking out out the GH. Didn't see any suggestions of future milestones.

I'd like to figure out a way to make a kind of meta package that includes all of the additional suggestions from this gist: https://gist.github.com/jasongilman/d1f70507bed021b48625

Plus proto repl

And see if I can help with getting CLJS/figwheel working out of the box, if possible.

@john Unless you have a beautifully clean, uses-Component-from-the-ground-up project, you’ll probably want some adjustment to those settings BTW. And I ended up dropping a couple of those packages and adding different ones. Jason’s setup is pretty opinionated. I don’t know that I’d recommend it to beginners.

Really, I'd like to survey a number of folks to see what they believe an ideal beginner setup would look like. Do you have any suggestions?

I'd like to work and advocate towards a one supported way IDE, for some of the community to persistently recommend, so documentation can be built from that common base.

Which hopefully takes out some of the indeterminacy and paradox of choice that surrounds some of the existing tooling.

And I think atom/protorepl might be clean enough to deliver on the dream.

For beginners, I’d suggest turning off the three namespace refresh options in ProtoREPL.

I don’t remember what other parts of Jason’s guide I found got in my way. It’s been a long time now since I set ProtoREPL up (on two machines) and I’ve tweaked it a bit, on and off, since then.

Do you use it daily?

Yeah, I switched from Emacs to Atom/ProtoREPL completely after last year’s Conj!

It's pretty sharp.

I think the tab length 1 setting (language-clojure) is too subtle so I have tab length 2.

I have display executed code off — I found that way too annoying with large blocks of code.

On to lisp-paredit and I have the following indentation forms:

try, catch, finally, let, are, /^def.*/, fn, /^cond-.*/, if, if-let, for, /when.*/, testing, do, doseq, dotimes, loop, ns, /with/, proxy

try, catch, finally, /^let/, are, /^def/, fn, cond, condp, /^if.*/, /.*\/for/, for, for-all, /^when.*/, testing, doseq, dotimes, ns, routes, GET, POST, PUT, DELETE, extend-protocol, loop, do, case, with-bindings, checking, with-open

But that’s definitely a matter of taste and it depends what type of code you work on…

I have several additional community plugins installed and configured (most notably git-plus — which is great).

Where my config goes off the beginner trail is that I have emacs-plus and disable-keybindings installed… which greatly eased my transition from Emacs! 🙂

So… probably refresh settings are the thing that catches out more folks new to ProtoREPL than anything else I’ve seen reported here.

Cool. Thanks for the tips 🙂

@john in terms of the community supported recommended IDE I would say Atom+Parinfer+ProtoREPL are really the only game in town for now. I also think we need to make it much better for cljs users, who will encounter the same sort of issues you did where most docs are targeted only at clj(jvm) users. Long run I think vscode is really promising because it has an integrated debugger which would be a big plus, but at present has no way to draw the inline results in the editor the way proto can with atom ink.

One other tip I think we should push, is to show users how to make parenthesis a lighter grey... it will help with the too many parenthesis complaints.

I’m surprised no one has ported something like rainbow parens to Atom…

I found “swackets” but it doesn’t work with Clojure (and the readme warns about performance problems with long files so I doubt it’s a good option anyway).

It's too bad it requires so much setup instructions. It'd be nice if there were some way to deliver a working CLJS repl out-of-the-box, via some package of some sort.

Googling atom ide meta package doesn't return much helpful

Actually, here's a simple meta package: https://github.com/spark/particle-dev-complete

So it could just be a matter of making a custom package with all the necessary custom settings, and then a meta package that includes that and protorepl and all the other packages?