On 8/17/14, 1:47 AM, Linda Walsh wrote:
> ?? Could this be a cygwin bug? It's hard to see why cygwin
> would start using lseek calls when running bash unless bash called
> them... but then tha's not to say something else entirely may be going on as
> this is running on Windows... ;-/
The origina
Thanks, I'll pass this on...(back)? (busybodiesRus?)
Chet Ramey wrote:
The original poster's speculation is correct. Bash is not allowed to
read more input from stdin than it actually consumes, so commands that
it runs get the intended input. To that end, it tries to detect whether
or not t
