FVWM: Re: FvwmCpp, quotes and .fvwmrc.

From: Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes_at_inria.fr>
Date: Wed, 18 Oct 1995 10:45:40 +0100

>>>>> "mb" == Mark Borges <mdb_at_cdc.noaa.gov> writes:

>>> On Tue, 17 Oct 1995 14:50:21 +0100, Jean-Marc Lasgouttes(J)
>>> wrote:
    J> - the use of # as a comment delimiter for fvwm conflicts with
    J> cpp. I had to insert a space in front of the comments, which is
    J> not very nice. I'd like to see an alternate comment delimiter
    J> in fvwm.

    mb> Since cpp strips comments by default, you could use C style
    mb> comments (/* comment */) in your .fvwmrc as well, since fvwm
    mb> will never see them.

Thats a good idea.

    J> PS: On a related subject, does somebody knows of a clever way
    J> to use cpp on the .Xdefaults file transparently?

    mb> I'm not sure I understand -- xrdb invokes cpp on the
    mb> .Xdefaults file by default. Is something besides xrdb used to
    mb> get your .Xdefaults into the X database?

>From what I read in the X man page, xrdb is not used to read
.Xdefaults. In fact, only the #include directive is recognized, but it
seems to be a hack. It is easy to check that if I edit my .Xdefaults
to add some cpp-isms, my apps complain about their resources. If there
is some kind of magic option somewhere to force the use of xrdb, I'd
like to know about it.

Jean-Marc.




--
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 Wed Oct 18 1995 - 04:46:04 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:57 BST