Re: Reading /dev/stdin Input with a Timeout

[arnold]

Hi All.

Sorry for the long delay in replying. I think I prefer the attached patch.
I will try to get it into Git in the next day or so.

Thanks,

Arnold

"Andrew J. Schorr" <aschorr@telemetry-investments.com> wrote:

> Hi,
>
> I think the attached patch fixes this, but I fear that I may be missing
> something subtle about how GAWK_READ_TIMEOUT is supposed to work, because I
> can't fathom why it was coded the other way previously...
>
> Regards,
> Andy
>
> On Thu, Dec 14, 2023 at 07:02:58AM -0600, Ed Morton wrote:
> > Though this doesn't work:
> > 
> >    GAWK_READ_TIMEOUT=1000 gawk '
> >         { print "You entered: " $0 }
> >    '
> > 
> > this does:
> > 
> >    GAWK_READ_TIMEOUT=1000 gawk '
> >         BEGIN {
> >             if ( !("-","READ_TIMEOUT") in PROCINFO ) {
> >                 PROCINFO["-","READ_TIMEOUT"] = ENVIRON["GAWK_READ_TIMEOUT"]
> >             }
> >         }
> >         { print "You entered: " $0 }
> >    '
> >    gawk: cmd. line:4: fatal: error reading input file `-': Connection
> >    timed out
> > 
> > so there's a workaround, though it seems like a fix should be
> > possible for this GAWK_READ_TIMEOUT problem (which is apparently
> > different from John's original PROCINFO["-","READ_TIMEOUT"]  MinGW
> > problem).
> > 
> >     Ed.

timeout.diff
Description: Text document