Hello,
Quoting Christopher A. Smith,
| What I noticed was this: When starting fvwm, telling it to preprocess the
| .fvwmrc with FvwmM4, the cosmetic configuration (borders, colors, etc.) was
| completely wrong (default values, methinks), but when I ran the .fvwmrc
| file generated by FvwmM4 through fvwm (i.e. fvwm -f "Read /tmp/fvwmrc..."
| or something like that), everything came up fine. Pathnames to modules,
| colors, borders, everything.
|
| This also happened with FvwmCpp.
Well I have such a setup for my Solaris/SunOs boxes.
It works just fine, except for the string of command line options needed in
my Solaris startup because the cpp is in a non-standard place and the makefile
didn't figure it out/isn't setup to figure it out?.
Here is the .fvwmrc clip:
#ifdef SOLARIS
ModulePath /home/jon/Fvwm/solaris/
#else
ModulePath /home/jon/Fvwm/sunos/
#endif
and here is a bit from my .xinitrc:
if [ x$sysv = xYES ]
then
# SOLARIS
Fvwm/solaris/fvwm -f "/home/jon/Fvwm/solaris/FvwmCpp -Cppprog /usr/ccs/lib/cpp
-Cppopt -DSOLARIS /home/jon/.fvwm2rc"
else
# SUNOS
Fvwm/sunos/fvwm -f "/home/jon/Fvwm/sunos/FvwmCpp /home/jon/.fvwm2rc"
fi
Jon
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Nov 17 1995 - 08:43:59 GMT