Compare commits

...

4 Commits

Author SHA1 Message Date
fuggy 33bd679037
Status bars: add short intro what Eww is (#697)
Co-authored-by: Mihai Fufezan <mihai@fufexan.net>
2024-06-25 22:17:51 +03:00
Leon bc3c066321 Nix/Contributing: fix typo 2024-06-25 22:11:14 +03:00
Leon 13ea15aa9c
Using hyprctl: clarify usage of `hyprctl setprop` and `exec` dispatcher with dynamic rules (#696) 2024-06-25 22:09:07 +03:00
Vaxry d59d2c18f3 selector: add 0.41.2 2024-06-25 13:54:04 +02:00
5 changed files with 43 additions and 2 deletions

View File

@ -180,6 +180,9 @@ bind = SUPER, C, movetoworkspace, special
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
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:
@ -190,5 +193,5 @@ bind = mod, key, exec, [rules...] command
For example:
```
bind = SUPER, E, exec, [workspace 2 silent;float;noanim] kitty
bind = SUPER, E, exec, [workspace 2 silent; float; move 0 0] kitty
```

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
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 | comment |
| --- | --- |
@ -228,6 +260,7 @@ Prop List:
| activebordercolor | gradient, -1 means not set |
| inactivebordercolor | gradient, -1 means not set |
For example:
```sh
hyprctl setprop address:0x13371337 forcenoanims 1 lock # with locking
hyprctl setprop address:0x13371337 nomaxsize 0 # without locking

View File

@ -25,7 +25,7 @@ To keep a failed build directory, pass the `--keep-failed` flag.
## Building the Wayland stack with ASan
Run `nix develop` first, then follow the
[Building with ASan](https://wiki.hyprland.org/Crashes-and-Bugs/#bisecting-an-issue)
[Building with ASan](https://wiki.hyprland.org/Crashes-and-Bugs/#building-the-wayland-stack-with-asan)
guide.
## Manual building

View File

@ -77,6 +77,10 @@ configuration:
## Eww
[Eww](https://github.com/elkowar/eww) (ElKowar's Wacky Widgets) is a widget system made in Rust, which lets you
create your own widgets similarly to how you can in AwesomeWM. The key difference
is that it is independent of your window manager/compositor.
In order to use [Eww](https://github.com/elkowar/eww), you first have to install
it, either using your distro's package manager, by searching `eww-wayland`, or
by manually compiling. In the latter case, you can follow the

View File

@ -6,6 +6,7 @@ weight: 1
Select your preferred wiki version below:
- [Latest Git](https://wiki.hyprland.org/)
- [v0.41.2](https://wiki.hyprland.org/0.41.2/)
- [v0.41.1](https://wiki.hyprland.org/0.41.1/)
- [v0.41.0](https://wiki.hyprland.org/0.41.0/)
- [v0.40.0](https://wiki.hyprland.org/0.40.0/)