From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] How to move to rc from sh/bash
Date: Mon, 11 Feb 2008 18:25:01 -0500 [thread overview]
Message-ID: <CD1CAF77-AB96-47CC-B9EF-74077DA3D8EE@mac.com> (raw)
In-Reply-To: <20080211230315.GA843@shodan.homeunix.net>
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
>
next prev parent reply other threads:[~2008-02-11 23:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 7:53 Hongzheng Wang
2008-02-09 8:01 ` mattmobile
2008-02-09 8:41 ` Hongzheng Wang
2008-02-09 8:57 ` mattmobile
2008-02-09 9:00 ` erik quanstrom
2008-02-09 9:21 ` Hongzheng Wang
2008-02-09 10:11 ` Charles Forsyth
2008-02-09 10:27 ` Lluís Batlle
2008-02-09 15:06 ` Uriel
2008-02-09 17:54 ` Charles Forsyth
2008-02-09 21:59 ` geoff
2008-02-09 13:00 ` Anthony Sorace
2008-02-10 16:59 ` Gorka Guardiola
2008-02-10 17:16 ` Pietro Gagliardi
2008-02-10 17:47 ` erik quanstrom
2008-02-10 18:12 ` Martin Neubauer
2008-02-11 15:04 ` erik quanstrom
2008-02-11 23:03 ` Martin Neubauer
2008-02-11 23:25 ` Pietro Gagliardi [this message]
2008-02-20 15:04 ` maht
2008-02-20 15:08 ` Federico G. Benavento
2008-02-20 15:24 ` erik quanstrom
2008-02-20 15:55 ` maht
2008-02-11 23:59 ` Uriel
2008-02-12 11:57 ` Martin Neubauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD1CAF77-AB96-47CC-B9EF-74077DA3D8EE@mac.com \
--to=pietro10@mac.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).