On Sat, May 04, 2013 at 03:49:42PM -0400, Dan Espen wrote: > Dominique Michel <dominique.mic...@vtxnet.ch> writes: > > > Hi, > > > > I am writing a font selector for fvwm-crystal with FvwmScript. > > Most of it work, but I didn't succeeded to use environment variables. > > > > Also thing like > > Set $PanelFont = (GetOutput {echo $[panel_font]} 1 -1) > >
I belive you could do something hackish like this if you don't want to patch for actual support. But you need to be a little more creative. First I belive GetOutput is excuting a shell command, so you may just need (GetOutput {echo $PANEL_FONT} 1 -1) this should work for the enviorment variables but not infostore (I'm hoping a new shell isn't spawned with a new enviorment). If this doesn't work my next thought is Use FvwmCommand with Echo (from fvwm) which can echo a string to your stderr ($HOME/.xsession-errors is common for this). Then parse the value from $HOME/.xsession-errors with grep/regex tools. This should work with either EnvVars or InfoStore since you can echo their values as well. The only issue I see with this portability as not everyone may have stderr of their Xserver redirected to $HOME/.xsession-errors jaimos