From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.emacs.devel,gmane.lisp.guile.devel Subject: Re: GSoC: Emacs Lisp support for GNU Guile Date: Tue, 31 Mar 2009 23:23:55 +0100 Message-ID: <87vdppnxfo.fsf@arudy.ossau.uklinux.net> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1238538259 13028 80.91.229.12 (31 Mar 2009 22:24:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 31 Mar 2009 22:24:19 +0000 (UTC) Cc: guile-devel@gnu.org, emacs-devel@gnu.org To: Daniel Kraft Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 01 00:25:37 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LomOm-00079y-9Y for ged-emacs-devel@m.gmane.org; Wed, 01 Apr 2009 00:25:36 +0200 Original-Received: from localhost ([127.0.0.1]:54386 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LomNO-0006Gj-7a for ged-emacs-devel@m.gmane.org; Tue, 31 Mar 2009 18:24:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LomNH-0006Co-FD for emacs-devel@gnu.org; Tue, 31 Mar 2009 18:24:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LomNC-0005zT-9c for emacs-devel@gnu.org; Tue, 31 Mar 2009 18:24:02 -0400 Original-Received: from [199.232.76.173] (port=38185 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LomNB-0005yb-Gn; Tue, 31 Mar 2009 18:23:57 -0400 Original-Received: from mail3.uklinux.net ([80.84.72.33]:44384) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LomNB-0006yP-1m; Tue, 31 Mar 2009 18:23:57 -0400 Original-Received: from arudy (host86-157-180-39.range86-157.btcentralplus.com [86.157.180.39]) by mail3.uklinux.net (Postfix) with ESMTP id 3E5BB1F668E; Tue, 31 Mar 2009 23:23:56 +0100 (BST) Original-Received: from arudy.ossau.uklinux.net (arudy [127.0.0.1]) by arudy (Postfix) with ESMTP id A05BD38013; Tue, 31 Mar 2009 23:23:55 +0100 (BST) In-Reply-To: (Daniel Kraft's message of "Tue\, 31 Mar 2009 21\:44\:11 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109951 gmane.lisp.guile.devel:8369 Archived-At: Daniel Kraft writes: > Hi all, > > as already discussed briefly with the Guile guys behind the new VM > thing, I got the idea to implement Emacs Lisp as supported language > for the Guile VM system. > > Below is a proposal for a GSoC project I submitted to GNU as mentoring > organization; Karl Berry replied that it sounds interesting but they > needed to find a mentor / mentors for this project; what do you (Emacs > and Guile people) think about it? Well I guess I could mentor this... On the other hand, if anyone else is very keen to, I'd be happy to let them! (Simply because of time pressure.) Having worked on Guile/Elisp on and off for some time, I think it would really help if you had a concrete goal in mind - i.e. something more concrete than implementing Emacs Lisp in general on the VM. I don't want to preempt your own ideas, but this could take the form of - identifying some existing (non-trivial) Emacs Lisp library or application - thinking of some cool extra thing that could be done with that, if it was combined with Guile (and maybe other guile libraries, such as guile-gnome) - then the concrete goal would be to get Elisp/VM working well enough to run that existing Elisp code and do the cool extra thing. If you followed this kind of approach, note that it would also need work - in addition to the Elisp/VM translation - to implement whatever Emacs primitives the Elisp code relies on. That would make the project as a whole less pure-language-translation, but (in my view) more real and useful. What do you think? Regards, Neil