I tried with and without BEGIN{ ENVIRON["GAWK_READ_TIMEOUT"]=1000.
Did you set it before invoking gawk? Also, I am using 64-bit gawk
compiled by Volker Kiefel volker.kiefel@freenet.de
http://vkiefel.de/compiled-sw/gawk-5.3.0-win64.zip
The benchmark tests you & I did the other day ran 6% faster under gawk
64-bit vs gawk 32-bit (eli-zaretskii, Ezwinports). I guess I was
expecting a little faster, but not complaining. What I really want is
access to more ram, which I get.
I'll try a few other things to see how timeout works. Just to be able
to match results with you and others. I can easily live without the
timeout.
Aside: I see and read many things you have written about gawk up to 20
years ago. The compilation of Ed Morton's responses on Stack
Overflow/stackexchange would be a great gawk guide. Thanks for years
of selfless sharing! John naman
On Wed, Dec 13, 2023 at 8:27 PM Ed Morton <mortoneccc@comcast.net> wrote:
FWIW it works for me with gawk 5.3 on cygwin.
Just out of curiosity, do you have the same problem if you set the
`GAWK_READ_TIMEOUT` environment variable instead of
`PROCINFO["/dev/stdin", "READ_TIMEOUT"]`?
Ed.
On 12/13/2023 7:07 PM, J Naman wrote:
Date: Thu Dec 14 2023 00:34:43 UTC
Configuration Information [Automatically generated, do not change]:
Gawk Version: GNU Awk 5.3.0, API 4.0
Machine: AMD64(64-bit gawk)
OS: Windows_NT = Win 7 [Version 6.1.7601]
platform: mingw
LC_ALL: C
I have read:https://www.gnu.org/software/gawk/manual/html_node/Bugs.html
Yes or No: Yes
Description:
PROCINFO["/dev/stdin", "READ_TIMEOUT"] = 1000
getline < "/dev/stdin"
# does not timeout in 1 second; waits (forever) until Return key is pressed
# ERRNO is not set if timeout is exceeded
# Ref: 4.11 Reading Input with a Timeout, p.96
Comment: This behavior MIGHT be due to the Mingw-console and not be a bug.
print "Hello World" >"/dev/con" works on gawk mingw platform.
Obviously this is not a debilitating bug, but I thought that I should
report it.