From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <20080211230315.GA843@shodan.homeunix.net> References: <20080210181244.GA801@shodan.homeunix.net> <20080211230315.GA843@shodan.homeunix.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pietro Gagliardi Subject: Re: [9fans] How to move to rc from sh/bash Date: Mon, 11 Feb 2008 18:25:01 -0500 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 505e2906-ead3-11e9-9d60-3106f5b1d025 The only advantage to getflags is that we can say rcsrcipt -xy instead of rcscript -x -y which is why I use it in my 12 script. On Feb 11, 2008, at 6:03 PM, Martin Neubauer wrote: > * erik quanstrom (quanstro@quanstro.net) wrote: >> i would think that the reason to do this would be for consistency. i >> don't know that that's a compelling argument. but i can see the >> attraction of all or nothing; it would be nice if either none of the >> scripts used getflags or all of them did. >> >> - erik > > That's actually quite compelling to me. I'd be just in favour of > some kind > of `lazy evaluation' (if some script needs to be changed, put in > getflags; > ditto for new ones.) And I admit that if one is really tght pressed > on space > (which might still happen nowadays, if not nearly as often than a > couple of > years ago) it won't really matter havin to put in some effort to > customise > what's in /bin/rc. I'm still amused by the argument that getflags > is faster, > though. > > Martin >