unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Howto run guix.el correctly?
Date: Wed, 26 Nov 2014 23:14:17 +0300	[thread overview]
Message-ID: <87lhmxu3c6.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1411222152540.10197@sandbox.cz> (Adam Pribyl's message of "Sat, 22 Nov 2014 22:04:44 +0100 (CET)")

Adam Pribyl (2014-11-23 00:04 +0300) wrote:

> On Sat, 22 Nov 2014, Alex Kost wrote:
>
>> Adam Pribyl (2014-11-22 01:28 +0300) wrote:
>>
>>> I have folloed the instruction in
>>> http://www.gnu.org/software/guix/manual/guix.html#Emacs-Interface
>>> to get the emacs interface for guix, but there is something missing
>>> probably.
>>>
>>> Installation of emacs and geiser was OK, I changed the path to guix.el
>>> (there is no /usr/share/ in my guix installation, I had to find guix.el
>>> in the /gnu/store), after that I can start emacs and "M-x guix-..." but
>>> every action says "Cannot open load file: no such file or directory
>>> geiser-mode".
>>
>> If you mean you did (add-to-list 'load-path "/gnu/store/..."), then it's
>> definitely not right.
>>
>>> There should probably be also the geiser path in the emacs init file or
>>> something?
>>
>> I assume you use a Guix (or GNU or whatever it should be called)
>> system.  I must admit I have not tried it yet, and all I know about
>> setting "guix.el" there I learnt from a chat with davexunit on #guix
>> today.
>>
>> So I think the following should be added to your emacs config:
>>
>> - Add dirs with "guix.el" and "geiser" to load-path (I'm absolutely
>>  not sure about the correctness of the paths, so double check please):
>>
>>  (add-to-list 'load-path "/run/current-system/profile/share/emacs/site-lisp/")
>>  (add-to-list 'load-path "~/.guix-profile/share/emacs/site-lisp")
>>
>> - Initial setup of geiser:
>>
>>  (require 'geiser-install)
>>
>> - Initial setup of guix:
>>
>>  (require 'guix-init)
>
> Right, I am testing it under GNU system (USB installed image with guix
> 0.8). Thanks for the point regarding geiser. This is now my ~/.emacs
>
> (add-to-list 'load-path
> "/gnu/store/ysh4fvnxr0p8xrphcikivpafgvf6g18m-guix-0.8/share/emacs/site-lisp/")
> (add-to-list 'load-path "~/.guix-profile/share/emacs/site-lisp")
> (require 'geiser-install)
> (require 'guix-init)
>
> Reason for the /gnu/store path is, that guix.el is a part of guix and I
> did not found it in any profile. I've added my profile path, where the
> geiser is (as it is installed by this user), but the /run/current-system
> has no share/emacs at all. I do not know why.

Did you check the right path?  It's
"/run/current-system/profile/share/emacs...", not
"/run/current-system/share/emacs/..."

> While I got further, it is still somewhat confused as invoking
> guix-all-available-packages results in error in process sentinel: Text
> is read-only
> No prompt found!

Thanks Adam and David for reporting.  You encouraged me to install the
system (at last).  So the problem was that a default directory with guix
scheme files was not added to the %load-path (it is fixed with commit
cbbc877).  As a workaround you may perform "guix pull" – after that the
REPL should start without errors.

So to recap, to make "guix.el" work in the current system one should do
the following:

1. "guix pull" to populate "~/.config/guix/latest"  (this step will not
   be required for the future releases)

2. Install geiser: "guix package -i geiser"

3. Setup geiser  (hopefully this step will not be required soon)
   Put in your emacs config:

   (add-to-list 'load-path "~/.guix-profile/share/emacs/site-lisp")
   (require 'geiser-install)

4. Setup "guix.el".  Put in your emacs config:

   (add-to-list 'load-path "<path-to-a-directory-with-guix.el>")
   (require 'guix-init)

I appreciate if someone confirm that the above works (or doesn't work :-)).

-- 
Alex

  parent reply	other threads:[~2014-11-26 20:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 22:28 Howto run guix.el correctly? Adam Pribyl
2014-11-22  8:03 ` Alex Kost
2014-11-22 10:52   ` Ludovic Courtès
2014-11-22 12:04     ` Alex Kost
2014-11-22 18:49 ` Alex Kost
2014-11-22 21:04   ` Adam Pribyl
2014-11-22 21:11     ` David Thompson
2014-11-22 22:17       ` Ludovic Courtès
2014-11-23  7:01         ` Alex Kost
2014-11-24 20:42           ` Ludovic Courtès
2014-11-25 13:58             ` Alex Kost
2014-11-26 16:23               ` Ludovic Courtès
2014-11-26 20:38                 ` Alex Kost
2014-11-26 22:41                   ` Ludovic Courtès
2014-12-01 12:20                     ` Alex Kost
2014-12-01 12:49                       ` Ludovic Courtès
2014-12-02  7:46                         ` Alex Kost
2014-12-02  8:39                           ` Ludovic Courtès
2014-12-02 19:13                             ` Alex Kost
2014-11-26 20:14     ` Alex Kost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-01 17:15 Federico Beffa
2014-12-02  7:52 ` 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=87lhmxu3c6.fsf@gmail.com \
    --to=alezost@gmail.com \
    --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).