more mumbo jumbo

This commit is contained in:
alterNERDtive 2023-11-02 17:37:17 +01:00
parent ddd877f73e
commit 880a5efec2
Signed by: alterNERDtive
GPG key ID: 547787A4FE6533F1

View file

@ -9,6 +9,20 @@ chosen randomly from the configuration file.
Thats it. Nothing fancy. Thats it. Nothing fancy.
## Why Should I Use This?
Eh, you dont have to. I was looking for a way to change my wallpaper at set
intervals that
* supported multi-monitor setups properly,
* didnt 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 didnt seem to exist, so I made it. And since Im _probably_ not the only
one looking for it, here it is. Have fun!
## How Does It Work? ## How Does It Work?
1. Copy `backgrounds.example.json` to `~/config/sway/backgrounds.json`. 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 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! 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, youll notice when it doesnt work. Since, you know, you dont
get your wallpapers.
## How Do I Get Rid Of It? ## How Do I Get Rid Of It?
You could just disable the timer. You could just disable the timer.