Ugh, no hack available. The issue is that the data structure is split into formatting ops up front, before any of the layout is available. So I can’t say something like: if there are x chars left on the line use these ops, otherwise use these others.

@cfleming thanks for the explanation!

sorry for delayed responses, splitting my time between cleaning, baby, and clojure 🙂

Hehe, no problem, that’s commonly my situation too 🙂

that issue arose mainly because I wasn't sure how whitespace in Clojure multiline strings was handled so I was debugging by printing the string itself and was confused why a more complicated function included the spaces

no idea how you have time to build such an awesome product 🙂

Well, it took several years! The first open beta was right before my daughter was born which delayed things a bit.

Actually she still delays things a bit now that I think about it.

ah awesome, haha. I installed Cursive a day before my daughter was born. And when I finally had time to try it my trial expired 🙂

Hehe, yes, 30 days is not enough under those circumstances!

yup, I gave emacs a shot but I previously had wrist pain back when I needed to actually use the control key 😄

anyway, back to cleaning... thanks!

Holy cow. Using Lumo for the first time today. Wow, it’s fast and easy to write useful things! Is there a way to run a Lumo REPL on Cursive Mac? I miss having the ability to send stuff to REPL inside Cursive! Thanks!

So, you can, but it’s a little fiddly. Use Tubular: https://github.com/mfikes/tubular

(If not, maybe back to Clojure. Cursive has made me quite spoiled. :)

Wow, thanks!!! Will check it out!

I’m planning first-class support for both Lumo and Planck though, Lumo support in particular requires better CLJS support for Node.

And they both need a custom SDK type to be able to resolve symbols correctly.