Re: Fwd: read -t 0 fails to detect input.

From	Bize Ma <binaryzebra@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Fwd: read -t 0 fails to detect input.
Date	2019-12-20 10:40 -0400
Message-ID	<mailman.1185.1576852856.1979.bug-bash@gnu.org> (permalink)
References	(1 earlier) <7e6fccb4-e5b5-eb2b-8b12-eeee9d638ae1@case.edu> <CAFra36iJqGfocqtVYqcdfkePJZ5xrWg8=pfKZXymD34Gaz02rA@mail.gmail.com> <CAFra36iUQqc-yUmZyu-3ty15jWiN=5o_XQ8pxLsZieEZP8=Lsw@mail.gmail.com> <20191220085747.1401a8011f54209747d32617@schrader-schulte.de> <CAFra36iHt+ah0xV7aUXrJh+CEU+fFEW1Xi=yYsOCu7x9+AVqMA@mail.gmail.com>

Show all headers | View raw

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 gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Fwd: read -t 0 fails to detect input. Bize Ma <binaryzebra@gmail.com> - 2019-12-20 10:40 -0400

csiph-web