FVWM: Re: FvwmCpp

From: Mark Borges <mdb_at_cdc.noaa.gov>
Date: Thu, 12 Oct 1995 12:04:31 -0600

>> On Thu, 12 Oct 1995 09:49:51 -0700 (PDT),
>> Gail Mara Gurman(G) wrote:
G> However, I still think the default should be the value of CPP in
G> the Makefile.
Good idea.

G> Meanwhile, Mark's suggestion isn't working. I created a file called
G> .fvwm-styles with one line:

G> #define INFO NoTitle, NoHandles, Sticky, WindowListSkip, BorderWidth 0

G> I call it in .fvwmrc like this just before my Style assignments:

G> FvwmCpp .fvwm-styles

G> The result is the following message:

G> fvwm: bad style command: INFO

G> Am I missing something?

Yes. This isn't what I suggested :-).

The CPP define *must* go in the same file that contains the
styles. You have to split off the styles from the rest of you .fvwmrc
file. All your style directives should be moved to .fvwm-styles (or
whatever you use).

What's happening to you is that FvwmCpp reads the #define INFO
performs any expansions (none) in your case, and then passes the
result to fvwm (comment lines in your case). Subsequently, INFO is not
defined for the rest of your .fvwmrc file, you try to use it, and fvwm
issues the error.

  -mb-
--
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 Thu Oct 12 1995 - 13:00:55 BST

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