From: malte@techfak.uni-bielefeld.de
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: subshell, interactive, login, etc
Date: Fri, 26 Jun 1992 06:33:16 -0400 [thread overview]
Message-ID: <9206261033.AA05577@dahlie.techfak.uni-bielefeld.de> (raw)
In-Reply-To: Mail from 'drazen@vlsi.cs.caltech.edu (D. Borkovic)' dated: Thu, 25 Jun 1992 20:26:17 -0400
drazen@vlsi.cs.caltech.edu (D. Borkovic) writes:
Every rc sources .rcrc, but before doing this defines
certain variable (say $mode) to have certain values
depending on the mode.
If this is seriously considered to be incorporated, the recent rc version will
be the last I use. There has never been an uglier, more resource waisting or
more problem causing mechanism than that. I fought serious wars to convince
csh users to switch to rc and now this !
NEVER!
Malte.
next reply other threads:[~1992-06-26 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-26 10:33 malte [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-06-26 13:57 Matthew Farwell
1992-06-26 3:57 Alan Watson
1992-06-26 1:41 Donn Cave
1992-06-26 2:07 ` Scott Schwartz
1992-06-26 8:10 ` Matthew Farwell
1992-06-26 0:26 D. Borkovic
1992-06-26 0:42 ` Scott Schwartz
1992-06-26 1:39 ` Chris Siebenmann
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=9206261033.AA05577@dahlie.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--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).