Perhaps setting g:conjure#client#clojure#nrepl#eval#print_options#length to something lower than the default of 500 so that longer sequences are truncated faster?

When I am dealing with something that's potentially big, I usually toss a (take 10 ...) around it first

or a (keys (first big-coll)) to see what is in there

It's because I'm using the hud more like a log file. Making a migration of say a million entries and using println for each one

tweak the prints to append to a file instead?

I think there's a function to clean the hud somewhere, at least I could try to run it when I see vim is about to hang

Yeah, that could work, but I like the convenience of the editor

Is there something like "interrupt current rendering operation" in nvim? Maybe it could still produce the value (mostly this is not a problem) but wouldn't print it. Emacs has C-g C-g or something that allows to interrupt the current operation. It doesn't work all the time but it worked for me in the past. Conjure has "interrupt the REPL operation" but I think that it doesn't work when the value is already put to the printer mechanism. Basically -- vim doesn't hang because the data is too large. It hangs because the rendering takes a lot of work (the data is too large for rendering).