Author: Anselm R Garbe <firstname.lastname@example.org>
Date: Sat, 27 Mar 2010 17:36:38 +0000
added a remark
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dwm.suckless.org/index.md b/dwm.suckless.org/index.md
@@ -34,7 +34,7 @@ In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.
* dwm is only a single binary, and its source code is intended to never exceed 2000 SLOC.
* dwm doesn't distinguish between layers: there is no floating or tiled layer. Whether or not the clients of currently selected tag(s) are in tiled layout, you can rearrange them on the fly. Popup and fixed-size windows are always floating, however.
* dwm is customized through editing its source code, which makes it extremely fast and secure - it does not process any input data which isn't known at compile time, except window titles and status text read from the root window's name. You don't have to learn Lua/sh/ruby or some weird configuration file format (like X resource files), beside C, to customize it for your needs: you only have to learn C (at least in order to edit the header file).
-* Because dwm is customized through editing its source code, it's pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions.
+* Because dwm is customized through editing its source code, it's pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions. There are some distributions that provide binary packages though.
* dwm reads from the root window's name to print arbitrary status text (like the date, load, battery charge). That's much simpler than larsremote, wmiir and what not...
* <b>NEW</b> dwm creates a view for each Xinerama screen.