From 880a5efec2fd25c83372a62451e359af9cc7b485 Mon Sep 17 00:00:00 2001 From: alterNERDtive Date: Thu, 2 Nov 2023 17:37:17 +0100 Subject: [PATCH] more mumbo jumbo --- README.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/README.md b/README.md index 0046f31..25ece32 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,20 @@ chosen randomly from the configuration file. That’s it. Nothing fancy. +## Why Should I Use This? + +Eh, you don’t have to. I was looking for a way to change my wallpaper at set +intervals that + +* supported multi-monitor setups properly, +* didn’t reinvent the wallpaper wheel, instead used `swaybg` in the background, +* integrated nicely with systemd (which I use to run _all_ my desktop related + things) and +* just worked. + +That didn’t seem to exist, so I made it. And since I’m _probably_ not the only +one looking for it, here it is. Have fun! + ## How Does It Work? 1. Copy `backgrounds.example.json` to `~/config/sway/backgrounds.json`. @@ -28,6 +42,16 @@ to do it “right”, set up some `sway-session.target` and a dropin config for service that binds it to that, then have sway run the target on startup. If you want to do it in any other way, go ahead! +## Known Issues + +Since I have hacked this in a couple h from concept to “eh, works well enough”, +it is not very resilient. You mess up the timer/service, you have syntax errors +in your configuration file … it will just die instead of spawning a `swaybg` +process. + +On the plus side, you’ll notice when it doesn’t work. Since, you know, you don’t +get your wallpapers. + ## How Do I Get Rid Of It? You could just disable the timer.