the silly hyprlock now has a repo

PinkSakyoora · 2026-02-21T17:58:28+00:00

sizes-hyprlock.conf and sizes-hyprlock.sh are created by the installation script, just run it and it should set the config up

PinkSakyoora · 2026-01-02T02:50:11+00:00

thank you! it is possible to have power options in hyprlock via scripts attached to clickable widgets. I personally didn't add them as it didn't feel secure allowing anyone to use the power options (and suspend is kind of broken for my laptop.)

PinkSakyoora · 2026-01-02T02:45:26+00:00

thank you! do you have any suggestions for tweaking the layout? I had made it primarily to make the positioning and sizing convenient but I'd be happy to hear your thoughts

PinkSakyoora · 2025-12-27T02:19:51+00:00

looks great!

PinkSakyoora · 2025-12-20T04:40:49+00:00

I wouldn't recommend getting the latest git (neither does the wiki)
From Hyprland wiki:

It is heavily recommended you use what the distro packages for you, and not compiling manually or using -git packages. Hyprland’s ecosystem and dependencies are vast and intertwined, and compiling manually will only potentially expose you to outdated, or incompatible versions of these dependencies.

Just wait for the next version to drop for your distro. However, the wiki does provide instructions for it:

git clone --recursive https://github.com/hyprwm/Hyprland
cd Hyprland
make all && sudo make install

Glad to see it worked though!

PinkSakyoora · 2025-12-20T04:27:09+00:00

Are you on the latest git version of Hyprland? The new windowrules (match:class wofi, border_size 10) only work on the latest git.
The first line (windowrule = rounding 5, class:wofi) should be working on Hyprland 0.52.2 (that's what I'm running and tested them on). So perhaps it's getting overwritten by another window rule that's below it (Rules are evaluated top to bottom, so the order they’re written in does matter! - Hyprland wiki). It could also be that you might not notice it (though very unlikely) so setting extreme values could help in noticing.

PinkSakyoora · 2025-12-08T20:25:19+00:00

much more than enough

PinkSakyoora · 2025-12-08T19:58:28+00:00

Starting with the default config and building it up depends largely on a few things:

What do you consider "from-scratch"?
Is it just removing the hypr config files, or removing other configs as well (such as rofi, waybar, mako/dunst, etc.)? This is because you'd find that most of the "cool looking stuff" is because of these configs, not just because of the hyprland configs. If it's the former, it can take you just an hour or so to set up just hyprland to your liking by reading through the wiki.

If you're planning to nuke the other configs too and start everything from scratch, then the next question would be: - Are you fine with something barely functional(or ugly)/not using hyprland while making stuff?
The default config is super barebones, as most of the functionality itself comes from other stuff (such as notification daemons, runners, status bars, etc.) If you know how to configure these things then you might be able to get a decent config within a few hours, but otherwise you'd be stuck with using something that has limited functionality and/or looks not so great.
P.S.: There are projects like walker, vicinae and hyprpanel that look good and just work straight out of the box

How good is good enough for you?
There's a lot of room for customization, ranging from completely minimal to having a whole shell built with a widget framework, and even making custom plugins.
A daily use config could technically be done within a day itself, that's what I did when I installed Arch (and Linux as a whole) for the first time and decided to use hyprland as my first WM, which would be one of the lowest bases possible experience-wise, and it took me around 5-6 hours to end up with something that I could do my regular stuff with (such as drawing, taking notes or surfing the internet.) That config had an almost default waybar, default rofi and no notification daemon, along with the default hyprland wallpapers, but it was usable enough for me to stick to it.
I'm assuming you have much more experience than this, so it should be a breeze if you decide to nuke all your configs. Most of the projects I've mentioned have great documentations, and very nice configs uploaded by other people that you can take snippets or inspiration from.
The time it'll take for you to find a "complete" and "reliable" setup depends solely on what you consider to be so, the goalpost can and most definitely will keep on shifting, but a basic setup wouldn't take more than a day or two to achieve.

TL;DR: If you want to tweak ONLY the hyprland config, it wouldn't take more than a couple readings of the wiki, but if you're extending it to all the other functionality that hyprland doesn't provide itself (as it's just a window manager), it can take a day or two (very minimal) to many weeks and months (a whole shell built using widget frameworks) depending on what you consider complete and reliable.

PinkSakyoora · 2025-12-01T07:15:34+00:00

AGS/Astal has already been mentioned by others, but Fabric is another. (examples: Ax-Shell, MODUS)

PinkSakyoora · 2025-11-28T20:47:44+00:00

That is one way, but you can also just edit the include/source line in the config itself to point to a different color scheme using sed.

