======================================================================
                   FVWM Frequently Asked Questions
======================================================================

INDEX

        1) What does FVWM stand for?
        2) Where do I find the current versions of fvwm?
        3) Any WWW Sites about FVWM?
        4) Where do I ask questions about FVWM?
        5) What are the differences between FVWM 1.xx and 2.xx?
        6) My .fvwmrc from version 1.xx no longer works.  What do I do?
        7) I have a window that is behaving unexpectedly under FVWM, but just
           fine under (whatever other window manager), or I have just some
           random bug.  What do I do?
        8) What's the relative memory usage for the various window managers
           out there?
        9) I used to use GoodStuff in FVWM 1.xx, but it's not in the 2.xx
           distribution.  What do I use now?
       10) I'm using FvwmButtons (or GoodStuff in 1.xx), and sometimes the
           buttons stay depressed, and other times they don't.  Why is that?
       11) What happened to the FVWM 1.xx 'include' command?
       12) I really like the horizontal bars that appear on the title bars of
           sticky windows.  Can I get those on other windows as well?
       13) I'm trying to build FVWM, but the linker is complaining about
           missing functions like 'XpmReadFileToPixmap'.  Why is that?
       14) I'm trying to compile FVWM under SunOS using cc, but the compiler
           is having lots of problems.  What gives?
       15) Why does the screen go blank at startup and during Recaptures now
           when it didn't in FVWM 1.xx?

======================================================================


1) What does FVWM stand for?

A: "Fill_in_the_blank_with_whatever_f_word_you_like_at_the_time
   Virtual Window Manager".  Rob Nation (the original Author of FVWM)
   doesn't really remember what the F stood for origninally, so we
   have several potential answers:

     Feeble, Fabulous, Famous, Fast, Foobar, Fantastic, Flexible,
     F!@#$%, FVWM (the GNU recursive approach), Free, Final, Funky,
     Fred's (who the heck is Fred?), etc.

   Just pick your favorite (which will of course change depending on
   your mood and whether or not you've run across any bugs recently).
   I prefer Fabulous myself.

----------------------------------------------------------------------

2) Where do I find the current versions of fvwm?

A: New main distribution site (official + beta code):
                ftp://ftp.hpc.uh.edu/pub/fvwm

   Alternate sites:

            USA:
                ftp://sunsite.unc.edu/pub/Linux/X11/window-managers/
                ftp://ftp.cs.columbia.edu/pub/cheah/

            Overseas:
                ftp://unix.hensa.ac.uk/pub/walnut.creek/FreeBSD/incoming/
                ftp://ftp.jussieu.fr/pub/X11/fvwm/
                ftp://ftp.loria.fr/pub/unix/fvwm/

   BTW, 1.24r was the last released version of the 1.xx series and the
   first official release of 2.xx will be 2.1.0.

----------------------------------------------------------------------

3) Any WWW Sites about FVWM?

A: Yup.  Try the following (note - the first one has changed recently):

        http://www.cs.hmc.edu/~tkelly/docs/proj/fvwm.html
        http://www.ssc.com/~roland/fvwm/fvwm.html
        http://xenon.chem.uidaho.edu/~fvwm/
        http://namu19.gwdg.de/fvwm/fvwm.html

----------------------------------------------------------------------

4) Where do I ask questions about FVWM?

