From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from groucho.cs.psu.edu ([130.203.2.10]) by hawkwind.utcs.toronto.edu with SMTP id <2711>; Thu, 25 Jun 1992 20:44:21 -0400
Received: from localhost by groucho.cs.psu.edu with SMTP id <2536>; Thu, 25 Jun 1992 20:43:07 -0400
To:	drazen@vlsi.cs.caltech.edu (D. Borkovic)
cc:	rc@hawkwind.utcs.toronto.edu
Subject: Re: subshell, interactive, login, etc 
In-reply-to: Your message of "Thu, 25 Jun 92 20:26:17 EDT."
             <9206260026.AA20589@vlsi.cs.caltech.edu> 
Date:	Thu, 25 Jun 1992 20:42:44 -0400
From:	Scott Schwartz <schwartz@groucho.cs.psu.edu>
Message-Id: <92Jun25.204307edt.2536@groucho.cs.psu.edu>


| What do people out there think about this:
| 
| Every rc sources .rcrc, but before doing this defines
| certain variable (say $mode) to have certain values
| depending on the mode. 

How about this instead:  every rc evaluates a function, rc_init, if
defined, when it starts up.  (Before or after .rcrc, if a login shell?)
This would preserve a nice property of the current scheme, that you
don't need to read .rcrc just to start a shell.

My dream fix: user defined read-eval-print loops.  Scheme-shell anyone?