kvarga01_at_fiu.edu said:
> What I mean is that the .xsession or .xinitrc or WHATEVER that calls
> fvwm2 is simply a shell script, and if you set environments within
> that shell script, fvwm2 should make those environments available to
> the programs that fvwm2 starts... Currently, only a few environments
> are made available to programs... $HOME, $PATH, $LD_LIBRARY_PATH, and
> a few other vital ones...
Is that true? My understanding was that all environment variables got passed
on (so long as the shell which runs .xsession or whatever exports them, of
course). Is this not true? Does fvwm2 *really* pick and choose which
variables to pass on?
What's more likely is that the person is running xdm, which runs .xsession,
and so never actually runs csh at all until they get an xterm up. So the
environment variables exist in the xterms, but not in anything else, and in
particular not in fvwm2 and modules. The trick there is to ensure that the
variables are set (and exported) in .xsession or .xinitrc.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed May 14 1997 - 04:24:43 BST