patched dwm eb184e02
Anselm R. Garbe · 2006-07-17 11:36 3 file(s) · +46 −30
config.mk +1 −1
8 8
X11INC = /usr/X11R6/include
9 9
X11LIB = /usr/X11R6/lib
10 10
11 -
VERSION = 0.2
11 +
VERSION = 0.3
12 12
13 13
# includes and libs
14 14
LIBS = -L${PREFIX}/lib -L/usr/lib -lc -L${X11LIB} -lX11
dwm.1 +1 −1
90 90
.B Control-[0..n]
91 91
Append
92 92
.B nth
93 -
tag to cureent
93 +
tag to current
94 94
.B window
95 95
.TP
96 96
.B Control-Button1
dwm.html +44 −28
28 28
		and all this hype about remote control through a 9P service, I only
29 29
		want to manage my windows in a simple, but dynamic way. wmii never got
30 30
		finished because I listened to users, who proposed arbitrary ideas I
31 -
		considered useful. This resulted in an extreme <a href="http://www.jwz.org/doc/cadt.html">CADT</a>
32 -
		development model, which was a mistake. Thus the philosophy of
33 -
		dwm is simply <i>to fit my needs</i> (maybe yours as well). That's it.
31 +
		considered useful. This resulted in an extreme <a
32 +
		href="http://www.jwz.org/doc/cadt.html">CADT</a> development model,
33 +
		which was a mistake. Thus the philosophy of dwm is simply <i>to fit my
34 +
		needs</i> (maybe yours as well). That's it.
34 35
		</p>
35 -
		<h3>Differences to wmii</h3	
36 +
		<h3>Differences to ion, larswm, and wmii</h3>
36 37
		<p>
37 -
		In contrast to wmii, dwm is only a window manager, and nothing else.
38 -
		Hence, it is much smaller, faster and simpler.
38 +
		In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.
39 39
		</p>
40 40
		<ul>
41 41
			<li>
42 -
			dwm has no 9P support, no editable tagbars, no shell-based
43 -
			configuration and remote control and comes without any additional
44 -
			tools like printing the selection or warping the mouse.
42 +
			dwm has no Lua integration, no 9P support, no menu, no editable
43 +
			tagbars, no shell-based configuration, no remote control, and comes
44 +
			without any additional tools like printing the selection or warping
45 +
			the mouse.
45 46
			</li>
46 47
			<li>
47 48
			dwm is only a single binary, it's source code is intended to never
48 49
			exceed 2000 SLOC.
49 50
			</li>
50 51
			<li>
51 -
			dwm is customized through editing its source code, that makes it
52 -
			extremely fast and secure - it does not process any input data which
53 -
			hasn't been known at compile time, except window title names.
52 +
			dwm is based on tagging and dynamic window management (however
53 +
			simpler than ion, wmii or larswm). It manages windows in
54 +
			tiling and floating modes. Either mode can be applied dynamically,
55 +
			depending on the application in use and the task performed.
54 56
			</li>
55 57
			<li>
56 -
			dwm is based on tagging and dynamic window management (however simpler
57 -
			than wmii or larswm).
58 +
			dwm don't distinguishes between layers, there is no floating or
59 +
			tiled layer. Wether the clients of currently selected tag are in
60 +
			tiled mode or not, you can re-arrange all clients on the fly.
61 +
			Popup- and fixed-size windows are treated floating, however. 
58 62
			</li>
59 63
			<li>
60 -
			dwm don't distinguishes between layers, there is no floating or
61 -
			managed layer. Wether the clients of currently selected tag are
62 -
			managed or not, you can re-arrange all clients on the fly. Popup-
63 -
			and fixed-size windows are treated unmanaged. 
64 +
			dwm is customized through editing its source code, that makes it
65 +
			extremely fast and secure - it does not process any input data
66 +
			which hasn't been known at compile time, except window title names
67 +
			and status text read from standard input. You don't have to learn
68 +
			Lua/sh/ruby or some weird configuration file format (like X
69 +
			resource files), beside C to customize it for your needs,
70 +
			you <b>only</b> have to learn C.
71 +
			</li>
72 +
			<li>
73 +
			Because dwm is customized through editing its source code, it's
74 +
			pointless to make binary packages of it. This keeps its userbase
75 +
			small and elitist. No novices asking stupid questions.
64 76
			</li>
65 77
			<li>
66 78
			dwm uses 1-pixel borders to provide the maximum of screen real
67 -
			estate to clients. Small titlebars are only drawn in front of unfocused
68 -
			clients.
79 +
			estate to clients. Small titlebars are only drawn in front of
80 +
			unfocused clients.
69 81
			</li>
70 82
			<li>
71 -
			dwm reads from <b>stdin</b> to print arbitrary status text (like the
72 -
			date, load, battery charge). That's much simpler than larsremote,
73 -
			wmiir and what not...
83 +
			dwm reads from standard input to print arbitrary status text (like
84 +
			the date, load, battery charge). That's much simpler than
85 +
			larsremote, wmiir and what not...
74 86
			</li>
75 87
			<li>
76 -
			Anselm <b>does not</b> want any feedback to dwm. If you ask for support,
77 -
			feature requests, or if you report bugs, they will be <b>ignored</b>
78 -
			with a high chance. dwm is only intended to fit Anselms needs.
79 -
			However you are free to download and distribute/relicense it, with the
80 -
			conditions of the <a href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
88 +
			dwm is only intended to fit Anselms needs. That means, Anselm
89 +
			<b>does not</b> want feedback to dwm. If you ask for support,
90 +
			feature requests, or if you report "bugs" (<i>real bugs are welcome
91 +
			though</i>), they will be <b>ignored</b> with a high
92 +
			chance.  However you are free to download and distribute/relicense
93 +
			it, with the conditions of the <a
94 +
			href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
81 95
			</li>
82 96
		</ul>
97 +
		<h3>Documentation</h3>
98 +
		There is a <a href="http://wmii.de/cgi-bin/man/man2html?query=dwm">man page</a>.
83 99
		<h3>Screenshot</h3>
84 100
		<p>
85 101
		<a href="http://wmii.de/shots/dwm-20060714.png">Click here for a screenshot</a> (20060714)