On 2017-03-01 12:18:41 +0100, Axel Beckert wrote: > Vincent Lefevre wrote: > > Note that something like "nonblock 5" has no effect. > > According to the man page, that seems unrelated as it configures how > screen behaves if the terminal it's running on is blocking.
Not sure. The man page is not clear. nonblock [on|off|numsecs] Tell screen how to deal with user interfaces (displays) that cease to accept output. [...] In the case of copy mode, it seems that the corresponding display ceases to accept output, though it is not clear whether this is done on purpose, this is a current limitation or this is unexpected. In the first two cases, there should be some kind of (optional) timeout. Then: This can happen if a user presses ^S or a TCP/modem connection gets cut but no hangup is received. [...] It is not clear whether these causes are exhaustive or not. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
