From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: drazen@vlsi.cs.caltech.edu (D. Borkovic)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: subshell, interactive, login, etc
Date: Thu, 25 Jun 1992 20:42:44 -0400 [thread overview]
Message-ID: <92Jun25.204307edt.2536@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 25 Jun 92 20:26:17 EDT." <9206260026.AA20589@vlsi.cs.caltech.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?
next prev parent reply other threads:[~1992-06-26 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-26 0:26 D. Borkovic
1992-06-26 0:42 ` Scott Schwartz [this message]
1992-06-26 1:39 ` Chris Siebenmann
1992-06-26 1:41 Donn Cave
1992-06-26 2:07 ` Scott Schwartz
1992-06-26 8:10 ` Matthew Farwell
1992-06-26 3:57 Alan Watson
1992-06-26 10:33 malte
1992-06-26 13:57 Matthew Farwell
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=92Jun25.204307edt.2536@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=drazen@vlsi.cs.caltech.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).