3 ms·
Been using Hyprland for about a year on my arch box. I do like using it but I don't like that they seem to make breaking changes to the config file format regu
by cmiller1 3y ago
Been using Hyprland for about a year on my arch box. I do like using it but I don't like that they seem to make breaking changes to the config file format regularly. There have been at least three time where an update left me with something not functioning correctly or a bunch of errors and I had to dig through my config file and find what things were no longer compatible with the new version.
- gchamonlive 3y agoWell, that is... Worrying. Can you give specifics about the occasions when hyprland broke on you?
- cmiller1 3y agoFor example with the 0.36.0 release ## was changed to mean "escaped #" instead of a valid start of a comment line (comments start with #) so some heading type comments I had like ### Input config ### were suddenly throwing errors.
- hollow-moe 3y agoit's a known issue https://github.com/hyprwm/hyprlang/issues/30 https://github.com/hyprwm/hyprlang/issues/30 and will likely be fixed in the future i use hyprland too since quite some time and when config options changed a red banner shows up and tells you what's broken, a quick look to the wiki and 5 minutes is all you need to fix configs breaking is expected since it's evolving really quickly
- earthling8118 3y agoThis is mostly correct, but I think 5 minutes is understating the effort for some changes. I've had a few head scratching moments where I wasn't sure what to do to get an equivalent configuration. That being said, it is still reasonable to do.
- Ferret7446 3y agoThat sounds like the earlier years of awesomewm. aweomsomewm's config API was notoriously volatile, but stabilized later on; hopefully Hyprland will also.