Does gq work for you on docstrings?

I think so

What don't you see?

Maybe I use gw on them

gq has never worked for me on docstrings, but I just tried gw and that worked (never heard of it before)

They are shades of the same action

@martinklepsch https://github.com/tpope/vim-fireplace/issues/299

As a part of that interaction, I learned about gw and switched to it because it's slightly better anyway.

It does what gq does and then puts the cursor back in the original position.

i've also gravitated towards gw. what set me on the path was that fireplace required an active connection in order to do gq

or maybe that was =? my memory is fuzzy

Interesting, thanks for all the pointers

I’ll use gw (it works for me too)

With Fireplace’s REPL buffer-less experience, where can I find stdout?

It seems it should be in :Last but isn’t in my case. This is a CLJS REPL and the evaluated from returns a promise.

Seems to also not work when not returning a promise

And seems to work when using CljEval

There's no persistent connection for stdout.

a selling point for conjure 🙂

The reason for the log buffer 😊

> There’s no persistent connection for stdout. Does that mean it’s just not possible?

If so I might just have to try Conjure 😄

Is there any docs or notes on using Conjure with Shadow CLJS?

some sort of log buffer was on the roadmap for future clojurists together funding. but it feels weird to need it

but i also recall stdout being ten kinds of janky with cljs, maybe that's a factor?

Very helpful for async.

Especially in clojurescript, when you're testing promises

Given that println debugging is basically my go-to “technique” it would be quite limiting

In my limited testing it didn’t seem that promise or no promise made a difference

that points to my ten kinds of janky suspicions

You should get output generally, just not in an async context

it might have even been a shadowcljs issue? i can no longer remember

I think it's very workflow dependant. I like the history in a buffer as something I can edit and reeval because I'm EXTREMELY forgetful.

If you do :Eval (println 1) and you don't see 1, something is wrong

yes do that