From: EuAndreh via <help-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <Help-Guix@gnu.org>, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: Guix as a package manager for Emacs
Date: Tue, 28 Jan 2020 12:34:36 -0300 [thread overview]
Message-ID: <87ftfzzjar.fsf@euandre.org> (raw)
In-Reply-To: <CAJ3okZ3kDVFmt7+7aMtxP6Uk8dbjFk9R0-50XLK1Fw2ayaR1yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> The easiest way to achieve similar is to use a manifest file, IMHO.
>
> Let consider the file below named '/tmp/my-emacs-config.scm', then it
> is easy to create a profile (or environment):
>
> guix package -m /tmp/my-emacs-config.scm -p /tmp/my-profile
>
> and the Emacs living in this very profile should be correctly setup-ed
> for your needs. Therefore let source the profile or whatever and done.
> :-)
At first I though guix would install the packages, but Emacs would be
unable to look them up on the store. I didn't realize the final profile
would setup Emacs to correctly look them up.
So I was missing an 'emacsWithPackage' tool that would do that binding,
but it doesn't actually seem necessary.
Using a manifest seems a good solution, I'll try it out.
Thanks for the code snippet too. Hopefull I'll get it working and
write/blog about it.
:)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-28 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 4:09 Guix as a package manager for Emacs EuAndreh via
2020-01-22 9:43 ` Pierre Neidhardt
2020-01-22 11:47 ` EuAndreh via
2020-01-22 14:14 ` zimoun
2020-01-22 14:17 ` zimoun
2020-01-22 15:11 ` John Soo
2020-01-23 15:26 ` zimoun
2020-01-28 15:32 ` EuAndreh via
2020-01-28 15:34 ` EuAndreh via [this message]
2020-01-23 15:23 ` zimoun
2020-01-28 15:22 ` EuAndreh via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftfzzjar.fsf@euandre.org \
--to=help-guix@gnu.org \
--cc=eu@euandre.org \
--cc=mail@ambrevar.xyz \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.