Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!batcomputer!jch
From: jch@batcomputer.tn.cornell.edu (Jeffrey C Honig)
Newsgroups: comp.windows.x
Subject: Re: Console xterms
Message-ID: <7452@batcomputer.tn.cornell.edu>
Date: 23 Feb 89 00:33:22 GMT
References: <20873@shemp.CS.UCLA.EDU>
Reply-To: jch@tcgould.tn.cornell.edu (Jeffrey C Honig)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 24

In article <20873@shemp.CS.UCLA.EDU> tek@CS.UCLA.EDU () writes:
>How can a program tell if it's running under a console xterm (ie xterm -C)
>versus a normal xterm? 

This may not be what you want, but I tailor my environment by defining a
unique name for my console window.  I use xprop in my .cshrc to set the
window name into the environment so I can check it in my .login to
determine if I should set biff y or n.

.cshrc:
if ($?WINDOWID) then
	eval setenv `xprop -id $WINDOWID -notype -f WM_NAME 8s ' $0' WM_NAME`
endif

.login:
if ($?WM_NAME) then
	if ("$WM_NAME" == "Console") then
		biff y
	else
		biff n
	endif
endif

Jeff