宋文武 <address@hidden> skribis: [...] Please make it a top-level procedure, for clarity. I think you should add a ‘match’ case here, for when (read port) returns something that is not a ‘pa
Can some of you share their .emacs config file? I am especially interested in the guix hacks. Do you pick up the load-path dynamically? What packages are in your list? Thanks, Pj. --
After commits 004ea62 and <FIXME commit after updating guix-devel guix code without additional hacks, which can be removed now. * gnu/system.scm (emacs-site-file, emacs-site-directory): Remove. (oper
Alex Kost <address@hidden> skribis: [...] Maybe: “Return the list of directories under PROFILE that contain Emacs packages. This includes both `share/emacs/site-lisp/guix.d/PACKAGE' sub-directories
After commit 13fe4891fa247d306e203ee14c6886513bd86b52, Emacs package includes "site-start.el", and it has a priority over "/etc/emacs/site-start.el" on GuixSD because "/etc/emacs" is added to the end
Or even better, move the code for auto-loading emacs packages from "guix-init.el" to "guix-emacs.el", so "site-start.el" will consist of a single line: (require 'guix-emacs). Great, thanks! I have se
Fine with me. I don't have preferences on this. If you want, feel free to modify and push my patch as needed. At the moment your patches do not apply on my checkout (I'm behind master by a few weeks)
[...] Ah, now I see what you mean, thanks! And emacs can be started with "--no-site-file" so my concerns about avoiding this are fulfilled. For simplicity, we can even add "site-start.el" to the guix
That's the easy part. Once we know how to load a minimal version of your code, we add it to 'site-start.el'. Emacs automatically loads it. I've done this, but it doesn't load as 'guix-config' is miss
Hm, OK, so your "proof of concept patch" will have the same problem. Could you please answer <http://lists.gnu.org/archive/html/guix-devel/2016-01/msg00021.html>, as I still don't understand how your
Not for me! As a user, I always want to have pure upstream packages if possible, without unnecessary modifications made by package maintainers. Such modifications have an intention to make users life
Federico Beffa <address@hidden> skribis: Indeed, I think it would be too much. Yeah. Alex, any idea how to add the guix.d subdirectories to the search path without duplicating all of guix.el in the
Attached is a proof of concept patch showing one way to do it. If you don't want to add the full 'guix.el', then we should definitely add code in a similar way to instruct emacs to look in the right
No ideas. I also think we should mention Emacs packages in the manual. What about the attached patch? Attachment: 0001-doc-Describe-how-to-configure-Emacs-packages.patch Description: Text Data
Federico Beffa <address@hidden> skribis: I don’t see how to make that happen automatically on foreign distros. Any ideas? We still have the option of making it more prominent in the documentation,