From: zimoun <zimon.toutoune@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Erlang + Emacs profile
Date: Mon, 29 Jun 2020 10:50:03 +0200 [thread overview]
Message-ID: <86sgeeb6is.fsf@gmail.com> (raw)
In-Reply-To: <8211be1b-21d0-36bb-c89d-a92581af594a@posteo.de>
Dear,
On Thu, 25 Jun 2020 at 21:25, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> * It requires keeping multiple Emacs on my system. How will they
> interact with the same ~/.emacs.d/.init.el?
Emacs reads init.el when it starts so yes all Emacs will interact with
this file if you do not specify explicitly to not do it. Well, if you
use 'with-eval-after-load' in your Emacs configuration files, it should
not be a problem. Otherwise give a look at "emacs-guix" or try "emacs -q
-l /path/to/your/specific/config.el", as Maxim pointed.
> How did you package emacs-ob-erlang? (I did not yet package a single
> package for Guix, so I assume no prior knowledge.) Or is it a rather
> lengthy procedure to do so? I think this might be one of the next things
> I learn about Guix, which is very useful, because if a package is
> missing, one can add it oneself, without having to rely on others to add it.
For this specific package, I do not know because I have not checked but
the first step when a package is not in Guix is: try the importer! :-)
guix import elpa -a melpa -r foo
where foo is the name of package in MELPA. This works very well.
> I usually install Emacs packages inside Emacs, instead of using Guix for
> it. I do this, because probably not all packages I want are available in
> Guix, but I have not checked this assumption at all.
I did that (installing with 'use-package') too but then I switched all
to manifest.scm file and 'with-eval-after-load' tracking channels.scm
(guix describe -f channels). This way, I have a working setup
everywhere and everytime. Anyway! :-)
The point is that Guix has a really large collection of Emacs packages:
--8<---------------cut here---------------start------------->8---
$ du -sh gnu/packages/*.scm | sort -nr | head -n5
908K gnu/packages/crates-io.scm
884K gnu/packages/emacs-xyz.scm
784K gnu/packages/cran.scm
732K gnu/packages/python-xyz.scm
636K gnu/packages/bioinformatics.scm
--8<---------------cut here---------------end--------------->8---
and if your needs is not there then "guix import elpa" eases the task
for adding it. :-)
All the best,
simon
next prev parent reply other threads:[~2020-06-29 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 22:49 Erlang + Emacs profile Zelphir Kaltstahl
2020-06-24 20:29 ` Maxim Cournoyer
2020-06-25 19:25 ` Zelphir Kaltstahl
2020-06-28 4:41 ` Maxim Cournoyer
2020-06-29 8:50 ` zimoun [this message]
2020-06-29 19:37 ` Zelphir Kaltstahl
2020-06-29 20:24 ` Ricardo Wurmus
2020-06-29 20:37 ` Zelphir Kaltstahl
2020-06-29 20:49 ` zimoun
2020-06-29 21:12 ` Zelphir Kaltstahl
2020-06-29 22:08 ` zimoun
2020-06-29 20:26 ` Zelphir Kaltstahl
2020-06-30 18:34 ` Zelphir Kaltstahl
2020-06-30 18:41 ` Zelphir Kaltstahl
2020-07-06 3:50 ` Maxim Cournoyer
2020-07-07 10:23 ` Zelphir Kaltstahl
2020-07-07 15:55 ` Maxim Cournoyer
2020-07-16 21:34 ` Zelphir Kaltstahl
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=86sgeeb6is.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zelphirkaltstahl@posteo.de \
/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).