Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!brownfld
From: brownfld@ux1.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Re: .login file
Message-ID: <18600013@ux1.cso.uiuc.edu>
Date: 13 Oct 90 14:38:00 GMT
References: <23904@<1990Oct13>
Lines: 23
Nf-ID: #R:<1990Oct13:23904:ux1.cso.uiuc.edu:18600013:000:1061
Nf-From: ux1.cso.uiuc.edu!brownfld    Oct 13 09:38:00 1990


     When you login to console, .cshrc and .login are not executed.  They
are only executed when you enter csh, which only occurs when your pull up
a terminal or shell.  Thus, whenever you can pull up a value for `tty`
it will be the ttyp0 etc. for the shell, NOT the login.  The .cshrc and .login
like files for the Workspace are in .NeXT in your home directory.
     Couldn't you put this application in the dock?  You could choose whether
it would load or just keep the icon available on the dock.  If you just want
to tell if you are running on the console, you can do the following:

if	( ${?Workspace} )	then
	whatever_you_want
endif

     This will only run when you run a shell, but this is good for setting
your default editor to WriteNow if you're on the console and in a terminal
window.  If you have Terminal execute in your dock, you can have your
<application0> load automatically on boot-up with ${?Workspace}.

							Ken.
Kenneth R. Brownfield				   ken-b@uiuc.edu
University of Illinois, Urbana-Champaign
Junior, Computer Science/Engineering.