Stan Marsh wrote: > >What, no takers? Come on, guys, that can't be normal for the read > >command to get stuck like that. After all, I've given it the timeout > >option, "read -t 1", which means, "In one second, read-or-not, be out > >of there!", does it not? There must be something I could do to avoid > >getting stuck like that. > > This sounds more like a question for [email protected].
That's your contribution? Thank you. Getting stuck when a timeout option is given seems like maybe a bug. Which is why I posted it here.
