[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Getting a table from commandline output
- From: Roberto Ierusalimschy <roberto@...>
- Date: Mon, 7 Nov 2011 12:30:46 -0200
> On my cheapo Windows XP machine the lines-driven for-loop (as shown
> above) always comes to a screeching halt. Using a loop around a read
> "*l" call may look less elegant, but works just fine. Obviously, in
> the latter case the broken pipe situation is still there. It just
> doesn't bring the script to its knees, because no alert is thrown.
By "bring the script to its knees" you mean that the script ends with
a regular error condition?