From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Emacs-guix: variable is void: guix-current-profile
Date: Thu, 3 Jan 2019 18:54:08 +0100 [thread overview]
Message-ID: <CAJ3okZ25jPg-ashELVquZB-ojd-aU2hU_enWTy-pqbdxOgiCxQ@mail.gmail.com> (raw)
In-Reply-To: <87pntdc2er.fsf@ambrevar.xyz>
Dear Pierre,
> > If I install the non-elisp requirements with Guix then emacs-guix from
> > MELPA, it should work the same, isn't it?
>
> No, because the MELPA version and the Guix version are not the same and the
> requirements might be different.
Ok, I naively assumed that they were synced.
My bad.
A quick check proves me that they are not. :-)
Well, it does not solve the issue.
The emacs-guix popup installed with Guix does not work, neither.
clean ~/.emacs.d
clean ~/.cache
guix package -i emacs-guix
emacs # version 26.1
M-x guix
Then there is issue with the menu. For example the letter p is binded
to processes and also to package.
But it is another story. :-)
> Emacs package management is rather simple while Guix gives you much more power,
> including reproducibility. If you install everything from Guix, it gives you a
> fairly strong guarantee that things will work out of the box.
Yes for sure. :-)
But when I install ELisp packages with MELPA, then I can easily modify
on-the-fly the code of some function, e.g., change the docstring or
add message or whatever.
Easily because I am just doing `M-x find-function foo' then I edit
`foo' as I want.
When installed with Guix, it is not "so easy" because the ELisp
package lives in the store and it is not a good idea to modify it. So
I need to extract the function, etc.
That's why I prefer MELPA for emacs packages than Guix (or Debian or
whatever) package management. :-)
Thank you for your explanations.
All the best,
simon
next prev parent reply other threads:[~2019-01-03 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 15:34 Emacs-guix: variable is void: guix-current-profile zimoun
2019-01-03 11:26 ` Pierre Neidhardt
2019-01-03 12:22 ` zimoun
2019-01-03 13:10 ` Pierre Neidhardt
2019-01-03 17:54 ` zimoun [this message]
2019-01-03 18:10 ` Alex Kost
2019-01-03 21:58 ` zimoun
2019-01-04 20:20 ` Alex Kost
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=CAJ3okZ25jPg-ashELVquZB-ojd-aU2hU_enWTy-pqbdxOgiCxQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).