From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/7] Add "guix-devel-…" commands.
Date: Tue, 25 Aug 2015 22:59:59 +0200 [thread overview]
Message-ID: <878u8zhynk.fsf@gnu.org> (raw)
In-Reply-To: <87bne32egh.fsf@gmail.com> (Alex Kost's message of "Wed, 19 Aug 2015 23:47:10 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2015-08-18 16:50 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> And finally, I'm afraid building guix package in a Geiser REPL may not
>>> be very useful because of <https://github.com/jaor/geiser/issues/28>
>>> (you have wait for the REPL command to be finished before continuing to
>>> edit .scm-file).
>>
>> Bummer, indeed. I wonder if that could be worked around by spawning a
>> new Guile server thread that would be used to build the package, and
>> opening a new Geiser REPL connected to that thread? Maybe too complex,
>> though.
>
> That's what I did for *Guix REPL*: it is a server by default, and there
> is *Guix Internal REPL* which connects to it (there is a commentary
> about it in "emacs/guix-backend.el").
>
> But I don't think it should be done here: as a user I expect that the
> building will be performed in the current Geiser REPL, so it's up to me
> (as a user) to decide what repl it is.
>
> Also to avoid that limitation, a user can just run another Geiser REPL
> after the building begins, and can continue to edit a scheme file with
> the help of the current REPL, while the building will continue in the
> previous one. (I will mention this in the manual)
OK, sounds good!
Ludo’.
next prev parent reply other threads:[~2015-08-25 21:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 8:49 [PATCH 0/7] Add "guix-devel-…" commands Alex Kost
2015-07-25 8:49 ` [PATCH 1/7] emacs: Move guile related code to "guix-guile.el" Alex Kost
2015-08-18 13:50 ` Ludovic Courtès
2015-08-18 13:51 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 2/7] emacs: Move code for evaluating to "guix-geiser.el" Alex Kost
2015-08-18 13:52 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 3/7] emacs: Add code to call guile procedures Alex Kost
2015-08-18 13:52 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 4/7] emacs: Add 'guix-devel-use-current-module' Alex Kost
2015-07-25 18:51 ` Mathieu Lirzin
2015-07-26 8:29 ` Alex Kost
2015-07-26 14:00 ` Mathieu Lirzin
2015-07-26 18:11 ` Alex Kost
2015-07-28 9:19 ` Mathieu Lirzin
2015-08-18 14:05 ` Ludovic Courtès
2015-08-19 20:47 ` Alex Kost
2015-08-26 11:07 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 5/7] ui: Add 'show-derivation-outputs' Alex Kost
2015-08-18 14:07 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 6/7] guix build: Add 'build-package' Alex Kost
2015-08-18 14:15 ` Ludovic Courtès
2015-08-19 20:50 ` Alex Kost
2015-08-26 11:12 ` Ludovic Courtès
2015-08-26 17:44 ` Alex Kost
2015-08-28 9:24 ` Ludovic Courtès
2015-09-06 9:03 ` Alex Kost
2015-09-06 9:32 ` Alex Kost
2015-09-08 19:59 ` Ludovic Courtès
2015-09-08 20:10 ` Ludovic Courtès
2015-09-10 10:25 ` [PATCH] Add (guix scripts) Alex Kost
2015-09-14 13:34 ` Ludovic Courtès
2015-09-14 18:39 ` Alex Kost
2015-09-16 20:21 ` Ludovic Courtès
2015-09-18 18:52 ` Alex Kost
2015-09-18 18:51 ` [PATCH 6/7] guix build: Add 'build-package' Alex Kost
2015-09-22 15:12 ` Ludovic Courtès
2015-09-22 19:10 ` Alex Kost
2015-09-22 21:39 ` Ludovic Courtès
2015-07-25 8:49 ` [PATCH 7/7] emacs: Add 'guix-devel-use-current-module' Alex Kost
2015-08-18 14:17 ` Ludovic Courtès
2015-08-19 20:51 ` [PATCH 7/7] emacs: Add 'guix-devel-build-current-package-definition' Alex Kost
2015-08-26 11:14 ` Ludovic Courtès
2015-09-22 19:10 ` [PATCH 1/2] emacs: Add development utils Alex Kost
2015-09-22 21:44 ` Ludovic Courtès
2015-08-18 13:50 ` [PATCH 0/7] Add "guix-devel-…" commands Ludovic Courtès
2015-08-19 20:47 ` Alex Kost
2015-08-25 20:59 ` Ludovic Courtès [this message]
2015-09-22 19:11 ` [PATCH 2/2] emacs: Add 'guix-devel-build-package-definition' Alex Kost
2015-09-22 21:47 ` Ludovic Courtès
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=878u8zhynk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=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).