On 7/12/07, Ryan Daly <[EMAIL PROTECTED]> wrote:
Hans Voss said:
> You CAN actually use them in shells and all other programs started
> from FVWM. (FVWM is the parent and propagates its environment to its
> children).
>
> I even use fvwm to set some environment variables for my shells
> instead of in .bashrc or some-such.
I have converted my config to use the FVWM SetEnv instead of via .cshrc
or the like.
One issue I appear to be having, though, is that when the root user logs
in, I do not see the various environment variables if I issue an 'env'.
However, I do feel they're getting set because various settings
(ImagePath for one) relies on these environment variables.
Is there any reason why root wouldn't see these variables?
If the vars are set by a user then root can't see them, and the same
applies the other way round. (I guess, can't test that now..)
Renato
