From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 29 Apr 2011 11:17:31 -0400 To: 9fans@9fans.net Message-ID: <25321b4258988e7615bcacfd9f1878d1@coraid.com> In-Reply-To: <2345D520-5F13-4A07-A96B-48B0A725A4C9@fastmail.fm> References: <20110427131041.GA21774@skaro.cthulhu.dircon.co.uk> <0bc37e9990e3c3ebde8276275a170a88@quintile.net> <20110428121127.GD1020@skaro.cthulhu.dircon.co.uk> <3B3CAD91-6623-4E25-AB8A-FE1613ACFD83@fastmail.fm> <2345D520-5F13-4A07-A96B-48B0A725A4C9@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: d903568e-ead6-11e9-9d60-3106f5b1d025 > I always change it back immediately; a nuisance in for() as it has to > be set before and re-set inside. I'm considering whether a new shell > builtin would be desirable, similar to ` but always splitting on > newlines and only newlines, regardless of $ifs. this is one thing that byron understood in his version of rc. he had x=``ifs {cmd} the `` was required since `singleton was allowed in his version. i think that one could just extend the grammar to allow x=`ifs {cmd} and i think it would be even better if it were x=`splitchars {cmd} so ifs is never set. - erik