%% Neil Zanella <nzanella_at_cs.mun.ca> writes:
nz> Your first suggestion:
nz> "I" Exec xterm -fg `fg.sh` -bg `bg.sh`
nz> does work for me. I should have thought of it. It seems to me
nz> that with the current implementation of Exec I can follow exec by
nz> any shell command I want so long as it does not use environment
nz> variables.
Why can't it use environment variables? You may need to quote the $ to
get fvwm to ignore it, I can't remember if it will do something with $
variables or not.
Any valid shell command is OK for Exec, including ones that reference
environment variables. But, the variables are expanded by the shell
that Exec invokes, not by FVWM before it's invoked.
nz> As to your second suggestion:
nz> PipeRead "echo Exec xterm -bg `bg.sh` -fg `fg.sh`"
nz> This also works. For the particulr problem I posed the first
nz> solution is a little bit cleaner but your second solution shows
nz> that PipeRead is even more powerful than I thought eliminating the
nz> need for a generalized version. Thanks! Keep up the good work!
PipeRead isn't any more or less powerful; it's invoking a shell. Shells
are _very_ powerful :). Any shell operations are valid in a PipeRead
command. The `` is being expanded by the shell that FVWM runs, not by
the PipeRead builtin. You probably grok that, I'm just making it clear
in case someone else is confused...
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue May 09 2000 - 18:56:40 BST