From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from harvard.harvard.edu ([128.103.1.1]) by archone.tamu.edu with SMTP id <22531>; Fri, 23 Aug 1991 17:46:20 -0500 Received: by harvard.harvard.edu (5.54/a0.25) (for rc@archone.tamu.edu) id AA03799; Fri, 23 Aug 91 18:48:14 EDT Received: from gatech.UUCP (uucp.gatech.edu) by gatech.edu (4.1/Gatech-9.1) id AA11401 for archone.tamu.edu!rc; Fri, 23 Aug 91 18:43:39 EDT Received: from skeeve.UUCP by gatech.UUCP (4.1/SMI-4.1) id AA03706; Fri, 23 Aug 91 18:43:37 EDT Received: by skeeve.ATL.GA.US (smail2.5) id AA01674; 23 Aug 91 16:47:52 EDT (Fri) From: gatech!skeeve!arnold@harvard.harvard.edu (Arnold D. Robbins) Date: Fri, 23 Aug 1991 15:47:49 -0500 X-Mailer: Mail User's Shell (6.5.6 6/30/89) To: Boyd Roberts , rc@archone.tamu.edu Subject: Re: early reaction(s) to rc Message-Id: <9108231647.AA01674@skeeve.ATL.GA.US> > 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