Mihai Fufezan

I don't have enough context about your `pkgs` to know what's wrong. Are you setting `nixpkgs.pkgs` like I do [here](https://github.com/fufexan/dotfiles/blob/addf49068c05a1dffeb4fb22cfc0734f456fa1c3/modules/minimal.nix#L34)? Or are you letting the module system import it by...

> **Edit 2** Try adding this to your inputs > > ```nix > inputs.nixpkgs.follows = "nixpkgs"; > ``` Why, exactly? This means you no longer get cache hits.

The nix package actually does install the protocols (copy, rather) in `protocols/hyprland-protocols`. Meson should find the files automatically if the subproject is where it's supposed to be (protocols/hyprland-protocols).

@MrRoy what commit did you test that on? Is it broken with hyprland-protocols master?

I have no idea, I've never used NixOS in a VM.

You don't *need* HM to configure Hyprland. It'll create a config file if `~/.config/hypr/hyprland.conf` doesn't exist. You can then modify that as usual. I'm not opposed to this change but...

Can I close this? Hyprland auto-generates a config file, which you do not need to manage with Home Manager.

A solution until this is properly taken care of would be to write your config to `/etc/xdg/hyprland.conf` and starting hyprland with `Hyprland -c /etc/xdg/hyprland.conf`. I don't know when I will...

Is this issue still relevant? Doesn't `movetoworkspace` do the same thing, essentially?

Hyprland supports groups, which are rendered like this (ignore my ugly theming though).  If you want more of the i3/sway functionality, take a look at the [hy3 plugin](https://github.com/outfoxxed/hy3/).