Len Philpot <[EMAIL PROTECTED]> writes:
> Is there a concise, authoritative guide to the proper syntax,
> organization and such of .fvwm2rc contents somewhere? What I see in the
> fvwm man page often conflicts with what's in the sample system.fvwm2rc
> file

Please point out the conflicts so that they can be repaired.

> Sorry if I sound frustrated, but I am...
...
> I can change the border widths and nothing ever happens.

There are 2 borderwidths, for windows and menus.

For menus, this works:

MenuStyle * BorderWidth 10

I suspect you are having problems with the borders on windows.
Perhaps you missed this in the man page:

              With  the  NoHandles style, the window does not get
              the handles in the window corners that are commonly
              used  to resize it.  With NoHandles, the width from
              the BorderWidth style is used.  By default,  or  if
              Handles  is  is  specified, the width from the HanĀ­
              dleWidth style is used.

So, if you have

 Style * NoHandles

Then this works:

 Style * BorderWidth 10

Otherwise, use this:

 Style * HandleWidth 10

> I'm rapidly reaching my frustration threshold before moving on to
> something else.
> 
> There has to be somewhere a definition of exactly what is and isn't
> allowed configuration-wise, where specific entries need to go,
> recommended order, syntax restrictions, case-sensitivity, etc., etc.
> 
> If anyone can help, I'd appreciate it. I really like the speed and small
> size of fvwm, but the appalling lack of documentation is about to
> convince me to look elsewhere...

Fvwm may be speedy and small, but the amount of configuration possible
is massive.  Hence the extremly large man page, and difficulty getting
started.

-- 
Dan Espen                           E-mail: [EMAIL PROTECTED]
444 Hoes Lane  Room RRC 1C-214      Phone: (732) 699-5570
Piscataway, NJ 08854
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to