Hyprland
Hyprland copied to clipboard
global config file?
What do you guys think about a global config file directory like $XDG_CONFIG_DIRS/hypr and /etc/xdg/hypr as fallback for all hypr related stuff?
Having a system-wide configuration file is actually part of the xdg base directory specification.
$XDG_CONFIG_DIRSdefines the preference-ordered set of base directories to search for configuration files in addition to the$XDG_CONFIG_HOMEbase directory. The directories in$XDG_CONFIG_DIRSshould be seperated with a colon ':'.
Another benefit would that NixOSers wouldn't have to use home-manager to configure Hyprland from their configuration.nix.
@fufexan kowalski, analysis
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 using HM and having this be done are orthogonal.
You need home manager to place config files reproducably in your home directory. For global config files, you can use environment.etc.
Can I close this? Hyprland auto-generates a config file, which you do not need to manage with Home Manager.
I don't see how configuration file auto generation solves this. To change the configuration globally, one would need to recompile the changed nix expression every time and even then Hyprland would only use the new global config, if i delete the old one. Yes, i can have editable configuration files floating around in my XDG_CONFIG_HOME, which i don't need home-manager to manage. But if i want to include my Hyprland config in my reproducible NixOS config repository, I would either need home-manager, or a global config file.
Also, I don't see this as a NixOS only issue, because a global config file is something that could concern people on other distros too.
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 have time, but I'll try to implement this.
Yeah, i gotta be honest, I've gone back to i3 at the moment, but thanks
@Quantenzitrone this issue should be closed or?
idk, not supporting the full xdg base directory specification is still not fixed, right?