Re: Fascinating problem with bash
- From: Oliver Schneider <Borbarad@xxxxxxxxxx>
- Date: Mon, 23 Aug 2010 23:15:35 +0000
On 23.08.2010 21:45, Burton Samograd wrote:
You might have to >> the source file name to a temporary file fromOkay, thanks. I was surprised by the behavior, since SHLVL didn't show
the sourced scripts and then read that after the loop is done. Since
while seems to capture variable setting in its own scope it might be
the only way for what you want to do to work. It also seems that for
loops don't have the same variable capture that while loops do, so
if you could somehow convert them you might now have to use a
any differences between outside, inside the outer and inside the inner loop.
In fact I don't need the names (originally I used a counter instead,
using arithmetic expressions, but the problem was the same) - it's only
important to know *that* something got successfully sourced.
ps. Whatever you used to format your code before sending reallySorry for that. Sent it via the web mailer while at the office. That
messed it up :)
must have caused the mess-up. I wasn't sure whether attachments are allowed.
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Prev by Date: Re: Fascinating problem with bash
- Next by Date: Re: Intel Wifi Link 5100 -> halt system on Squeeze
- Previous by thread: Re: Fascinating problem with bash
- Next by thread: Re: Fascinating problem with bash