From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1304104623.9113.1446566425@webmail.messagingengine.com> From: "Ethan Grammatikidis" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" 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> <25321b4258988e7615bcacfd9f1878d1@coraid.com> In-Reply-To: <25321b4258988e7615bcacfd9f1878d1@coraid.com> Date: Fri, 29 Apr 2011 20:17:03 +0100 Subject: Re: [9fans] spaces in filenames (and filesystems...) Topicbox-Message-UUID: d93299f8-ead6-11e9-9d60-3106f5b1d025 On Fri, 29 Apr 2011 11:17 -0400, "erik quanstrom" wrote: > > 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. I don't quite understand the first two examples. Do they set ifs only within the {} ? I guess that risks breaking any scripts you might want to run as cmd, so yeah, the 3rd looks good.