"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "WindowMaker-0.92.0/FAQ" of archive WindowMaker-0.92.0.tar.gz:


As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
    1 
    2 WindowMaker FAQ
    3 ====================================================================
    4 Last modified: Tue Apr 20 20:15:17 EST 1999
    5 
    6 the latest info can be found at
    7 http://www.dpo.uab.edu/~grapeape/wmfaq.html or
    8 http://wm.current.nu/wmfaq/
    9 --------------------------
   10 
   11 Summary of Contents:
   12 
   13 1 - Introduction 
   14      1.1 What is Window Maker? 
   15      1.2 Where can I get Window Maker? 
   16      1.3 Where are the mailing list archives? 
   17      1.4 Where is more documentation on configuring Window Maker? 
   18      1.5 What is an App Icon? 
   19      1.6 How can I get a question added to the FAQ? 
   20      1.7 How do I report bugs? 
   21      1.8 Is there an anomymous cvs server? 
   22 
   23 2 - Installation 
   24      2.1 Where can I get proplist.h? 
   25      2.2 Why do no icons show up after installing Window Maker 0.15.0
   26          when I've followed all the directions? 
   27      2.3 How do I get libtiff to work? 
   28      2.4 How do I get libjpeg to work? 
   29      2.5 How do I get libpng to work? 
   30      2.6 How do I get libgif (or libungif) to work? 
   31      2.7 Does wmsound work with 0.1x.x? 
   32      2.8 Can I use WindowMaker with KDE or GNOME or CDE? 
   33      2.9 How do I get Window Maker working with xdm in Redhat 5.[01]? 
   34      2.10 Do I need to rerun wmaker.inst with every new version of
   35           Window Maker? 
   36      2.11 When I install Window Maker, I've used wmaker.inst correctly
   37           and I only get aroot menu with xterm and exit. How do I fix this? 
   38      2.12 How do I get Window Maker to use more than 16 colors on my
   39           SGI Indy Workstation? 
   40      2.13 Using WindowMaker with Solaris 2.6 CDE 
   41      2.14 How do I switch CDE's windowmanager to use Window Maker?
   42      2.15 When I run wmaker it quits complaing about something
   43           "__register_frame_info".
   44      2.16 When I run wmaker it complains about something like library is
   45      	  62, caller expects 61
   46 
   47 3 - Usage 
   48      3.1 How do I get new apps on the dock (The line of pixmaps on the
   49          right side of the screen by default) 
   50      3.2 What is the difference between the Exit and Exit Session Option?
   51      3.3 How do I "dock" AppIcons on the Clip? 
   52      3.4 Why do none of my Key Bindings work in Window Maker 0.1x.x 
   53      3.5 How do I rename workspaces? 
   54      3.6 How can I resize a window if the window is larger than my currect
   55          desktop? 
   56      3.7 How do I "undock" AppIcons? 
   57      3.8 I docked an application but when I run it the button is permanently
   58 	 shaded and I can't run new instances.
   59      3.9 When I run wmaker it complains about not being able to load any
   60      	 fonts.
   61      3.10 When I set the root background with wmsetbg by hand it works,
   62      	 but when I do that from the configuration files it doesnt!
   63 
   64 4 - Configuration 
   65      4.1 What are those files inside my ~/GNUstep directory? 
   66      4.2 How do I enable the normal X sloppy focus mode? 
   67      4.3 How do I get my auto-arrange icons to work? 
   68      4.4 How do I get my Meta-Tab to cycle through windows correctly? 
   69      4.5 How can I define my own Icon for a program? (instead of the Icon
   70          the Application Supplies?) 
   71      4.6 How do I get a pixmap background for my appicons (those things
   72          in the dock)? 
   73      4.7 How do you dock <insert program here> that doesn't have an
   74          appicon in the new version of Window Maker? 
   75      4.8 How do I get x11amp to not have a title bar? (or any other
   76          program for that matter?) 
   77      4.9 How do I set a pixmap background? 
   78      4.10 Can I put pixmaps in my root menu and title bars? 
   79      4.11 How do I get my Minimize Icon to look like the triangle I see in
   80           screenshots? 
   81      4.12 How do I get superfluous bells and whistles working? 
   82      4.13 How do I get my oldstyle back? 
   83      4.14 How do I get the window menu with only a two button mouse? 
   84      4.15 How do I edit my root menu? 
   85      4.16 How can I set dock/clip to use single click to launch applications,
   86    	  instead of double click?
   87 
   88 5 - Other Applications 
   89      5.1 How do I assign gimp an appicon? 
   90      5.2 How do I get an appicon for XEmacs 20.3+? 
   91      5.3 Where do you get that clock program I always see on people's
   92          desktops? 
   93      5.4 How do you dock asclock? 
   94      5.5 How do you dock wmload? 
   95      5.6 What other apps exist for the dock? 
   96      5.7 How do I get an appicon for rxvt so I can dock it? 
   97      5.8 How do I get different icons for rxvt's (or xterms) running different
   98          programs?
   99      5.9 How do I launch multiple instances of XTerm from one appicon? 
  100      5.10 How do I allow Alt+# to work in an rxvt session? (with irc for
  101           example) 
  102      5.11 Window Maker breaks scilab
  103      5.12 Netscape icons show up in black and white
  104      5.13 Snow flakes from xsnow don't acumulate on titlebars!
  105      5.14 I'm using RedHat 6.0 and Netscape dies without reason.
  106 
  107 6 - Programming 
  108      6.1 How do I get a normal X application to produce an appicon? 
  109      6.2 How do I get my tcl/tk application to produce an appicon? 
  110      6.3 What is WINGs? 
  111      6.4 Where can I get more information about WINGs?
  112 
  113 7 - Miscellaneous Questions 
  114      7.1 Is there a pager for Window Maker? 
  115      7.2 Can I have folders like in AfterStep? 
  116      7.3 How do I use getstyle and setstyle? 
  117      7.4 Why don't you distribute {normal diff, xdelta} patches?
  118      7.5 Will you add GNOME support?
  119 
  120 8 - Themes 
  121      8.1 What exactly are Themes? 
  122      8.2 How do I install a Theme? 
  123      8.3 How do I make a Theme? 
  124 
  125 
  126 ========================================================================
  127 
  128 
  129 
  130 -=-=-=-=-=-=-
  131 Introduction:
  132 -=-=-=-=-=-=-
  133 
  134 1.1 What is Window Maker? 
  135 ----------------------------------
  136 Window Maker is an elegant X11 window manger that emulates the
  137 OpenStep desktop with some noticeable enhancements. Look at
  138 http://wm.current.nu/themes/my-themes.html and
  139 http://wm.current.nu/themes/screenshots.html
  140 here for example screenshots. 
  141 
  142 
  143 1.2 Where can I get Window Maker? 
  144 ----------------------------------
  145 The official site to get new developmental versions from is
  146 ftp://ftp.windowmaker.org/pub/beta/srcs/. 
  147 
  148 NOTE: Also see http://wm.current.nu/downloads.html for the latest 
  149 Stable and Development versions. 
  150 
  151 The development versions are usually very stable themselves, so if you
  152 want to have all the newest features, you can rather safetly go with the
  153 development versions. Just remember to save any unsaved data before
  154 you go playing around with the config files. Also, remember they are
  155 developmental versions, so your mileage may vary, don't get angry if they
  156 crash. 
  157 
  158 
  159 1.3 Where are the mailing list archives? 
  160 ----------------------------------------
  161 Phillip Smith from Netplex, our wonderful provider of windowmaker.org, has set
  162 up some new lists from the domain.  Please read the information on the web
  163 pages at http://www.windowmaker.org/lists.html for information on how to
  164 subscribe, the posting guidelines, and how to access the web archives.
  165 
  166 Many thanks to Ed Orcutt who hosted the original lists from his own machine
  167 for many years and Caldera who graciously allowed Ed to continue hosting
  168 from them when he moved to his new position with them.  Ed provided a very
  169 valuable service for many years and we are sad to see him go.
  170 
  171 
  172 1.4 Where is more documentation on configuring Window Maker? 
  173 ----------------------------------
  174 Besides the mailing list archives, there are nice documents in
  175 ftp://ftp.windowmaker.org/pub/docs/, at
  176 http://wm.current.nu/downloads.html on my download page and at 
  177 http://wm.current.nu/user-guide/index.htm in the online user-guide. 
  178 
  179 
  180 1.5 What is an appicon? 
  181 ----------------------------------
  182 An appicon is the icon (without the tiny titlebar a minimized application icon
  183 has) produced by most applications that initially is in the bottom left corner
  184 of the screen while an application is running. For an example, run xterm and
  185 notice the icon in the corner. (Make sure that you use xterm and not a
  186 default older rxvt because older versions of rxvt do not properly set their
  187 window attributes.) 
  188 
  189 
  190 1.6. How can I get a question added to the FAQ? 
  191 ----------------------------------
  192 Right now, the only method is to mail Chris Green <sprout@dok.org> or
  193 myself <largo@current.nu> the question or post it on the Window Maker
  194 Mailing list, and see if enough people have the same problem. 
  195 
  196 If you are a developer and would like to be able to edit the official FAQ on
  197 Chris's site, let him know at <sprout@dok.org>
  198 
  199 He is currently pondering writing a front end that allows everyone to add
  200 entries and only require a moderator approval before being posted. 
  201 
  202 
  203 1.7. How do I report bugs? 
  204 ----------------------------------
  205 You can look at the BUGFORM file in your tarball of Window Maker.
  206 Alternatively, you can use the Window Maker Bugtracker at
  207 http://windowmaker.org/cgi-bin/bugs. 
  208 
  209 
  210 1.8. Is there an anomymous cvs server? 
  211 ----------------------------------
  212 Yes there is. To check out from cvs, first 
  213 
  214             export CVSROOT=":pserver:anoncvs@cvs.net-community.com:/gnustep"
  215             cvs login
  216           
  217 'anoncvs' is the password. 
  218 
  219 Then issue the command. "wm" is the name of the module. 
  220 
  221             cvs -z3 checkout -d WindowMaker wm
  222           
  223 
  224 To update your source tree, cd to the WindowMaker directory and type 
  225 
  226             cvs -z3 update 
  227           
  228 inside the WindowMaker directory. 
  229 
  230 
  231 
  232 
  233 -=-=-=-=-=-=-
  234 Installation:
  235 -=-=-=-=-=-=-
  236 
  237 2.1 Where can I get libPropList/proplist.h?
  238 -------------------------------------------
  239 starting with Window Maker 0.70.0, libPropList is no longer needed.
  240 It was obsoleted by adding property list handling code to the WINGs library.
  241 
  242 
  243 
  244 2.2 Why do no icons show up after installing Window Maker >= 0.15.x 
  245     when I've followed all the directions? 
  246 -------------------------------------------------------------------
  247 Under normal circumstances, this should not happen because Window Maker
  248 should detect if libtiff is going to be compiled in and then it will make the
  249 default theme use .tiff or .xpm icons, depending if TIFF support is compiled
  250 in or not.
  251 
  252 As of Window Maker version 0.15.0, the default setup includes .tiff icons
  253 which require you to have compiled Window Maker with libtiff support, if you
  254 want them to be used. If you are happy with the .xpm icons, then you don't
  255 need libtiff. Window Maker will detect that TIFF support is not available and
  256 use .xpm icons instead. For some help on compiling with libtiff, look at the
  257 libtiff section of this FAQ. 
  258 
  259 
  260 2.3 How do I get libtiff to work? 
  261 ----------------------------------
  262 The whole key to getting libtiff working for me was to upgrade to >=
  263 tiff-v3.4beta037-tar.gz availible at ftp.sgi.com. 
  264 
  265 Rerun ./configure and make and it should work. I had previously been using
  266 tiff-v3.4-tar.gz instead so the library was there just not working. A note to
  267 keep in mind, is that the tiff libs are versioned rather oddly, version
  268 tiff-v3.4beta037 is actually newer than tiff-v3.4. 
  269 
  270 Make sure to rm config.cache and rerun ./configure before attempting to
  271 compile again. 
  272 
  273 Also, make sure to use gnu-make for the Window Maker compile. 
  274 
  275 
  276 2.4 How do I get libjpeg to work? 
  277 ----------------------------------
  278 The newest jpeg libs are availible at ftp://ftp.uu.net/graphics/jpeg/. 
  279 
  280 How many of you have seen that darned "lib reports 62 caller expects 61" type of
  281 error?
  282 Well, I have more than once, and here are some answers to possibly help
  283 you out. 
  284 
  285 First things first. As always, make sure there are not older copies of libjpeg
  286 floating around on your system. By default my Slackware distribution came
  287 with an old libjpeg.so.1 in the /usr/X11R6/lib/ directory. This can simply be
  288 deleted. Or if something complains after you delete it, recompile it if you
  289 can to look for the new lib in the right place, or if that fails, as a last resort,
  290 you might add a symlink to the new lib like so:
  291 ln -s /usr/local/lib/libjpeg.so.6.0.2 libjpeg.so.1 
  292 
  293 Now on to the error.
  294 This is basically caused by your application having been compiled to
  295 dynamically use the libjpeg.so shared library. When you install a new lib and
  296 then try to run your program again, it expects the lib it was compiled
  297 against, in this case the older libjpeg.so.6.0.1 and instead finds libjpeg.so.6.0.2
  298 and reports the error. 
  299 
  300 The fix is actually rather simple. Along with adding a libjpeg.so.6 symlink
  301 like so (just in case):
  302 ln -s libjpeg.so.6.0.2 libjpeg.so.6
  303 where you installed your new lib, you simply need to recompile your app to
  304 link it against the new library. :) 
  305 
  306 Make sure to rm config.cache and rerun ./configure before attempting to
  307 compile again. 
  308 
  309 Also, make sure to use gnu-make for the Window Maker compile. 
  310 
  311 
  312 2.5 How do I get libpng to work? 
  313 ----------------------------------
  314 The newest png libs are availible at
  315 http://www.cdrom.com/pub/png/pngcode.html. 
  316 
  317 You should also get the newest zlib libs from
  318 http://www.cdrom.com/pub/infozip/zlib/. 
  319 
  320 I had a few problems with this lib as well, basically I had an old libz.so in my
  321 /usr/X11R6/lib/ directory which configure was finding first, and which failed the
  322 test, being an older lib. 
  323 
  324 Generally the same applies here as with libjpeg, make sure there are no
  325 older versions of the necessary libs floating around on your system, then try
  326 and configure and make again. 
  327 
  328 Make sure to rm config.cache and rerun ./configure before attempting to
  329 compile again. 
  330 
  331 Also, make sure to use gnu-make for the Window Maker compile. 
  332 
  333 
  334 2.6 How do I get libgif (or libungif) to work? 
  335 ----------------------------------
  336 The newest libgif is availible at
  337 ftp://sunsite.unc.edu/pub/Linux/libs/giflib/. 
  338 
  339 The newest libungif is availible at
  340 ftp://sunsite.unc.edu/pub/Linux/libs/graphics/. 
  341 
  342 I had a few problems with libgif... it seems that the install process didn't
  343 install the header file libgif.h, so although the Window Maker configure found
  344 the lib (libgif.so.x), when you actually try to compile, it fails when it looks for
  345 the header to include the make. I simply copied it from the libgif source
  346 directory to the system include directory. (/usr/local/include/ on my system). 
  347 
  348 Make sure to rm config.cache and rerun ./configure before attempting to
  349 compile again. 
  350 
  351 Also, make sure to use gnu-make for the Window Maker compile. 
  352 
  353 
  354 2.7 Does wmsound work with 0.1x.x? 
  355 ----------------------------------
  356 As of Window Maker 0.15.x, sound is now included by default but requires
  357 the authors sound server. For more information, read the NEWS file in the
  358 Window Maker distribution. 
  359 
  360 The author Anthony Quinn <southgat@frontiernet.net> has released a 
  361 version that works with Window Maker >= 0.15.x. It is available from 
  362 it's home page at http://www.frontiernet.net/~southgat/wmsound/ 
  363 or on Largo's site at http://wm.current.nu/files.html#wmsound 
  364 for your convenience. 
  365 
  366 
  367 2.8 Can I use WindowMaker with KDE or GNOME or CDE? 
  368 ---------------------------------------------------
  369 Contrary to what a lot of people think, KDE is NOT a window manager. KDE is
  370 a suite of various applications that includes a custom window manager (kwm).
  371 The same is true for CDE. 
  372 
  373 Now, answering the question: Yes, you can use WindowMaker in these
  374 environments. To use Window Maker with GNOME, you don't need to do
  375 anything special. To use it with CDE, read the answer for "How do I switch
  376 CDE's windowmanager to use Window Maker?" 
  377 
  378 To use it with KDE, read it's documentation to get rid of kwm (and possibly
  379 kpanel) and replace it with wmaker. Then, start WPrefs.app, go to "Mouse
  380 Preferences" and set the "Disable mouse actions" check box. You will
  381 need to restart Window Maker to make this change take effect. The
  382 "Disable mouse actions" change is needed to allow you to use krootwm,
  383 wich enables you to use kfm's desktop icons, but will prevent you from
  384 accessing Window Maker's Applications and Window List menus with the
  385 mouse. 
  386 
  387 
  388 2.9 How do I get Window Maker working with xdm in Redhat 5.[01]? 
  389 ----------------------------------------------------------------
  390 After running wmaker.inst and letting it write to .xinitrc,
  391 cp .xinitrc .xsession
  392 and make sure that /usr/local/bin is in your $PATH for the Xserver. You can
  393 make sure of this by including a statement like 
  394 
  395             export PATH=$PATH:/usr/local/bin 
  396           
  397 
  398 in your .xsession file. 
  399 
  400 Make sure to chmod +x .xsession so that the Xsession script of xdm can
  401 execute it. 
  402 
  403 This is how the Xsession script is designed: 
  404 
  405             startup=$HOME/.xsession
  406 
  407             if [ -x "$startup" ]; then
  408                     exec "$startup"
  409             elif [ -x "$HOME/.Xclients" ]; then
  410                     exec "$HOME/.Xclients"
  411             elif [ -x /etc/X11/xinit/Xclients ]; then
  412                     exec /etc/X11/xinit/Xclients
  413             else
  414                     if [ -f "$resources" ]; then
  415                             xrdb -load "$resources"
  416                     fi
  417                     exec xsm
  418             fi
  419           
  420 
  421 You could also have a .Xclients file as was mentioned in previous revisions
  422 of this question. 
  423 
  424 
  425 2.10 Do I need to rerun wmaker.inst with every new version of
  426      Window Maker? 
  427 ----------------------------------
  428 There is no need to do this. You can do it, but keep in mind, that all your
  429 preferences will be lost, overwritten by the defaults. You can update the
  430 files and add the changes yourself if you need to, but else in most cases is
  431 sufficient to rely on WPrefs and it will update for you the new missing
  432 options if they differ from the default ones.
  433 
  434 The way domain files are read beginning from 0.15.0 makes the need for update
  435 almost redundant. The user config files are merged with the global ones in
  436 /usr/local/share/WindowMaker/Defaults.
  437 So even if new options are added, they will be reflected in the user
  438 configuration. 
  439 Only if user wishes to change the default behavior, he needs to add that
  440 option to the config file.
  441 
  442 If there ever happens to be a need for all users to rerun wmaker.inst in a
  443 future version, this will be noted in the NEWS file.
  444 
  445 
  446 2.11 When I install Window Maker, I've used wmaker.inst correctly
  447      and I only get aroot menu with xterm and exit. How do I fix this? 
  448 ----------------------------------
  449 Most likely, the problem is that Window Maker can not find a copy of the C
  450 pre processor in a directory such as /lib. The file /lib/cpp should be a
  451 symbolic link to whatever c compiler's cpp you are using. Mine reads as: 
  452 
  453             cpp -> ../usr/lib/gcc-lib/i586-pc-linux-gnu/pgcc-2.90.29/cpp*
  454           
  455 
  456 There seems to be another common problem that exhibits this same
  457 behavior. If you find another solution that matches this question please
  458 email <sprout@dok.org> or <largo@current.nu>. 
  459 
  460 
  461 2.12 How do I get Window Maker to use more than 16 colors on my
  462      SGI Indy Workstation? 
  463 ----------------------------------
  464 Thanks to Peter H. Chou <pchou@leland.Stanford.EDU> for this answer: 
  465 
  466 By default, the SGI X Server uses 8-bit Pseudocolor mode.
  467 To change it, edit (as root) the file /usr/lib/X11/xdm/Xservers.
  468 Change it to read: 
  469 
  470             :0 secure /usr/bin/X11/X -bs -c -class TrueColor -depth 24
  471           
  472 
  473 
  474 
  475 
  476 2.13 Using WindowMaker with Solaris 2.6 CDE 
  477 ----------------------------------
  478 (thanks to Rob Funk, Unix God of osu.edu) 
  479 
  480 Assuming you installed Window Maker according to the README's that
  481 come with the source, all you need to run Window Maker on a Solaris box
  482 is an entry in the .xinitrc. Only 0.17 - 0.19 versions have been tested, but
  483 when you run the configure script, let it make changes to the .xinitrc file. It
  484 should look something like this: 
  485 
  486             #!/bin/sh
  487             # Window Maker Default .xinitrc
  488             exec /usr/local/bin/wmaker
  489           
  490 
  491 Believe it or not, that's all that it takes. This, in fact, runs WindowMaker
  492 instead of OpenWindows. In order to choose WindowMaker, you simply
  493 choose "OpenWindows Desktop" in the "Options - Session" Menus.
  494 Choose "CDE Desktop" if you want CDE. 
  495 
  496 The Color schemes and settings for Window Maker are seperate from
  497 CDE. Tested on a SPARC 10, Solaris x86 should work also. (better,
  498 hopefully) 
  499 
  500 
  501 2.14 How do I switch CDE's window-manager to use Window Maker? 
  502 ----------------------------------
  503 Method 1: 
  504 
  505 Peter Ilberg <peter.ilberg@natinst.com> gives us this answer: 
  506 
  507 Install WM wherever you want it, mine is in /opt/WindowMaker-0.16.0
  508 (eg. use ./configure --prefix=/opt/WindowMaker-0.16.0).
  509 Run the install script wmaker.inst in your home directory. 
  510 
  511 Add the following two lines to .dtprofile in your home directory: 
  512 
  513 SESSIONTYPE=xdm; export SESSIONTYPE
  514 PATH=:/usr/contrib/bin/X11:$PATH:.; export PATH 
  515 
  516 This tells CDE to go looking for an .xinitrc/.xsession instead of using the
  517 default environment. 
  518 
  519 Make your .xsession/.xinitrc executable (VERY IMPORTANT, wmaker.inst did
  520 NOT do this automatically for me) using eg. 
  521 
  522 chmod ugo+x .xsession 
  523 
  524 Your .xsession/.xinitrc should look something like this: 
  525 
  526 #!/bin/sh
  527 <some other init stuff that you want/need>
  528 exec wmaker 
  529 
  530 Things to try if it doesn't work: (somewhat fuzzy and random) 
  531 
  532 This should do it although I did have problems sometimes initially which I
  533 fixed by randomly trying absolute pathes for wmaker in .xsession/.xinitrc and/or
  534 making the dtprofile/.xinitrc/etc executable. It helps logging in on the console
  535 (select from CDE login screen) and start X manually using 'X'.
  536 If it works that way it should work when logging into the CDE environment.
  537 Remember to Check your paths! 
  538 
  539 If it doesn't work, you can also substitute some other window manager for
  540 wmaker in the .xinitrc and see if that works. If it does you know at least that
  541 .xinitrc is getting called/executed, so your WM path is wrong or not set. 
  542 
  543 
  544 Method 2: 
  545 
  546 Thomas Hanselman gave this alternative answer (via Peter Ilberg): 
  547 
  548 Build and install WM wherever you want, as described in Method 1. You
  549 can install and run WM just fine from your home directory. That's what I'm
  550 doing, since I don't have root access at work :(. Then, in your .Xdefaults file in
  551 your home directory, add the following line: 
  552 
  553 Dtsession*wmStartupCommand: <path to Window Maker executable> 
  554 
  555 Then, log out, and log back in, and, unless I've forgotten a step (or this is a
  556 custom Nortel thing), you should be in Window Maker heaven ;). 
  557 
  558 Difference between the methods: (according to Thomas) 
  559 
  560 I've been told that the difference between setting the resource and Peter's
  561 method is that if you override the window manager with the resouce, you
  562 still get the CDE resources read into the resource database (so you still
  563 have your color settings & such from CDE), whereas with Peter's, the CDE
  564 resource don't get read into the database. I don't know if this is true or not,
  565 however. Also, another thing to note with Window Maker and HP-UX 10.20
  566 -- if you select "Exit Session" from the WM root menu, Window Maker and
  567 all of your applications are killed, but you may not be logged out. Again, this
  568 might be an artifact from my work environment, or the way I start Window
  569 Maker. 
  570 
  571 Owen Stenseth <iplenergy.com> adds: 
  572 
  573 When using this method it is possible to exit Window Maker cleanly by
  574 using the dtaction command. I use the following in my Window Maker menu: 
  575 
  576 "Exit Session"      EXEC dtaction ExitSession 
  577 
  578 The only problem I have at the moment is I seem to get multiple copies of
  579 asclock running when I log in again. 
  580 
  581 You can also use the normal "Exit Session" command from the WM root
  582 menu and place additional commands required to shutdown CDE in
  583 ~/GNUstep/Library/WindowMaker/exitscript 
  584 
  585 So, if you add "dtaction ExitSession" in that file, the command to shutdown
  586 CDE will be automatically executed when you exit WindowMaker. 
  587 
  588 
  589 2.15 When I run wmaker it quits complaing about something
  590      __register_frame_info. 
  591 ----------------------------------
  592 This is due to using gcc >= 2.8.0 or egcs to compile Window Maker or a
  593 library it uses, then running these precompiled binaries on a system using
  594 libraries compiled with gcc 2.7.2.x
  595 
  596 You will have to compile Window Maker yourself on this system.  Please read
  597 the INSTALL file for the instructions on how to do so.
  598 
  599 
  600 2.16 When I run wmaker it complains about something like expected
  601      libjpeg 61 got 62.
  602 ----------------------------------
  603 Upgrade your libjpeg library and/or recompile Window Maker.
  604 
  605 
  606 2.17 How do I fix an error such as "libwraster.so.1: cannot open shared
  607 	 object file" ?
  608 ----------------------------------
  609 Like most software using GNU autoconf, Window Maker by default will install
  610 under the /usr/local prefix.  This has the repercussion on many systems that
  611 the libraries that are part of Window Maker will be installed in
  612 /usr/local/lib, which is usually not in the default system LD_LIBRARY_PATH.
  613 This is why the library cannot be found.
  614 
  615 Under Linux, you will need to list this directory in /etc/ld.so.conf and
  616 run /sbin/ldconfig.  Both these operations will need to be performed as the
  617 superuser.
  618 
  619 Under BSD, as the superuser you will need to run
  620 
  621     ldconfig -m /usr/local/lib
  622 
  623 which will merge this directory into the system library path.
  624 
  625 If the problem persists, you may be able to use "ldd" to track down why the
  626 library cannot be loaded (it will print a list of dynamic objects used by
  627 the executable or library listed on the command line, and where it is
  628 expecting to find it).
  629 
  630 
  631 -=-=-=-
  632 Usage:
  633 -=-=-=-
  634 
  635 3.1 How do I get new apps on the dock (The icon or line of icons on
  636     the right side of the screen by default) 
  637 ----------------------------------
  638 Launch an application. If there is a little icon that pops up in the bottom
  639 corner of the screen, drag it over to the dock icon(s). You should see a
  640 whiteish square indicating when it is close enough to dock, and where it will
  641 be placed. To make sure this application will be there next time you start up
  642 windowmaker, exit windowmaker with the "exit session" option. 
  643 
  644 
  645 3.2 What is the difference between the 'Exit' and 'Exit Session' Options? 
  646 ----------------------------------
  647 'Exit' exits wmaker, but leaves the other apps running, and if wmaker was
  648 not the last app launched in the .xinitrc the X server is not closed, until
  649 the last app started by .xinitrc is closed.
  650 'Exit session' will exit wmaker, but also will close all running apps, thus
  651 the X server will be closed, and your session will end.
  652 
  653 
  654 3.3 How do I "dock" AppIcons on the Clip? 
  655 -----------------------------------------
  656 Just drag icons near it like you would for the dock.  Note that if you place
  657 the clip near the dock, you may have problems docking appicons in either.
  658 Move the clip away first.
  659 
  660 
  661 3.4 Why do none of my Key Bindings (ie: Alt+#) work in Window Maker 0.1x.x 
  662 ----------------------------------
  663 If you are using XFree86, make sure scroll lock and numlock are off or no
  664 bindings will work (XFree bug). You can try using the XFree86 Numlock
  665 Hack by editing the line #undef NUMLOCK_HACK in $WindowMakerdir/src/wconfig.h
  666 and changing it to #define NUMLOCK_HACK. 
  667 As of 0.18.0, this hack functions properly.
  668 
  669 
  670 3.5 How do I rename workspaces? 
  671 ----------------------------------
  672 Right click on the "desktop" (root window) to show the menu (don't hold the
  673 button down). Go to the workspaces menu and hold the Control key down
  674 and click on the workspace you would like to rename and type the name. 
  675 
  676 If you use the clip, use the "Rename Workspace" command in the clip
  677 menu. 
  678 
  679 
  680 3.6 How can I resize a window if the window is larger than my
  681     currect desktop? 
  682 ----------------------------------
  683 David Reviejo <dreviejo@arrakis.es> best summed up this answer: 
  684 
  685      "Maybe you know:
  686      Alt+Left click and drag
  687      to move the window. 
  688 
  689      Try this:
  690      Alt+Right click and drag
  691      to resize (by moving the nearest window corner) 
  692 
  693      Another move/resize tip: while you are moving or resizing a window,
  694      you
  695      can change the move/resize mode by pressing the SHIFT key." 
  696 
  697 
  698 
  699 
  700 3.7 How do I "undock" AppIcons? 
  701 ----------------------------------
  702 If the program is not running, just drag the icon to the middle of your
  703 desktop (away from the dock and clip) and watch it disappear. 
  704 
  705 If the program is running, hold down Meta (usually CTRL) and drag the icon
  706 off the dock. You can also right click on it and choose 'Kill', then undock as
  707 usual. 
  708 
  709 
  710 3.8 I docked an application but when I run it the button is permanently
  711     shaded and I can't run new instances.
  712 ----------------------------------
  713 You probably docked the application with dockit. To fix it
  714 remove the icon and use the "Emulate Application Icon" checkbox in
  715 the Advanced Options section of the Attributes panel for the window.
  716 Then restart the application to get the application icon you
  717 must use to dock the application. 
  718 It can also mean that you did something you shouldn't, which is
  719 changing the program that is ran from the docked icon. For example,
  720 if you docked rxvt you must NOT change it to xterm, for example.
  721 You also can't do any changes that might alter the contents of
  722 the WM_CLASS hint for the window, like the -name parameter for
  723 xterm, rxvt and other programs.
  724 
  725 
  726 
  727 3.9 When I run wmaker it complains about not being able to load any fonts.
  728 ----------------------------------
  729 Check if the locale settings are correct. If you're not sure what to
  730 do, unset the LANG environment variable before running wmaker.
  731 
  732 TODO: give complete explanation
  733 
  734 
  735 
  736 3.10 When I set the root background with wmsetbg by hand it works,
  737      but when I do that from the configuration files it doesnt!
  738 ----------------------------------
  739 
  740 DOH! If you set the root background with wmsetbg by hand, it will obviously
  741 find the image, since you have explicitly specified it by hand. But if you
  742 simply put it in ~/GNUstep/Defaults/WindowMaker in some option like
  743 WorkspaceBack, it will not find the image because Window Maker can't read
  744 your mind to figure where you put the image. So, to fix it, you have to
  745 either place the full path for the image in the texture specification or put
  746 the path for the directory you put your background images in the PixmapPath
  747 option. You can also put all your background images in places like
  748 ~/GNUstep/Library/WindowMaker/Backgrounds or
  749 /usr/local/share/WindowMaker/Backgrounds
  750 These directories will be listed under the "Search Path" section of WPrefs.
  751 
  752 
  753 
  754 -=-=-=-=-=-=-=-
  755 Configuration:
  756 -=-=-=-=-=-=-=-
  757 
  758 4.1 What are those files inside my ~/GNUstep directory? 
  759 ----------------------------------
  760 ~/GNUstep/WindowMaker/WindowMaker 
  761 
  762      The main config file. This file controls options such as keybindings,
  763      fonts, pixmaps, and focus modes. 
  764 
  765 
  766 ~/GNUstep/WindowMaker/WMWindowAttributes 
  767 
  768      The Controls "attributes" for individual applications and appicons.
  769      Options such as what icon to use are set here. For the most part, this
  770      is now best accessed via a right click on a title bar of an application
  771      and selecting "Attributes" 
  772 
  773 
  774 ~/GNUstep/Defaults/WMState 
  775 
  776      This is the file that is automatically generated and contains the current
  777      dock settings. It is not recommended to edit this file by hand. 
  778 
  779 
  780 ~/GNUstep/Defaults/WMRootMenu 
  781 
  782      This file specifies what file to use as the root menu.  In Window Maker
  783 	 0.19.0 and higher, you can replace this file with the one called plmenu
  784 	 in ~/GNUstep/Defaults/WindowMaker, and you can then use WPrefs to edit
  785 	 the menu.
  786 
  787 
  788 ~/GNUstep/Library/WindowMaker/menu 
  789 
  790      This is the file to edit to change your root menu. 
  791 
  792 ~/GNUstep/Library/WindowMaker/plmenu
  793 
  794 	 This is the same menu file, in property list format - WPrefs needs a
  795 	 menu in this format if you wish to edit it using WPrefs.
  796 
  797 
  798 
  799 
  800 4.2 How do I enable the normal X sloppy focus mode? 
  801 ----------------------------------
  802 In the ~/GNUstep/Defaults/WindowMaker, change the following: 
  803 
  804 FocusMode = sloppy; 
  805 
  806 
  807 4.3 How do I get my auto-arrange icons to work? 
  808 ----------------------------------
  809 In ~/GNUstep/Defaults/WindowMaker set AutoArrangeIcons=Yes; and the icons
  810 should now auto-arrange. 
  811 
  812 
  813 4.4 How do I get my Meta-Tab to cycle through windows correctly? 
  814 ----------------------------------
  815 Make sure that these settings are true in your ~/GNUstep/Defaults/WindowMaker
  816 file: 
  817 
  818 CirculateRaise = Yes;
  819 RaiseDelay = 1; 
  820 
  821 This will not give you MS Windows(tm) style application switching where
  822 alt-tab is changes context. 
  823 
  824 Paul Warren <<pdw@ferret.lmh.ox.ac.uk>> has released a patch that will
  825 give this style of Context Switching to Window Maker. 
  826 
  827 It is availible from http://ferret.lmh.ox.ac.uk/~pdw/patches/
  828 
  829 
  830 4.5 How can I define my own Icon for a program? (instead of the
  831     Icon the Application Supplies?) 
  832 ----------------------------------
  833 You can right click on the titlebar of the running app and choose the
  834 "Attributes..." option, then click on the "Ignore client supplied icon"
  835 checkbox. Click "Apply", "Save" and close the Attributes Editor. 
  836 
  837 Another method is to edit ~/GNUstep/Defaults/WMWindowAttributes by hand and
  838 use the AlwaysUserIcon=YES; option for the app. For example: 
  839 
  840 xmcd = { Icon = "Radio.xpm";
  841 AlwaysUserIcon=Yes;
  842 }; 
  843 
  844 
  845 4.6 How do I get a Tile background for my AppIcons (those things in
  846     the dock)? 
  847 ----------------------------------
  848 You need to change 1 line to your ~/GNUstep/Defaults/WindowMaker file. 
  849 
  850 IconBack = (spixmap, tile.black.xpm, white);
  851 or
  852 IconBack = (tpixmap, tile.black.xpm, white);
  853 
  854 spixmap will scale the pixmap to fit the tile, tpixmap will tile it as is. 
  855 
  856 As Random@efnet says, The last parameter is the color that fills in any
  857 Transparent parts of your icon. 
  858 
  859 IconBack takes other options too, search the NEWS file.
  860 
  861 
  862 4.7 How do you dock <insert program here> that doesn't have an
  863     appicon in the new version of Window Maker? 
  864 ----------------------------------
  865 There is now an option available to emulate appicons so that Window
  866 Maker can dock just about anything now. 
  867 
  868 To dock a misbehaving application, right click on the title bar and select the
  869 attributes menu. Next, select the pull down menu's "Advanced Options"
  870 item. Under the ``Advanced Options'' menu, select the ``Emulate
  871 Application Icon'' Option then Save, Apply and close the dialog. 
  872 
  873 This should allow you do dock the program normally. 
  874 
  875 Emulate Appicon does exactly the same thing as dockit, a small app
  876 distributed with ancient versions of Window Maker before the Attribute
  877 Editor existed (now depricated for the obvious reason).  If Emulate Appicon
  878 does not work, dockit will not work either.  Such applications violate the
  879 ICCCM (Inter-Client Communication Conventions Manual) and are considered
  880 badly coded for not setting the instance.class hints.
  881 
  882 
  883 4.8 How do I get x11amp to not have a title bar? (or any other
  884     program for that matter?) 
  885 ----------------------------------
  886 Right Click on the title bar and choose "Attributes". Click on Panel 2 and
  887 click the the "Disable titlebar" and "Disable resizebar" options. Click
  888 "Save", "Apply" and then close the Attributes panel. 
  889 
  890 By Default, to get back to the attributes menu once you've removed the
  891 titlebar, hit the key F10 while the window is focused. 
  892 
  893 Here is an example entry in ~/GNUstep/WMWindowAttributes for x11amp. 
  894 
  895 x11amp={
  896 Icon="x11amp.xpm";
  897 NoTitlebar=Yes;
  898 NoResizebar=Yes;
  899 NoAppIcon=Yes;
  900 }; 
  901 
  902 
  903 4.9 How do I set a pixmap background? 
  904 ----------------------------------
  905 Here is the in depth explanation straight from the NEWS file: 
  906 
  907 wmsetbg now accepts the following options: 
  908 usage: wmsetbg [-options] image 
  909 options: 
  910 -d 
  911               dither image
  912 -m 
  913               match colors
  914 -t 
  915               tile image
  916 -s 
  917               scale image (default)
  918 -u 
  919               update Window Maker domain database
  920 -D <domain> 
  921               update <domain> database
  922 -c <cpc> 
  923               colors per channel to use
  924 
  925 
  926 
  927 By default, it will try to guess if dithering is needed or not and proceed
  928 accordingly.
  929 Using -d or -m will force it to dither or match colors. 
  930 
  931 Dithering for more than 15bpp is generally not needed, and will only result
  932 in a slower processing.
  933 Don't use dithering except when needed, because it is slower. Else rely on
  934 wmsetbg which will detect if dithering is needed and use it. 
  935 
  936 -u 
  937    will update the WorkspaceBack in the default database
  938    domain file in ~/GNUstep/Defaults/WindowMaker, and let Window
  939    Maker refresh the screen. Please note that this option only
  940    works under Window Maker, and will have no effect under
  941    other window managers, since it rely on Window Maker to
  942    update the image after it reads the updated defaults
  943    database.
  944 
  945 -D 
  946    <domain> is same as above, but will update the domain
  947    <domain> instead of the default Window Maker domain.
  948 
  949 -c 
  950    <cpc> will set the color per channel to use. Only needed for
  951    PseudoColor visuals. Window Maker will automatically pass
  952    the value read from the Window Maker domain database.
  953 
  954 
  955 
  956 The following line is straight from your WindowMaker-0.15.x
  957 ~/GNUstep/Library/WindowMaker/menu file and should all be on one line. 
  958 
  959 "Images" OPEN_MENU BACKGROUNDS_DIR
  960 ~/GNUstep/Library/WindowMaker/Backgrounds WITH wmsetbg -u -t 
  961 
  962 This should give you an idea on how to add other entries for different image
  963 directories. See the help info at the top of the
  964 ~/GNUstep/Library/WindowMaker/menu file for more information. 
  965 
  966 If you for some reason would like to set your background image with XV, for
  967 instance to use an image format not yet supported by wmsetbg or to use one
  968 of XV's special modes, edit the file ~/GNUstep/Library/WindowMaker/autostart
  969 and insert the line 
  970 
  971 xv -root -quit -maxpect ~/background.jpg
  972 or
  973 xv -root -quit -max ~/background.jpg 
  974 
  975 you can also try variations of this to get different tiling and other effects
  976 (where X is a number 1-9 I believe):
  977 'xv -root -quit -rmodeX ~/background.jpg' 
  978 
  979 If you would like xv functionality in your menu, heres a nice little tip from
  980 Alfredo: 
  981 
  982 Add the following line to your ~/GNUstep/Library/WindowMaker/menu file. (all on
  983 one line) 
  984 
  985 "More Backgrounds" OPEN_MENU /home/whoever/backgrounds xv -root -maxpect -quit 
  986 
  987 
  988 4.10 Can I put pixmaps in my root menu and title bars? 
  989 ----------------------------------
  990 With the release of WindowMaker-0.14.1, you can now put pixmaps
  991 anywhere you would have either a gradient or a color. This means now that 
  992 
  993 MenuTextBack=(tpixmap, foo.xpm, acolor); 
  994 
  995 in ~/GNUstep/Defaults/WindowMaker will put the correct pixmap tiled in your
  996 menu. 
  997 
  998 FTitleBack = (spixmap, foo.xpm, black); 
  999 
 1000 Would have the effect of streching a pixmap to fit the titlebar of the active
 1001 window.
 1002 You can use png, gif, ppm, tiff, jpeg and xpm images interchangeably in
 1003 Window Maker if you have compiled in support for those formats. 
 1004 
 1005 
 1006 4.11 How do I get my Minimize Icon to look like the triangle I see in
 1007      screenshots? 
 1008 ----------------------------------
 1009 This involves a minor source tweak. Instructions are available at
 1010 http://wm.current.nu/tips.html#titlebar_icons
 1011 
 1012 Example screenshot at 
 1013 http://wm.current.nu/themes/images/screenshots/Midnight3.jpg
 1014 
 1015 
 1016 4.12 How do I get superfluous bells and whistles working? 
 1017 ----------------------------------
 1018 Add Superfluous=YES; to your ~/GNUstep/Defaults/Windowmaker file. 
 1019 
 1020 This option was added as a runtime option in Window Maker >= 0.16.1. 
 1021 
 1022 
 1023 4.13 How do I get the classic NeXT(tm)-like style back? 
 1024 ----------------------------------
 1025 Add NewStyle=NO; to your ~/GNUstep/Defaults/Windowmaker file. 
 1026 
 1027 This option was added as a runtime option in Window Maker >= 0.16.1 
 1028 
 1029 
 1030 4.14 How do I get the window menu with only a two button mouse? 
 1031 ----------------------------------
 1032 Jim Noble <jmknoble@ntrnet.net> writes: 
 1033 
 1034 If you've got a two-button mouse under some versions of Solaris x86,
 1035 there's no way (that i'm aware of) to emulate a 3-button mouse. The right
 1036 button can be either MB2 or MB3, but chording doesn't work. 
 1037 
 1038             ApplicationMenuMouseButton = Left;
 1039 
 1040 and 
 1041 
 1042             WindowListMouseButton = Right; 
 1043           
 1044 
 1045 in ~/GNUstep/Defaults/WindowMaker ought to allow the left button to
 1046 activate the root menu, and the right button (as MB2) to activate the
 1047 windows menu. 
 1048 
 1049 
 1050 4.15 How do I edit my root menu? 
 1051 ----------------------------------
 1052 You can now use WPrefs.app 
 1053 (see http://wm.current.nu/features/configuration.html for more info) 
 1054 if you have the new PropList style menu, or you can manually edit the 
 1055 oldstyle menu file 
 1056 
 1057             ~/GNUstep/Library/WindowMaker/menu
 1058 
 1059 (or you can also manually edit the newstyle menu file) 
 1060 
 1061             ~/GNUstep/Defaults/WMRootMenu
 1062 
 1063 and save your changes. Window Maker should detect the change and
 1064 automatically update. If you are having a problem getting it to reload the
 1065 menu, try 
 1066 
 1067             touch ~/GNUstep/Library/WindowMaker/menu
 1068 
 1069             (or 'touch ~/GNUstep/Defaults/WMRootMenu' for the newstyle menu)
 1070 
 1071 to force the modification time into the future. 
 1072 
 1073 
 1074 4.16 How can I set dock/clip to use single click to launch
 1075      applications, instead of double click?
 1076 ----------------------------------
 1077 This question was officially answered as follows:
 1078 
 1079     You cannot do this. This is because single click is used to select
 1080     app-icons, or to raise/lower the app-icon or the dock/clip.  If
 1081     this is impelmented then you will be unable to select or
 1082     raise/lower dock/clip or app-icons, without also launching the
 1083     application it represents.
 1084 
 1085     So don't ask for this to be implemented, because it will not
 1086     be. Double click is used for a reason, is not just some weird idea
 1087     we got in a morning when we wake up too early.
 1088 
 1089 Regardless of that, there is now an option in WPrefs, under "Expert
 1090 User Preferences," which allows you to set "Launch applications and
 1091 restore windows with a single click."  (See the files contrib/README
 1092 and contrib/single_click.diff in the source package for details.)
 1093 
 1094 If you set that option, a left button single click will launch or
 1095 restore, rather than select, the app-icon.  You can use other methods
 1096 (or temporarily turn the option off again) to select app-icons or
 1097 raise/lower the dock/clip.  You can toggle the selected state of any
 1098 app-icon via its right button menu, and there are auto-raise and
 1099 keep-on-top options for the dock and clip.
 1100 
 1101 
 1102 4.18 How do I restore the configuration app to the dock?
 1103 ----------------------------------]
 1104 You should start it from a terminal using its full path name, which is
 1105 /usr/local/GNUstep/Applications/WPrefs.app/WPrefs
 1106 by default.
 1107 
 1108 
 1109 4.19 How do I define my own icon for a program?  I don't like the one it
 1110      supplies.
 1111 ----------------------------------
 1112 Right-click the titlebar of the running application and start the Attributes
 1113 Editor.  Check the "Ignore client supplied icon" box.  "Apply" and "Save",
 1114 and close the Attributes Editor.
 1115 
 1116 Another method is to edit ~/GNUstep/Defaults/WMWindowAttributes by hand and
 1117 use the AlwaysUserIcon=YES; option for the app. For example: 
 1118 
 1119 xmcd = { Icon = "Radio.xpm"; AlwaysUserIcon=Yes; }; 
 1120 
 1121 
 1122 -=-=-=-=-=-=-=-=-=-
 1123 Other Applications:
 1124 -=-=-=-=-=-=-=-=-=-
 1125 
 1126 5.1 How do I assign gimp an appicon? 
 1127 ----------------------------------
 1128 Window Maker now can assign Icons from within the windowmanager, to
 1129 do so, right click on the title bar of an app or hit F10 while the desired app
 1130 is focused, choose "Attributes...", click on the "4" Button, enter the icon file
 1131 name (make sure this is in your pixmap path, or you can type in the full path
 1132 without using ~/ type path names), click "Update", "Apply", "Save" and then
 1133 close the Attributes Editor. 
 1134 
 1135 You can also enter the following line in
 1136 ~/GNUstep/Library/WindowMaker/WMWindowAttributes: 
 1137 
 1138 gimp={Icon="gimp.xpm";}; 
 1139 
 1140 
 1141 5.2 How do I get an appicon for XEmacs 20.3+? 
 1142 ----------------------------------
 1143 Thanks to Michael Hafner <hayfi@rz.fh-augsburg.de> for this answer. 
 1144 
 1145 You don't need to patch the XEmacs code, just run 
 1146 
 1147 ./configure --with-session=yes (in addition to any other options you use) 
 1148 
 1149 in your XEmacs 20.3+ sourcedir and rebuild it. Then XEmacs shows an
 1150 appicon when running and you can easily dock it. 
 1151 
 1152 
 1153 5.3 Where do you get that clock program I always see on people's
 1154     desktops? 
 1155 ----------------------------------
 1156 Its called asclock. It was included with each version of Window
 1157 Maker until version 0.17.5, and was no longer included in
 1158 0.18.0 and above.
 1159 You could find it in ./WindowMaker-0.xx.x/misc/asclock.tgz and it was
 1160 prepatched to be able to dock. Some other (older) versions you might find
 1161 on the net don't dock. 
 1162 
 1163 Since it was pulled from the distribution (probably to save space), I've
 1164 included it at http://wm.current.nu/files.html#asclock for your convenience. 
 1165 
 1166 
 1167 5.4 How do you dock asclock? 
 1168 ----------------------------------
 1169 asclock -shape -iconic -12 & 
 1170 
 1171 Drag it from the top right corner of the clock to the dock. Right click on the
 1172 icon and select autolaunch.
 1173 You have to drag the appicon by clicking on the edge of the icon, because
 1174 the actual pixmap belongs to the app itself, and any clicks on the pixmap
 1175 are interpreted by the app rather than X or the window manager. Therefor,
 1176 you need to click somewhere on the appicon where the background tile
 1177 shows through (usually the edges), and drag it that way. 
 1178 
 1179 
 1180 5.5 How do you dock wmload? 
 1181 ----------------------------------
 1182 wmload -withdrawn -shape & 
 1183 
 1184 Then dock it similar to asclock. 
 1185 
 1186 
 1187 5.6 What other apps exist for the dock? 
 1188 ----------------------------------
 1189 Several Nice applications are available: 
 1190 
 1191      wmmixer and wmcd and wmmount
 1192      http://www.geocities.com/SiliconValley/Vista/2471/linux.htm#xapps 
 1193 
 1194      ascd,WMRack,asmixer,asmodem, and others
 1195      ftp://ftp.windowmaker.org/pub/wmaker/contrib/srcs/apps/ 
 1196 
 1197      wmavgload, wmmount, and wmload
 1198      ftp://ftp.windowmaker.org/pub/wmaker/contrib/srcs/utils/ 
 1199 
 1200      wmppp-wmifs, wmtime, wmmon and other nifty apps
 1201      http://windowmaker.mezaway.org/ 
 1202 
 1203 A huge index of most available dockapps is available at:
 1204 
 1205 	 http://www.bensinclair.com/dockapp/
 1206 
 1207 
 1208 5.7 How do I get an appicon for rxvt so I can dock it? 
 1209 ----------------------------------
 1210 The default rxvt that comes with most distribtions is an outdated version of
 1211 rxvt. The newest development version of rxvt is availible from
 1212 ftp://ftp.math.fu-berlin.de/pub/rxvt/devel/. As of the time of this writing, the
 1213 version is 2.4.7 and it natively produces an appicon without a patch. 
 1214 
 1215 John Eikenberry has also created an rpm which is available from
 1216 ftp://ftp.coe.uga.edu/users/jae/windowmaker/ 
 1217 
 1218 For your convenience, I have rxvt-2.4.7.tar.gz at
 1219 http://wm.current.nu/files/rxvt-2.4.7.tar.gz for download. As of
 1220 version 2.4.7, rxvt includes Window Maker support as well as John
 1221 Eikenberry's NeXT scrollbar hack. 
 1222 
 1223 
 1224 5.8 How do I get different icons for rxvt's (or xterms) running
 1225     different programs? 
 1226 ----------------------------------
 1227 The simplest way is to run each rxvt with a different -name parameter. 
 1228 
 1229 For example, I want to run an rxvt for irc and one for mail. This is an
 1230 example of what I'd do: 
 1231 
 1232 for the irc rxvt:
 1233 rxvt -name "irc" -e "irc" 
 1234 
 1235 for the mail rxvt:
 1236 rxvt -name "mail" -e "pine" 
 1237 
 1238 This would result in each rxvt now having the instance and class of irc.Xterm
 1239 and mail.Xterm respectively, so that Window Maker can now set Attributes
 1240 for them individually. 
 1241 
 1242 
 1243 5.9 How do I launch multiple instances of XTerm from one appicon?
 1244 ----------------------------------
 1245 The easiest way to accomplish this is to dock XTerm as normal. Then Go
 1246 to the 'Attributes menu' -> 'Application Specific' and select 'no application
 1247 icon' for XTerm. 
 1248 
 1249 You can also right-click on the docked appicon and select settings. Change
 1250 the 'Application Path with arguments' section to 
 1251 
 1252             foo.sh
 1253 
 1254 where foo.sh is the following script 
 1255 
 1256             #!/bin/sh
 1257             exec xterm
 1258 
 1259 This should allow unlimited XTerms without appicon clutter. 
 1260 
 1261 
 1262 5.10 How do I allow Alt+# to work in an rxvt session? (with irc for
 1263      example) 
 1264 ----------------------------------
 1265 First, Launch a unique instance of rxvt or xterm.
 1266 This can be done using the -name option of rxvt.
 1267 For example: 
 1268 
 1269 rxvt -name foo -e irc 
 1270 
 1271 Then, go to the Attributes menu (right click on titlebar (or hit F10) and
 1272 choose 'Attributes...')
 1273 Then choose 'Advanced Options' from the listbox and enable 'Don't Bind
 1274 Keyboard shortcuts'.
 1275 Click 'Save' and 'Apply' and you should be able to run your session without
 1276 the shortcuts. 
 1277 
 1278 
 1279 5.11 Window Maker breaks scilab
 1280 ----------------------------------
 1281 
 1282 If you refer to the problem of the "graphics" window of scilab not showing
 1283 up in Window Maker, this is caused by a bug in scilab. You can see the
 1284 cause of the problem by yourself, by running xprop on the graphic window:
 1285 WM_NORMAL_HINTS(WM_SIZE_HINTS):
 1286                 user specified location: 136679205, 1074468360
 1287                 user specified size: 400 by 300
 1288                 program specified minimum size: 400 by 300
 1289 
 1290 Now, when scilab opens it's window, Window Maker nicely does exactly what it
 1291 is told, that is, map the window at position 136679205, 1074468360 which
 1292 obviously falls outside the screen no matter how big is your monitor ;) 
 1293 
 1294 Meanwhile, the workaround for this is to open the window list menu
 1295 (click on the root window with the middle mouse button) and click 
 1296 on the ScilabGraphic entry. The window should be brought to your
 1297 reach. Then, open the window commands menu (right click on window's
 1298 titlebar) and open the Attributes panel. Go to the "Advanced Options"
 1299 section, check the "Keep inside screen" option and save.
 1300 
 1301 If you can recompile Scilab, this came from a Scilab developer:
 1302 
 1303 replace 
 1304  size_hints.flags = USPosition | USSize | PMinSize;
 1305 with
 1306  size_hints.flags = /** USPosition |**/ USSize | PMinSize;
 1307 
 1308 in routines/xsci/jpc_SGraph.c
 1309 
 1310 
 1311 5.12 Netscape shows black and white icons
 1312 ----------------------------------
 1313 
 1314 I have seen this happen on some systems if you run Netscape in a high
 1315 colour depth (32bpp). That is a Netscape bug. Therefore, bug Netscape.
 1316 
 1317 
 1318 5.13 Snow flakes from xsnow don't acumulate on titlebars!
 1319 ----------------------------------
 1320 
 1321 Because of the way xsnow is coded, it seems that it can't "see"
 1322 windows with the SaveUnder attribute turned on. So, if snow
 1323 accumulation on windows is vital for you, disable SaveUnders in
 1324 WPrefs, in the advanced options section.
 1325 
 1326 
 1327 5.14 I'm using RedHat 6.0 and Netscape dies without reason.
 1328 ----------------------------------
 1329 
 1330 Er... well, I don't know why you're looking in this Window Maker FAQ 
 1331 for a RedHat/Netscape problem, but anyway, the answer is in:
 1332 
 1333 http://www.redhat.com/cgi-bin/support?solution&11-990511-0082&100-926468988&14-0&15-0&25-&3-&30-
 1334 
 1335 
 1336 -=-=-=-=-=-=-
 1337 Programming:
 1338 -=-=-=-=-=-=-
 1339 
 1340 6.1 How do I get a normal X application to produce an appicon? 
 1341 ----------------------------------
 1342  You must define the WM_CLASS (XSetClassHint()) and the
 1343 CLIENT_LEADER or XWMHints.window_group properties, which are
 1344 automatically set by most applications that use Xt (Motif, Athena ...),
 1345 but if you use plain Xlib you must set them by hand. 
 1346 
 1347 Also you must make a call to XSetCommand(dpy, leader, argv, argc); 
 1348 
 1349 Take a look at Window Maker-0.1x.x/test/test.c that is an example for
 1350 writing such an app (which also have an app menu).
 1351 
 1352 
 1353 6.2 How do I get my tcl/tk application to produce an appicon? 
 1354 ----------------------------------
 1355 Oliver Graf <ograf@fga.de> writes: 
 1356 
 1357 The main window (normally this is called '.' [dot] in tk) should use the
 1358 following lines: 
 1359 
 1360 wm command . [concat $argv0 $argv] 
 1361 wm group . . 
 1362 
 1363 All child windows attached to the same app-icon should use: 
 1364 
 1365 toplevel .child
 1366 wm group .child . 
 1367 
 1368 where .child should be replaced by the actual window path. 
 1369 
 1370 Replace '.' with the actual main-window path and 'wm group .child .' should
 1371 be added for each 'toplevel .child' call. 
 1372 
 1373 
 1374 6.3 What is WINGs? 
 1375 ----------------------------------
 1376 WINGs Is Not GNUstep. ;) 
 1377 
 1378 It is the Widget Library written for the widgets in Window Maker. 
 1379 
 1380 It is currently under heavy development but several people have started
 1381 writing applications in it. Its goal is to emulate the NeXT(tm)-style widgets. 
 1382 
 1383 http://www.ozemail.com.au/~crn/wm/wings.html is the closest thing to an
 1384 information center about WINGs by <crn@ozemail.com.au>. 
 1385 
 1386 
 1387 6.4 Where can I get more information about WINGs? 
 1388 ----------------------------------
 1389 Nic Berstein <nic@postilion.org> has created a WINGs Developement list. 
 1390 
 1391 The purpose of this list is to provide a forum for support, ideas,
 1392 suggestions, bug reports etc. for the WINGs widget set library. 
 1393 
 1394 To subscribe to this list, send a message with the word ``subscribe'' in the
 1395 _BODY_ of the message to: <wings-request@postilion.org>. 
 1396 
 1397 
 1398 
 1399 -=-=-=-=-=-=-=-=-=-=-=-=-
 1400 Miscellaneous Questions:
 1401 -=-=-=-=-=-=-=-=-=-=-=-=-
 1402 
 1403 7.1 Is there a pager for Window Maker? 
 1404 ----------------------------------
 1405 Not at the moment because there is not a pressing need for a pager. The
 1406 concept of multiple desktops does exist and there are currently 3 ways to
 1407 switch between them. 
 1408 
 1409 First, the Alt+Number combination will switch between desktops. The
 1410 Workspaces menu will also let you switch workspaces. Lastly, the Clip will
 1411 also scroll one through workspaces. 
 1412 
 1413 For those that would like to send an application to a specific workspace,
 1414 either drag it to an edge of the desktop onto the next workspace or you can
 1415 right click on the titlebar, choose "Move to..." and choose the appropriate
 1416 workspace. 
 1417 
 1418 BUT, Window Maker does support KDE and GNOME protocols, including the
 1419 workspace management stuff, so you can use Window Maker in these
 1420 environments and use their pagers.
 1421 
 1422 
 1423 
 1424 7.2 Can I have folders like in AfterStep? 
 1425 ----------------------------------
 1426 No. Window Maker does however support the collapsable Clip per desktop
 1427 for a similar functionality. 
 1428 
 1429 
 1430 7.3 How do I use getstyle and setstyle? 
 1431 ----------------------------------
 1432 To capture the current Window Maker style, use the command 
 1433 
 1434             getstyle > current.style 
 1435           
 1436 
 1437 To replace the current style, use the command 
 1438 
 1439             setstyle filename.style
 1440 
 1441 
 1442 7.4 Why don't you distribute {normal diff, xdelta} patches? 
 1443 ----------------------------------
 1444 Whenever possible plain diff patches are distributed. If the new version has
 1445 new binary files, normal diff won't be able to handle them, so a patch
 1446 package is distributed, instead. We don't use xdelta because: - most
 1447 systems do not have xdelta installed; - xdelta is picky and require the file to
 1448 be patched to be exactly the same as the one used to make the patch. The
 1449 patch package scheme used is much more flexible. 
 1450 
 1451 We do not distribute a simple diff with the binary files separately (and
 1452 variations, like uuencoding the binary files) because: - it is more
 1453 complicated and error prone to require the user to manually move the files
 1454 to the correct places; - the current patch package scheme *does* distribute
 1455 the binary files and diff files separately. If the user wants to install everything
 1456 by hand, nobody will object to that; - sooner or later someone will certainly
 1457 ask for a script to automate the file moving stuff. 
 1458 
 1459 So we hacked a script (mkpatch) that automatically creates a patch
 1460 package with the normal text diff file, a list of removed files and the binary
 1461 files that have changed or been added, plus a script that does the patching
 1462 automatically. If you don't like the script, you can apply the patch and move
 1463 the files manually. Or download the whole distribution. 
 1464 
 1465 
 1466 7.5 Will you add GNOME or KDE support?
 1467 --------------------------------------
 1468 
 1469 Support for GNOME (and KDE) hints is included since 0.50.0.  You have to
 1470 enable them at compile-time using the appropriate arguments to ./configure.
 1471 Please read the INSTALL file for more details.
 1472 Note: starting with version 0.90.0, support for legacy Gnome-1.x and KDE-2.x
 1473 was dropped in favor of NETWM support (used by both Gnome-2.x and KDE-3.x)
 1474 
 1475 
 1476 -=-=-=-=-
 1477 Themes:
 1478 -=-=-=-=-
 1479 
 1480 8.1 What exactly are themes? 
 1481 ----------------------------------
 1482 Themes are a great aspect of Window Maker allowing a user to simply
 1483 save the entire 'look' of their desktop in a Archive to distribute freely among
 1484 friends, fellow users and/or the whole net in general. :) 
 1485 
 1486 See the theme-HOWTO at http://wm.current.nu/themes/theme-HOWTO.html 
 1487 for an in-depth walk-through on making a Theme archive. 
 1488 
 1489 
 1490 8.2 How do I install a Theme? 
 1491 ----------------------------------
 1492 This should be as simple as untarring the Theme.tar.gz into one of two
 1493 places. You can untar it to the global /usr/local/share/WindowMaker/* directory,
 1494 and have it be accessable to all users, or you can untar it to your own
 1495 ~/GNUstep/Library/WindowMaker/ directory for your own personal use. 
 1496 
 1497 Use your favorite variation of the following: 
 1498 
 1499 gzip -dc "Theme.tar.gz" | tar xvf - 
 1500 
 1501 *(directory may differ on some systems) 
 1502 
 1503 
 1504 8.3 How do I make a Theme? 
 1505 ----------------------------------
 1506 There is a neat little file called README.themes distributed with Window
 1507 Maker that explains everything in intricate detail.  You can also read
 1508 http://wm.current.nu/themes/themepacks.html
 1509 
 1510 
 1511 ====================================================================
 1512 and they lived happily ever after.
 1513 ====================================================================
 1514 (The End.)