commit e7c345285a7ba9c2db7ef3e633910d16b25929c9
parent 33c32473bfb99f34473a27c552cec97425918137
Author: Eddie Thieda <eddie.thieda@gmail.com>
Date: Wed, 11 Dec 2019 15:12:16 -0500
Update dwm customisation rules and add secondary display startup tag example.
Diffstat:
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/dwm.suckless.org/customisation/rules/index.md b/dwm.suckless.org/customisation/rules/index.md
@@ -3,24 +3,27 @@ Setting rules in config.h
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
+The `rules` array allows treating of certain applications (clients) uniquely.
+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
+(`WM_CLASS`) and title (`WM_NAME`) properties and then the given tag with
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`.
+means the currently viewed tags and the default mode is tiled so isfloating is
+`False` or `0`.
Example from the default config:
static Rule rules[] = {
/* class instance title tags mask isfloating monitor */
- { "Gimp", NULL, NULL, 0, True, -1 },
- { "Firefox", NULL, NULL, 1 << 8, True, -1 },
+ { "Gimp", NULL, NULL, 0, 1, -1 },
+ { "Firefox", NULL, NULL, 1 << 8, 1, -1 },
+ { "Telegram", NULL, NULL, 1 << 7, 0 0 }
};
These rules make every Gimp and Firefox window floating and makes Firefox
-windows appear on tag 9 instead of the currently viewed tags.
+window appear on tag 9 instead of the currently viewed tag.
+Telegram similiarly displays its window on tag 8 for a secondary display
+monitor.
How does the matching work?
---------------------------
