Hello ! I'm not sure what the problem is with this particular package, but: guix environment emacs-commander
will create an env with all you need to BUILD emacs-commander while guix environment --ad-hoc emacs-commander will create an env in which emacs-commander is installed. Now, if guix environment --ad-hoc emacs-commander doesnt work, it may mean that one of the native-input of emacs-commander should be an input or a propagated-input instead. That would explain why guix environment emacs-commander --ad-hoc emacs-commander works: because it installs this native-input in the env as well. I hope this makes sense, if not please ask away. Cheers, Edouard. jgart <jg...@dismail.de> writes: > Hi, > > I'm trying to use emacs-commander with guix environment on a foreign distro. > > I'm only able to properly source the library into the environment if I run > the following: > > `guix environment emacs-commander --ad-hoc emacs-commander` > > Why do I have to provide emacs-commander twice to the environment command? > > I tested only using --ad-hoc or without and none of those work. > > I'm only able to properly source emacs-commander when I include it twice as in > the above command. > > Could someone explain the reason for this to me? > > Any help is much appreciated. > > all best, > > jgart > > https://github.com/rejeep/commander.el > > 3B1D 7F19 E36B B60C 0F5B 2CA9 A52A A2B4 77B6 DD35
