Path: utzoo!attcan!uunet!anise.acc.com!ucbvax!bloom-beacon!athena.mit.edu!jik
From: jik@athena.mit.edu (Jonathan I. Kamens)
Newsgroups: comp.unix.questions
Subject: Re: YAPQ (yet another prompt question)
Message-ID: <13542@bloom-beacon.MIT.EDU>
Date: 16 Aug 89 05:22:38 GMT
References: <1356@unhd.unh.UUCP> <2113@infmx.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: jik@athena.mit.edu (Jonathan I. Kamens)
Organization: Massachusetts Institute of Technology
Lines: 20

In article <2113@infmx.UUCP> aland@infmx.UUCP (alan denney) writes:
=In article <1356@unhd.unh.UUCP> rg@unh.UUCP (Roger   Gonzalez) writes:
=|
=|Since a child 'csh' is spawned whenever I 'su', I thought it would be
=|nice to have the prompt reflect the 'su-ed' state.  Hence, in .cshrc, I
=|had:
=|[problem text deleted]
=Did you try su-ing to uid that definitely has csh as its shell?
=I suspect that root on your system uses sh by default. sh(1) would
=gag on the "set prompt" command, as it is not valid set syntax
=for sh.

  Ahem.  Since when does /bin/sh even look for a file called ".cshrc"
when it starts up?  The characters "csh" in the filename ".cshrc" are
significant, no?

Jonathan Kamens			              USnail:
MIT Project Athena				432 S. Rose Blvd.
jik@Athena.MIT.EDU				Akron, OH  44320
Office: 617-253-4261			      Home: 216-869-6432