Getting started

Pypr consists in two things:

• a tool: pypr which runs the daemon (service), but also allows to interract with it
• some config file: ~/.config/hypr/pyprland.toml (or the path set using --config)

The pypr tool only have two built-in commands:

• help lists available commands (including plugins commands)
• reload reads the configuration file and apply some changes:
  • new plugins will be loaded
  • configuration items will be updated (most plugins will use the new values on the next usage)

Important

• with no argument it runs the daemon (doesn't fork in the background)

• if you pass parameters, it will interact with the daemon instead.

Note

Pypr command names are documented using underscores (_) but you can use dashes (-) instead. Eg: pypr shift_monitors and pypr shift-monitors will run the same command

Other commands are implemented by adding plugins.

The config file uses the following syntax:

[pyprland]
plugins = ["plugin_name"]

[plugin_name]
plugin_option = 42

[plugin_name.another_plugin_option]
suboption = "config value"

Installation

Check your OS package manager first, eg, for archlinux, you can find it on AUR, eg with yay: yay pyprland

Otherwise, use the python package manager inside a virtual environment (python -m venv somefolder && source ./somefolder/bin/activate):

pip install pyprland

Don't forget to start the process with hyprland, adding to hyprland.conf:

exec-once = pypr

Note

Using a virtual environment, you may want to set the full path (eg: /home/bob/venv/bin/pypr)

Running

Once the pypr daemon is started (cf exec-once), you can list the eventual commands which have been added by the plugins using pypr -h or pypr help, those commands are generally meant to be use via key bindings, see the hyprland.conf part of Configuring section below.

Configuring

Create a configuration file in ~/.config/hypr/pyprland.toml enabling a list of plugins, each plugin may have its own configuration needs or don't need any configuration at all. Most default values should be okay, just set when you are not satisfied with the default.

Check the TOML format for details about the syntax.

Simple example:

[pyprland]
plugins = [
    "shift_monitors",
    "workspaces_follow_focus"
]

More complex example:

[pyprland]
plugins = [
  "scratchpads",
  "lost_windows",
  "monitors",
  "toggle_dpms",
  "magnify",
  "expose",
  "shift_monitors",
  "workspaces_follow_focus",
]

[workspaces_follow_focus]
max_workspaces = 9

[expose]
include_special = false

[scratchpads.stb]
animation = "fromBottom"
command = "kitty --class kitty-stb sstb"
class = "kitty-stb"
lazy = true
size = "75% 45%"

[scratchpads.stb-logs]
animation = "fromTop"
command = "kitty --class kitty-stb-logs stbLog"
class = "kitty-stb-logs"
lazy = true
size = "75% 40%"

[scratchpads.term]
animation = "fromTop"
command = "kitty --class kitty-dropterm"
class = "kitty-dropterm"
size = "75% 60%"

[scratchpads.volume]
animation = "fromRight"
command = "pavucontrol"
class = "pavucontrol"
lazy = true
size = "40% 90%"
unfocus = "hide"

[monitors]
unknown = "wlrlui"

[monitors.placement]
"Sony".top_of = ["Brand X", "Other Brand"]
"Acer".left_end_of = "Sony"
"MSI Gaming stuff".bottom_center_of = "(HDMI-A-1)"

Which is easy to use with a couple of bind configuration rules in hyprland.conf, eg:

bind = $mainMod SHIFT, Z, exec, pypr zoom
bind = $mainMod ALT, P,exec, pypr toggle_dpms
bind = $mainMod SHIFT, O, exec, pypr shift_monitors +1
bind = $mainMod, B, exec, pypr expose
bind = $mainMod, K, exec, pypr change_workspace +1
bind = $mainMod, J, exec, pypr change_workspace -1
bind = $mainMod,L,exec, pypr toggle_dpms
bind = $mainMod SHIFT,M,exec,pypr toggle stb stb-logs
bind = $mainMod,A,exec,pypr toggle term
bind = $mainMod,V,exec,pypr toggle volume

Optimization

Plugins

Only enable the plugins you are using in the plugins array (in [pyprland] section).

Leaving the configuration for plugins which are not enabled will have no impact.

Pypr command

In case you want to save some time when interracting with the daemon you can use socat instead (needs to be installed). Example of a pypr-cli command (should be reachable from your $PATH):

#!/bin/sh
socat - "UNIX-CONNECT:/tmp/hypr/${HYPRLAND_INSTANCE_SIGNATURE}/.pyprland.sock" <<< $@

On slow systems this may make a difference. Note that the "help" command will require usage of the standard pypr command.

Troubleshoot

You can enable debug logging and saving to file using the --debug argument, eg:

pypr --debug /tmp/pypr.log

More info in the troubleshooting page.