This manual page describes the openbsd-cwm(1)
The current line can be extended over multiple lines using a backslash
(‘\’). Comments can be put anywhere in the file using a hash
mark (‘#’), and extend to the end of the current line. Care
should be taken when commenting out multi-line text: the comment is effective
until the end of the entire block.
Arguments containing whitespace should be surrounded by double quotes (").
The following options are accepted:
Automatically add new windows to
group if their class property matches
windowclass, or if their name and class
properties match windowname and
windowclass, respectively. The more
specific last match wins. group is a
number between 0 and 9. If group is 0,
matching windows will not be added to any group; this may be used to
override “sticky group mode”.
The name and class values, respectively, for existing windows are both set
in the WM_CLASS property and may be obtained using
Cause the creation of a key binding, or replacement of a
default key binding. The modifier keys come first, followed by a
The following modifiers are recognised:
The Control key.
The Meta key.
The Shift key.
The Mod4 key (normally the windows key).
The ‘-’ should be followed by a keysym name, taken from
command may either be one from the
BIND COMMAND LIST
(see below) or the command line that is to be executed.
A special command keyword
“unmap” can be used to remove the named key binding. This
can be used to remove a binding which conflicts with an application.
Every name entry is shown
in the application menu. When selected, the defined
path is executed with
The name entries
term and lock
have a special meaning. They point to the terminal and screen locking
programs specified by key bindings. The defaults are
Define a “gap” in pixels at the edge of the
screen, so that when a window is maximized it will not overlap this area.
This “gap” can be used for applications such as
xclock(1), where the user may wish to remain