From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Fri, 29 Apr 2011 10:00:36 -0400
To: 9fans@9fans.net
Message-ID: <dd6a13d16c739ff5a6f299c84950bbcf@coraid.com>
In-Reply-To: <3B3CAD91-6623-4E25-AB8A-FE1613ACFD83@fastmail.fm>
References: <20110427131041.GA21774@skaro.cthulhu.dircon.co.uk>
	<0bc37e9990e3c3ebde8276275a170a88@quintile.net>
	<BANLkTin+93BDbjWXzn5Myii6eXAoJb8-nQ@mail.gmail.com>
	<20110428121127.GD1020@skaro.cthulhu.dircon.co.uk>
	<3B3CAD91-6623-4E25-AB8A-FE1613ACFD83@fastmail.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] spaces in filenames (and filesystems...)
Topicbox-Message-UUID: d8e58c8a-ead6-11e9-9d60-3106f5b1d025

> Parsing the output of programs which return filenames is the only
> common case where I see any complexity from spaces, and then the
> complexity only consists of setting and reverting $ifs. Granted that
> could be smoother still, especially where you want a big file list in
> for().

be careful.  setting ifs is global, and changes ifs for the whole
command, and doesn't change the behavior of external programs.
so it is both less and more than you want.

- erik