Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15760 > unrolled thread
| Started by | Bize Ma <binaryzebra@gmail.com> |
|---|---|
| First post | 2019-12-20 10:40 -0400 |
| Last post | 2019-12-20 10:40 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Fwd: read -t 0 fails to detect input. Bize Ma <binaryzebra@gmail.com> - 2019-12-20 10:40 -0400
| From | Bize Ma <binaryzebra@gmail.com> |
|---|---|
| Date | 2019-12-20 10:40 -0400 |
| Subject | Re: Fwd: read -t 0 fails to detect input. |
| Message-ID | <mailman.1185.1576852856.1979.bug-bash@gnu.org> |
On Fri., 20 dec. 2019 at 3:57, Martin Schulte (<gnu@schrader-schulte.de>) wrote: > Hello! > > > Could you please comment about this assertions: > > > > 1.- bash will either do a select() or an ioctl(FIONREAD), or neither > > of them, but not both, as it should for it to work. read -t0 is broken. > > 2.- Conclusion: read -t0 is *broken* in bash. Don't use it. – > > No. It works as intended. It's not usable in a pipe in the way you try, > but this is caused by the principles of a pipe, not by a bug in read. > > Hello Martin! I am not the one making those comments. I don't have enough C expertise to neither confirm or deny them. But that also makes me unable to answer to the author of the comments in the proper way. I intended to receive something to correct his (incorect?) opinion. In any case, thanks. Best regards, Isaac
Back to top | Article view | gnu.bash.bug
csiph-web