aewl
view aewl.1 @ 772:0c1e9952a278
naming change from dwm to aewl; cleanups
| author | meillo@marmaro.de |
|---|---|
| date | Sat, 06 Dec 2008 11:15:51 +0100 |
| parents | 583c0adeee79 |
| children | 794a83e74023 |
line source
1 .TH AEWL 1 aewl-VERSION
4 .SH NAME
5 aewl \- a fork of dwm, the dynamic window manager
8 .SH SYNOPSIS
9 .B aewl
10 .RB [ \-v ]
13 .SH DESCRIPTION
14 This man page is the one from dwm 4.4.1 on which aewl is based.
15 It is partly updated, but not totally.
16 .P
17 dwm is a dynamic window manager for X. It manages windows in tiling and
18 floating modes. Either mode can be applied dynamically, optimizing the
19 environment for the application in use and the task performed.
20 .P
21 In tiling mode windows are managed in a master and stacking area. The master
22 area contains the windows which currently need most attention, whereas the
23 stacking area contains all other windows. In floating mode windows can be
24 resized and moved freely. Dialog windows are always managed floating,
25 regardless of the mode applied.
26 .P
27 Windows are grouped by tags. Each window can be tagged with one or multiple
28 tags. Selecting certain tags displays all windows with these tags.
29 .P
30 dwm contains a small status bar which displays all available tags, the mode,
31 the title of the focused window, and the text read from standard input. The
32 selected tags are indicated with a different color. The tags of the focused
33 window are indicated with a filled square in the top left corner. The tags
34 which are applied to one or more windows are indicated with an empty square in
35 the top left corner.
36 .P
37 dwm draws a small border around windows to indicate the focus state.
40 .SH OPTIONS
41 .TP
42 .B \-v
43 prints version information to standard output, then exits.
46 .SH USAGE
48 .SS Status bar
49 .TP
50 .B Standard input
51 is read and displayed in the status text area.
52 .TP
53 .B Button1
54 click on the bar to display the other tag.
56 .SS Keyboard commands
57 .TP
58 .B Mod1-Shift-Return
59 Start
60 .BR xterm (1).
61 .TP
62 .B Mod1-Tab
63 Focus next window.
64 .TP
65 .B Mod1-i
66 Increase the number of windows in the master area (tiling mode only).
67 .TP
68 .B Mod1-d
69 Decrease the number of windows in the master area (tiling mode only).
70 .TP
71 .B Mod1-F1
72 View other tag.
73 .TP
74 .B Mod1-F3
75 Move current window to other tag.
76 .TP
77 .B Mod1-^
78 Start
79 .BR dmenu (1)
80 .TP
81 .B Mod1-1
82 Zooms/cycles current window to/from master area (tiling mode), toggles maximization current window (floating mode).
83 .TP
84 .B Mod1-2
85 Close focused window.
86 .TP
87 .B Mod1-space
88 Toggle between tiling and max mode (affects all windows).
89 .TP
90 .B Mod1-Shift-space
91 Toggle focused window between floating and non-floating state.
92 .TP
93 .B Mod1-Shift-q
94 Quit dwm.
96 .SS Mouse commands
97 .TP
98 .B Mod1-Button1
99 Move current window while dragging (floating mode only).
100 .TP
101 .B Mod1-Button3
102 Resize current window while dragging (floating mode only).
105 .SH CUSTOMIZATION
106 dwm is customized by creating a custom config.h and (re)compiling the source
107 code. This keeps it fast, secure and simple.
110 .SH SEE ALSO
111 .BR dmenu (1)
114 .SH BUGS
115 The status bar may display
116 .BR "EOF"
117 when dwm has been started by an X session manager like
118 .BR xdm (1),
119 because those close standard output before executing dwm.
120 .P
121 Java applications which use the XToolkit/XAWT backend may draw grey windows
122 only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
123 JDK 1.6 versions, because it assumes a reparenting window manager. As a workaround
124 you can use JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or you
125 can set the following environment variable (to use the older Motif
126 backend instead):
127 .BR AWT_TOOLKIT=MToolkit .