hyprwm/hyprland-wiki
1
0
Fork 0
mirror of https://github.com/hyprwm/hyprland-wiki.git synced 2024-11-22 20:55:59 +01:00
Code Issues Projects Releases Packages Wiki Activity

Using hyprctl: clarify usage of hyprctl setprop and exec dispatcher with dynamic rules (#696)

Browse source
This commit is contained in:
Leon 2024-06-25 21:09:07 +02:00 committed by GitHub
parent d59d2c18f3
commit 13ea15aa9c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 37 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
pages/Configuring/Dispatchers.md
View file

@ -180,6 +180,9 @@ bind = SUPER, C, movetoworkspace, special
The `exec` dispatcher supports adding rules. Please note some windows might work The `exec` dispatcher supports adding rules. Please note some windows might work
better, some worse. It records the PID of the spawned process and uses that. For example, if better, some worse. It records the PID of the spawned process and uses that. For example, if
your process forks and then the fork opens a window, this will not work. your process forks and then the fork opens a window, this will not work.
Rules will only be applied once. This means dynamic rules will be overridden as soon as a
property of the window changes (e.g. switching focus). To make dynamic rules stick around
use `hyprctl setprop` (see [Using hyprctl](./Using-hyprctl)).
The syntax is: The syntax is:
@ -190,5 +193,5 @@ bind = mod, key, exec, [rules...] command
For example: For example:
``` ```
bind = SUPER, E, exec, [workspace 2 silent;float;noanim] kitty bind = SUPER, E, exec, [workspace 2 silent; float; move 0 0] kitty
``` ```

33
pages/Configuring/Using-hyprctl.md
View file

@ -198,6 +198,38 @@ Sets a window prop. Can be locked by adding `lock` at the end. If `lock` is not
added, will be unlocked. Locking means a dynamic windowrule _cannot_ override added, will be unlocked. Locking means a dynamic windowrule _cannot_ override
this setting. this setting.
Usage:
```sh
hyprctl setprop <mode:regex> <property> <value> [lock]
```
Regex supports different modes. The supported modes are:
```ini
class - class
title - title
initialclass - initialClass
initialtitle - initialTitle
active - active window
address - address prefixed with 0x
pid - process ID
floating - first floating window on the current workspace
tiled - first tiled window on the current workspace
```
If no mode is specified `class` is used by default.
{{< callout type=info >}}
To get more information about a window, you can use `hyprctl clients`.
{{< /callout >}}
{{< callout type=warning >}}
Please beware that `hyprctl clients` will display the fields as **initialClass** and **initialTitle** while the regex mode uses `initialclass` and `initialtitle`.
{{< /callout >}}
Prop List: Prop List:
| prop | comment | | prop | comment |
| --- | --- | | --- | --- |
@ -228,6 +260,7 @@ Prop List:
| activebordercolor | gradient, -1 means not set | | activebordercolor | gradient, -1 means not set |
| inactivebordercolor | gradient, -1 means not set | | inactivebordercolor | gradient, -1 means not set |
For example:
```sh ```sh
hyprctl setprop address:0x13371337 forcenoanims 1 lock # with locking hyprctl setprop address:0x13371337 forcenoanims 1 lock # with locking
hyprctl setprop address:0x13371337 nomaxsize 0 # without locking hyprctl setprop address:0x13371337 nomaxsize 0 # without locking