From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] usage of CPU server
Date: Fri, 3 Nov 2000 19:54:36 +0100 [thread overview]
Message-ID: <05cc01c045c7$83971920$0ab9c6d4@cybercable.fr> (raw)
In-Reply-To: <3a02def3@news.core.genedata.com>
> "rob pike" <rob@plan9.bell-labs.com> wrote in message
> news:20001103145607.93809199DC@mail...
> > I never understood the resistance. I still don't.
neither did i. the solution was to either change
the environment or be conservative on how much of
the environment you burnt up with functions.
personally, i've never run into environment/NCARGS
problems, but i've seen shell scripts that have,
written by idiots.
i used to use rc and before that i hacked 8th ed
stuff into the svr2 shell. after getting used to
8th ed shell i couldn't live without history,
whatis, builtin or exportable functions. i had
the code, so i coded the it. it's not hard.
next prev parent reply other threads:[~2000-11-03 18:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 14:56 rob pike
2000-11-03 16:55 ` Elliott Hughes
2000-11-03 18:54 ` Boyd Roberts [this message]
2000-11-06 9:44 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 13:05 rob pike
2000-11-02 18:02 rob pike
2000-11-03 14:22 ` Douglas A. Gwyn
2000-11-02 10:20 forsyth
2000-11-02 10:02 nigel
2000-11-02 16:03 ` Rick Hohensee
2000-11-02 16:27 ` Boyd Roberts
2000-11-01 9:53 okamoto
2000-11-01 10:03 ` Lucio De Re
2000-11-01 14:46 ` Rick Hohensee
2000-11-01 15:19 ` nigel
2000-11-02 1:06 ` Rick Hohensee
2000-11-02 1:24 ` Boyd Roberts
2000-11-02 8:21 ` Rick Hohensee
2000-11-02 17:44 ` Douglas A. Gwyn
2000-11-02 7:55 ` Steve Kilbane
2000-11-02 11:25 ` Boyd Roberts
2000-11-01 9:08 forsyth
2000-11-01 7:27 okamoto
2000-11-01 8:21 ` Lucio De Re
2000-11-01 6:03 Russ Cox
2000-11-01 4:09 okamoto
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='05cc01c045c7$83971920$0ab9c6d4@cybercable.fr' \
--to=boyd@planete.net \
--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).