• Workspaces
• Window
• Language
• Submap

The workspaces module displays the currently used workspaces in hyprland compositor.

Addressed by hyprland/workspaces

The rules are regexes that may match against class, title, or both in order to fine tune window representation. In order to understand them, let's break the possible rules in 4 categories:

When a user's config only contains "vague" rules, they will be used to match against windows classes. This is both for backwards compatibility and performance reasons: this feature originally supported only classes, since they usually don't change during a program's lifetime. When the title config was introduced, matching previously existing rules to both classes and titles wound cause a whole lot of "wrong" matches, so it's disabled by default. Additionally, matching against the title requires listening to window title changes via Hyprland's IPC, which is not necessary when not in use.

When the config contains at least one "title-only" or "hybrid" rewrite rule, then all of the "vague" rules will match against both class and title. Though confusing at first, this is in place to allow users to define vague rules, where it doesn't matter whether the class or title matched.

Examples that use all 4 categories are available below.

Additional to workspace name matching, the following format-icons can be set.

How to sort workspaces.

"hyprland/workspaces": {
  "format": "<sub>{icon}</sub>\n{windows}",
  "format-window-separator": "\n",
  "window-rewrite-default": "",
  "window-rewrite": {
    "title<.*youtube.*>": "", // Windows whose titles contain "youtube"
    "class<firefox>": "", // Windows whose classes are "firefox"
    "class<firefox> title<.*github.*>": "", // Windows whose class is "firefox" and title contains "github". Note that "class" always comes first.
    "foot": "", // Windows that contain "foot" in either class or title. For optimization reasons, it will only match against a title if at least one other window explicitly matches against a title.
    "code": "󰨞",
	},
  ...
}

Each entry of persistent-workspace names a workspace that should always be shown. Associated with that value is a list of outputs indicating where the workspace should be shown, an empty list denoting all outputs

"hyprland/workspaces": {
    "persistent-workspaces": {
             "*": 5, // 5 workspaces by default on every monitor
             "HDMI-A-1": 3 // but only three on HDMI-A-1
       }
}

"hyprland/workspaces": {
    "persistent-workspaces": {
      "1": [
        "DP-3" // workspace 1 shown on DP-3
      ],
      "2": [
        "DP-1" // workspace 2 shown on DP-1
      ],
      "3": [
        "DP-1" // workspace 3 shown on DP-1
      ],
    }
}

"hyprland/workspaces": {
   "persistent-workspaces": {
      "DP-3": [ 1 ], // workspace 1 shown on DP-3
      "DP-1": [ 2, 3 ], // workspaces 2 and 3 shown on DP-1
    }
}

"hyprland/workspaces": {
	"format": "{name}: {icon}",
	"format-icons": {
		"1": "",
		"2": "",
		"3": "",
		"4": "",
		"5": "",
		"active": "",
		"default": ""
	},
       "persistent-workspaces": {
             "*": 5, // 5 workspaces by default on every monitor
             "HDMI-A-1": 3 // but only three on HDMI-A-1
       }
}

• #workspaces
• #workspaces button
• #workspaces button.active
• #workspaces button.empty
• #workspaces button.persistent
• #workspaces button.special
• #workspaces button.visible
• #workspaces button.urgent
• #workspaces button.hosting-monitor (gets applied if workspace-monitor == waybar-monitor)

This order makes it so that my priority of styling is special cases override the norm. If you wanted to include persistent in here, I'd throw it in before empty, personally.

Active Monitor: Green icon for active workspace.

Inactive Monitor: Blue icon for visible but not active.

The window module displays the title of the currently focused window of Hyprland, the Wayland compositor.

Addressed by hyprland/window

See the output of "hyprctl clients" for examples

"hyprland/window": {
    "format": "👉 {}",
    "rewrite": {
        "(.*) — Mozilla Firefox": "🌎 $1",
        "(.*) - fish": "> [$1]"
    },
    "separate-outputs": true
}

• #window

The following classes can apply styles to the entire Waybar (see the Sway module's page for more info):

• window#waybar.empty When no windows are in the workspace
• window#waybar.solo When one tiled window is visible in the workspace (floating windows may be present)
• window#waybar.<app_id> Where <app_id> is the class (e.g. chromium) of the solo tiled window in the workspace (use hyprctl clients to see classes)
• window#waybar.floating When there are only floating windows visible in the workspace
• window#waybar.fullscreen When there is a fullscreen window in the workspace; useful with Hyprland's fullscreen, 1 mode
• window#waybar.swallowing When there are hidden windows in the workspace; usually occurs due to window swallowing

This will change the color of the entire bar when either Chromium or kitty occupy the screen.

#window {
    border-radius: 20px;
    padding-left: 10px;
    padding-right: 10px;
}

window#waybar.kitty {
    background-color: #111111;
    color: #ffffff;
}

window#waybar.chromium {
    background-color: #eeeeee;
    color: #000000;
}

/* make window module transparent when no windows present */
window#waybar.empty #window {
    background-color: transparent;
}

The language module displays the currently selected keyboard language (layout) for Hyprland, the Wayland compositor.

Addressed by hyprland/language

"hyprland/language": {
    "format": "Lang: {}",
    "format-en": "AMERICA, HELL YEAH!",
    "format-tr": "As bayrakları",
    "keyboard-name": "at-translated-set-2-keyboard"
}

• #language

#language {
    border-radius: 20px;
    padding-left: 10px;
    padding-right: 10px;
}

The submap module displays the currently active submap similar to sway/mode for Hyprland, the Wayland compositor.

Addressed by hyprland/submap

"hyprland/submap": {
    "format": "✌️ {}",
    "max-length": 8,
    "tooltip": false
}

• #submap
• #submap.<name>