[wiki] [official] clarify dwm/customization/rules || nsz
changeset: 209:a14805ca656d
tag: tip
user: nsz <nszabolcs_AT_gmail.com>
date: Wed Feb 18 17:35:54 2009 +0100
files: dwm/customisation/rules.md
description:
clarify dwm/customization/rules
diff -r a5f248ca3a83 -r a14805ca656d dwm/customisation/rules.md
--- a/dwm/customisation/rules.md Wed Feb 18 11:15:49 2009 +0100
+++ b/dwm/customisation/rules.md Wed Feb 18 17:35:54 2009 +0100
_AT_@ -1,13 +1,15 @@
Setting rules in config.h
=========================
-What does `rules` do?
----------------------
-The `rules` array is to treat certain applications (clients) in a special way.
-The window class, instance (`WM_CLASS` property) and title (`WM_NAME` property)
-can be matched to select the client. The possible actions are applying tags to
-the selected client (default is `0` which means the currently viewed tags)
-and setting the client floating (default is `False` which means tiled client).
+What does '`rules`' do?
+-----------------------
+The `rules` array allows to treat certain applications (clients) in a special
+way. A rule has a matching and an action part. When a new client appears (sends
+a maprequest), it is matched against the rules based on its class, instance
+(`WM_CLASS`) and title (`WM_NAME`) properties and then the given tag and
+floating mode setting actions are performed. The default tag mask is `0`, which
+means the currently viewed tags, and the default mode is tiled so isfloating is
+`False`.
Example from the default config:
_AT_@ -17,15 +19,15 @@
{ "Firefox", NULL, NULL, 1 << 8, True },
};
-This makes every Gimp and Firefox window floating and makes Firefox windows
-appear on tag 9 instead of the currently viewed tags.
+These rules make every Gimp and Firefox window floating and makes Firefox
+windows appear on tag 9 instead of the currently viewed tags.
How does the matching work?
---------------------------
-A client is matched if its corresponding properties contain the given strings
-as substrings (case-sensitively) or `NULL` is given (which is matched on anything).
+A client is matched if its properties contain the given strings as substrings
+(case-sensitively) or `NULL` is given (which means anything is matched there).
-The rules are matched in order, so more than one rule can be applied to a client.
+More than one rule can be applied to a client, the rules are matched in order.
How to check these properties of a client?
------------------------------------------
Received on Wed Feb 18 2009 - 17:57:14 CET
This archive was generated by hypermail 2.3.0
: Thu Sep 13 2012 - 19:30:30 CEST