On Sun, 20 May 2018 02:00:18 -0500 R0b0t1 <r03...@gmail.com> wrote: > Hello, > > When using pyserial, I believe the error is something like "device > notified ready but no bytes to read." Screen may or may not be > encountering the same condition. > > This is happening over a USB serial adapter connected to an embedded > system. During early boot the connection will be interrupted 2 or 3 > times in quick succession. Afterwards the connection is much more > stable but disconnects still occur. > > The cause isn't something obvious such as crossed wires or me touching > something. > > > Based on the error I received with pyserial I think it may be possible > to write some C code to get around this problem, but that will quickly > become more trouble than it's worth as many many programs have no > uniform interface to disable their output of terminal control > characters. > > Cheers, > R0b0t1 > > _______________________________________________ > screen-users mailing list > screen-users@gnu.org > https://lists.gnu.org/mailman/listinfo/screen-users
Hi, well, I can't do much without knowing the exact nature of problem, and it sounds more, like your serial device is behaving in unspecified way than that screen is broken. Anyway if you want to take a look at it, check win_readev_fn function in window.c Seeing that pythons tells that no bytes to read, maybe look at that line: https://git.savannah.gnu.org/cgit/screen.git/tree/src/window.c?h=screen-v4#n1913 or maybe check if it returns some errno in checks above. Cheers, Amadeusz _______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
