From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: a tricky question
Date: Sun, 15 Dec 1991 16:07:46 -0600 [thread overview]
Message-ID: <91Dec15.170748est.2689@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: byron's message of Thu, 12 Dec 91 10:58:56 -0500. <91Dec12.103008cst.18907@archone.tamu.edu>
I think it's worth adding '-p' to rc (which would not import
functions from the environment) just to make rc shell scripts
more reliable in the face of random users using them. I know
that I've been starting all my scripts with something that
clears out the defined functions, but it's not foolproof;
'-p' would be better and more convenient. Never allowing
'fn' and 'builtin' to be redefined as functions would
probably also suffice, but I'd prefer '-p'.
- cks
next prev parent reply other threads:[~1991-12-15 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-12-12 15:58 Byron Rakitzis
1991-12-15 22:07 ` Chris Siebenmann [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-12-12 15:54 Byron Rakitzis
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=91Dec15.170748est.2689@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.edu \
--cc=rc@archone.tamu.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).