all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Yagnesh Raghava Yakkala <hi@yagnesh.org>
Cc: guix-devel@gnu.org
Subject: Re: [GSoC] Emacs UI for Guix
Date: Thu, 27 Feb 2014 14:33:20 +0100	[thread overview]
Message-ID: <87txbkbrz3.fsf@gnu.org> (raw)
In-Reply-To: <87d2iedgwo.fsf@yagnesh.org> (Yagnesh Raghava Yakkala's message of "Sun, 23 Feb 2014 05:35:51 +0900")

Hi Yagnesh,

Yagnesh Raghava Yakkala <hi@yagnesh.org> skribis:

>> I would recommend that you first familiarize yourself with Guix by
>> installing it, reporting any problems, and browsing the docs and code.
>
> Sure, I will do that.
>
>> This project may require a little bit of Scheme hacking to factorize
>> code between the ‘guix package’ command and what the Emacs UI would be
>> using (in the (guix profiles) module, specifically.)  Do you have
>> experience with Scheme and Guile?
>
> I don't have much experience with scheme except reading couple of books.

OK.  With this and your elisp background, it may not be too difficult to
get started.

>> Most of the rest of the code will be elisp though, obviously.  There
>> will be design choices to be made, such as whether the UI would
>> communicate with Guile/Guix via Geiser or through some ad hoc mechanism.
>
> I see. I hope as we progress to proposal stage I/we may get better
> understanding which way is the best.

Yes.

Make sure to stop by on #guix to discuss things.  I would be pleased if
we could get this project going.

Thanks,
Ludo’.

      reply	other threads:[~2014-02-27 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 22:08 GSoC ideas for GNU Guix Ludovic Courtès
2014-02-19 22:27 ` Jose E. Marchesi
     [not found] ` <87iosagz9m.fsf@yagnesh.org>
2014-02-20 11:05   ` [GSoC] Emacs UI for Guix Ludovic Courtès
2014-02-22 20:35     ` Yagnesh Raghava Yakkala
2014-02-27 13:33       ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87txbkbrz3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=hi@yagnesh.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.