From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: guile-emacs for gsoc
Date: Wed, 07 Apr 2010 23:18:59 +0200 [thread overview]
Message-ID: <878w8zota4.fsf@gnu.org> (raw)
In-Reply-To: m3d3yb3rqb.fsf@pobox.com
Hi,
Andy Wingo <wingo@pobox.com> writes:
> Also, the project is a bit nebulous at this point -- Ken has come at it
> from the C-and-emacs side, and Daniel, Neil and I have come at it from
> the Elisp-in-Guile side, and it's really unclear what's in the middle.
> That's part of the hack, is finding that out.
FWIW I think finding out how to put it all together should be central to
the project. I think it would help the Guile-in-Emacs project to start
working on this as much as possible before further improving the elisp
compiler front-end.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-04-07 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 19:55 guile-emacs for gsoc Brian Templeton
2010-04-07 20:58 ` Andy Wingo
2010-04-07 21:18 ` Ludovic Courtès [this message]
2010-04-08 3:39 ` Ken Raeburn
-- strict thread matches above, loose matches on Subject: below --
2010-04-07 20:05 Brian Templeton
2010-04-07 20:55 ` Daniel Kraft
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=878w8zota4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-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.
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).