Observe ZDNET: Add us as a most popular supply on Google.
ZDNET’s key takeaways
- Configuring the Hyprland window supervisor is difficult.
- I needed to see how nicely AI would carry out at making a .conf file.
- There’s an essential lesson to be discovered right here.
That is the 12 months I spotted how a lot I take pleasure in tiling window managers, and Hyprland is my favourite up to now.
In the event you’ve by no means skilled a tiling window supervisor, know that they don’t seem to be precisely for the faint of coronary heart. They’re pushed by keyboard shortcuts, of which there are loads to memorize. On high of that, most of them require configuration through textual content information.
Such is the case with Hyprland.
Hyprland is configured through the ~/.config/hyrp/hyrpland.conf file; for the uninitiated, it may be moderately daunting. You actually ought to know what you are entering into earlier than you make that first edit to the file.
I’ve executed a little bit of Hyprland dotfile ricing (a elaborate method of claiming I’ve hung out customizing hyprland.conf information), however I made a decision to run somewhat experiment.
I needed to see if AI might create a hyperland.conf file based mostly on my immediate. I made a decision to begin recent with a CachyOS set up. (I chosen each the Hyrpland and KDE Plasma desktops — why I added each will turn out to be clear shortly.) As soon as I had CachyOS up and operating, I began the method. I made a decision to attempt three totally different AI instruments: Opera’s Aria, Ollama, and Codex.
Of the three AI instruments, Codex was the one one able to making a remotely usable configuration. Here is the way it went.
The immediate
To create the customization, I used the next immediate:
Create a hyprland.conf configuration file for Hyprland model 0.55.2 that makes use of Waybar with a glassy, rounded-corner theme, a coloration palette of purple and pink, and makes use of the next keybindings: Tremendous+t to open the terminal, Tremendous+b to open the net browser, and the default keybindings for shifting home windows and window focus.
Upon operating the question, each AI service I used knowledgeable me that many configuration choices can be placeholders and that I would want to customise them to suit my wants.
It took a number of tries, however ultimately Codex gave me this .conf file, which you’ll be able to view in my GitHub repository.
I had my doubts that it could work. Even so, I added the contents from Codex and reloaded the window supervisor with:
hyprctl reload
I used to be not shocked to come across quite a few errors. I would noticed a number of the errors even earlier than I copied the output to the .conf file, however needed to see what occurred regardless.
Listed here are the issues I discovered at first look:
- There was no default terminal set.
- The border_radius choice not works in 0.55.2.
- Within the rounding = 12px choice, the px would trigger an error, so it needed to be eliminated.
- Windowrule doesn’t work.
I additionally needed to set up the next to make this work:
- kitty terminal app
- Waybar
- rofi
With out the above put in, Hyprland would not be very useful.
After resolving the above points, I used to be shocked that the .conf file labored. It wasn’t a really elegant desktop, nor did it apply the colour scheme I added in my question, however I had a skeleton .conf file I might use to additional tweak.
Why did I set up KDE Plasma?
After I first set out to do that, I solely put in Hyprland on CachyOS. After including the contents to the config file as-is (as a result of I needed to see the way it labored), I wound up with what was basically a non-functioning desktop. The principle cause for that is that kitty, Waybar, and Rofi weren’t put in.
I put in CachyOS a second time, solely with KDE Plasma alongside for the trip. With KDE Plasma added, I knew I had a backup desktop setting to make use of, ought to issues go awry. All I needed to do was reboot CachyOS, log into KDE Plasma, and repair the problems.
As soon as I had the entire points fastened throughout the Codex-derived .conf file, Hyprland labored as anticipated. After all, there have been plenty of tweaks that wanted to be taken care of to get it precisely how I needed it to look,
A lesson discovered
I used to be pretty sure how this experiment would end up, and it solidified my opinion that AI is commonly mistaken however can no less than function a launching level. Although I defined to Codex (the one AI to return near making a functioning hyprland.conf file) which model of Hyprland I used to be utilizing, it nonetheless used choices which might be not viable.
To those that may be excited about migrating to the Linux working system, I first wish to say that Hyprland just isn’t the window supervisor for you. Follow KDE Plasma, Cinnamon, or GNOME. For individuals who wish to attempt to use Hyprland (or any tiling window supervisor configured with a textual content file), take into account AI to be a way to see how the configuration information work, however be sure to be taught from what AI presents to you, so you’ll be able to perceive the way it works and might begin creating information by yourself.
Consider AI as nothing greater than a way to take your first steps, however know that you’ll have to appropriate its errors.
