Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!mace.cc.purdue.edu!abe
From: abe@mace.cc.purdue.edu (Vic Abell)
Newsgroups: comp.sys.next
Subject: one New Shell answer
Message-ID: <7183@mace.cc.purdue.edu>
Date: 8 Apr 91 13:47:49 GMT
Organization: Purdue University
Lines: 24


In article <7112@mace.cc.purdue.edu> I wrote:
>export: Command not found.
>TERM=Workspace: Command not found.

>	2.  Why is /bin/csh being fed what appear to be Bourne or Korn Shell
>	    startup commands?   Are the commands stored in a file?  (They can
>	    be found in "strings /usr/lib/NextStep/Workspace.app/Workspace".)

I am embarrassed to report that the answer to this question is that I still
have a .cshrc that contains:

	if ( ! $?LOGINDONE ) then
		source ~/.login
	endif

and a .login that contains:

	set noglob; eval `tset -Q -s`; unset noglob

Now if I could just file a way to direct the Workspace Manager to start my
login shell instead of csh.

Vic Abell <abe@mace.cc.purdue.edu>