jerch
jerch
@Tyriar Not by sixel directly, but could be used by the slave app to determine the actual cell size in pixel which might come handy for graphics output like sixel,...
I think this is the same bug I stumbled over here https://github.com/Tyriar/node-pty/issues/72#issuecomment-291813706 The pty pipe gets closed and invalidated as soon as the pty slave process terminates discarding any leftover...
Sadly the problem is caused by a false assumption in libuv's polling mechanism (node's underlying event library). The fix I came up with involves to many changes of the low...
@starpit The problem is within libuv, that drives nodejs' event system and IO stuff. It cannot handle a POLLHUP and keep reading until all data is drained (Thats a special...
@starpit Some addtional notes - since the process already exited a `setTimeout` does not help here. Reason - the exit of the process also closes the slave end of the...
@Tyriar Imho that is not related to the problem I see with this snippet: ```js var ptyProcess = pty.spawn('python', ['-c', 'for i in range(50000):\n print i;'], { name: 'xterm-color', cols:...
Hmm the more I test this the more I have the feeling it is not working correctly at all. Taken the snippet from above and remove all exit/data handlers: ```js...
@Tyriar Any chance to reproduce it with a simpler case? Imho it is related to the async data cycling (with a possible buffer delay), while the exit gets through earlier....
@Tyriar Not sure yet if it is related, but if I run the following snippet under linux, the output will stop at different positions in data and kinda never finishes...
I drilled down the last problem to node's stream handling - neither `net.Socket` nor `tty.ReadStream` will reliably output the full data. The exit of the slave program kinda always happens...