>> On Fri, 17 Nov 1995 09:11:40 -0500 (EST),
>> Christopher A Smith(C) wrote:
C> What I noticed was this: When starting fvwm, telling it to preprocess the
C> .fvwmrc with FvwmM4, the cosmetic configuration (borders, colors, etc.) was
C> completely wrong (default values, methinks), but when I ran the .fvwmrc
C> file generated by FvwmM4 through fvwm (i.e. fvwm -f "Read /tmp/fvwmrc..."
C> or something like that), everything came up fine. Pathnames to modules,
C> colors, borders, everything.
I've seen something similar when restarting fvwm -- perhaps that bug
is related to this one.
Anyway, in my .fvwmrc I have lines like
# Font selection -- can be conditionalized via CPP or M4.
#FvwmM4 -m4-prefix ".fvwm/fonts-m4"
#Read ".fvwm/fonts"
FvwmCpp ".fvwm/fonts-cpp"
and that works fine (fonts-cpp is appended below). Maybe you can
strucuture your .fvwmrc to work around this bug. Personally, I like
having a .fvwm directory, with files categorized by function within
it, but I know some don't care for it.
-mb-
/*
Window and icon fonts
*/
#if Y_RESOLUTION >= 3700
#define WINDOWFONT -adobe-times-bold-r-*-*-18-*-*-*-*-*-*-*
#define ICONFONT -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
#else
#define WINDOWFONT -adobe-times-bold-r-*-*-16-*-*-*-*-*-*-*
#define ICONFONT -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
#endif
WindowFont WINDOWFONT
IconFont ICONFONT
--
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 - 11:37:16 GMT