From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Emacs load path
Date: Wed, 06 Jan 2016 19:56:56 +0300 [thread overview]
Message-ID: <87mvsi4pev.fsf@gmail.com> (raw)
In-Reply-To: CAKrPhPM+AsZoxmeEvQjNQEk-o0jpV_Nd0mUx=sdy_MFrgvVS+Q@mail.gmail.com
Federico Beffa (2016-01-05 16:21 +0300) wrote:
> On Tue, Jan 5, 2016 at 10:40 AM, Alex Kost <alezost@gmail.com> wrote:
>>>> Returning to 'guix-config' problem, we can make a "soft" dependency on
>>>> 'guix-profiles' (see the attached patch), so the only file needed for
>>>> finding emacs packages in "guix.d" will be "guix-emacs.el". And the
>>>> code that should be loaded by Emacs to find guix emacs packages will be:
>>>>
>>>> (when (require 'guix-emacs nil t)
>>>> (add-to-list 'load-path (guix-emacs-directory))
>>>> (guix-emacs-load-autoloads))
>>>
>>> I've done this, but it doesn't load as 'guix-config' is missing. I
>>> guess it needs your patch which I didn't try.
>>
>> Yes, it meant to be used with the patch.
>>
>> So IIUC we need the following patches to make our Emacs find packages in
>> a user profile:
>>
>> - patch for stripping "guix-emacs.el" from extra dependencies (attached
>> to the previous message);
>>
>> - patch for adding "site-start.el" (attached to this message);
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).
>> - modified version of your patch to copy "site-start.el" and
>> "guix-emacs.el" to the proper places.
>>
>
> If you want, feel free to modify and push my patch as needed.
Great, thanks! I have sent a final patchset (including a modified
version of your patch) to improve our Emacs so it should find guix
packages out of the box.
--
Alex
next prev parent reply other threads:[~2016-01-06 16:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 22:16 Emacs load path (was: Re: Multiple versions) Federico Beffa
2015-12-28 22:15 ` Emacs load path Alex Kost
2015-12-29 0:30 ` Taylan Ulrich Bayırlı/Kammer
2015-12-30 12:16 ` Federico Beffa
2015-12-30 18:55 ` Alex Kost
2015-12-30 22:18 ` Federico Beffa
2015-12-31 9:02 ` Alex Kost
2015-12-31 9:27 ` Federico Beffa
2015-12-31 20:45 ` Alex Kost
2015-12-30 16:29 ` Ludovic Courtès
2015-12-30 16:55 ` Federico Beffa
2016-01-01 14:25 ` Federico Beffa
2016-01-01 15:22 ` Ludovic Courtès
2016-01-01 16:28 ` Alex Kost
2016-01-01 16:53 ` Federico Beffa
2016-01-02 14:13 ` Alex Kost
2016-01-04 10:18 ` Federico Beffa
2016-01-05 9:40 ` Alex Kost
2016-01-05 13:21 ` Federico Beffa
2016-01-06 16:56 ` Alex Kost [this message]
2016-01-01 16:28 ` Alex Kost
2015-12-31 22:47 ` Alex Kost
2016-01-01 15:24 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2015-12-26 23:02 Multiple versions Dmitry Bogatov
2015-12-27 14:11 ` Alex Kost
2015-12-27 16:47 ` Emacs load path (was: Re: Multiple versions) Dmitry Bogatov
2015-12-27 21:42 ` Emacs load path Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvsi4pev.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).