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
