commit a9941db4a61e9c4f8032278427b048aadc9061c1
Author: aleks <aleks.stier_AT_icloud.com>
Date: Wed Dec 11 22:00:12 2019 +0100
[customisation][rules] delete whitespace and tabs mixed with spaces
diff --git a/dwm.suckless.org/customisation/rules/index.md b/dwm.suckless.org/customisation/rules/index.md
index 5139dc28..bbecbf50 100644
--- a/dwm.suckless.org/customisation/rules/index.md
+++ b/dwm.suckless.org/customisation/rules/index.md
_AT_@ -3,10 +3,10 @@ Setting rules in config.h
What does '`rules`' do?
-----------------------
-The `rules` array allows treating of certain applications (clients) uniquely.
+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 with
+(`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` or `0`.
_AT_@ -15,14 +15,14 @@ Example from the default config:
static Rule rules[] = {
/* class instance title tags mask isfloating monitor */
- { "Gimp", NULL, NULL, 0, 1, -1 },
- { "Firefox", NULL, NULL, 1 << 8, 1, -1 },
- { "Telegram", NULL, NULL, 1 << 7, 0 0 }
+ { "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
window appear on tag 9 instead of the currently viewed tag.
-Telegram similiarly displays its window on tag 8 for a secondary display
+Telegram similiarly displays its window on tag 8 for a secondary display
monitor.
How does the matching work?
Received on Wed Dec 11 2019 - 22:01:18 CET