Hello,
answering to both in one email, since the question are in the same direction. Rutherther <ruthert...@ditigal.xyz> writes: > Hi Tomas, > > You probably need to add guile-geiser to the shell as well, to add the geiser > guile package in the corresponding search path. Possibly also other geiser > related packages. Cant check if this will resolve the issue completely now, > though. > > Rutherther Noé Lopez <n...@xn--no-cja.eu> writes: > Hi Thomas, > > What’s in manifest.scm? > I do not have emacs-geiser-guile package in the manifest, and I do not have it on the command line neither, however I am not sure it would help. Even ignoring the fact that I have Geiser with some transformations, so installing it via command line would not help, there is also a second problem. My Emacs is usually long running, and I guix-pull fairly regularly. So I am not sure how to prevent the version mismatch of Geiser between what Emacs has and what would be installed into the container. I assume the geiser-guile-scheme-dir could be a key, but not sure how to use it effectively. I mean, exposing the whole store is a workable solution, I have just hoped there is something more elegant I could do. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
