Date: 02 Dec 2001 18:38:28 -0800 From: swear@blarg.net (Gary W. Swearingen) To: Darren Pilgrim <dmp@pantherdragon.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Changing $IFS in a bash shell Message-ID: <5xpu5xni3f.u5x@localhost.localdomain> In-Reply-To: <3C0AC0D9.BFD0604B@pantherdragon.org> References: <200112022343.fB2Nh6k27466@c1742628-a.vncvr1.wa.home.com> <3C0AC0D9.BFD0604B@pantherdragon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Darren Pilgrim <dmp@pantherdragon.org> writes:
> How else do you recommend I alter the criteria bash uses for its
> word-splitting routine?
And it's common to do this sort of thing to limit the scope of the
change (though I guess it starts a subprocess which you said you
wanted to avoid):
(IFS='
' for dir in `find * -type f` ; do echo -n "test ${dir}"; done)
I thought you could just do "IFS=$NEWLINE for ... done" and avoid
the subshell, but a quick test shows it's not so. I guess it's only
for non-built-in cmds.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5xpu5xni3f.u5x>