A: If your local FVWM maintainer can't help you, then the newsgroup
   comp.windows.x.apps is a good place, but the fvwm mailing list is
   usually better.  The new FVWM discussion mailing list address is:

                           fvwm@hpc.uh.edu

   And there is an announce mailing list as well:

                       fvwm-announce@hpc.uh.edu

   They are maintained by Jason Tibbitts.  Here's the descriptions and
   instructions directly from him:

   =================================================================
   (fvwm)

   Description
   -----------
   
   This list is for discussion relating to the FVWM window manager,
   which is intended to have a small memory footprint and a rich
   feature set, be extremely customizable and extendable and have a
   high degree of Motif mwm compatibility.  All relevant discussion is
   encouraged.  Posting of binaries or irrelevant discussion is
   strongly frowned upon.  Posting of short patches (less than 200
   lines) is acceptable, but all patches should be sent to the FVWM
   maintainer for inspection and possible inclusion in the
   distribution.  The current maintainer is
   
   Charles Hines <chuck_hines@VNET.IBM.COM>
   
   
   Instructions
   ------------
   
   To send a message to the list, mail to fvwm@hpc.uh.edu.  For help
   on dealing with the mailing list software (for getting the archives
   or other files which may be made available) send the message "help"
   to majordomo@hpc.uh.edu.  If you have problems with the mailing
   list itself and need to talk to a human, send mail to
   fvwm-owner@hpc.uh.edu.  This address is for mailing list issues
   only; reports on the FVWM software will be sent to /dev/null.
   
   Archives of previous messages are available; to get them send the
   above mentioned help message and investigate the "index" and "get"
   commands or ftp them from ftp.hpc.uh.edu in /pub/fvwm/list-archive.
   
   
   (fvwm-announce)
   
   This list is for announcements relating to the FVWM window manager,
   which is intended to have a small memory footprint and a rich
   feature set, be extremely customizable and extendable and have a
   high degree of Motif mwm compatibility.
   
   Replies to messages from this list are set by default to go the
   FVWM discussion list, fvwm@hpc.uh.edu.
   
   The current FVWM distribution is available for ftp at
   ftp.hpc.uh.edu in /pub/fvwm.
   =================================================================

----------------------------------------------------------------------

5) What are the differences between FVWM 1.xx and 2.xx?

A: A lot.  To name a few general ones:
        - Bugfixes.  1.xx is not worked on at all any more.
        - Better rc file format.  No longer order dependent.
        - More flexible and powerful.  For example, many previously
          global options now operate on a per window group level
          instead.
        - More and better modules.
        - OpaqueResize is gone.
        - M4 preprocessing is no longer part of the fvwm exec, but
          rather has been moved to a module.  There is also a module
          to use cpp too.  See the FvwmM4 and FvwmCpp man pages.

----------------------------------------------------------------------

6) My .fvwmrc from version 1.xx no longer works.  What do I do?

