HTT - Hyprland Toggle Tiling

Logo taken from Papirus. I'm not a designer, don't judge me.

A simple program to toggle tiling and floating modes for windows in the Hyprland Wayland compositor.

Check out the demo!

Features • Installation • Usage • Integration with Hyprland

Features

• Quickly switch between tiling and floating modes for all windows on the active workspace.
• After switching, the program creates a hyprland config file to respect the new windowing mode. Let's say you switched to tiling mode. From that point on, new windows will open in tiling mode as well. Switch to floating mode again and newly opened windows will be in floating mode.
• Floating/tiling window rules are isolated between workspaces. You can set one workspace to be floating, and all the rest to tiling for example.
• Returns applied rule for the current workspace. Useful for scripting.
• Useful for workflows that require both tiling and floating window management.
• Lightweight and easy to integrate with your Hyprland setup.

Installation

You have a few options of obtainting the program.

Install from AUR

You may install this program from the AUR.

Download the release

You can also download the release binary.

or go nuts and...

Compile from source

1. Clone this repository:

   git clone https://typofelho.ddns.net/TypoMustakes/hyprland-toggle-tiling.git
   

2. Enter project directory:

   cd hyprland-toggle-tiling/
   

3. Create build directory:

   cmake -S . -B build/
   

4. Enter build directory:

   cd build/
   

5. Build the projects:

   cmake --build .
   

Usage

./htt <config-file-path> (-q)

• -q: Print the rule applied on the current workspace to STDOUT, but don't change anything. If there isn't an active rule for the current workspace, it returns a tiling rule. The returned string is a valid Hyprland window rule configuration line, like so:

# (On workspace 2...)
$ ./htt ~/.cache/htt/rules -q

windowrule = tile on, match:workspace 2

Potential applications for this are mainly scripts, like my waybar module here:

• If the specified configuration file does not exist, it will be created.
• If the configuration contains existing rules, this should still work, but your existing configuration will probably get a bit messy, syntax-wise. I advise against it.

Integration with Hyprland

1. Whatever configuration path you specify, include it in your Hyprland config, like so: /path/to/your/hyprland.conf:

   source = ~/path/to/specified/config/file.conf
   

2. Bind the script to a key in your Hyprland config:

   bind = $mod + t, exec, /path/to/htt <config-file-path>
   

   Or not. Do whatever you want.