I tried recently to use FvwmCpp to process my .fvwmrc (I didnot want
m4 because of the 'include' mess).
- First problem, I could not get FvwmCpp to work at all. I guess I
did not use the good options, and would be pleased if someone told me
what to do...
So, what I have done now is to convert my .fvwmrc to use cpp, which is
applied manually each time I make a change :-( Nevertheless, I had
several problems:
- the use of # as a comment delimiter for fvwm conflicts with cpp. I
had to insert a space in front of the comments, which is not very
nice. I'd like to see an alternate comment delimiter in fvwm.
- Since I use a sun, all the references to pixmap xterm-sun.xpm has
been replaced with xterm-1.xpm :-( No problem, I thought, I've just to
enclose the pixmap name in quotes. This does *not* work! This is
contradictory with the man page of fvwm which basically says that
quotes can be used anywhere.
- And, finally, something that I've already written (but since I had
no echo, I could perhpas repeat it): I'd like to have the default
ModulePath hardcoded in fvwm, in order to use 'fvwm -f' in a simple
manner (It should be easy, since this info is known to the Imakefile).
Jean-Marc.
PS: On a related subject, does somebody knows of a clever way to use
cpp on the .Xdefaults file transparently?
--
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 Tue Oct 17 1995 - 08:50:32 BST