[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 variables, then. However,
> this happens:
>
> Exec echo $fvwmdir
> ===> ${HOME}/.fvwm
> Exec echo $bindir
> ===> $fvwmdir/bin
>
> The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
> of course, SetEnv's not supposed to expand environment variables.
Some more possibly strange things:
SetEnv fvwmdir ${HOME}/.fvwm
ImagePath /usr/share/icons
ImagePath +:$fvwmdir/pixmaps
doesn't work either. However, using
SetEnv fvwmdir /home/viper/.fvwm
*does* work.
--
An Thi-Nguyen Le
|It may be better to be a live jackal than a dead lion, but it is better
|still to be a live lion. And usually easier.
| -- Lazarus Long
--
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 message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
