You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, after sly-connect it seems sb-sys:*stdout* become line buffered and won't flush. If I (princ "something") nothing comes out. If I disconnect, it all comes out. (terpri) will make it happy before a (finish-output) or something and then it's out.
I tried to describe the stream while connected and disconnected but found no significant differences. Interactive is false, BUFFERING is :LINE and Sly's global redirection is nil and dedicated output stream is not being used (SSH tunnel, plus it's set to nil). Not sure how to investigate further.
Of note, a SLIME server is also running in the application. SBCL is 2.1.10. Slynk protocol 1.0.43.
The text was updated successfully, but these errors were encountered:
So, after
sly-connect
it seemssb-sys:*stdout*
become line buffered and won't flush. If I(princ "something")
nothing comes out. If I disconnect, it all comes out.(terpri)
will make it happy before a(finish-output)
or something and then it's out.I tried to
describe
the stream while connected and disconnected but found no significant differences. Interactive is false,BUFFERING is :LINE
and Sly's global redirection isnil
and dedicated output stream is not being used (SSH tunnel, plus it's set to nil). Not sure how to investigate further.Of note, a SLIME server is also running in the application. SBCL is
2.1.10
. Slynk protocol1.0.43
.The text was updated successfully, but these errors were encountered: