commit 9ecb4a73b56b38905b861846b8f2c8ccf9229bae
parent e3f6d8e426a6a706566a1d79aff919effae0a737
Author: a@0au.de <unknown>
Date: Wed, 11 Mar 2009 19:23:39 +0100
Removed references to dwm's reading of stdin and replaced them with root window stuff.
Diffstat:
2 files changed, 12 insertions(+), 19 deletions(-)
diff --git a/dwm.suckless.org/index.md b/dwm.suckless.org/index.md
@@ -20,9 +20,9 @@ Windows are grouped by tags. Each window can be tagged with one or multiple
tags. Selecting certain tags displays all windows with those tags.
dwm contains a small status bar which displays all available tags, the layout,
-the title of the focused window, and text read from standard input. The
-selected tags are highlighted with a different color, while the tags of the focused
-window are highlighted with a small point.
+the title of the focused window, and the text read from the name of the
+root window. The selected tags are highlighted with a different color, while the
+tags of the focused window are highlighted with a small point.
dwm draws a small border around windows to indicate their focus state.
@@ -35,9 +35,9 @@ In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.
* dwm has no Lua integration, no 9P support, no shell-based configuration, no remote control, and comes without any additional tools, such as for printing the selection or warping the mouse.
* 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 been known at compile time, except window titles and status text read from the standard input. 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 editing header files).
+* 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 editing header files).
* 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.
-* dwm reads from the standard input to print arbitrary status text (like the date, load, battery charge). That's much simpler than larsremote, wmiir and what not...
+* 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...
Links
-----
diff --git a/dwm.suckless.org/manpage.md b/dwm.suckless.org/manpage.md
@@ -31,13 +31,13 @@ tags. Selecting certain tags displays all windows with these tags.
<P>
dwm contains a small status bar which displays all available tags, the layout,
-the title of the focused window, and the text read from standard input. A
-floating window is indicated with an empty square and a maximised
-floating window is indicated with a filled square before the windows
-title. The selected tags are indicated with a different color. The tags of
-the focused window are indicated with a filled square in the top left
-corner. The tags which are applied to one or more windows are indicated
-with an empty square in the top left corner.
+the title of the focused window, and the text read from the name of the
+root window (xsetroot -name "string" to set the name). A floating window
+is indicated with an empty square and a maximised floating window is
+indicated with a filled square before the windows title. The selected tags are
+indicated with a different color. The tags of the focused window are indicated
+with a filled square in the top left corner. The tags which are applied to one
+or more windows are indicated with an empty square in the top left corner.
<P>
dwm draws a small border around windows to indicate the focus state.
@@ -208,13 +208,6 @@ code. This keeps it fast, secure and simple.
<A NAME="lbAL"> </A>
<H2>BUGS</H2>
-The status bar may display
-<B>EOF</B>
-when dwm has been started by an X session manager like
-<B>xdm</B>(1),
-because those close standard output before executing dwm.
-<P>
-
Java applications which use the XToolkit/XAWT backend may draw grey windows
only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
JDK 1.6 versions, because it assumes a reparenting window manager. As a workaround
