Add wmmemload to dockapps webpage.
[whome.git] / FAQ.php
blob4df3dc79cec05dac5df1934d81663451f269dce0
1 <html xmlns="http://www.w3.org/1999/xhtml">
2 <head>
3 <meta name="generator" content="HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
5 <title>Window Maker: Home</title>
6 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
7 <link href="title.css" rel="stylesheet" type="text/css" />
8 </head>
10 <body>
11 <?php include("dock.php"); ?>
12 <?php include("header.php"); ?>
14 <div>
15 <table class="inner" border="0" cellpadding="1" cellspacing="1">
16 <tr>
17 <td content="content" colspan="2" valign="top">
18 <br />
19 <br />
22 $chapter = $_GET["chapter"];
23 if ($chapter == "") {
26 <h1>FAQ</h1>
28 <p>Have questions about Window Maker? If so, look no further. Below is our collection of Frequently Asked Questions and
29 their corresponding answers. Many of these have been adapted from the <a href=
30 "http://web.archive.org/web/20030401182339/http://www.dpo.uab.edu/~grapeape/wmfaq.html">original FAQ</a> by Chris
31 Green. Questions are routinely taken and added in from the mailing lists and IRC forums.</p>
33 <ol>
34 <li><a href="FAQ.php?chapter=1">Introduction to Window Maker</a></li>
36 <li><a href="FAQ.php?chapter=2">Installing Window Maker</a></li>
38 <li><a href="FAQ.php?chapter=3">Configuring Window Maker</a></li>
40 <li><a href="FAQ.php?chapter=4">Using Window Maker</a></li>
42 <li><a href="FAQ.php?chapter=5">Application Compatibility</a></li>
44 <li><a href="FAQ.php?chapter=6">Themes and Dockapps</a></li>
46 <li><a href="FAQ.php?chapter=7">Miscellaneous Questions</a></li>
48 <li><a href="FAQ.php?chapter=8">Troubleshooting Tips</a></li>
50 <li><a href="FAQ.php?chapter=9">Programming for Window Maker</a></li>
51 </ol>
54 if ($chapter == 1) {
56 <h1>Chapter 1: Introduction to Window Maker</h1>
57 <UL type="disc">
58 <B>1.1</B> &nbsp; <A href="#30">What is Window Maker?</A><BR>
59 <B>1.2</B> &nbsp; <A href="#31">Where can I get Window Maker?</A><BR>
60 <B>1.3</B> &nbsp; <A href="#32">Where are the mailing lists and archives?</A><BR>
61 <B>1.4</B> &nbsp; <A href="#33">Where can I find more documentation?</A><BR>
62 <B>1.5</B> &nbsp; <A href="#34">What is an appicon?</A><BR>
63 <B>1.6</B> &nbsp; <A href="#35">How can I get a question added to the FAQ?</A><BR>
64 <B>1.7</B> &nbsp; <A href="#36">How do I report bugs?</A><BR>
65 <B>1.8</B> &nbsp; <A href="#37">Is there an anomymous cvs server?</A><BR>
66 <B>1.9</B> &nbsp; <A href="#38">Where can I find the Window Maker IRC channel?</A><BR>
67 <B>1.10</B> &nbsp; <A href="#39">What is the difference between appicons, mini-windows, and minimized applications?</A><BR>
68 <B>1.11</B> &nbsp; <A href="#126">How do I make sense of Window Maker's version number scheme?</A><BR>
69 </UL>
70 <BR><HR><BR>
71 <A name="30"></A>
72 <h2>1.1 &nbsp;What is Window Maker?</h2>
73 Window Maker is an X11 window manager
74 originally designed to provide integration
75 support for the GNUstep Desktop Environment.
76 In every way possible, it reproduces the
77 elegant look and feel of the NEXTSTEP[tm]
78 user interface. It is fast, feature rich,
79 easy to configure, and easy to use. It is
80 also free software and part of the GNU
81 Project, with contributions being made by
82 programmers from around the world
83 <A name="31"></A>
84 <h2>1.2 &nbsp;Where can I get Window Maker?</h2>
85 Window Maker can be obtained from the
86 official website, http://windowmaker.org/,
87 or from various mirror sites listed at
88 http://windowmaker.org/mirrors.html
89 <A name="32"></A>
90 <h2>1.3 &nbsp;Where are the mailing lists and archives?</h2>
91 All information regarding the Window Maker
92 mailing lists can be found at http://windowmaker.org/lists.html
93 <A name="33"></A>
94 <h2>1.4 &nbsp;Where can I find more documentation?</h2>
95 Additional documentation can be found in
96 the Window Maker source distribution, or
97 at http://windowmaker.org/documentation.html
98 <A name="34"></A>
99 <h2>1.5 &nbsp;What is an appicon?</h2>
100 An appicon is the icon produced by an
101 application that initially is in the
102 bottom left corner of the screen while
103 an application is running. For an example,
104 run xterm and notice the icon in the
105 corner (make sure that you use xterm and
106 not a default rxvt when testing, because
107 many versions of rxvt do not properly set
108 their window attributes).<BR><BR>
110 For a more indepth discussion of how an
111 appicon relates to Window Maker, see
112 question 1.10
113 <A name="35"></A>
114 <h2>1.6 &nbsp;How can I get a question added to the FAQ?</h2>
115 For now, the best method is to E-mail your
116 question to faq@windowmaker.org. We are
117 working on a web-based submission form
118 to our FAQ system, which will enable
119 users to submit questions for review.
120 <A name="36"></A>
121 <h2>1.7 &nbsp;How do I report bugs?</h2>
122 You can look at the BUGFORM file in
123 the source distribution of Window Maker.
124 Alternatively, you can use the
125 Window Maker Bug Tracker at
126 http://windowmaker.org/cgi-bin/bugs
127 <A name="37"></A>
128 <h2>1.8 &nbsp;Is there an anomymous cvs server?</h2>
129 Yes there is. To check out from cvs, first
131 <PRE>
132 export CVSROOT=":pserver:anoncvs@cvs.windowmaker.org:/cvsroot"
133 cvs login
134 </PRE>
135 There is no password, so simply hit enter when prompted.
137 Then issue the following command ("wm" is the name of the module):
139 <PRE>
140 cvs -z3 checkout -d WindowMaker wm
141 </PRE>
142 To update your source tree, cd to the WindowMaker directory and type
144 <PRE>
145 cvs -z3 update -dP
146 </PRE>
147 inside the WindowMaker directory.
150 For more detailed CVS instructions, please
151 visit http://windowmaker.org/development-cvs.html
152 <A name="38"></A>
153 <h2>1.9 &nbsp;Where can I find the Window Maker IRC channel?</h2>
154 The official Window Maker IRC channel can be accessed by connecting to irc.windowmaker.org on port 6667,
155 and joining #WindowMaker
157 <A name="39"></A>
158 <h2>1.10 &nbsp;What is the difference between appicons, mini-windows, and minimized applications?</h2>
159 Thanks to Jim Knoble for this answer:
161 Many window managers are capable of turning large windows into
162 smaller `icons' which represent the window yet don't take as much
163 screen real estate. We're all familiar with that model.
165 Window Maker has two kinds of these icons. One kind is created when
166 an application---technically, a window group---is started. It
167 represents the entire application and is called an `appicon'. Such
168 icons are square tiles containing only the picture which represents
169 the application; they have no titles.
171 The second kind of icon in Window Maker is created when a particular
172 window (possibly one belonging to an application displaying more than
173 one window) is `miniaturized' (which is the same action as
174 `minimizing' or `iconifying' in other window management models) using
175 the miniaturization button on the window's titlebar. These
176 miniaturized windows are called `miniwindows' and can normally be
177 distinguished from appicons by their small titlebar at the top of the
178 tile.
179 <A name="126"></A>
180 <h2>1.11 &nbsp;How do I make sense of Window Maker's version number scheme?</h2>
181 The numbering scheme is relatively simple,
182 and is in the format of three numbers separated
183 by dots. The first number is the "major" revision
184 number. The second is the "minor" revision number.
185 And finally, the third is the "patch level" number.
187 To put this all into perspective, let's examine the
188 version number "0.65.1". This number signifies
189 that there has not been a major revision release,
190 that its minor revision is newer than the previous
191 one (0.64.x), and that it's on the first patch level
192 after the 0.65.0 release. This still might be
193 confusing, so go away with this in mind: numbers
194 ending in .0 tend to be new feature releases
195 but less stable than .1, .2, .3 patch level releases,
196 the latter of which are used to fix bugs.
198 It is generally safe to go with the highest numbered
199 patch release.
203 if ($chapter==2) {
206 <h1>Chapter 2: Installing Window Maker</h1>
207 <UL type="disc">
208 <B>2.1</B> &nbsp; <A href="#41">Why are no icons showing up after installing Window Maker?</A><BR>
209 <B>2.2</B> &nbsp; <A href="#42">How do I make Window Maker link against libtiff?</A><BR>
210 <B>2.3</B> &nbsp; <A href="#44">How do I switch CDE's window manager to use WindowMaker?</A><BR>
211 <B>2.4</B> &nbsp; <A href="#46">Do I need to rerun wmaker.inst with every new version of Window Maker?</A><BR>
212 <B>2.5</B> &nbsp; <A href="#47">Why am I only getting a root menu with xterm and exit items?</A><BR>
213 <B>2.6</B> &nbsp; <A href="#48">How do I get Window Maker to use more than 16 colors on my SGI Indy Workstation?</A><BR>
214 <B>2.7</B> &nbsp; <A href="#49">Using WindowMaker with Solaris 2.6 CDE</A><BR>
215 <B>2.8</B> &nbsp; <A href="#51">How do I install Window Maker on a Solaris box?</A><BR>
216 <B>2.9</B> &nbsp; <A href="#52">How do I fix an error such as libwraster.so.1: cannot open shared object file?</A><BR>
217 <B>2.10</B> &nbsp; <A href="#53">How do I fix an error dealing with aclocal: configure.in: 15: macro 'AM_PROG_LIBTOOL' not found in library?</A><BR>
218 <B>2.11</B> &nbsp; <A href="#55">When I run wmaker, it quits complaining about '__register_frame_info'</A><BR>
219 <B>2.12</B> &nbsp; <A href="#56">How do I make libjpeg link against Window Maker?</A><BR>
220 <B>2.13</B> &nbsp; <A href="#57">How do I start Window Maker after running wmaker.inst?</A><BR>
221 <B>2.14</B> &nbsp; <A href="#58">How do I make libpng link against Window Maker?</A><BR>
222 <B>2.15</B> &nbsp; <A href="#59">How do I make giflib or libungif to link against Window Maker?</A><BR>
223 <B>2.16</B> &nbsp; <A href="#60">How do I fix an error similar to "wrlib: could not allocate shared memory segment: invalid argument"</A><BR>
224 <B>2.17</B> &nbsp; <A href="#61">How do I add Window Maker to the Solaris dtlogin screen?</A><BR>
225 <B>2.18</B> &nbsp; <A href="#127">What happened to libPropList?</A><BR>
226 </UL>
227 </FONT>
228 <BR><HR><BR>
229 <A name="41"></A>
230 <h2>2.1 &nbsp;Why are no icons showing up after installing Window Maker?</h2>
231 As of WindowMaker version 0.15.0, the default setup includes .tiff icons which
232 require you to have compiled Window Maker with libtiff support. For assistance
233 on compiling libtiff, see the following question.
234 <A name="42"></A>
235 <h2>2.2 &nbsp;How do I make Window Maker link against libtiff?</h2>
236 Many UNIX operating systems have
237 difficulty finding third party libraries
238 by default. Unfortunately, there are too
239 many of these to include instructions for
240 them all.
242 In general, you will want to ensure the
243 latest version of libtiff is installed (see
244 ftp://www.libtiff.org). Typically on non-Linux
245 systems, libtiff will be located under
246 /usr/local, with includes and libs in those
247 respective sub-directories.
249 Often, it will be necessary to add /usr/local/lib
250 to the system's LD_LIBRARY_PATH environment
251 variable (especially so on Solaris, but see 'man ld'
252 for details on your platform). Furthermore,
253 it is possible to supply special flags to the
254 configure script to help it find where the libraries
255 are. An example is given below:<BR>
257 <PRE>
258 ./configure --with-libs-from="-L/usr/local/lib" \
259 --with-incs-from="-I/usr/local/include"
260 </PRE>
263 Also, you will want to make sure you're using GNU make
264 (gmake) for the Window Maker compile.
265 <A name="44"></A>
266 <h2>2.3 &nbsp;How do I switch CDE's window manager to use WindowMaker?</h2>
267 Method 1:
269 Peter Ilberg gives us this answer:
271 Install WM wherever you want it, mine is in /opt/WindowMaker-0.16.0 (eg. use
272 ./configure --prefix=/opt/WindowMaker-0.16.0). Run the install script wmaker.inst in
273 your home directory.
275 Add the following two lines to .dtprofile in your home directory:
277 <PRE>
278 SESSIONTYPE=xdm; export SESSIONTYPE
279 PATH=:/usr/contrib/bin/X11:$PATH:.; export PATH
280 </PRE>
281 This tells CDE to go looking for an .xinitrc/.xsession instead of using the default
282 environment.
284 Make your .xsession/.xinitrc executable (VERY IMPORTANT, wmaker.inst did NOT
285 do this automatically for me) using eg.
287 <PRE>
288 chmod ugo+x .xsession
289 </PRE>
290 Your .xsession/.xinitrc should look something like this:
292 <PRE>
293 #!/bin/sh
294 </PRE>
295 <PRE>
296 &lt;some other init stuff that you want/need&gt;
297 </PRE>
298 <PRE>
299 exec wmaker
300 </PRE>
301 Things to try if it doesn't work: (somewhat fuzzy and random)
303 This should do it although I did have problems sometimes initially which I fixed by
304 randomly trying absolute pathes for wmaker in .xsession/.xinitrc and/or making the
305 dtprofile/.xinitrc/etc executable. It helps logging in on the console (select from CDE
306 login screen) and start X manually using "X". If it works that way it should work when
307 logging into the CDE environment. Remember to Check your paths!
309 If it doesn't work, you can also substitute some other window manager for wmaker in
310 the .xinitrc and see if that works. If it does you know at least that .xinitrc is getting
311 called/executed, so your WM path is wrong or not set.
313 Method 2:
315 Thomas Hanselman gave this alternative answer (via Peter Ilberg):
317 Build and install WM wherever you want, as described in Method 1. You can install
318 and run WM just fine from your home directory. That's what I'm doing, since I don't
319 have root access at work :(. Then, in your Xdefaults file in your home directory, add
320 the following line:
322 <PRE>
323 Dtsession*wmStartupCommand: &lt;path to WindowMaker executable&gt;
324 </PRE>
325 Then, log out, and log back in, and, unless I've forgotten a step (or this is a custom
326 Nortel thing), you should be in Window Maker heaven ;).
328 Difference between the methods: (according to Thomas)
330 I've been told that the difference between setting the resource and Peter's method is
331 that if you override the window manager with the resouce, you still get the CDE
332 resources read into the resource database (so you still have your color settings &amp;
333 such from CDE), whereas with Peter's, the CDE resource don't get read into the
334 database. I don't know if this is true or not, however. Also, another thing to note with
335 Window Maker and HP-UX 10.20 -- if you select "Exit Session" from the WM root
336 menu, WindowMaker and all of your applications are killed, but you may not be
337 logged out. Again, this might be an artifact from my work environment, or the way I
338 start Window Maker.
340 Owen Stenseth adds:
342 When using this method it is possible to exit Window Maker cleanly by using the
343 dtaction command. I use the following in my Window Maker menu:
345 <PRE>
346 "Exit Session" EXEC dtaction ExitSession
347 </PRE>
349 The only problem I have at the moment is I seem to get multiple copies of asclock
350 running when I log in again.
351 <A name="46"></A>
352 <h2>2.4 &nbsp;Do I need to rerun wmaker.inst with every new version of Window Maker?</h2>
353 Dan Pascu reveals the answer:
355 If this is necessary, it will be listed in the NEWS
356 file included in the source distribution.
357 Since 0.15.x, the domain files have been changed
358 in such a way that re-running wmaker.inst is
359 redundant. The user config files are by default
360 merged in with the global ones normally located
361 in /usr/local/share/WindowMaker/Defaults.
362 So, even if new options are added, they should
363 be automatically added to the environment.
364 <A name="47"></A>
365 <h2>2.5 &nbsp;Why am I only getting a root menu with xterm and exit items?</h2>
366 Most likely, the problem is that Window Maker can not find a copy of the C pre
367 processor in a directory such as /lib. The file /lib/cpp should be a symbolic link to
368 whatever C compiler's cpp you are using. For example:
370 <PRE>
371 cpp -&gt; /usr/bin/cpp-2.95*
372 </PRE>
373 Another possibility is your /usr/X11/lib/X11/xinit/xinitrc is a
374 broken symlink. Either create a new symlink, or do something like:
376 <PRE>
377 $ cp /usr/X11/lib/X11/xinit/xinitrc.fvwm2 \
378 /usr/X11/lib/X11/xinit/xinitrc.wmaker
379 </PRE>
380 <PRE>
381 $ ln -sf /usr/X11/lib/X11/xinit/xinitrc.wmaker \
382 /usr/X11/lib/X11/xinit/xinitrc
383 </PRE>
384 then just edit /usr/X11/lib/X11/xinit/xinitrc and replace the exec of 'fvwm2'
385 by '/usr/local/bin/wmaker' (should be somewhere towards the end of the file,
386 most probably the very last line).
388 Thanks to Tomas Szepe for the second part.
389 <A name="48"></A>
390 <h2>2.6 &nbsp;How do I get Window Maker to use more than 16 colors on my SGI Indy Workstation?</h2>
391 Thanks to Peter H. Choufor this answer:
393 By default, the SGI X Server uses 8-bit Pseudocolor mode.
394 To change it, edit (as root) the file /usr/lib/X11/xdm/Xservers.
395 Change it to read:
397 <PRE>
398 :0 secure /usr/bin/X11/X -bs -c -class TrueColor -depth 24
399 </PRE>
400 <A name="49"></A>
401 <h2>2.7 &nbsp;Using WindowMaker with Solaris 2.6 CDE</h2>
402 Thanks to Rob Funk for this answer:
404 Assuming you installed Window Maker according to the README's that come
405 with the source, all you need to run Window Maker on a Solaris box is
406 an entry in the .xinitrc. This should work for any version. When
407 you run wmaker.inst the first time, allow it to make changes
408 to the .xinitrc file. Mine looks like this:
410 <PRE>
411 #!/bin/sh
412 # Window Maker Default .xinitrc
413 exec /usr/local/bin/wmaker
414 </PRE>
415 Believe it or not, that's all that it takes. This, in fact, runs Window Maker
416 instead of OpenWindows. In order to choose Window Maker, you simply choose
417 "OpenWindows Desktop" in the "Options - Session" Menus And Choose "CDE
418 Desktop" if you want CDE.
420 The color schemes and settings for Window Maker are seperate from CDE.
421 I tested on a SPARC 10, but I assume Solaris x86 would work also.
423 (webmaster note: It works fine on Solaris x86)
424 <A name="51"></A>
425 <h2>2.8 &nbsp;How do I install Window Maker on a Solaris box?</h2>
426 Here are some hints from John Kemp:
428 Installing Window Maker on a Solaris 2.6 box might require
429 one or two little hints. Here you are (this was on a system
430 running xdm by the way, but similar suggestions apply otherwise):
432 1) /usr/openwin/lib/X11/xdm/Xservers like this:
434 :0 local /usr/openwin/bin/X -dev /dev/fb defdepth 24 defclass TrueColor
436 2) Turn off shm in the WindowMaker configure:
438 ./configure --disable-shm
440 3) might have to modify your LD_LIBRARY_PATH:, or make "wmaker"
441 <PRE>
442 a script that does it for you (mv wmaker wmaker.exe):
443 </PRE>
444 LD_LIBRARY_PATH=/usr/local/lib:/usr/local/X11/lib:/usr/lib:/usr/openwin/lib
445 export LD_LIBRARY_PATH
446 /usr/local/bin/wmaker.exe $*
448 The real key is the "--disable-shm".
450 (webmaster note: Window Maker should work fine with
451 SHM enabled, at least it does under Solaris 8. Try
452 the default first, and then use this if you run into
453 problems with it)
454 <A name="52"></A>
455 <h2>2.9 &nbsp;How do I fix an error such as libwraster.so.1: cannot open shared object file?</h2>
456 If you have an error when running Window Maker such as
458 <PRE>
459 libwraster.so.1: cannot open shared object file
460 </PRE>
461 These are the instructions for Linux.
463 First, make sure that /usr/local/lib ( or whatever directory you installed Window Maker to)
464 is listed in your /etc/ld.so.conf ). You need to run ldconfig so the new shared libraries will be loaded.
465 After running ldconfig as root, the linker should properly load the libraries.
466 You need to run this every time you update Window Maker.
468 Thanks to Joseph Czapiga, the BSD procedure for adding shared
469 library directories is
471 <PRE>
472 ldconfig -m /usr/local/lib (m means merge)
473 </PRE>
474 <A name="53"></A>
475 <h2>2.10 &nbsp;How do I fix an error dealing with aclocal: configure.in: 15: macro 'AM_PROG_LIBTOOL' not found in library?</h2>
476 You need to install libtool.
477 It also must be a libtool different from version 1.2b ( shipped with redhat 5.2 ).
478 You can get libtool from ftp.gnu.org/pub/gnu
479 Make sure the autoconf and automake versions you have installed are at
480 least:
481 autoconf 2.12
482 automake 1.3
483 libtool 1.2
485 <PRE>
486 From Blaine Horrocks:
487 </PRE>
488 "You can also work around this problem on RedHat5.2 by copying the
489 distributed aclocal.m4 to acinclude.m4 before running configure for the
490 first time. Configure works fine and doing the make succeeds."
491 <A name="55"></A>
492 <h2>2.11 &nbsp;When I run wmaker, it quits complaining about '__register_frame_info'</h2>
493 This is related to having compiled Window Maker on a system whose libraries were compiled
494 by egcs or gcc 2.8.0, and then using the binaries on a system whose libraries were compiled
495 by gcc 2.7.2.x
497 Try compiling Window Maker with the newer gcc or recompile your system libraries
498 with the older gcc. It's generally a bad idea to mix and match.
499 <A name="56"></A>
500 <h2>2.12 &nbsp;How do I make libjpeg link against Window Maker?</h2>
501 The newest jpeg libs are availible at http://www.ijg.org
503 How many of you have seen that darned "lib reports 62 caller expects 61" type
504 of error? Here are some answers that will possibly help you out.
506 First things first. As always, make sure there are not older copies of libjpeg
507 floating around on your system. ]Some distributions by default come
508 with an old libjpeg.so.1 in the /usr/X11R6/lib/ directory. This can simply be
509 deleted. Or if something complains after you delete it, recompile it if you
510 can to look for the new lib in the right place, or if that fails, as a last
511 resort, you might add a symlink to the new lib like so:
512 ln -s /usr/local/lib/libjpeg.so.6.0.2 libjpeg.so.1
514 Note that you should use your system's version of ldconfig
515 to properly manage your library cache (or other appropriate
516 mechanism).
518 On Linux, this would mean having /usr/local/lib in
519 /etc/ld.so.conf and then running ldconfig.
521 Now on to the error. This is basically caused
522 by your application having been compiled to
523 dynamically use the libjpeg.so shared library.
524 When you install a new lib and then try to run
525 your program again, it expects the lib it was
526 compiled against, in this case the older
527 libjpeg.so.6.0.1 and instead finds libjpeg.so.6.0.2
528 and reports the error.
530 The fix is actually rather simple. Along with adding a
531 libjpeg.so.6 symlink like so (just in case):
532 ln -s libjpeg.so.6.0.2 libjpeg.so.6 where you installed
533 your new lib, you simply need to recompile your app to
534 link it against the new library.
536 Also, make sure to use GNU make for the Window Maker compile.
537 <A name="57"></A>
538 <h2>2.13 &nbsp;How do I start Window Maker after running wmaker.inst?</h2>
539 As of version 0.53.0, the wmaker.inst script will modify your X startup script
540 ( .xinitrc or .Xclients or .Xsession ) to do something thats (hopefully)
541 appropriate.
543 In order to run wmaker, a user needs to have an ~/.xinitrc
544 file consisting of something similar to
546 <PRE>
547 #!/bin/sh
548 exec wmaker
549 </PRE>
551 This will vary from system to system, but the existance
552 of an .xinitrc file will generally override the system
553 defaults.
554 <A name="58"></A>
555 <h2>2.14 &nbsp;How do I make libpng link against Window Maker?</h2>
556 The newest png libs are availible at http://www.libpng.org/pub/png/libpng.html
558 You should also get the newest zlib libs from
559 http://www.gzip.org
561 Generally, the same rules apply here as with libjpeg. Make sure there are no
562 older versions of the necessary libs floating around on your system, then try
563 to configure and make again.
565 Also, make sure to use GNU make (gmake) for the Window Maker compile.
566 <A name="59"></A>
567 <h2>2.15 &nbsp;How do I make giflib or libungif to link against Window Maker?</h2>
568 The newest versions of both these libraries are available at
569 http://prtr-13.ucsc.edu/~badger/software/
572 Users have had a few problems with giflib... it seems that the install process didn't
573 install the header file libgif.h, so although the Window Maker configure found
574 the lib (libgif.so.x), when you actually try to compile, it fails when it looks for
575 the header to include the make. One solution is to simply copy it from the libgif
576 source directory to the local system include directory. (/usr/local/include/ on many
577 systems).
579 Also, make sure to use GNU make (gmake) for the Window Maker compile.
580 <A name="60"></A>
581 <h2>2.16 &nbsp;How do I fix an error similar to "wrlib: could not allocate shared memory segment: invalid argument"</h2>
582 This relates to a shared memory problem on
583 Solaris. Usually one can't see it - but it is visible if X
584 is started from command line (or fail-safe session for that
585 matter). In any of the cases, on the stderr you get an error
586 message like this:
588 <PRE>
589 "wrlib: could not allocate shared memory segment: invalid argument"
590 </PRE>
591 This one is generated by wrlib if Window Maker is compiled with
592 shared-memory usage enabled (which is the default). The explanation
593 is that Solaris by default comes with a shared memory segment size
594 of maximum 1 M. What happends is that if you have a really-really
595 cool(tm) background, it is usually much bigger than that 1 M segment
596 of shared memory. To see your defaults relating the IPC settings check
597 the output of the "sysdef" command (look for IPC Shared Memory). There
598 you should see the maximum allocable size for a shared memory segment. If
599 it is less than 5 M you should really increase it by adding the following
600 line in your /etc/system file:
602 <PRE>
603 set shmsys:shminfo_shmmax=20971520
604 </PRE>
606 *) Make sure you don't already have this value set. If you do,
607 simply increase the value. In case you have a much
608 bigger value, stick to what you have, because you should have
609 no problems with it.<BR>
610 *) The value allows a maximum segment size of 20 M, which really
611 should be enough for anyone. If not, try using a smaller background
612 image!<BR>
613 *) Make sure you spell the line <I>exactly</I> as shown, otherwise
614 at boot time the kernel will complain of not finding such a module
615 name and will not set a thing about it!<BR>
616 *) Make sure you don't delete other lines or modify them "beyond
617 recognition", for evil things may happen at boot time.<BR>
619 After adding this to your /etc/system you need to reboot
620 in order for the new limit to take effect.
621 Also, you may want to check the new limit just
622 to make sure it has been set.
624 Thanks to Bogdan Iamandei for this answer.
625 <A name="61"></A>
626 <h2>2.17 &nbsp;How do I add Window Maker to the Solaris dtlogin screen?</h2>
627 The two files that
628 determine alternate window managers are:
630 <PRE>
631 /usr/dt/config/C/Xresources.d/Xresources.*
632 /usr/dt/config/Xsession.*
633 </PRE>
634 If you look in there, you'll find Xresources.ow and Xsession.ow,
635 respectively. All you need are two files that set up Window Maker (or
636 any other window manager) in a similar fashion, calling them
637 Xresources.wm and Xsession.wm (or whichever extension you prefer).
639 Here is an example setup:
642 <PRE>
644 **************************************************************************
646 # Window Maker config file
647 # Mike Bland &lt;mbland@cmu.edu&gt;
649 # /usr/dt/config/C/Xresources.d/Xresources.wm
651 # used by dtlogin
654 **************************************************************************
655 </PRE>
656 <PRE>
657 Dtlogin*altDtsIncrement: True
658 </PRE>
659 <PRE>
660 Dtlogin*altDtName: Window Maker
661 Dtlogin*altDtKey: /usr/local/bin/wmaker
662 Dtlogin*altDtStart: /usr/dt/config/Xsession.wm
663 #Dtlogin*altDtLogo: /usr/local/share/logos/WM_logo.xpm
664 </PRE>
665 <PRE>
666 # Once I get a logo ready, I'll add it to the dtlogin screen by
667 uncommenting
668 # the last line.
669 </PRE>
671 And this example script:
673 <PRE>
674 #!/bin/ksh
676 **************************************************************************
678 # Window Maker startup script
679 # Mike Bland &lt;mbland@cmu.edu&gt;</A>
680 # /usr/dt/config/Xsession.wm
682 # used by dtlogin
685 **************************************************************************
686 </PRE>
687 <PRE>
688 . /usr/local/etc/.profile # Sources the file containing necessary
689 # environment variables (especially
690 # LD_LIBRARY_PATH=/usr/local/lib:...);
691 # make sure it's executable.
692 </PRE>
693 <PRE>
694 WINDOW_MANAGER=/usr/local/bin/wmaker
695 </PRE>
696 <PRE>
697 export WINDOW_MANAGER
698 </PRE>
699 <PRE>
700 /usr/local/bin/wmaker
701 </PRE>
702 <A name="127"></A>
703 <h2>2.18 &nbsp;What happened to libPropList?</h2>
704 The libPropList dependency has been removed as of Window Maker version 0.70.0,
705 and is replaced by cleaner, more robust code in the WINGs toolkit. This new code maintains existing proplist compatibility,
706 so there are no visable changes for users, and existing file formats will work as they did before.
710 For developers, there is a proplist-compat.h header that provides a mapping between the old and new function names. See the comments in this file for further instructions.<BR>
711 </BLOCKQUOTE>
715 if ($chapter == 3) {
717 <h1>Chapter 3: Configuring Window Maker</h1>
718 <UL type="disc">
719 <B>3.1</B> &nbsp; <A href="#73">What are those files inside my ~/GNUstep directory?</A><BR>
720 <B>3.2</B> &nbsp; <A href="#74">How do I enable the normal X sloppy focus mode?</A><BR>
721 <B>3.3</B> &nbsp; <A href="#75">How do I get my auto-arrange icons to work?</A><BR>
722 <B>3.4</B> &nbsp; <A href="#76">How do I get my Meta-Tab to cycle through windows correctly?</A><BR>
723 <B>3.5</B> &nbsp; <A href="#77">How do I get a tile background for my appicons (those things in the dock)?</A><BR>
724 <B>3.6</B> &nbsp; <A href="#78">How do you dock &lt;insert program here&gt; that doesn't have an appicon in the new version of WindowMaker?</A><BR>
725 <B>3.7</B> &nbsp; <A href="#79">How do I get x11amp to not have a title bar ( or any other program for that matter )?</A><BR>
726 <B>3.8</B> &nbsp; <A href="#80">How do I set a pixmap background?</A><BR>
727 <B>3.9</B> &nbsp; <A href="#81">Can I put pixmaps in my root menu and title bars?</A><BR>
728 <B>3.10</B> &nbsp; <A href="#82">How do I get my Minimize Icon to look like the triangle I see in screenshots?</A><BR>
729 <B>3.11</B> &nbsp; <A href="#83">Why does Netscape have a black and white Icon when I minimize it?</A><BR>
730 <B>3.12</B> &nbsp; <A href="#84">How do I get superfluous bells and whistles working?</A><BR>
731 <B>3.13</B> &nbsp; <A href="#85">How do I get the classic NeXT(tm)-like style back?</A><BR>
732 <B>3.14</B> &nbsp; <A href="#86">How do I get the window menu with only a two button mouse?</A><BR>
733 <B>3.15</B> &nbsp; <A href="#87">How do I edit my root menu?</A><BR>
734 <B>3.16</B> &nbsp; <A href="#88">WPrefs disappeared from the Dock! How do I get it back?</A><BR>
735 <B>3.17</B> &nbsp; <A href="#89">How can I define my own Icon for a program? (instead of the Icon the Application Supplies?)</A><BR>
736 <B>3.18</B> &nbsp; <A href="#90">How do I turn off the workspace titles between workspaces?</A><BR>
737 <B>3.19</B> &nbsp; <A href="#91">How do I add dynamic items to my root menu?</A><BR>
738 <B>3.20</B> &nbsp; <A href="#92">How do I remove or hide appicons?</A><BR>
739 <B>3.21</B> &nbsp; <A href="#93">I disabled my titlebar. How can I get it back?</A><BR>
740 <B>3.22</B> &nbsp; <A href="#94">How do I remove ALT+Mouse1 from the action Window Maker grabs for an application?</A><BR>
741 <B>3.23</B> &nbsp; <A href="#95">How do I configure the Dock and Clip to use less space on a small screen?</A><BR>
742 <B>3.24</B> &nbsp; <A href="#128">Why do dashes not work as menu entries?</A><BR>
743 </UL>
744 </FONT>
745 <BR><HR><BR>
746 <A name="73"></A>
747 <h2>3.1 &nbsp;What are those files inside my ~/GNUstep directory?</h2>
748 Here is a synopsis of the files in ~/GNUstep
750 ~/GNUstep/WindowMaker/WindowMaker is main config file. This
751 file controls options such as keybindings, fonts,
752 pixmaps, and focus modes.
754 ~/GNUstep/WindowMaker/WMWindowAttributes controls the
755 "attributes" for individual applications and appicons.
756 Options such as what icon to use are set here. For the
757 most part, this is now best accessed via a right click
758 on a title bar of an application and selecting
759 "Attributes"
761 ~/GNUstep/Defaults/WMState is the file that is
762 automatically generated and contains the current
763 dock settings. It is not recommended to edit this
764 file by hand.
766 ~/GNUstep/Defaults/WMRootMenu specifies what file to use
767 as the root menu. In Window Maker 0.19.0 and higher, this
768 file should be replaced by plmenu from ~/GNUstep/Defaults/WindowMaker
769 so that one can use WPrefs.app to edit the menu.
771 ~/GNUstep/Library/WindowMaker/menu is used to change your root menu,
772 if you are using the old menu style.
773 <A name="74"></A>
774 <h2>3.2 &nbsp;How do I enable the normal X sloppy focus mode?</h2>
775 If you are using WPrefs, you can choose the ``Window Focus Prefrences''
776 tab and then select the ``Input Focus Mode'' Slider.
778 Scroll Down and choose ``Sloppy'' Focus Mode.
780 You may also use a text editor on
782 <PRE>
783 ~/GNUstep/Defaults/WindowMaker
784 </PRE>
785 and change the following:
787 <PRE>
788 FocusMode = sloppy;
789 </PRE>
790 <A name="75"></A>
791 <h2>3.3 &nbsp;How do I get my auto-arrange icons to work?</h2>
792 In WPrefs, choose the ``Icon Prefrences Tab'' and select the
793 ``Auto Arrange Icons'' Checkbox.
795 Or in
796 <PRE>
797 ~/GNUstep/Defaults/WindowMaker
798 </PRE>
800 <PRE>
801 AutoArrangeIcons=YES;
802 </PRE>
803 and the icons should now auto-arrange.
804 <A name="76"></A>
805 <h2>3.4 &nbsp;How do I get my Meta-Tab to cycle through windows correctly?</h2>
806 To use WPrefs to modify these, choose the ``Ergonomic Prefrences'' tab and
807 check ``Raise window when switching focus with keyboard (Circulate Raise)''
809 Or you can use a text editor to make sure that these settings are in your
810 ~/GNUstep/Defaults/WindowMaker file:
812 <PRE>
813 CirculateRaise = YES;
814 RaiseDelay = 1;
815 </PRE>
816 As of 0.61.0, MS Window's Style application tabbing is supported by default.
817 <A name="77"></A>
818 <h2>3.5 &nbsp;How do I get a tile background for my appicons (those things in the dock)?</h2>
819 These can all be adjusted by the ``Appearance Preferences'' tab in
820 WPrefs.
822 Select the tile and then choose the edit texture dialog. Then you may
823 choose any of the different tile background options in the
824 The old text editor method is provided below for convience.
826 You need to change one line in your '~/GNUstep/Defaults/WindowMaker' file.
828 <PRE>
829 IconBack = (spixmap, tile.black.xpm, white);
830 </PRE>
831 The last parameter is the color that fills in any transparent
832 parts of your icon.
833 <A name="78"></A>
834 <h2>3.6 &nbsp;How do you dock &lt;insert program here&gt; that doesn't have an appicon in the new version of WindowMaker?</h2>
835 There is now an option available to emulate appicons so that Window Maker
836 can dock just about anything now. To dock a misbehaving application, right click
837 on the title bar and select the attributes menu. Next, select the pull down menu's
838 "Advanced Options" item. Under the ``Advanced Options'' menu, select the ``Emulate
839 Application Icon'' Option then Save, Apply and close the dialog.
841 This should allow you do dock the program normally.
843 Dan Pascu adds:
845 Emulate Appicon does exactly the same as dockit. So if Emulate Appicon
846 does not work, dockit will not work either.
847 For such apps you can do nothing. They are badly coded (they do not
848 set the instance.class hints). For these Attributes are also not
849 available, since attributes apply to an instance and/or class hint.
851 Note: Dockit was previously distributed with Window Maker and was launched
852 from the top dock icon.
854 Elliott Potter adds:
856 There's another way to dock applications that misbehave ... I've only
857 done this with a couple of things (Adobe AcroRead is the only one I
858 remember at the moment).
860 If Attributes -> Advanced Options -> Emulate Application Icon doesn't
861 work:
863 Dock another application to the clip, where you want your application to
864 go. I used gv, but anything you can dock will work.
865 Quit WindowMaker
866 Edit ~/GNUstep/Defaults/WMState
867 If you're docking to the clip, scroll down to the Workspaces section.
868 When you find whatever you docked, you'll see:
869 <PRE>
871 Command = gv;
872 Name = GV.gv;
873 AutoLaunch = No;
874 Forced = No;
875 BuggyApplication = No;
876 Position = "6,0"
877 Omnipresent = No;
878 DropCommand = "gv %d";
880 </PRE>
881 Edit it to use the info for your new application:
882 <PRE>
884 Command = acroread; # use the full pathname if you have to
885 Name = acroread.acroread;
886 AutoLaunch = No;
887 Forced = No;
888 BuggyApplication = No;
889 Position = "6,0"
890 Omnipresent = No;
891 DropCommand = "acroread %s";
893 </PRE>
894 Then edit WMWindowAttributes, and add a line for your application's
895 icon...you can edit the line that was inserted, or make a new one - I
896 just make a new one:
897 acroread.acroread = {Icon = pdf.tiff;};
900 Then re-start WindowMaker, and your icon should be there! You can move
901 it around like any other docked app now, but the Attributes section
902 still won't work.
903 <A name="79"></A>
904 <h2>3.7 &nbsp;How do I get x11amp to not have a title bar ( or any other program for that matter )?</h2>
905 Right Click on the title bar and go to the attributes menu. Click on Window Attributes and click
906 the the Disable titlebar and Disable Resizebar options. Click Save, and then click
907 Apply then close the Attributes panel.
909 By Default, to get back to the attributes menu, use the key combination Control-Esc.
910 <A name="80"></A>
911 <h2>3.8 &nbsp;How do I set a pixmap background?</h2>
912 Here is the in depth explanation straight from the NEWS file:
914 wmsetbg now accepts the following options:
915 <PRE>
916 usage: wmsetbg [-options] image
917 options:
919 dither image
921 match colors
923 tile image
925 scale image (default)
927 update Window Maker domain database
928 -D &lt;domain&gt;
929 update &lt;domain&gt; database
930 -c &lt;cpc&gt;
931 colors per channel to use
932 </PRE>
935 By default, it will try to guess if dithering is needed or not and proceed
936 accordingly.
937 Using -d or -m will force it to dither or match colors.
939 Dithering for more than 15bpp is generally not needed, and will only result
940 in a slower processing.
941 Don't use dithering except when needed, because it is slower. Else rely on
942 wmsetbg which will detect if dithering is needed and use it.
945 <PRE>
946 will update the WorkspaceBack in the default database
947 domain file in ~/GNUstep/Defaults/WindowMaker, and let Window
948 Maker refresh the screen. Please note that this option only
949 works under Window Maker, and will have no effect under
950 other window managers, since it rely on Window Maker to
951 update the image after it reads the updated defaults
952 database.
953 </PRE>
955 <PRE>
956 &lt;domain&gt; is same as above, but will update the domain
957 &lt;domain&gt; instead of the default Window Maker domain.
958 </PRE>
960 <PRE>
961 &lt;cpc&gt; will set the color per channel to use. Only needed for
962 PseudoColor visuals. Window Maker will automatically pass
963 the value read from the Window Maker domain database.
964 </PRE>
967 The following line is straight from your WindowMaker-0.15.x
968 ~/GNUstep/Library/WindowMaker/menu file and should all be on one line.
970 "Images" OPEN_MENU BACKGROUNDS_DIR
971 ~/GNUstep/Library/WindowMaker/Backgrounds WITH wmsetbg -u -t
973 This should give you an idea on how to add other entries for different image
974 directories. See the help info at the top of the
975 ~/GNUstep/Library/WindowMaker/menu file for more information.
977 If you for some reason would like to set your background image with XV, for
978 instance to use an image format not yet supported by wmsetbg or to use one
979 of XV's special modes, edit the file ~/GNUstep/Library/WindowMaker/autostart
980 and insert the line
982 <PRE>
983 xv -root -quit -maxpect ~/background.jpg
984 </PRE>
986 <PRE>
987 xv -root -quit -max ~/background.jpg
988 </PRE>
989 you can also try variations of this to get different tiling and other effects
990 (where X is a number 1-9 I believe):
991 'xv -root -quit -rmodeX ~/background.jpg'
993 If you would like xv functionality in your menu, heres a nice little tip from
994 Alfredo:
996 Add the following line to your ~/GNUstep/Library/WindowMaker/menu file. (all on
997 one line)
999 "More Backgrounds" OPEN_MENU /home/whoever/backgrounds xv -root -maxpect -quit
1000 <A name="81"></A>
1001 <h2>3.9 &nbsp;Can I put pixmaps in my root menu and title bars?</h2>
1002 Put the pixmaps in a directory that is located in your pixmap path set
1003 on ``Search Path Configuration'' Tab.
1005 Then switch ``Appearance Preferences'' tab and select what widget you would
1006 to adjust under the ``Texture'' tab. Click edit. Chose an image texture format
1007 and then search for the texture.
1009 You can use a similar procedure for any type of menu editing.
1011 You can use png, gif, ppm, tiff, jpeg and xpm images interchangeably in
1012 Window Maker if you have compiled in support for those formats.
1013 <A name="82"></A>
1014 <h2>3.10 &nbsp;How do I get my Minimize Icon to look like the triangle I see in screenshots?</h2>
1015 This involves a minor source tweak. Instructions are available at
1016 http://largo.windowmaker.org/tips.php#titlebar_icons
1017 <A name="83"></A>
1018 <h2>3.11 &nbsp;Why does Netscape have a black and white Icon when I minimize it?</h2>
1019 Craig Maloney has this answer:
1021 If you happen to --enable-openlook at compile time,
1022 Netscape (and presumably other apps as well) believe
1023 they're running under OLVWM, and minimise with
1024 monochrome icons. Once compiled without OpenLook support,
1025 Netscape minimizes with the correct icon.
1026 <A name="84"></A>
1027 <h2>3.12 &nbsp;How do I get superfluous bells and whistles working?</h2>
1028 Open WPrefs and go under the ``Other Configurations'' tab. Under
1029 ``Animations and Sound'', depress the Superfluous tab.
1031 Alternatively, you may add
1032 <PRE>
1033 Superfluous=YES;
1034 </PRE>
1035 to your ~/GNUstep/Defaults/Windowmaker file.
1036 </PRE>
1037 <A name="85"></A>
1038 <h2>3.13 &nbsp;How do I get the classic NeXT(tm)-like style back?</h2>
1039 Open WPrefs and go under the ``Other Configurations'' tab. Under ''Title Bar Style'',
1040 select the classic look.
1042 Or you can add
1043 <PRE>
1044 NewStyle=NO;
1045 </PRE>
1046 to your ~/GNUstep/Defaults/Windowmaker file.
1047 <A name="86"></A>
1048 <h2>3.14 &nbsp;How do I get the window menu with only a two button mouse?</h2>
1049 In WPrefs, under ``Mouse Prefrences'', the mouse actions can be mapped
1050 to a button of choice.
1052 Jim Noble explains another way to do this:
1054 If you've got a two-button mouse under some versions of Solaris x86, there's no way
1055 (that I'm aware of) to emulate a 3-button mouse. The right button can be either MB2
1056 or MB3, but chording doesn't work.
1058 <PRE>
1059 ApplicationMenuMouseButton = Left;
1060 </PRE>
1062 <PRE>
1063 WindowListMouseButton = Right;
1064 </PRE>
1065 in ~/GNUstep/Defaults/WindowMaker ought to allow the left button to activate the root
1066 menu, and the right button (as MB2) to activate the windows menu.
1067 <A name="87"></A>
1068 <h2>3.15 &nbsp;How do I edit my root menu?</h2>
1069 You can now use WPrefs.app ( its appicon looks like a heart rate meter
1070 with a GNUStep icon backgroud ). Note that this will replace any oldstyle
1071 menus and there is no way to convert the oldstyle menu to the
1072 new libproplist style menu.
1074 For old style menus, edit the file
1076 <PRE>
1077 ~/GNUstep/Library/WindowMaker/menu
1078 </PRE>
1079 and save your changes. Window Maker should detect the change and
1080 automatically update. If you are having a problem getting it to reload the menu,
1083 <PRE>
1084 touch menu
1085 </PRE>
1086 to force the modification time into the future.
1087 <A name="88"></A>
1088 <h2>3.16 &nbsp;WPrefs disappeared from the Dock! How do I get it back?</h2>
1089 Pascal Hofstee offers this answer:
1091 You should just start it from a terminal by supplying it's FULL path-name,
1092 which is usually the following:
1094 <PRE>
1095 /usr/local/GNUstep/Apps/WPrefs.app/WPrefs
1096 </PRE>
1098 At this point, a new appicon should be generated
1099 which can be placed back into the Dock.
1100 <A name="89"></A>
1101 <h2>3.17 &nbsp;How can I define my own Icon for a program? (instead of the Icon the Application Supplies?)</h2>
1102 You can right click on the titlebar of the running app and choose the
1103 "Attributes..." option, then click on the "Ignore client supplied icon"
1104 checkbox. Click "Apply", "Save" and close the Attributes Editor.
1106 Another method is to edit ~/GNUstep/Defaults/WMWindowAttributes by hand and
1107 use the AlwaysUserIcon=YES; option for the app. For example:
1109 xmcd = { Icon = "Radio.xpm";
1110 AlwaysUserIcon=Yes;
1112 <A name="90"></A>
1113 <h2>3.18 &nbsp;How do I turn off the workspace titles between workspaces?</h2>
1114 In Window Maker 0.60.0, an option was added to turn this off.
1116 By editing
1117 <PRE>
1118 ~/GNUstep/Defaults/WindowMaker
1119 </PRE>
1120 insert or modify the key
1122 <PRE>
1123 WorkspaceNameDisplayPosition = none;
1124 </PRE>
1125 Other valid options for this include
1126 center/top/bottom/topleft/topright/bottomleft/bottomright;
1127 <A name="91"></A>
1128 <h2>3.19 &nbsp;How do I add dynamic items to my root menu?</h2>
1129 A few programs are floating about, notably wkdemenu.pl that can produce
1130 output from other menu styles. In order to get WindowMaker to launch the process everytime
1131 you want to use the menu, use something like
1133 <PRE>
1134 ("External Menu", OPEN_MENU, "| bob.sh")
1135 </PRE>
1136 in a proplist style menu. You can tell if you have a proplist style menu if you can
1137 edit it with WPrefs.
1139 You can do this directly in WPrefs by going to the menu editor, adding an "external menu",
1140 and then clicking the "ask guru button" and filling in the process name.
1142 Thanks to Igor P. Roboul
1143 <A name="92"></A>
1144 <h2>3.20 &nbsp;How do I remove or hide appicons?</h2>
1145 There are two options here, and you need to consider which one you prefer.
1146 Read both of these before you decide.
1148 First, if you do not want to use the clip or dock at all, you can launch wmaker with
1149 with
1151 <PRE>
1152 wmaker --no-clip --no-dock
1153 </PRE>
1154 and then in
1156 <PRE>
1157 ~/GNUstep/Defaults/WMWindowAttributes
1158 </PRE>
1161 <PRE>
1162 "*" = {NoAppIcon=Yes;};
1163 </PRE>
1164 The problem with this method is if you use the dock for dockapps, it renders them
1165 with out an appicon to write to.
1166 An alternative method if you are willing to let the clip be on your desktop is
1167 to right click on the clip > clip options > auto attract.
1168 Double click the clip so that it is grayed and all appicons will be hidden.
1169 Then you can hide the clip behind the dock so that it is out of your way.
1170 This will allow appicons to work.
1171 <A name="93"></A>
1172 <h2>3.21 &nbsp;I disabled my titlebar. How can I get it back?</h2>
1173 Thanks to Jim Knoble for this answer
1175 Set the focus to the window and then use the keystroke assigned to the
1176 titlebar menu. If you're not sure what the keystroke is, you can find
1177 out using WPrefs: in the keyboard section, select the `Open window
1178 commands menu' item in the list of actions. The keystroke assigned to
1179 it ought to appear in the `Shortcut' area'.
1181 Typically it is Control-Esc or F10 in older version of WindowMaker.
1182 <A name="94"></A>
1183 <h2>3.22 &nbsp;How do I remove ALT+Mouse1 from the action Window Maker grabs for an application?</h2>
1184 Do [Button3Down] (for righthanded mouse users, [RightButtonDown]) on
1185 the titlebar of the desired window. Choose ``Attributes...''. In the
1186 Attributes inspector, choose ``Advanced Options''. Check ``Don't Bind
1187 Mouse Clicks''. Apply or Save as desired, then close the Attributes
1188 inspector.
1190 The result is that [Alt+Button1] (which usually grabs a window to move
1191 it around), [Alt+Button2] (which usually grabs a window to move it
1192 around without changing the window stacking order), and [Alt+Button3]
1193 (which usually resizes a window) all get passed to the application
1194 instead of performing their usual action.
1195 <A name="95"></A>
1196 <h2>3.23 &nbsp;How do I configure the Dock and Clip to use less space on a small screen?</h2>
1197 This answer is current as of WindowMaker-0.61.1.
1199 For the Clip, either:
1201 (a) Disable the Clip from WPrefs (panel number 7), or<BR>
1202 (b) Hide the Clip under the Dock (for example, in the upper righth
1203 and corner of the screen).
1205 [b] is probably more useful on desktops with limited space, since you
1206 can still set the Clip to attract app-icons so they don't clutter your
1207 desktop.
1209 For the Dock, try the following:
1211 (1) Exit Window Maker.<BR>
1212 (2) Log in via a text console or using a different window manager.<BR>
1213 (3) Edit ~/GNUstep/Defaults/WMState using your favorite text editor
1214 (for example, vi, emacs, or pico).<BR>
1215 (4) Find the `Applications' part of the `Dock' structure. Find the
1216 item with `Position = "0,0";'. Change the `Command' item to the
1217 command you want the top tile to launch. Change the `Name' item
1218 to the "&lt;instance&gt;.&lt;class&gt;" name of the application you just made
1219 the Command item start (for example, if `Command' is `"xedit"',
1220 then `Name' should be `xedit.Xedit').<BR>
1221 (5) Save the WMState file.<BR>
1222 (6) Start an X session with Window Maker.<BR>
1223 (7) Check that the top tile starts the command you told it to. (You
1224 should still also be able to move the Dock up and down using
1225 [LeftDrag] on the top tile.)<BR>
1226 (8) You can configure the tile (including autolaunch and the
1227 drop-command) in the regular manner ([RightButtonDown] on the
1228 tile and choose `Settings...' from the resulting menu).
1229 <A name="128"></A>
1230 <h2>3.24 &nbsp;Why do dashes not work as menu entries?</h2>
1231 If you wish to use a - as part of a menu item name, you must enclose the name in double quotes. This will only apply if you're editing the ~/GNUstep/Defaults/WMRootMenu file manually, as it is handled properly within WPrefs.
1233 <pre>
1234 This will work:
1236 (ssh,
1237 ("us-gw", EXEC, "Eterm -e ssh us-gw"),
1239 This will not:
1241 (ssh,
1242 (us-gw, EXEC, "Eterm -e ssh us-gw"),
1243 </pre>
1246 Thanks to Martin Sillence for pointing this out.<BR>
1247 </BLOCKQUOTE>
1250 if ($chapter==4) {
1252 <h1>Chapter 4: Using Window Maker</h1>
1253 <UL type="disc">
1254 <B>4.1</B> &nbsp; <A href="#62">How do add new icons to the Dock?</A><BR>
1255 <B>4.2</B> &nbsp; <A href="#63">What is the difference between the Exit and Exit Session Option?</A><BR>
1256 <B>4.3</B> &nbsp; <A href="#64">How do I "dock" icons on the clip?</A><BR>
1257 <B>4.4</B> &nbsp; <A href="#65">Why do none of my key bindings (ie: Alt+#) work in Window Maker?</A><BR>
1258 <B>4.5</B> &nbsp; <A href="#66">How do I rename workspaces?</A><BR>
1259 <B>4.6</B> &nbsp; <A href="#67">How can I resize a window if the window is larger than my current desktop?</A><BR>
1260 <B>4.7</B> &nbsp; <A href="#68">How do I "undock" appicons?</A><BR>
1261 <B>4.8</B> &nbsp; <A href="#69">I docked an application but when I run it the button is permanently shaded and I can't run new instances.</A><BR>
1262 <B>4.9</B> &nbsp; <A href="#70">When I run wmaker it complains about not being able to load any fonts.</A><BR>
1263 <B>4.10</B> &nbsp; <A href="#71">When I set the root background with wmsetbg by hand it works, but when I do that from the configuration files it doesnt!</A><BR>
1264 <B>4.11</B> &nbsp; <A href="#72">What is the purpose of being able to draw a box on the root menu with a left click?</A><BR>
1265 </UL>
1266 </FONT>
1267 <BR><HR><BR>
1268 <A name="62"></A>
1269 <h2>4.1 &nbsp;How do add new icons to the Dock?</h2>
1270 First, launch an application. If an icon (henceforth called an ``appicon'')
1271 appears in the bottom left corner of the screen, left click and drag it over
1272 near the Dock. You will see a slightly opaque square of where the
1273 Dock will place the appicon. When you do, release the mouse
1274 button and the appicon should now be in the Dock.
1276 Next, right click on the desktop to bring up the menu.
1277 Select Workspace -> Save Session to make this permanent.
1278 <A name="63"></A>
1279 <h2>4.2 &nbsp;What is the difference between the Exit and Exit Session Option?</h2>
1280 Another answer from Dan Pascu:
1282 "Exit will exit wmaker, but can leave other X apps running, provided that it was
1283 not the last app launched in the .xinitrc (for instance, if you had exec wmaker,
1284 followed by exec xterm, exiting wmaker using 'Exit' will leave the xterm
1285 running so you could start another window manager, etc.) This is accomplished
1286 because X will not shutdown unless all X apps are closed.
1288 Exit session will exit wmaker, but will also
1289 close all running apps, thus the X server will be closed
1290 too."
1291 <A name="64"></A>
1292 <h2>4.3 &nbsp;How do I "dock" icons on the clip?</h2>
1293 Just drag icons near it like you would for the dock. If you are having a problem
1294 docking icons, you should try moving the clip away from the dock.
1295 <A name="65"></A>
1296 <h2>4.4 &nbsp;Why do none of my key bindings (ie: Alt+#) work in Window Maker?</h2>
1297 If you are using XFree86, make sure scroll lock and numlock are off or no bindings
1298 will work (XFree bug). You can try using the XFree86 Numlock Hack by editing the
1299 line #undef NUMLOCK_HACK in $(WindowMaker)/src/wconfig.h and changing it to
1300 #define NUMLOCK_HACK.
1302 With the release of 0.18.0, this hack is now working and hopefully no
1303 one will have to ask this question again.
1304 <A name="66"></A>
1305 <h2>4.5 &nbsp;How do I rename workspaces?</h2>
1306 Right click to bring up the root menu. Go under
1307 the Workspaces menu item and hold the control key down.
1308 Next, click on the workspace entry you
1309 would like to rename, type the name, and
1310 press enter.
1311 <A name="67"></A>
1312 <h2>4.6 &nbsp;How can I resize a window if the window is larger than my current desktop?</h2>
1313 David Reviejo best summed up this answer:
1315 "Maybe you know:
1316 Alt+Left click and drag
1317 to move the window.
1319 Try this:
1320 Alt+Right click and drag
1321 to resize (by moving the nearest window corner)
1323 Another move/resize tip: while you are moving or resizing a window, you
1324 can change the move/resize mode by pressing the SHIFT key."
1325 <A name="68"></A>
1326 <h2>4.7 &nbsp;How do I "undock" appicons?</h2>
1327 If the program is not running, just drag the icon to the middle of your
1328 desktop and watch it disappear. If the program is running, hold down Meta and drag the icon off the dock.
1329 <A name="69"></A>
1330 <h2>4.8 &nbsp;I docked an application but when I run it the button is permanently shaded and I can't run new instances.</h2>
1331 You probably docked the application with dockit. To fix it
1332 remove the icon and use the "Emulate Application Icon" checkbox in
1333 the Advanced Options section of the Attributes panel for the window.
1334 Then restart the application to get the application icon you
1335 must use to dock the application.
1336 It can also mean that you did something you shouldn't, which is
1337 changing the program that is ran from the docked icon. For example,
1338 if you docked rxvt you must NOT change it to xterm, for example.
1339 You also can't do any changes that might alter the contents of
1340 the WM_CLASS hint for the window, like the -name parameter for
1341 xterm, rxvt and other programs.
1342 <A name="70"></A>
1343 <h2>4.9 &nbsp;When I run wmaker it complains about not being able to load any fonts.</h2>
1344 Check if the locale settings are correct. If you're not sure what to
1345 do, unset the LANG environment variable before running wmaker.
1347 TODO: give complete explanation
1348 <A name="71"></A>
1349 <h2>4.10 &nbsp;When I set the root background with wmsetbg by hand it works, but when I do that from the configuration files it doesnt!</h2>
1350 If you set the root background with wmsetbg by hand, it will obviously
1351 find the image, since you have explicitly specified it by hand. But if you
1352 simply put it in
1353 <PRE>
1354 ~/GNUstep/Defaults/WindowMaker
1355 </PRE>
1356 in some option like WorkspaceBack, it will not find the image because Window Maker can't read
1357 your mind to figure where you put the image. So, to fix it, you have to
1358 either place the full path for the image in the texture specification or put
1359 the path for the directory you put your background images in the PixmapPath
1360 option. You can also put all your background images in places like
1361 <PRE>
1362 ~/GNUstep/Library/WindowMaker/Backgrounds
1363 </PRE>
1365 <PRE>
1366 /usr/local/share/WindowMaker/Backgrounds
1367 </PRE>
1368 David Green says that another possibility is that you have two copies of the worker programs:
1369 wmsetbg (and possibly setstyle) and the wrong one is in the path first.
1370 <A name="72"></A>
1371 <h2>4.11 &nbsp;What is the purpose of being able to draw a box on the root menu with a left click?</h2>
1372 Its purpose is two-fold.
1374 First, it is used to select multiple windows on a desktop at a time. When these
1375 windows are selected, they can be moved around on your desktop and will retain
1376 their relative positions.
1378 Second, once selected, they are persistent through desktop changes. So it
1379 is useful for moving large numbers of windows between desktops.
1381 You can also select windows with shift+click.<BR>
1382 </BLOCKQUOTE>
1385 if ($chapter==5) {
1387 <h1>Chapter 5: Application Compatibility</h1>
1388 <UL type="disc">
1389 <B>5.1</B> &nbsp; <A href="#96">How do I assign gimp an appicon?</A><BR>
1390 <B>5.2</B> &nbsp; <A href="#97">How do I get an appicon for XEmacs 20.3+?</A><BR>
1391 <B>5.3</B> &nbsp; <A href="#98">Where do I get the nifty clock program I always see on people's desktops?</A><BR>
1392 <B>5.4</B> &nbsp; <A href="#99">How do you dock asclock?</A><BR>
1393 <B>5.5</B> &nbsp; <A href="#100">Where can I get more dockapps?</A><BR>
1394 <B>5.6</B> &nbsp; <A href="#101">How do I get an appicon for rxvt so I can dock it?</A><BR>
1395 <B>5.7</B> &nbsp; <A href="#102">How do I allow Alt+# to work in an rxvt/xterm session?</A><BR>
1396 <B>5.8</B> &nbsp; <A href="#103">How do I get different icons for different rxvt's and xterms?</A><BR>
1397 <B>5.9</B> &nbsp; <A href="#104">How do I launch multiple instances of XTerm from one appicon?</A><BR>
1398 <B>5.10</B> &nbsp; <A href="#105">Window Maker breaks scilab.</A><BR>
1399 <B>5.11</B> &nbsp; <A href="#106">How do I get a transparent xterm/rxvt/xconsole?</A><BR>
1400 <B>5.12</B> &nbsp; <A href="#107">How do I dock an arbitrary console application like mutt?</A><BR>
1401 <B>5.13</B> &nbsp; <A href="#108">How do I get an appicon for Netscape?</A><BR>
1402 <B>5.14</B> &nbsp; <A href="#109">How can I dock an application from a remote machine using ssh?</A><BR>
1403 <B>5.15</B> &nbsp; <A href="#110">How do you make an omnipresent window not take focus whenever switching workspaces?</A><BR>
1404 </UL>
1405 </FONT>
1406 <BR><HR><BR>
1407 <A name="96"></A>
1408 <h2>5.1 &nbsp;How do I assign gimp an appicon?</h2>
1409 You can enter the following line in WMWindowAttributes:
1411 <PRE>
1412 gimp={Icon="gimp.tiff";};
1413 </PRE>
1414 Window Maker now can assign Icons from within the windowmanager. To do so, right
1415 click on the title bar of an app, click on the droplist->Icon and WorkSpace entry, enter the icon file name (
1416 make sure this is in your pixmap path ), click update, apply, and then save.
1417 <A name="97"></A>
1418 <h2>5.2 &nbsp;How do I get an appicon for XEmacs 20.3+?</h2>
1419 Thanks to Michael Hafner for this answer.
1421 You don't need to patch the XEmacs code, just run
1423 <PRE>
1424 ./configure --with-session=yes (in addition to any other options you use)
1425 </PRE>
1426 in your XEmacs 20.3+ sourcedir and rebuild it. Then XEmacs shows an appicon
1427 when running and you can easily dock it.
1428 <A name="98"></A>
1429 <h2>5.3 &nbsp;Where do I get the nifty clock program I always see on people's desktops?</h2>
1430 It's called asclock. Once included with Window Maker, it now is available
1431 at <A HREF="ftp://ftp.windowmaker.org/pub/contrib/srcs/apps/asclock.tgz">ftp://ftp.windowmaker.org/pub/contrib/srcs/apps/asclock.tgz</A>
1433 asclock was written by Beat Christen and used to have its own website, which
1434 seems to have disappeared. However, references to it exist all over
1435 the place, and can be found by searching <A href=http://www.google.com/search?q=asclock%22>Google</A>.
1436 Beat Christen wrote this awhile back:
1438 "Please note that the asclock-gtk version 2.0 beta 4
1439 (asclock-gtk-2.0b4.tar.gz) does not have the -d switch yet and that the
1440 asclock-xlib-2.1b2.tar.gz does not have the shaped asclock builtin."
1442 A wonderful alternative to asclock is Jim Knoble's
1443 <A href="http://www.ntrnet.net/~jmknoble/WindowMaker/wmclock/">wmclock</A>.
1444 It duplicates asclock and adds some much needed improvements.
1445 <A name="99"></A>
1446 <h2>5.4 &nbsp;How do you dock asclock?</h2>
1447 It is highly recommended that you use the asclock mentioned previously in question 5.3. The asclock that is typically included in AfterStep will not properly dock with Window Maker. At this point, there are at least four or five different versions of asclock floating about.
1449 For older versions such as asclock-classic , use a command line similar to
1451 <PRE>
1452 asclock -shape -iconic -12 &amp;
1453 </PRE>
1454 For newer versions such as asclock-xlib 2.0 and asclock-gtk use
1456 <PRE>
1457 asclock -shape -iconic -12 -d &amp;
1458 </PRE>
1459 Drag it from the top right corner of the clock to the dock. Right click on the icon and
1460 select autolaunch.
1462 In order to make asclock launch every time you start Window Maker, right click on the
1463 outer edge of the border for asclock until a menu appears. Select the "Settings" item
1464 and then select the "Lauch this Program Automatically" option then select the "OK"
1465 button.
1467 If you get an error such as sh: /dev/console: Permission denied, login as root, cd to /dev/ and run
1468 <PRE>
1469 ./MAKEDEV console
1470 </PRE>
1471 <A name="100"></A>
1472 <h2>5.5 &nbsp;Where can I get more dockapps?</h2>
1473 The Window Maker team got tired of people E-mailing constantly asking where the websites for obscure dockapps disappeared to. So we've created the ultimate dockapps community website.
1474 Visit <a href="http://dockapps.org/">dockapps.org</a> for the latest, up-to-date links, information, and download for Window Maker and related dockapps.
1476 Another large index of dockapp links is available at <A HREF="http://www.bensinclair.com/dockapp">http://www.bensinclair.com/dockapp</A> . The downside to this is that they're only links, so if someone stops maintaining a dockapp, or their web hosting provider cuts them off, you won't be able to get to it. Still, Ben Sinclair's site was the first big "dockapp warehouse" site, so we give credit where credit is due. :)
1478 <A name="101"></A>
1479 <h2>5.6 &nbsp;How do I get an appicon for rxvt so I can dock it?</h2>
1480 The default rxvt that comes with most distributions is an outdated version of rxvt. The
1481 newest development version of rxvt is availible from
1482 <A HREF="ftp://ftp.math.fu-berlin.de/pub/rxvt/devel">ftp://ftp.math.fu-berlin.de/pub/rxvt/devel</A>/. As of the time of this writing, the version is
1483 2.4.7 and it natively produces an appicon without a patch.
1485 John Eikenberry has also created an rpm which is available from
1486 <A HREF="ftp://ftp.coe.uga.edu/users/jae/windowmaker">ftp://ftp.coe.uga.edu/users/jae/windowmaker</A>
1487 <A name="102"></A>
1488 <h2>5.7 &nbsp;How do I allow Alt+# to work in an rxvt/xterm session?</h2>
1489 First, Launch a unique instance of rxvt or xterm. This can be done using the -N
1490 option of rxvt.
1492 rxvt -name foo -e irc
1494 Then, go to the Attributes menu ( right click on titlebar -&gt; Attributes) / Advanced
1495 Options and enable "Don't Bind Keyboard shortcuts". Click Save and Apply and you
1496 should be able to run your session without the shortcuts.
1497 <A name="103"></A>
1498 <h2>5.8 &nbsp;How do I get different icons for different rxvt's and xterms?</h2>
1499 The hint is the -name option for xterm or rxvt. This will allow you to change the exact
1500 WM_CLASS in the attributes menu and assign a unique icon.
1502 <PRE>
1503 rxvt -name foo -title Testing
1504 </PRE>
1505 Then Right click on the title bar to bring up the attributes menu, and you will be able
1506 to edit the properties for foo.XTerm (ie: assign a unique icon).
1507 <A name="104"></A>
1508 <h2>5.9 &nbsp;How do I launch multiple instances of XTerm from one appicon?</h2>
1509 Thanks for the update by Sara C. Pickett:
1511 The easiest way to accomplish this is to dock XTerm as normal. Then
1512 Go to the Attributes menu -> Application Specific and select no application icon
1513 for XTerm.
1515 Then right-click on the docked appicon and select settings. Change the
1516 Application Path with arguments section to
1518 <PRE>
1519 '/bin/sh -c "exec xterm &amp;"'
1520 </PRE>
1521 <A name="105"></A>
1522 <h2>5.10 &nbsp;Window Maker breaks scilab.</h2>
1523 If you refer to the problem of the "graphics" window of scilab not showing
1524 up in Window Maker, this is caused by a bug in scilab. You can see the
1525 cause of the problem by yourself, by running xprop on the graphic window:
1526 WM_NORMAL_HINTS(WM_SIZE_HINTS):
1527 <PRE>
1528 user specified location: 136679205, 1074468360
1529 user specified size: 400 by 300
1530 program specified minimum size: 400 by 300
1531 </PRE>
1532 Now, when scilab opens it's window, Window Maker nicely does exactly what it
1533 is told, that is, map the window at position 136679205, 1074468360 which
1534 obviously falls outside the screen no matter how big is your monitor ;)
1536 Meanwhile, the workaround for this is to open the window list menu
1537 (click on the root window with the middle mouse button) and click
1538 on the ScilabGraphic entry. The window should be brought to your
1539 reach. Then, open the window commands menu (right click on window's
1540 titlebar) and open the Attributes panel. Go to the "Advanced Options"
1541 section, check the "Keep inside screen" option and save.
1543 If you can recompile Scilab, this came from a Scilab developer:
1545 replace
1546 <PRE>
1547 size_hints.flags = USPosition | USSize | PMinSize;
1548 </PRE>
1549 with
1550 <PRE>
1551 size_hints.flags = /** USPosition |**/ USSize | PMinSize;
1552 </PRE>
1553 in routines/xsci/jpc_SGraph.c
1554 <A name="106"></A>
1555 <h2>5.11 &nbsp;How do I get a transparent xterm/rxvt/xconsole?</h2>
1556 You need a terminal emulator that has support for transparency, like
1557 Eterm, the latest rxvt, wterm, aterm or gnome-terminal.
1559 You can find these programs on <A HREF="http://www.freshmeat.net/">http://www.freshmeat.net</A>
1560 <A name="107"></A>
1561 <h2>5.12 &nbsp;How do I dock an arbitrary console application like mutt?</h2>
1562 There are two key things to do if you want a program (such as mutt) to
1563 be able to start in a terminal window from the Dock or the Clip:
1565 (1) Make the terminal window start the program you want to run
1566 instead of a shell. Both xterm and rxvt (and its descendants)
1567 are capable of doing this. For example:
1569 <PRE>
1570 xterm -e mutt
1571 rxvt -e mutt
1572 gnome-terminal -e mutt
1573 </PRE>
1574 (2) Convince Window Maker that the resulting terminal window is not a
1575 regular terminal window, but rather some other program instance.
1576 Both xterm and rxvt are also capable of doing this. Make sure
1577 that -e is the last command option. For example:
1579 <PRE>
1580 xterm -name muttTerm -e mutt
1581 rxvt -name muttTerm -e mutt
1582 gnome-terminal --name=muttTerm -e mutt
1583 </PRE>
1584 This causes the instance of the terminal window that you start to
1585 have an &lt;instance-name&gt;.&lt;class-name&gt; pair of `muttTerm.XTerm'
1586 (usually rxvt's class is also XTerm; don't know about its
1587 descendants, such as wterm and Eterm).
1589 Do not use spaces or periods in the instance name. For example,
1590 these are BAD instance names:
1592 <PRE>
1593 xterm -name mutt.term -e mutt
1594 rxvt -name 'mutt term' -e mutt
1595 </PRE>
1596 Window Maker will not like you if you use them.
1598 With a different instance name, you can now do the following:
1600 - Dock the resulting appicon in the dock, or clip it to the Clip.
1602 - Assign a different icon and different window properties to
1603 the `special' terminal window running your program (make
1604 sure you choose the exact `muttTerm.XTerm' window
1605 specification in the Attributes editor).
1607 - Specify different resource settings for muttTerm in your
1608 ~/.Xdefaults file (e.g., different default foreground and
1609 background colors).
1611 There are a few other non-key things you can do to complete the process:
1613 (3) Tell the terminal window to display a more meaningful or prettier
1614 title and icon title than what gets put there due to `-e'. For
1615 example:
1617 <PRE>
1618 rxvt -title 'Mail (mutt)' -n 'Mail' -name muttTerm -e mutt
1619 </PRE>
1620 Xterm works the same way.
1622 (4) These are getting to be a lot of command-line options. Make a
1623 wrapper script to use so you don't have to remember them all:
1625 <PRE>
1626 mkdir ~/bin
1627 cat &gt;~/bin/muttTerm &lt;&lt;EOF
1628 #!/bin/sh
1629 rxvt -title 'Mail (mutt)' -n 'Mail' -name muttTerm -e mutt
1631 chmod +x ~/bin/muttTerm
1632 </PRE>
1633 Now you can do the same thing as that really long command in [3]
1634 above using the simple:
1636 <PRE>
1637 ~/bin/muttTerm
1638 </PRE>
1639 If you put ~/bin in your PATH, you can use the even simpler:
1641 <PRE>
1642 muttTerm
1643 </PRE>
1644 (5) If you want to be sly, you can change the docked muttTerm to use
1645 your new wrapper script instead of the really long command; then,
1646 when you want to change anything in the really long command
1647 except for the instance name, you can just change the wrapper
1648 script, and it's done. Here's the procedure:
1650 (a) [RightButtonDown] on the muttTerm dock tile
1652 (b) Choose `Settings...'
1654 (c) Replace the text in the `Application path and arguments'
1655 field with the following:
1657 <PRE>
1658 muttTerm
1659 </PRE>
1660 (d) Choose `OK'
1662 Note that Window Maker needs to know that ~/bin is on your PATH
1663 for this to work; you may need to exit your X session and start
1664 it again.
1666 To change the instance name of the terminal window (e.g., from
1667 `muttTerm' to `mailTerm' or `blah' or
1668 `terminalWindowRunningMutt'), you need to do the following
1670 (e) Change your muttTerm script
1671 (f) Undock your old muttTerm
1673 (g) Run your muttTerm script
1675 (h) Dock the resulting terminal window
1677 (i) Do the stuff in [a] through [d] above again.
1679 Good luck.
1682 Thanks to Jim Knoble for this answer.
1683 <A name="108"></A>
1684 <h2>5.13 &nbsp;How do I get an appicon for Netscape?</h2>
1685 If you are not using one of the latest Navigators, you can
1687 1) Right click on the title bar
1689 2) Click ``Attributes''
1691 3) Select ``Advanced Options'' from the pull down menu
1693 4) Select ``Emulate Application Icon''
1695 5) Click Save
1697 and older netscapes should now produce an application icon.
1699 If you are using a newer rpm from Redhat Linux, try running
1700 <PRE>
1701 grep irix `which netscape`
1702 </PRE>
1703 This seems to have been introduced in their 4.7 update. Comment out
1704 irix-session management restart netscape. Alternatively, you may run
1705 either
1707 <PRE>
1708 /usr/lib/netscape/netscape-communicator
1709 </PRE>
1711 <PRE>
1712 /usr/lib/netscape/netscape-navigator
1713 </PRE>
1714 depending on which rpms you have installed.
1715 <A name="109"></A>
1716 <h2>5.14 &nbsp;How can I dock an application from a remote machine using ssh?</h2>
1717 This answer asumes that you have already set up RSA
1718 authentication using ``ssh-keygen''. To be able to launch applications
1719 <PRE>
1720 without being prompted for the password, you can use ``ssh-agent'' and
1721 </PRE>
1722 ``ssh-add'' as follows.
1724 With the addition to ~/.xsession of
1726 <PRE>
1727 eval `ssh-agent`
1728 ssh-add /dev/null
1729 </PRE>
1730 just before
1731 <PRE>
1732 exec wmaker
1733 </PRE>
1734 Then ssh will no longer prompt for the RSA-key passphrase.
1735 The ``/dev/null'' argument to ``ssh-add'' causes it to use the
1736 ``ssh-askpass'' graphical dialog.
1738 The following procedure shows how to dock a remote xterm
1739 using ``ssh''. This procedure should work well for any well-behaved
1740 X11 application, including most Dock applets.
1742 1) From a terminal window, start an ssh session with ``xterm'' as the command:
1744 <PRE>
1745 ssh -a -C -X remote.example.net "xterm -name blah"
1746 </PRE>
1747 (The '-a' switch turns off agent forwarding, for security reasins and
1748 the '-X' switch turns on X11 forwarding, required for the remote xterm
1749 to run. The -C option turns on compression, very
1750 useful for things such as X)
1752 2) When the remote xterm appears, find the appicon. If it's not
1753 already in the Clip, drag it there.
1755 3) [RightButtonDown] on the appicon and choose 'Settings...' from
1756 the menu. Note that the 'Application path and arguments' field
1757 contains only:
1759 <PRE>
1760 xterm -name blah
1761 </PRE>
1762 Change that to:
1764 <PRE>
1765 ssh -a -C -X remote.example.net "xterm -name blah"
1766 </PRE>
1767 The backslashes and double quotes are critical. Change the
1768 contents of 'Command for files dropped with DND' in the same
1769 fashion, putting '%d' inside the double quotes.
1771 If you wish, change the icon so that you can recognize the tile
1772 easily. Press 'OK'.
1774 4) [RightButtonDown] on the appicon again and choose 'Keep Icon(s)'.
1776 5) Exit the remote xterm. The new Clip tile should remain, with the
1777 three dots at the lower lefthand corner to indicate the app is no
1778 longer running.
1780 6) [DoubleClick] on the new Clip tile. You should get the remote
1781 xterm again after a short while, depending on the speed of your
1782 network and of the remote machine.
1785 7) You may either leave the remote application in the Clip, or drag it
1786 to the Dock.
1788 [NOTE: You should be wary of docking
1789 something like ``wminet'' or ``wmnet'' in the manner, since you may
1790 create a feedback loop by causing additional network traffic, which
1791 the program monitors, causing yet more network traffic... ]
1792 <A name="110"></A>
1793 <h2>5.15 &nbsp;How do you make an omnipresent window not take focus whenever switching workspaces?</h2>
1794 Typically, on applications like xmms, they are set to omnipresent so
1795 they will appear on every workspace. This causes the app to often get
1796 the focus unintentionally when switching workspaces.
1798 To remedy this,
1800 1) Bring up the ``Attributes'' menu. You can do this by [Right Clicking]
1801 on the title bar and seletcing ``Attributes''. Alternatively, you may
1802 hit 'Control+ESC' at the same time to bring up the title bar menu on apps
1803 that do not have a title bar.
1805 2) In the ``Window Attributes'' menu, select ``Skip Window List''
1807 3) Push ``Save'' and then hit the close dialog window icon in the upper
1808 right corner of the window frame.
1810 Now the window will not take focus when switching workspaces.
1812 [NOTE: this will also make the window non-focusable via keyboard window
1813 switching. The only way to shift focus to the window is via the mouse. ]<BR>
1814 </BLOCKQUOTE>
1817 if ($chapter==6) {
1819 <h1>Chapter 6: Themes and Dockapps</h1>
1820 <UL type="disc">
1821 <B>6.1</B> &nbsp; <A href="#121">What exactly are themes?</A><BR>
1822 <B>6.2</B> &nbsp; <A href="#122">How do I install a theme?</A><BR>
1823 <B>6.3</B> &nbsp; <A href="#123">Why do my themes not load the background?</A><BR>
1824 <B>6.4</B> &nbsp; <A href="#124">How do I make a Theme?</A><BR>
1825 <B>6.5</B> &nbsp; <A href="#125">I untarred a theme in ~/GNUstep/Library/WindowMaker like the README says,but it doesnt show up in the menu!</A><BR>
1826 </UL>
1827 </FONT>
1828 <BR><HR><BR>
1829 <A name="121"></A>
1830 <h2>6.1 &nbsp;What exactly are themes?</h2>
1831 Themes are a great aspect of Window Maker allowing a user to simply
1832 save the entire 'look' of their desktop in an archive to distribute freely among
1833 friends, fellow users and/or the whole net in general. :)
1835 See the <a href="themepacks.php">theme-HOWTO</a> for an in-depth walk-through on making a Theme archive.
1836 <A name="122"></A>
1837 <h2>6.2 &nbsp;How do I install a theme?</h2>
1838 This should be as simple as untarring the Theme.tar.gz into one of two
1839 places. You can untar it to the global /usr/local/share/WindowMaker/* directory,
1840 and have it be accessable to all users, or you can untar it to your own
1841 ~/GNUstep/Library/WindowMaker/ directory for your own personal use.
1843 Use your favorite variation of the following:
1845 <PRE>
1846 gzip -dc "Theme.tar.gz" | tar xvf -
1847 </PRE>
1848 Note that directory may differ on different systems
1849 <A name="123"></A>
1850 <h2>6.3 &nbsp;Why do my themes not load the background?</h2>
1851 Likely you have not compiled Window Maker with support for the background
1852 image format, usually JPEG.
1854 You can check this by the following command
1856 <PRE>
1857 ldd `which wmaker`
1858 </PRE>
1859 If libjpeg is not listed, you will need to install libjpeg that is available
1860 from ftp.windowmaker.org
1861 <A name="124"></A>
1862 <h2>6.4 &nbsp;How do I make a Theme?</h2>
1863 Please see the <a href="themepacks.php">theme-HOWTO</a> for details on making both new and old style themes (and the differences
1864 between the two), here is a short summary on making old style themes.
1865 Also, read the README.themes file included with the Window Maker
1866 distribution in the WindowMaker/ directory.
1868 In this walk-through when I use WindowMaker/, it can refer to the global
1869 /usr/local/share/WindowMaker/ directory or the users own
1870 ~/GNUstep/Library/WindowMaker/ directory.
1872 To make a Theme.tar.gz, these are the steps I take:
1874 1. Optionally create a README for your theme in WindowMaker/, call it
1875 something like "ThemeName.txt"
1877 2. Use the following command to add the Theme files to your .tar file.
1879 <PRE>
1880 tar cvf ThemeName.tar ThemeName.txt Themes/ThemeName
1881 Backgrounds/ThemeNameBG.jpg Backgrounds/ThemeNameTile.xpm
1882 </PRE>
1883 You can add as many more images as you need from the
1884 appropriate directories under WindowMaker/ following that general
1885 idea. You can even optionally add an IconSets/ThemeName.iconset and
1886 it's associated icons to your theme in the same manner. This should
1887 be stated in your README if you decide to include these.
1889 3. Then gzip your .tar file to make your ThemeName.tar.gz file with this command:
1891 <PRE>
1892 gzip -9 ThemeName.tar
1893 </PRE>
1894 4. Now give it to your friends!
1895 <A name="125"></A>
1896 <h2>6.5 &nbsp;I untarred a theme in ~/GNUstep/Library/WindowMaker like the README says,but it doesnt show up in the menu!</h2>
1897 Make sure the OPEN_MENU command for the Themes entry in your menu has
1898 the path for your personal themes directory included in it. To be sure,
1900 <PRE>
1901 #define USER_THEMES_DIR ~/GNUstep/Library/WindowMaker/Themes
1902 </PRE>
1903 in your wmmacros file.<BR>
1904 </BLOCKQUOTE>
1907 if ($chapter==7) {
1909 <h1>Chapter 7: Miscellaneous Questions</h1>
1910 <UL type="disc">
1911 <B>7.1</B> &nbsp; <A href="#115">Is there a pager for Window Maker?</A><BR>
1912 <B>7.2</B> &nbsp; <A href="#116">How do I use getstyle and setstyle?</A><BR>
1913 <B>7.3</B> &nbsp; <A href="#117">Why was libPropList removed from the distribution?</A><BR>
1914 <B>7.4</B> &nbsp; <A href="#118">Why don't you distribute normal diff or xdelta patches?</A><BR>
1915 <B>7.5</B> &nbsp; <A href="#119">Will you add GNOME or KDE support?</A><BR>
1916 <B>7.6</B> &nbsp; <A href="#120">How can I produce a backtrace when Window Maker keeps crashing?</A><BR>
1917 </UL>
1918 </FONT>
1919 <BR><HR><BR>
1920 <A name="115"></A>
1921 <h2>7.1 &nbsp;Is there a pager for Window Maker?</h2>
1922 Not at the moment because there is not a pressing need for a pager. The concept of
1923 multiple desktops does exist and there are currently 3 ways to switch between them.
1925 First, the Meta+Number combination will switch between desktops. The Workspaces
1926 menu will also let you switch workspaces. Lastly, the clip will also scroll one through
1927 workspaces. For those that would like to send an application to a specific workspace, either drag
1928 it to the edge of the desktop onto the next workspace, or right click on its
1929 title bar, select 'Move To', and click the workspace you want it to be
1930 moved to.
1932 However, Window Maker does support KDE and GNOME protocols, including their
1933 workspace management, so you may use their pager in conjunction with Window Maker
1934 in these. Note that in order for this to work, you must enable support when
1935 you configure Window Maker (using the --enable-kde and
1936 --enable-gnome configure options).
1938 Note also that the Blackbox pager application will work with
1939 Window Maker.
1940 <A name="116"></A>
1941 <h2>7.2 &nbsp;How do I use getstyle and setstyle?</h2>
1942 To capture the current Window Maker style, use the command
1944 <PRE>
1945 getstyle > current.style
1946 </PRE>
1947 To replace the current style, use the command
1949 <PRE>
1950 setstyle filename.style
1951 </PRE>
1952 <A name="117"></A>
1953 <h2>7.3 &nbsp;Why was libPropList removed from the distribution?</h2>
1954 Alfredo Kojima writes:
1956 libPropList was removed from Window Maker because other programs also
1957 use it, such as GNOME. If libPropList is distributed with wmaker, it
1958 would cause problems with whatever version of libPropList you already
1959 had installed.
1961 Now, there is no more GNOME libproplist and Window Maker libproplist. There is
1962 only libPropList which is worked on as a single community effort.
1963 <A name="118"></A>
1964 <h2>7.4 &nbsp;Why don't you distribute normal diff or xdelta patches?</h2>
1965 Whenever possible, plain diff patches are distributed. If the new version has
1966 new binary files, normal diff won't be able to handle them, so a patch
1967 package is distributed instead. We don't use xdelta because a) most
1968 systems do not have xdelta installed and b) xdelta is picky and requires
1969 the files to be patched to be exactly the same as the one used to make the patch.
1970 The patch package scheme used is much more flexible.
1972 We do not distribute a simple diff with the binary files separately (and
1973 variations, like uuencoding the binary files) because a) it is more
1974 complicated and error prone to require the user to manually move the files
1975 to the correct places b) the current patch package scheme <I>does</I> distribute
1976 the binary files and diff files separately. If the user wants to install
1977 everything by hand, nobody will object to that and c) sooner or later someone will
1978 certainly ask for a script to automate the file moving stuff.
1980 So we hacked a script (mkpatch) that automatically creates a patch
1981 package with the normal text diff file, a list of removed files and the binary
1982 files that have changed or been added, plus a script that does the patching
1983 automatically. If you don't like the script, you can apply the patch and move
1984 the files manually. Or download the whole distribution.
1985 <A name="119"></A>
1986 <h2>7.5 &nbsp;Will you add GNOME or KDE support?</h2>
1987 Support for GNOME and KDE hints has been included since 0.50.0.
1989 Note that you must enable this support at compile time with the proper
1990 arguments to configure (--enable-kde and --enable-gnome).
1991 <A name="120"></A>
1992 <h2>7.6 &nbsp;How can I produce a backtrace when Window Maker keeps crashing?</h2>
1993 Thanks to Paul Seelig for this answer:
1995 You can use the GNU debugger "gdb" to get exact information about how
1996 and where wmaker crashed. Sending this information to the developers
1997 is the most convenient way to help in debugging.
1999 The wmaker binary needs to be compiled with debugging turned on
2000 ("./configure --with-debug etc.") for this to work.
2002 Exit wmaker and start a failsafe X session with an open xterm.
2004 First type the command "script" to log the following session into a
2005 file commonly called "~/typescript". Then enter "gdb wmaker" at the
2006 shellprompt:
2008 <PRE>
2009 [shell prompt]~ > script
2010 Script started, output file is typescript
2011 [shell prompt]~ > gdb wmaker
2012 GNU gdb 4.17.m68k.objc.threads.hwwp.fpu.gnat
2013 Copyright 1998 Free Software Foundation, Inc.
2014 GDB is free software, covered by the GNU General Public License, and you are
2015 welcome to change it and/or distribute copies of it under certain conditions.
2016 Type "show copying" to see the conditions.
2017 There is absolutely no warranty for GDB. Type "show warranty" for details.
2018 This GDB was configured as "i486-pc-linux-gnu"...
2019 (gdb)
2020 </PRE>
2021 At the gdb prompt simply type "run" to start the WMaker session:
2023 <PRE>
2024 (gdb) run
2025 Starting program: /usr/bin/X11/wmaker
2026 </PRE>
2027 Try to reproduce the error which has provoked the crash before and if
2028 you succeed the session will simply freeze and you will see something
2029 similiar to following prompt:
2031 <PRE>
2032 Program received signal SIGSEGV, Segmentation fault.
2033 0x809ea0c in WMGetFirstInBag (bag=0x0, item=0x811e170) at bag.c:84
2034 84 for (i = 0; i &lt; bag-&gt;count; i++) {
2035 (gdb)
2036 </PRE>
2037 Now you just type "bt" for "backtrace" and gdb will show you where the
2038 crash happened:
2040 <PRE>
2041 (gdb) bt
2042 #0 0x809ea0c in WMGetFirstInBag (bag=0x0, item=0x811e170) at bag.c:84
2043 #1 0x807c542 in wSessionSaveState (scr=0x80c28e8) at session.c:299
2044 #2 0x807bd88 in wScreenSaveState (scr=0x80c28e8) at screen.c:1089
2045 #3 0x807cf54 in Shutdown (mode=WSExitMode) at shutdown.c:111
2046 #4 0x8078101 in exitCommand (menu=0x80f7230, entry=0x80fdb38)
2047 at rootmenu.c:193
2048 #5 0x8078403 in wRootMenuPerformShortcut (event=0xbffff360) at rootmenu.c:401
2049 #6 0x80630f7 in handleKeyPress (event=0xbffff360) at event.c:1492
2050 #7 0x8061c86 in DispatchEvent (event=0xbffff360) at event.c:232
2051 #8 0x8093092 in WMHandleEvent (event=0xbffff360) at wevent.c:585
2052 #9 0x8061dae in EventLoop () at event.c:322
2053 #10 0x806b238 in main (argc=1, argv=0xbffff404) at main.c:594
2054 (gdb)
2055 </PRE>
2056 To quit the debugger just type "quit" and say "y":
2058 <PRE>
2059 (gdb) quit
2060 The program is running. Exit anyway? (y or n) y
2061 [shell prompt]~ >
2062 </PRE>
2063 To quit the script session type "exit" again:
2065 <PRE>
2066 [shell prompt]~ > exit
2067 exit
2068 Script done, output file is typescript
2069 [shell prompt]~ >
2070 </PRE>
2071 Send the resulting "~/typescript" together with a concise explanation
2072 about how to reproduce the bug (please use the included BUGFORM for
2073 instruction) to the <A HREF="http://www.windowmaker.org/feedback.php?mailto=developers">developers</A>.<BR>
2074 </BLOCKQUOTE>
2077 if ($chapter==8) {
2079 <h1>Chapter 8: Troubleshooting Tips</h1>
2080 No questions are currently available for this chapter.</FONT>
2084 if ($chapter==9) {
2086 <h1>Chapter 9: Programming for Window Maker</h1>
2087 <UL type="disc">
2088 <B>9.1</B> &nbsp; <A href="#111">How do I get a normal X application to produce an appicon?</A><BR>
2089 <B>9.2</B> &nbsp; <A href="#112">How do I get my tcl/tk application to produce an appicon?</A><BR>
2090 <B>9.3</B> &nbsp; <A href="#113">What is WINGs?</A><BR>
2091 <B>9.4</B> &nbsp; <A href="#114">Where can I get more information about WINGs?</A><BR>
2092 </UL>
2093 </FONT>
2094 <BR><HR><BR>
2095 <A name="111"></A>
2096 <h2>9.1 &nbsp;How do I get a normal X application to produce an appicon?</h2>
2097 Another insightful answer from who else but Dan Pascu.
2099 "You must define the WM_CLASS (XSetClassHint()) and the CLIENT_LEADER or
2100 XWMHints.window_group properties, which are automatically set by most
2101 applications that use Xt (Motif, Athena ...), but if you use plain Xlib you must set them
2102 by hand.
2104 Also you must make a call to XSetCommand(dpy, leader, argv, argc);
2106 Take a look at WindowMaker-0.12.3/test/test.c that is an example for writing such an
2107 app (which also have an app menu).
2108 <A name="112"></A>
2109 <h2>9.2 &nbsp;How do I get my tcl/tk application to produce an appicon?</h2>
2110 Oliver Graf writes:
2112 The main window (normally this is called '.' [dot] in tk) should use the following lines:
2114 <PRE>
2115 wm command . [concat $argv0 $argv]
2116 wm group . .
2117 </PRE>
2118 All child windows attached to the same app-icon should use:
2120 <PRE>
2121 toplevel .child
2122 wm group .child .
2123 </PRE>
2124 where .child should be replaced by the actual window path.
2126 Replace '.' with the actual main-window path and 'wm group .child .' should be
2127 added for each 'toplevel .child' call.
2128 <A name="113"></A>
2129 <h2>9.3 &nbsp;What is WINGs?</h2>
2130 WINGs Is Not GNUstep. ;)
2132 It is the widget library written for the widgets in Window Maker.<P>
2133 It is currently under heavy development but several people have started
2134 writing applications in it. Its goal is to emulate the NeXT(tm)-style widgets.
2136 <A HREF="http://www.ozemail.com.au/~crn/wm/wings.html">http://www.ozemail.com.au/~crn/wm/wings.html</A> is the closest thing to an
2137 information center about WINGs. You can find out more information in our
2138 <A href="http://www.windowmaker.org/development.php?show=wings">WINGs development</A> section.
2139 <A name="114"></A>
2140 <h2>9.4 &nbsp;Where can I get more information about WINGs?</h2>
2141 Nic Berstein has created a WINGs development list.
2143 The purpose of this list is to provide a forum for support, ideas,
2144 suggestions, bug reports etc. for the WINGs widget set library.
2146 To subscribe to this list, send a message with the word ``subscribe'' in
2147 the _BODY_ of the message to: <A HREF="mailto:wings-request@postilion.org">&lt;wings-request@postilion.org&gt;</A>.<BR>
2148 </BLOCKQUOTE>
2152 if ($chapter > 0) {
2154 <HR size="1" noshade width="100%" align="center">
2155 <DIV align="center">
2156 <A href="FAQ.php">Top level of FAQ</A>
2157 </DIV>
2165 </td>
2166 </tr>
2167 </table>
2171 <?php include("footer.php"); ?>
2173 </body>
2174 </html>