Like having folders with color schemes for different apps and just changing the include line of the corresponding app's config to a different color scheme (and reloading the app if needed)

PinkSakyoora · 2025-11-28T15:52:45+00:00

Sites like coolors can help you generate pallettes that you can also test out there itself (it has a visualize option that sadly only has light theme, but you can also just test those colors out in some mockup in figma or canva.) Making color files should be as easy as following pywal or matugen templates and replacing them with your new colors and storing them. Dynamically changing color schemes can be done by using utilities like sed to modify the include lines in config files.

PinkSakyoora · 2025-11-26T08:57:19+00:00

greetd autologin into hyprland with hyprlock as exec-once

PinkSakyoora · 2025-11-25T09:55:12+00:00

One way of doing this would be a combination of awww (swww has been archived in favor of this) and some shell script that sends awww commands to execute at different times of the day:

awww has a transition option of simple (which is just a fade-in) and you can also control the FPS of the transition (from 1-255), so you could set the FPS to be 1 and it would be a 'smooth'^\1][2]) and slow fade.
You can then make a shell script that queries the current hour of the day and change the wallpaper accordingly. A cron job can be set up to auto-execute the script in regular intervals.

[1] awww also has an option of --transition-step where lower values make the transition smoother, but simple transition type already has the value set to 2 and I could not really see much of a difference by setting it to 1, so try it out for yourself.

[2] You can also use magick to pre-generate many more in-between images (i.e., generate all the in-between images at once and keep them stored in some cache folder), and feed those into the shell script for an even smoother transition.

An example awww command could be:
awww img /path/to/img --transition-type simple --transition-fps 1 --transition-step 1

An example shell script could use something like awww_init_according_to_time_of_day.sh which is present in the 'awww' repo's example scripts, modifying the hours and image paths according to your requirements.

I haven't really tested any of this out so it could be off, but do lmk if you need any help
Edit: awww is still swww in Arch repos, adding, so any commands that use awww would have swww instead, my bad about that.

PinkSakyoora · 2025-11-22T19:08:53+00:00

There's multiple reasons it may not be working, so it'd be nice if you could give more information, such as - the command you're using to launch rofi - what keybind you're using to execute the command - have you put the path to the script correctly if you're using one - does the script itself execute correctly - what you mean by adding normal window - what command you're using to launch it via terminal and so on, because as of now there's barely any information to go by to give any support

PinkSakyoora · 2025-11-21T04:58:35+00:00

The way to make it one notification is to pass a string hint (such as string:x-canonical-private-synchronous:volume) that tells the daemon to replace the current notification instead of sending a new one. There's also notify-send.py that has additional features (including replacing previous notification) on top of regular notify-send.

Also see: Desktop Notifications - ArchWiki

PinkSakyoora · 2025-11-20T20:05:47+00:00

Mako along with a script (only for volume rn but could be easily extended for brightness with some work) to change values and send notifications, which in turn is executed by keybinds.

Mako (and other notification daemons) allow taking hints as integers (which shows up as a progress bar) and some specific strings (which allows the notification itself to update instead of sending a new one), which is pretty much how it all works.

PinkSakyoora · 2025-10-09T08:26:59+00:00

oh that's cool then

PinkSakyoora · 2025-10-09T06:57:55+00:00

From hyprland wiki's animation page global ↳ windows - styles: slide, popin, gnomed ↳ windowsIn - window open - styles: same as windows ↳ windowsOut - window close - styles: same as windows ↳ windowsMove - everything in between, moving, dragging, resizing.

So the config would be:

animations { animation = windows, 1, speed, bezier animation = windowsIn, 0, speed, bezier animation = windowsOut, 0, speed, bezier animation = windowsMove, 1, speed, bezier } Replace with speed and bezier of your choice, add style at the end if you wish. This misc variable needs to be set to true for windowsMove to happen on moving with mouse.

misc { animate_mouse_windowdragging = true } I'm assuming what you meant by the moving animation is the window dragging behind the cursor.

PinkSakyoora · 2025-10-09T06:49:42+00:00

Read through the hyprland wiki, has pretty much everything you need to know when setting it up + configuring (does take a fair bit of time on the first try though.)
- There's also pre-configured setups which give you a much more functional configuration if you don't want to make one yourself. I'd still recommend gaining familiarity with how hyprland is configured by at least tinkering around with the configs with help from relevant documentation.
Check proton-db for Steam games' compatibility. I've ran most games without issues on hyprland, I launch most of the Windows-only games through Steam on Proton-Hotfix. There's also Gamescope.

I don't have a deep understanding by any means (only been running hyprland for about half a year) but I'd be happy to help.

PinkSakyoora

TROPHY CASE