-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on startup: Unbound variable: %max-returned-list-size #21
Comments
This variable ( Maybe the problem is that compiled (.go) files are from the previous version. Could you switch to Also you may try to remove |
Yes, I use Guix from MELPA. Note that I did not update the Guix package manager (no Both load paths point to the same store items. How to reprocude:
I can repeat the above process ad infinitum. More general question: Is it possible to skip Guix-managed packages when updating all packages from the |
OK, but do you have some other version of Emacs-Guix installed otherwise (with Guix, for example)? If you install it from MELPA, then .scm files are not compiled, but it looks like Guile still finds the compiled (.go) files from another version and loads them, so there is this conflict between .scm and .go files.
This shouldn't matter.
Could you show the values of these variables?
Sorry, I cannot reproduce, I use Emacs-Guix from the git checkout and it works fine for me. My guess is that there is a mismatch between .scm and .go files somewhere.
I think there is no easy way but since this 'list-package' machinery is just the elisp code, you can probably make your workaround. BTW I have the same plan (and I do nothing on implementing it 😄): I install 16 emacs packages with Guix and several dozens from melpa (quelpa rather), and I have never experienced any conflicts using this approach. |
Right, I had two version installed: one from MELPA, one from Guix. I've
removed the one from Guix for the time being (I'll switch to fully
Guix-managed Emacs packages later).
After removing the emacs-guix package from Guix, removing the cache and
re-logging, everything went back to normal!
I think you should document this in the info file and the package description.
|
Suggested by Pierre Neidhardt: <#21 (comment)>. * README: Mention potential problems with .scm and .go files. * doc/emacs-guix.texi (Installation): Likewise.
I have mentioned it in the manual and README (commit 2d16d16). Thanks! As for the package description of the |
The first time I run a guix command, I get the following error:
Running the command again works though.
The text was updated successfully, but these errors were encountered: