From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: A delicious thought
Date: Tue, 18 May 1993 14:19:12 -0400 [thread overview]
Message-ID: <9305181819.AA22839@oldp.astro.wisc.edu> (raw)
I should never post before lunch: my hunger even affected the title.
You can't do cd et al. properly in the way I suggested, as rc does not keep
all of its state in the environment (specifically, it doesn't keep where it
is an a flow control construct, the input stack, $*, and $status). So, you
couldn't use a not-built-in command in an if () statement, couldn't use
it in a script, and couldn't find out if it worked or not.
I thought that we might at least salvage a non-builtin-in limit, but then
I realized that probably the most common use of limit is to set coredumpsize
to 0 in .rcrc.
Of course, we could have rc realize its entire state in the environment,
but I hear the wolves baying over in the es list, so I won't even
suggest this.
Alan.
next reply other threads:[~1993-05-18 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-18 18:19 Alan Watson [this message]
1993-05-19 10:00 ` Richard Brooksby
-- strict thread matches above, loose matches on Subject: below --
1993-05-19 14:04 Alan Watson
1993-05-18 17:10 Byron Rakitzis
1993-05-18 17:08 Arnold Robbins
1993-05-18 17:01 Alan Watson
1993-05-18 19:39 ` root
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=9305181819.AA22839@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.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).