unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Brian Templeton <bpt@tunes.org>
Cc: Daniel Kraft <d@domob.eu>, raeburn@mit.edu, guile-devel@gnu.org
Subject: Re: guile-emacs for gsoc
Date: Wed, 07 Apr 2010 22:58:04 +0200	[thread overview]
Message-ID: <m3d3yb3rqb.fsf@pobox.com> (raw)
In-Reply-To: <878w8z9gwf.fsf@lupus.terpri.org> (Brian Templeton's message of "Wed, 07 Apr 2010 15:55:28 -0400")

Hi!

Briefly, as time grows short: I'm excited that you're interested in
hacking Guile into Emacs. I can offer some mentorship, though my
bandwidth is a bit strained at this point. I would prefer if someone
else stepped up to mentor, though I will do it if no one else can.

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.

The job seems to me more of painstakingly correct refactorings than of
strokes of creative brilliance. You do have to be a bit daring -- the
whole project is a little crazy -- but precise in the execution.

Still interested? I would be very happy to accept a proposal from you.
But please, do us all a favor, and really immerse yourself in the state
of things as they are now, as much as is possible tomorrow -- raeburn's
guilemacs tree and Guile's elisp implementation.

> One obvious project would be to finish up the Emacs Lisp
> implementation; I just started looking at it last night, so I don't
> know how complete it really is.

I don't really know that either. Daniel probably knows best; but I know
that there is some work to do on Guile's elisp still: the compiler needs
to take advantage of advances in Guile's compiler (prompts/aborts,
"native" fluid binding, optional/keyword args) -- unfortunately
documenting some of this is still next on my to-document list.
(literally next)

> Another might be to go ahead with replacing the Emacs Lisp evaluator
> even if Guile's Emacs Lisp implementation is not quite complete,
> enough to get it booting (and then improving the Emacs Lisp language
> implementation would have immediate benefits).

This would be good; but tough, as I mentioned.

> And then there are side
> projects like writing a bytecode interpreter.

I don't think we should be interpreting existing compiled elisp
bytecode. we should compile elisp source to guile's vm.

What do you think?

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2010-04-07 20:58 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 [this message]
2010-04-07 21:18   ` Ludovic Courtès
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=m3d3yb3rqb.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=bpt@tunes.org \
    --cc=d@domob.eu \
    --cc=guile-devel@gnu.org \
    --cc=raeburn@mit.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).