Email or username:

Password:

Forgot your password?
blake shaw 🇵🇸

When I first go into #guix, I experimented with every little thing. Now I only change my configuration every three months or so, while for anything else I just use guix shell. And my system remains solid and predictable, with no weird state and quick environment variable tweeks building up leading to library collisions etc that can come to haunt you at a moments notice. Just my studio, as I designed it to be.

3 comments
blake shaw 🇵🇸

This has meant that I havent contributed much in a while. But I'm honestly not the type to try out the newest software as its released. Everything I need is packaged in guix already. And of all the things I've packaged, I never started actually using any of them lol. So I'm kind of glad I didn't submit them upstream, because im not sure if we really need to include any packages that noone is using.

Andres Moreno

@rml

How do you manage your Emacs packages? Do you have a core set under your profile and then load others on demand via Guix shell?

Or do you have a manifest that you use for each project as needed?

I declared Emacs bankruptcy and am considering moving to Guix and starting from scratch.

Suggestions welcome

blake shaw 🇵🇸

@monkey1

I use #rde to declare my entire init.el within my home-configuration.scm. it's not the most efficient (probably because I don't take advantage of any of the rde-specific features that provide greater feature modularity), but it's fun to have your entire personal computing setup in a single emacs-style file:
git.sr.ht/~reproducible/.guix/

Go Up