From: Chris Siebenmann <cks>
To: rc@hawkwind.utcs.utoronto.ca (rc Shell)
Subject: Re: non login "rc" needs customized environment
Date: Tue, 26 Feb 2002 21:16:03 -0500 [thread overview]
Message-ID: <02Feb26.211609edt.75678@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: Your message of "Tue, 26 Feb 2002 20:46:23 EST." <20020227014623.10430.qmail@merton.aus.deuba.com>
| It seems to me the default is backwards. Due to rc being invoked from
| various place over which you may not have control (and hence can't add
| the -l flag), rc should by default read .rcrc (or something). It is easy
| to avoid reading it by adding a test to the first line, eg. (using the
| level count variable someone suggested):
Consulting .rcrc for every new shell requires reading and parsing all
of it on every semi-interactive subshell. (The same is true for any
other file rc would be looking at, of course.)
I spawn a lot of copies of rc over the course of my day. I'm not
really enthused about adding this overhead (and this dependancy on
$home responding right now) to them.
This is a long way to go just because rsh (and ssh) have problems
that can easily be fixed via wrappers.
- cks
next prev parent reply other threads:[~2002-02-27 2:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 4:11 Byron Rakitzis
2002-02-15 14:04 ` Tim Goodwin
2002-02-27 1:46 ` callum.gibson
2002-02-27 2:16 ` Chris Siebenmann [this message]
2002-02-27 13:32 ` Carlo Strozzi
2002-02-27 13:29 ` Carlo Strozzi
2002-02-27 22:24 ` Matt H
2002-02-27 6:13 ` Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 6:29 Byron Rakitzis
2002-02-27 6:26 Russ Cox
2002-02-27 0:52 Byron Rakitzis
2002-02-14 17:44 Byron Rakitzis
2002-02-15 0:18 ` Dave Mason
2002-02-15 3:21 ` Scott Schwartz
2002-02-14 13:35 Smarasderagd
2002-02-15 0:37 ` Greg A. Woods
[not found] <chet@nike.ins.cwru.edu>
2002-02-13 20:36 ` Chet Ramey
2002-02-14 2:16 ` Scott Schwartz
2002-02-14 23:35 ` Markus Friedl
2002-02-15 3:05 ` Scott Schwartz
2002-02-13 19:21 Peter Koch
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=02Feb26.211609edt.75678@hawkwind.utcs.toronto.edu \
--to=rc@hawkwind.utcs.utoronto.ca \
/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).