Re the issue opened above: I'm musing about adding two different hard limits on Clojure nREPL output by default that would self document with how to raise or remove them where required. This should guard against accidental printing of the entire universe quite nicely. I think this will be a good addition despite the fact that I've printed things that result in 100k+ lines of output in the log and Neovim + Conjure has handled it okay, even if the syntax highlighting switches off etc.

Honestly amazed by how much data can be handled by this simple "just dump it in a buffer after running it through some Lua". The less magic I do, the more text it can handle. It's the main reason why I've been pushing things like "async browsing of data structures" down my feature list, it's just not 100% essential for most work right now, dump it in the buffer and grep 😄

Is the data transformed into lua data at some point or is it just text as far as lua goes?

The reason I ask is that I've thought about writing a function that I can wrap all my evals in and it will look through the data for things that are too big (like a vector with 10k entries) and it truncates it. That way the output is useful, but not complete.

And it doesn't bog down my neovim.

But if that was built in to conjure, or I could register a function with conjure to do it, and then call a different mapping, that could be useful.

I hope this makes sense.

Conjure only sees text, no data I'm afraid

You could send Clojure down the pipe and wrap your evals in something extra though

Then it would be data