sites

public wiki contents of suckless.org
git clone git://git.suckless.org/sites
Log | Files | Refs

commit 8f1de030d8a655008d9fbd1173c9b64999d185a6
parent a9941db4a61e9c4f8032278427b048aadc9061c1
Author: Hiltjo Posthuma <hiltjo@codemadness.org>
Date:   Wed, 11 Dec 2019 22:26:10 +0100

customisation rules: small tweaks

from Eddie:

- change the proprietary Telegram example to deadbeef.
- typo similiarly -> similarly

Diffstat:
Mdwm.suckless.org/customisation/rules/index.md | 12++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/dwm.suckless.org/customisation/rules/index.md b/dwm.suckless.org/customisation/rules/index.md @@ -6,7 +6,7 @@ What does '`rules`' do? 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 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` or `0`. @@ -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 }, + { "deadbeef", 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 +windows appear on tag 9 instead of the currently viewed tags. +deadbeef similarly displays its window on tag 8 for a secondary display monitor. How does the matching work?