@cfleming You know what would be really cool? Here I am getting ready to submit a pull request, and I have to pull out all the pprint and js/console.log statements I’ve been using for debugging during dev. Wouldn’t it be handy if all those statements could be styled with a different background color so they’d be easier to spot?

Just a stray thought, back to work now.

@cfleming Thanks so much for the quick response — it’s been great using Cursive. If you’re interested, I can write up some thoughts about what it’s like coming from Atom/Visual Studio Code, and what I’m having to do to adapt… Two quick questions? 1. I’m having this problem where I can no longer see the text entry point in the REPL — I spent 15m floating/pinning/redocking/closing/re-opening… Almost tempted to re-install to try to get the text entry area back. In other words, whatever I type in the REPL, I cannot see until I hit ENTER! It was great when I could, though!!! 🙂

@genekim: Try double clicking on the handle (right above the event log)

I just shrunk my repl window to try and recreate your problem and got a little panicky when click and drag didn't fix it 🙂

2. I’m using parinfer mode, and when I type Tab when I’m in a “let binding”, it indents the whole line… instead of inserting a in the middle of the line… I love the demo where the let-bindings are auto-formatted, but I can’t get that to work… Sorry for all the newbie questions! (But despite all my difficulties, I am loving it — goto symbol is fantastic, I’m loving the “wrong arity” detection, and the REPL is wonderful!

@shaun-mahood — “panicky”. Yes! I totally relate to the feeling! Drats… I’m double-clicking everywhere, and not finding anything that brings the REPL text entry area back. Can you post screenshot of where I should click? Sorry! And thank you! 🙂

OMG! @shaun-mahood It worked!!! I had no idea that that area was the text entry area! I thought it was the editor window showing form beneath! Wonderful!

Awesome 🙂