pourko--- via Bug reports for the GNU Bourne Again SHell <bug-bash@gnu.org> writes:
> 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. You've waited less than 20 hours. Chill. > > Pourko
