1.1 --- a/config.mk	Mon Jul 17 10:09:57 2006 +0200
     1.2 +++ b/config.mk	Mon Jul 17 11:36:07 2006 +0200
     1.3 @@ -8,7 +8,7 @@
     1.4  X11INC = /usr/X11R6/include
     1.5  X11LIB = /usr/X11R6/lib
     1.6  
     1.7 -VERSION = 0.2
     1.8 +VERSION = 0.3
     1.9  
    1.10  # includes and libs
    1.11  LIBS = -L${PREFIX}/lib -L/usr/lib -lc -L${X11LIB} -lX11

     2.1 --- a/dwm.1	Mon Jul 17 10:09:57 2006 +0200
     2.2 +++ b/dwm.1	Mon Jul 17 11:36:07 2006 +0200
     2.3 @@ -90,7 +90,7 @@
     2.4  .B Control-[0..n]
     2.5  Append
     2.6  .B nth
     2.7 -tag to cureent
     2.8 +tag to current
     2.9  .B window
    2.10  .TP
    2.11  .B Control-Button1

     3.1 --- a/dwm.html	Mon Jul 17 10:09:57 2006 +0200
     3.2 +++ b/dwm.html	Mon Jul 17 11:36:07 2006 +0200
     3.3 @@ -28,58 +28,74 @@
     3.4  		and all this hype about remote control through a 9P service, I only
     3.5  		want to manage my windows in a simple, but dynamic way. wmii never got
     3.6  		finished because I listened to users, who proposed arbitrary ideas I
     3.7 -		considered useful. This resulted in an extreme <a href="http://www.jwz.org/doc/cadt.html">CADT</a>
     3.8 -		development model, which was a mistake. Thus the philosophy of
     3.9 -		dwm is simply <i>to fit my needs</i> (maybe yours as well). That's it.
    3.10 +		considered useful. This resulted in an extreme <a
    3.11 +		href="http://www.jwz.org/doc/cadt.html">CADT</a> development model,
    3.12 +		which was a mistake. Thus the philosophy of dwm is simply <i>to fit my
    3.13 +		needs</i> (maybe yours as well). That's it.
    3.14  		</p>
    3.15 -		<h3>Differences to wmii</h3	
    3.16 +		<h3>Differences to ion, larswm, and wmii</h3>
    3.17  		<p>
    3.18 -		In contrast to wmii, dwm is only a window manager, and nothing else.
    3.19 -		Hence, it is much smaller, faster and simpler.
    3.20 +		In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.
    3.21  		</p>
    3.22  		<ul>
    3.23  			<li>
    3.24 -			dwm has no 9P support, no editable tagbars, no shell-based
    3.25 -			configuration and remote control and comes without any additional
    3.26 -			tools like printing the selection or warping the mouse.
    3.27 +			dwm has no Lua integration, no 9P support, no menu, no editable
    3.28 +			tagbars, no shell-based configuration, no remote control, and comes
    3.29 +			without any additional tools like printing the selection or warping
    3.30 +			the mouse.
    3.31  			</li>
    3.32  			<li>
    3.33  			dwm is only a single binary, it's source code is intended to never
    3.34  			exceed 2000 SLOC.
    3.35  			</li>
    3.36  			<li>
    3.37 -			dwm is customized through editing its source code, that makes it
    3.38 -			extremely fast and secure - it does not process any input data which
    3.39 -			hasn't been known at compile time, except window title names.
    3.40 -			</li>
    3.41 -			<li>
    3.42 -			dwm is based on tagging and dynamic window management (however simpler
    3.43 -			than wmii or larswm).
    3.44 +			dwm is based on tagging and dynamic window management (however
    3.45 +			simpler than ion, wmii or larswm). It manages windows in
    3.46 +			tiling and floating modes. Either mode can be applied dynamically,
    3.47 +			depending on the application in use and the task performed.
    3.48  			</li>
    3.49  			<li>
    3.50  			dwm don't distinguishes between layers, there is no floating or
    3.51 -			managed layer. Wether the clients of currently selected tag are
    3.52 -			managed or not, you can re-arrange all clients on the fly. Popup-
    3.53 -			and fixed-size windows are treated unmanaged. 
    3.54 +			tiled layer. Wether the clients of currently selected tag are in
    3.55 +			tiled mode or not, you can re-arrange all clients on the fly.
    3.56 +			Popup- and fixed-size windows are treated floating, however. 
    3.57 +			</li>
    3.58 +			<li>
    3.59 +			dwm is customized through editing its source code, that makes it
    3.60 +			extremely fast and secure - it does not process any input data
    3.61 +			which hasn't been known at compile time, except window title names
    3.62 +			and status text read from standard input. You don't have to learn
    3.63 +			Lua/sh/ruby or some weird configuration file format (like X
    3.64 +			resource files), beside C to customize it for your needs,
    3.65 +			you <b>only</b> have to learn C.
    3.66 +			</li>
    3.67 +			<li>
    3.68 +			Because dwm is customized through editing its source code, it's
    3.69 +			pointless to make binary packages of it. This keeps its userbase
    3.70 +			small and elitist. No novices asking stupid questions.
    3.71  			</li>
    3.72  			<li>
    3.73  			dwm uses 1-pixel borders to provide the maximum of screen real
    3.74 -			estate to clients. Small titlebars are only drawn in front of unfocused
    3.75 -			clients.
    3.76 +			estate to clients. Small titlebars are only drawn in front of
    3.77 +			unfocused clients.
    3.78  			</li>
    3.79  			<li>
    3.80 -			dwm reads from <b>stdin</b> to print arbitrary status text (like the
    3.81 -			date, load, battery charge). That's much simpler than larsremote,
    3.82 -			wmiir and what not...
    3.83 +			dwm reads from standard input to print arbitrary status text (like
    3.84 +			the date, load, battery charge). That's much simpler than
    3.85 +			larsremote, wmiir and what not...
    3.86  			</li>
    3.87  			<li>
    3.88 -			Anselm <b>does not</b> want any feedback to dwm. If you ask for support,
    3.89 -			feature requests, or if you report bugs, they will be <b>ignored</b>
    3.90 -			with a high chance. dwm is only intended to fit Anselms needs.
    3.91 -			However you are free to download and distribute/relicense it, with the
    3.92 -			conditions of the <a href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
    3.93 +			dwm is only intended to fit Anselms needs. That means, Anselm
    3.94 +			<b>does not</b> want feedback to dwm. If you ask for support,
    3.95 +			feature requests, or if you report "bugs" (<i>real bugs are welcome
    3.96 +			though</i>), they will be <b>ignored</b> with a high
    3.97 +			chance.  However you are free to download and distribute/relicense
    3.98 +			it, with the conditions of the <a
    3.99 +			href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
   3.100  			</li>
   3.101  		</ul>
   3.102 +		<h3>Documentation</h3>
   3.103 +		There is a <a href="http://wmii.de/cgi-bin/man/man2html?query=dwm">man page</a>.
   3.104  		<h3>Screenshot</h3>
   3.105  		<p>
   3.106  		<a href="http://wmii.de/shots/dwm-20060714.png">Click here for a screenshot</a> (20060714)