unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: help-guix@gnu.org
Subject: Emacs use-package: Guix backend?
Date: Sat, 19 Dec 2020 10:42:51 +0100	[thread overview]
Message-ID: <87h7oim8ro.fsf@elephly.net> (raw)

Hi Guix,

I recently moved all my Emacs packages to a separate profile, which is
controlled by a manifest that’s generated from my init.org configuration
file.  I like this, because I can separately upgrade packages from my
main profile and keep my Emacs configuration self-contained.

What still annoys me, though, is that package installation is separate
from configuration.  I don’t really want to be forced to update the
manifest at the top of my init.org before I can configure the package
somewhere at the bottom of the init.org.

The “use-package” macro was designed to allow for both installation and
configuration in the same place.  By default it uses package.el to
install packages when they aren’t available yet.  I’d like to use
“use-package”, but I’d like it to install packages with Guix and also
install to a separate Guix profile, preferably via a manifest.

Package managers are supposed to override “use-package-ensure-function”
and/or “use-package-pre-ensure-function” to use something other than
package.el.

Before I embark on this journey, do any of you have travel reports to
share?  Do you think this is worth doing?  If so, where could we add
this feature so that all Guix users benefit from it?  Emacs-Guix?

-- 
Ricardo


             reply	other threads:[~2020-12-19  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  9:42 Ricardo Wurmus [this message]
2020-12-20  0:10 ` Emacs use-package: Guix backend? Fredrik Salomonsson
2020-12-20  7:24 ` zimoun
  -- strict thread matches above, loose matches on Subject: below --
2021-01-01  4:03 John Soo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7oim8ro.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).