rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: gatech!skeeve!arnold@harvard.harvard.edu (Arnold D. Robbins)
To: Boyd Roberts <emory!prl.dec.com!boyd@harvard.harvard.edu>,
	rc@archone.tamu.edu
Subject: Re: early reaction(s) to rc
Date: Fri, 23 Aug 1991 15:47:49 -0500	[thread overview]
Message-ID: <9108231647.AA01674@skeeve.ATL.GA.US> (raw)

> Duff told me:
> 
>     rcmain does the flags that affect initialization, to wit:
>           -p      `protected' -- don't read functions, set path=(. /bin)
>           -c      execute a command given on the command line
>           -i      `interactive' -- print prompts for commands
>           -l      `login shell' -- read $home/lib/profile before user's commands

I would love to know how this works.  -c is trivial:

	eval $*(2) ; exit

and so is -l, but -p and -i are harder --- is there some secret equivalent
of `set' in his rc?  In other words, how does the rc program tell the
shell itself what to do with the environment and whether or not to prompt?

Thanks,

Arnold


             reply	other threads:[~1991-08-23 22:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1991-08-23 20:47 Arnold D. Robbins [this message]
1991-08-24  0:15 ` John Mackin
1991-08-24  3:48   ` John Mackin
1991-08-24 15:10     ` Severe egg on face John Mackin
  -- strict thread matches above, loose matches on Subject: below --
1991-08-27  6:24 early reaction(s) to rc Paul Haahr
1991-08-27  7:15 ` Chris Siebenmann
1991-08-27 10:22 ` Boyd Roberts
1991-08-23 16:51 DaviD W. Sanderson
1991-08-23 17:07 ` Boyd Roberts
1991-08-23 16:24 Arnold D. Robbins
1991-08-27  2:33 ` Chris Siebenmann
1991-08-23  1:36 new list subscriber Byron Rakitzis
1991-08-23 13:40 ` early reaction(s) to rc John Mackin
1991-08-27  2:28   ` 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=9108231647.AA01674@skeeve.ATL.GA.US \
    --to=gatech!skeeve!arnold@harvard.harvard.edu \
    --cc=emory!prl.dec.com!boyd@harvard.harvard.edu \
    --cc=rc@archone.tamu.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).