~ruther/guix-config

ref: d57a2f44488ce323ed4943407fff99d7ba535ed3 guix-config/home d---------
d57a2f44 — Rutherther a year ago
chore: remove (ruther home fonts)

Already in guix.
c2467e5a — Rutherther 1 year, 1 month ago
feat: Add emacs from emacs-branch via inferiors
819ee341 — Rutherther 1 year, 1 month ago
chore: update
feat: add xdg data dirs env var to dwl wrapper profile
chore: move my dwl repo
feat: use spotify from flatpak in dwl
fix: stop wlr-services if running on dwl startup

When wlr-services services are running already from previous session,
ie. after a logout or a crash, they couldn't be started again, 1.
because wlr-services has been running still, it needs to be stopped
first, 2. because the services got disabled cause they crashed with no
possibility to connect to wayland display 5 times.

The point 1. is fixed by this commit, 2. is fixed in guix-exprs
feat: dmenu-wl -> mew
feat: add flatpak env
feat: install ykman
feat: start wlr-services with display variable
fix: custom waybar should keep upstream patches
feat: add flatpak
chore: new monitor setup
fix: add zathura pdf support
fix: waybar config icons for brightness, rewrite titles
feat: add syncthing
fix: commit missing encoding patch
feat: move to more robust solution than time-machine

The problem with time-machine is that the guix
derivation might need to be recomputed and rebuilt.
This can happen because the underlying guix version used
to build it can differ. The solution to this can be
to keep the resulting guix in a folder, and use it out of
that folder, instead of recomputing it every time.

This can still mean that there will be need for
duplicit recomputation between building the guix
and pulling it into user profile. I don't know what
a good solution to this is, yet.
feat: expand cache ttl for cron
Next