SetEnv not expanding environmental variables itself

Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these variables, then. However, this happens: Exec echo $fvwmdir

Re: SetEnv not expanding environmental variables itself

[An Thi-Nguyen Le - Thu, 10 May 2001 09:50:34 AM CDT] Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these

Re: SetEnv not expanding environmental variables itself

An Thi-Nguyen Le [EMAIL PROTECTED] writes: Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these variables, then.

Re: SetEnv not expanding environmental variables itself

[Dan Espen - Thu, 10 May 2001 10:14:34 AM CDT] Use the notation: Exec echo $[bindir] Ah. Okay. Never mind... Embarassed... -- An Thi-Nguyen Le -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a

Re: SetEnv not expanding environmental variables itself

On 10 May 2001 09:49:41 -0500, An Thi-Nguyen Le wrote: Maybe this is documented somewhere. Yes, in the man page. Enter /environment and press 'n' several times. You will find everything you wanted to know, including the fact that only 3 commands ImagePath, ModulePath and Restart expand