unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: shane.celis@uvm.edu, Guile Mailing List <guile-user@gnu.org>,
	BT Templeton <bpt@hcoop.net>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: GSoC: Guile-Emacs + Emacsy
Date: Mon, 3 Jun 2013 23:15:45 -0400	[thread overview]
Message-ID: <CA+U71=MUFmnnw9_d1-W94hAs5mZnUD4B9jCQWOVsh55=tsHSXw@mail.gmail.com> (raw)
In-Reply-To: <87r4gr2tln.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]

This is great news! I'm glad to hear about both of these projects. Please
do send updates to the mailing lists as they progress!

Thanks,
Noah


On Tue, May 28, 2013 at 8:10 AM, Ludovic Courtès <ludo@gnu.org> wrote:

> Hello Guilers & Emacsers!
>
> I’m pleased to announce that there will be two Guile-related projects
> going on as part of GSoC this year:
>
>   • Guile-Emacs, by BT Templeton
>
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/bpt/35002
>
>     BT will continue the excellent work that has been done on Guile and
>     Emacs integration.  Previous GSoCs focused on providing a
>     full-fledged Emacs Lisp front-end to Guile’s compiler and VM.  This
>     project focuses on the missing piece: replacing the Emacs Lisp
>     interpreter in Emacs by Guile.
>
>   • Emacsy, by Shane Celis
>
> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/shanecelis/1
>
>     This is another approach to the Emacs/Guile vision: Shane will work
>     on a framework, Emacsy, that will allow application developers to
>     easily “emacsify” them–i.e., by providing the mechanisms for a
>     “key-lookup-execute-command loop” similar to that of Emacs, with
>     Guile inside.
>
> (Shane and BT: feel free to introduce yourself and your project.)
>
> I’m the mentor for these two projects, but I really hope they will
> develop with good interaction with the Guile and Emacs folk.  In
> particular, I would like development issues and road maps to be
> discussed primarily on the relevant project mailing lists.
>
> I’m very excited about these two projects.  I think they will help
> promote a vision where users are in control and can readily exert their
> freedom to study and adapt the software to their needs.
>
> Thanks a lot to José and Giuseppe who have wonderfully handled GNU’s
> participation in GSoC, and happy hacking!
>
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 2558 bytes --]

  parent reply	other threads:[~2013-06-04  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 12:10 GSoC: Guile-Emacs + Emacsy Ludovic Courtès
2013-05-28 13:47 ` Grant Rettke
2013-05-28 17:21 ` Aurélien Aptel
2013-06-04  3:15 ` Noah Lavine [this message]
2013-06-06 16:42   ` Shane Celis
2013-06-06 20:45     ` 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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to='CA+U71=MUFmnnw9_d1-W94hAs5mZnUD4B9jCQWOVsh55=tsHSXw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=bpt@hcoop.net \
    --cc=emacs-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    --cc=shane.celis@uvm.edu \
    /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.
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).