Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mit-eddie!uw-beaver!Teknowledge.COM!unix!hplabs!hp-pcd!hpfcso!hpfcdj!jayavant
From: jayavant@hpfcdj.HP.COM (Rajeev Jayavant)
Newsgroups: comp.sys.hp
Subject: Re: Something useful for a change
Message-ID: <17330021@hpfcdj.HP.COM>
Date: 2 Nov 90 21:17:51 GMT
References: <25191@uflorida.cis.ufl.EDU>
Organization: Hewlett Packard -- Fort Collins, CO
Lines: 28

/ hpfcdj:comp.sys.hp / bb@reef.cis.ufl.edu (Brian Bartholomew) / 11:41 pm  Nov  1, 1990 /

>> How about having xterm itself make the mods to the tcsh's
>> environmental strings.  Does the environment scoping allow this?  Will
>> the programs the shell runs see the changed environment?

>> Xterm source that compiles under this environment should not be
>> impossible to get.

No can do.  The environment for a process cannot be accessed by any
other process.  Children inherit the environment from their parents
only because the child's initial environment is a copy of the parent's
environment (yeah, I know you can make the initial environment
different, but it's still a separate copy...).

If you really want to do something useful to xterm, modify it to send
a SIGWINDOW to the process group that is running under it.  If any
process in that group is smart enough to know what to do with a
SIGWINDOW, then you're in luck.  That means you'll have to hack up
tcsh to catch SIGWINDOW, query the terminal for its size, and set its
environment.  Ack!

Just use emacs in its own X window and avoid this whole mess :-).

							Rajeev
-------------------------------------------------------------------------------
Rajeev Jayavant (rajeev@hpfcla.hp.com)	      "Excuse me, I've lost my marbles"
Hewlett Packard - Graphics Technology Division        - P. Opus, [Bloom County]