A: Start with a new one or convert your old one.  This can be done by
   hand or with a little help from the 'conversion_script' in the
   sample.fvwmrc directory.

   And here is a list of rc file command changes compiled by Makoto
   'MAR_kun' MATSUSHITA <matusita@ics.es.osaka-u.ac.jp>.  It may or
   may not be 100% accurate or complete, especially as changes evolve,
   but it's a good start.

   ** Fvwm-1.xx commands **                   ** Fvwm-2.xx equiv **
   
   AppsBackingStore                           (obsoleted)
   AutoRaise delay                            (obsoleted, use FvwmAuto)
   BackingStore                               (obsoleted)
   BoundaryWidth Width                        Style (BorderWidth width)
   ButtonStyle button# WidthxHeight           <-
   CenterOnCirculate                          (obsoleted)
   CirculateSkip windowname                   Style (CirculateSkip)
   CirculateSkipIcons                         Style (CirculateSkipIcon)
   ClickTime delay                            <-
   ClickToFocus                               Style (ClickToFocus)
   Cursor  cursor_num cursor_type             (obsoleted)
   DecorateTransients                         Style (DecorateTransient)
   DeskTopScale Scale                         (obsoleted, use FvwmPager)
   DeskTopSize HorizontalxVertical            <-
   DontMoveOff                                (obsoleted)
   EdgeResistance scrolling moving            <-
   EdgeScroll horizontal vertical             <-
   Font fontname                              MenuStyle (arg4)
   Function FunctionName                      AddToFunc (not compatible)
   HiBackColor colorname                      HilightColor (arg1)
   HiForeColor colorname                      HilightColor (arg2)
   Icon windowname bitmap-file                Style (Icon iconname-file)
   IconBox left top right bottom              Style (IconBox l t r b)
   IconFont fontname                          <-
   IconPath path                              <-
   Key keyname Context Modifiers Function     <-
   Lenience                                   Style (Lenience)
   MenuBackColor colorname                    MenuStyle (arg2)
   MenuForeColor colorname                    MenuStyle (arg1)
   MenuStippleColor colorname                 MenuStyle (arg3)
   Module ModuleName                          <-
   ModulePath path                            <-
   Mouse Button Context Modifiers Function    <-
   MWMBorders                                 Style (MWMBorder)
   MWMButtons                                 Style (MWMButtons)
   MWMDecorHints                              Style (MWMDecor)
   MWMFunctionHints                           Style (MWMFunctions)
   MWMHintOverride                            Style (HintOverride)
   MWMMenus                                   MenuStyle (arg5)
   NoBorder windowname                        Style (NoBorder)
   NoBoundaryWidth Width                      Style (HandleWidth width)
   NoPPosition                                Style (NoPPosition)
   NoTitle windowname                         Style (NoTitle)
   OpaqueMove percentage                      OpaqueMoveSize percentage
   OpaqueResize                               (obsoleted, use FvwmPager)
   Pager  X_Location Y_Location               (obsoleted, use FvwmPager)
   PagerForeColor colorname                   (obsoleted, use FvwmPager)
   PagerBackColor colorname                   (obsoleted, use FvwmPager)
   PagerFont fontname                         (obsoleted, use FvwmPager)
   PagingDefault pagingdefaultvalue           (obsoleted)
   PixmapPath path                            <-
   Popup PopupName                            AddToMenu (not compatible)
   RandomPlacement                            Style (RandomPlacement)
   SaveUnders                                 (obsoleted)
   SloppyFocus                                Style (SloppyFocus)
   SmartPlacement                             Style (SmartPlacement)
   StartsOnDesk windowname desk-number        Style (StartsOnDesk desk-number)
   StaysOnTop windowname                      Style (StaysOnTop)
   StdBackColor colorname                     Style (BackColor color)
   StdForeColor colorname                     Style (ForeColor color)
   StickyBackColor colorname                  (obsoleted)
   StickyForeColor colorname                  (obsoleted)
   Sticky windowname                          Style (Sticky)
   StickyIcons                                Style (StickyIcon)
   StubbornIcons                              (obsoleted)
   StubbornIconPlacement                      (obsoleted)
   StubbornPlacement                          (obsoleted)
   Style windowname options                   <-
   SuppressIcons                              Style (NoIcon)
   WindowFont fontname                        <-
   WindowListSkip windowname                  Style (WindowListSkip)
   XORvalue number                            <-
                                              
   ** fvwm-1 built-in functions ***           
                                              
   Beep                                       <-
   CirculateDown [ name window_name ]         Next (not compatible)
   CirculateUp [ name window_name ]           Prev (not compatible)
   Close                                      <-
   CursorMove horizonal vertical              <-
   Delete                                     <-
   Desk arg1 arg2                             <-
   Destroy                                    <-
   Exec name command                          <-
   Focus                                      <-
   Function                                   <-
   GotoPage  x y                              <-
   Iconify [ value ]                          <-
   Lower                                      <-
   Maximize [  horizontal vertical ]          <-
   Module name ModuleName                     Module ModuleName
   Move [ x y ]                               <-
   Nop                                        <-
   Popup                                      <-
   Quit                                       <-
   Raise                                      <-
   RaiseLower                                 <-
   Refresh                                    <-
   Resize [ x y ]                             <-
   Restart  name WindowManagerName            <-
   Stick                                      <-
   Scroll horizonal vertical                  <-
   Title                                      <-
   TogglePage                                 (obsoleted)
   Wait name                                  <-
   Warp [ name window_name ]                  Next or Prev (not compatible)
   WindowsDesk new_desk                       <-
   WindowList arg1 arg2                       <-
   
   *** New in fvwm-2 **
   
   Destroy
   DestroyMenu
   KillModule
   Menu menu-name double-click-action
   Next [conditions] command
   None [arguments] command
   Prev [conditions] command
   Read filename
   Recapture
   +

----------------------------------------------------------------------

7) I have a window that is behaving unexpectedly under FVWM, but just
   fine under (whatever other window manager), or I have just some
   random bug.  What do I do?

