Say how to take a newer default, since seeding will not

Seeding never overwrites, which is the right contract and also means an
upgrade that improves a shipped default never reaches anyone who already
has that file. Both machines this was tested on keep the old autostart
line that waits for awww in an unbounded loop, and nothing will ever
replace it for them.

That is a trade worth making and not one worth hiding, so document the
way out: diff against the skeleton, then copy if you want it.
This commit is contained in:
2026-08-11 19:11:47 +07:00
parent e006e95e55
commit 06f974f09f
+10
View File
@@ -172,6 +172,16 @@ things follow: your edits survive every login and upgrade, and deleting a file
is how you ask for the default back. `~/.cache/hyprcosmic/session.log` records is how you ask for the default back. `~/.cache/hyprcosmic/session.log` records
what was seeded. what was seeded.
The cost of that is real and worth stating: an upgrade that improves a shipped
default will not reach a file you already have. If a release changes something
you want — the `autostart` line that sets the wallpaper did change once — take
it deliberately, after reading what you would lose:
```shell
diff -u ~/.config/hyprcosmic/autostart /usr/share/hyprcosmic/skel/hyprcosmic/autostart
cp /usr/share/hyprcosmic/skel/hyprcosmic/autostart ~/.config/hyprcosmic/
```
`autostart` is the one that matters most, because it is what starts waybar, the `autostart` is the one that matters most, because it is what starts waybar, the
wallpaper daemon and `hyprcosmic-conf watch`. Until the session seeded it, a wallpaper daemon and `hyprcosmic-conf watch`. Until the session seeded it, a
machine that had never run HyprCosmic logged in to a bare compositor: running, machine that had never run HyprCosmic logged in to a bare compositor: running,