From: Daniel Kraft <d@domob.eu>
To: guile-devel@gnu.org
Subject: Re: guile-emacs for gsoc
Date: Wed, 07 Apr 2010 22:55:31 +0200 [thread overview]
Message-ID: <4BBCF143.1030509@domob.eu> (raw)
In-Reply-To: <874ojn9gg5.fsf@lupus.terpri.org>
Hi Brian,
Brian Templeton wrote:
> I'm preparing Summer of Code applications and am considering working on
> Emacs-Guile integration. Here's my understanding of the current
> situation, from skimming list archives, source code, etc.:
this sounds great! I did the current elisp implementation in last
year's GSoC, so I'd love to see this covered further! Unfortunatly I
had nearly no time at all to work on this since last autumn because of
my studies, even though I would have liked to.
I do not really know about Ken's guile-emacs or emacs itself, but I hope
I can give you some hints on the "pure" elisp implementation:
First of all, see README in module/language/elisp. And of course,
module/language/elisp itself, there's where (nearly) all of it is
concentrated.
One important open thing I'm aware is "proper" handling of Elisp's nil
vs. Scheme's #f and '() -- this has been source of discussion for quite
some while now, and you should find plenty of threads in the archives.
And another thing is that Guile's "backend" got recently support for
things like optional arguments, while last summer I implemented this in
the elisp "front end"; so maybe a good first start (I don't know if an
easy start, though) could be to switch elisp's implementation to the
available Guile infrastructure instead.
Of the missing elisp bits, some are mentioned in the README file. Other
things, especially what I had in mind as doing "next", would be for
instance buffer- and frame-local bindings.
I think there may even be some threads in the mailing list archives
where I wrote some ideas about that; I'm not sure, though. I think my
idea was to mark the bindings in a special way (similarly to what is
currently done for void values) and back them by some kind of hash-table
that is indexed with the current buffer/frame/whatever on retrieval.
But if you want to work on that, you will no doubt find a good way to do
so :)
If you want to work (also) on the real emacs integration, I can not tell
you anything about that. But if that's your main focus of interest,
maybe I can even find some time again during the summer to work on the
elisp bits and help you that way -- I guess that the emacs work may be
far more than a single GSoC project... (I will not apply for Guile as
GSoC project though, this would be just "for fun" -- more so than GSoC
already is.)
Happy hacking!
Daniel
next prev parent reply other threads:[~2010-04-07 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 20:05 guile-emacs for gsoc Brian Templeton
2010-04-07 20:55 ` Daniel Kraft [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-07 19:55 Brian Templeton
2010-04-07 20:58 ` Andy Wingo
2010-04-07 21:18 ` Ludovic Courtès
2010-04-08 3:39 ` Ken Raeburn
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=4BBCF143.1030509@domob.eu \
--to=d@domob.eu \
--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).