A: First, check your rc file and your .Xdefaults to make sure that
   something blatantly obvious in there isn't causing the problem,
   plus check the FAQ, BUGS, TO-DO, and man pages (i.e. RTFM).

   If you still can't figure it out, send a DETAILED description of
   the problem to the FVWM mailing list.  By detailed I mean more than
   just "my window isn't behaving right" or "I found a bug":

        - Describe the problem as best you can
        - If applicable, include information from:
                xwininfo
                xprop
                FvwmIdent
                xdpyinfo (maybe)
        - What OS & version you are running under
        - What version of X11 are you running under
        - What exact version of FVWM you are running
        - How was FVWM compiled (compiler & version, options, etc)

----------------------------------------------------------------------

8) What's the relative memory usage for the various window managers
   out there?

A: Here's a little table comparing some of them.  It was done on an
   AIX based IBM RS6000 model 355 using the same number of windows (3)
   and XSession to switch between the window managers, and I used
   'top' to show the values:

      SIZE   RES
      545K  652K fvwm2 (fvwm 2.0-pl35)
      457K  528K fvwm  (fvwm 1.24rb)
      856K  960K ctwm  (ctwm 3.2p1)
     1004K 1156K mwm   (mwm 1.2)
      543K  632K twm   (???)
      263K  328K aixwm (a simple ugly window manager included w/ aix)

----------------------------------------------------------------------

9) I used to use GoodStuff in FVWM 1.xx, but it's not in the 2.xx
   distribution.  What do I use now?

A: GoodStuff was renamed to FvwmButtons.  Same module, new name (that
   fits in with the other modules naming convention).

----------------------------------------------------------------------

10) I'm using FvwmButtons (or GoodStuff in 1.xx), and sometimes the
    buttons stay depressed, and other times they don't.  Why is that?

A: This may be the biggest RTFM answerable question that we get on the
   mailing list!  But, since it is always asked anyways, I'll put it
   here.  From the FvwmButtons man page:

       If command is an fvwm Exec command, then the button
       will remain pushed in until a window whose name or
       class matches the qouted portion of the command is
       encountered. This is intended to provide visual
       feedback to the user that the action he has requested
       will be performed. If the qouted portion contains no
       characters, then the button will pop out immediately.
       Note that users can continue pressing the button, and
       re-executing the command, even when it looks "pressed
       in."

----------------------------------------------------------------------

11) What happened to the FVWM 1.xx 'include' command?

A: It was actually part of the M4 preprocessing (see above).  You can
   use the 'Read' builtin to get the same effect, or use the M4
   module.

----------------------------------------------------------------------

12) I really like the horizontal bars that appear on the title bars of
    sticky windows.  Can I get those on other windows as well?

A: Nope.  Maybe in the future, but not right now.  Unless you modify
   the code yourself, that is (which several people have for this).

----------------------------------------------------------------------

13) I'm trying to build FVWM, but the linker is complaining about
    missing functions like 'XpmReadFileToPixmap'.  Why is that?

A: You need to have the Xpm library on your system.  You can find the
   source for it at ftp.x.org in /contrib/libraries.  Or you can
   compile without Xpm support (see the configure.h file) and lose
   out on all the pretty color icons.  If you want more color icons,
   grab the ones out of the ctwm distribution (also at ftp.x.org)
   which has a lot of nice ones.

----------------------------------------------------------------------

14) I'm trying to compile FVWM under SunOS using cc, but the compiler
    is having lots of problems.  What gives?

A: cc under SunOS is not an ANSI C compiler.  Try using acc or gcc
   instead.

----------------------------------------------------------------------

15) Why does the screen go blank at startup and during Recaptures now
    when it didn't in FVWM 1.xx?

A: Rob put it in there for the following reason:

   Rob> Actually, I thought that this would make things happen more
   Rob> quickly/smoothly.  While fvwm is adding borders, it keeps
   Rob> raising and lowering and reparenting windows, which means that
   Rob> they get lots of expose events, and they redraw a lot, many
   Rob> times unnecessarily, because they soon get hidden again. I
   Rob> thought that the single black window covering everything would
   Rob> keep these windows from getting unneede expose events, and
   Rob> minimize redraws.

   Which makes a lot of sense.

   I've shut it off by default now.  Use the command line option
   -blackout to enable it.

----------------------------------------------------------------------


