<luis>
does anybody see having output buried in the *inferior-lisp* buffer as a feature?
<Shinmera>
no, it's quite annoying in fact when dealing with FFI that prints to stderr/stdout
<luis>
swank:*globally-redirect-io* doesn't help with that, though.
<Shinmera>
yeah, wish it did
<luis>
merging *inferior-lisp* and the repl buffer would though. 🤔
<luis>
not sure the built-in repl would appreciate it
<luis>
another option would be to have the *inferior-lisp* buffer relay output to the repl buffer
<adlai>
luis, I see it as a good thing that separate streams are not by default aggregated into one
<adlai>
especially when the most common cases i've experienced of my own code's stream output ending up in *inferior-lisp* instead of the repl is that multiple threads are printing simultaneously
<luis>
adlai: they'll be printing simultaneously into *inferior-lisp* won't they?
<luis>
what's the difference?
<adlai>
luis, that is a question of when and how each thread was started
<adlai>
e.g., I start a program from the shell, then a few hours later, start swank and connect a slime-repl. I don't want global redirection in this case, although I think you are talking specifically about images started from M-x slime
<luis>
Oh sure. That's how it works right now.
<luis>
And in fact, the claim that M-x slime turns *globally-redirect-io* on is true. It's just not doing that on my work PC for some reason.
<Shinmera>
I mean in the case of remote connection merging the two isn't possible anyhow.
<luis>
Right.
scymtym has quit [Ping timeout: 260 seconds]
<luis>
Shinmera: do you see the output of (cffi:foreign-funcall "puts" :string "Hello" :int) anywhere?
<Shinmera>
no
<luis>
Ah, it needs flushing. (cffi:foreign-funcall "fflush" :pointer (cffi:null-pointer) :int)
<luis>
Shinmera: does this annoy you with Qt log message or something else?