Previously from Neil Zanella
>It would be nice if there was a generalized version of PipeRead called
>PipeReadString which worked as follows: the output of
>
>PipeReadString command.sh
>
>would be the output of the (shell script) command. However, unlike with
>PipeRead, this output would not be Exec'ed directly. Instead the output
>would appear in front of an Exec command as an argument. For example:
>
>Exec xterm -bg PipeReadString bg.sh -fg PipeReadString fg.sh
>
>The advantage of PipeReadString over PipeRead is that of readability.
>Only the parameters that do change can be the output of the shell
>script rather than the whole command. That way the Fvwm script can
>more easily document which parameters are subject to change and which
>ones are not.
As your second question implies, this kind of functionality is, IMHO,
better achieved using a preprocessor. Even better would be to use
FvwmTheme to define a colorset and perform a variable substitution in
an Fvwm function, as in:
AddToFunc StartXTerm I Exec xterm -bg $[bg.cs0] -fg $[fg.cs0]
All in all, it's a better way to have consistent control over colors.
I take advantage of the fact that xrdb cpp-preprocesses
.Xdefaults/.Xresources to do something similar to my resource files.
Still haven't gotten around to setting up FvwmTheme and colorsets in
my .fvwm2rc though.
--
mikehan_at_best.com http://www.best.com/~mikehan/
coffee achiever San Francisco, California
Unix *is* user friendly. It just happens to be very selective about who its
friends are.
--
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 Sat May 06 2000 - 20:07:22 BST