From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Cc: storm@cua.dk, emacs-devel@gnu.org, gerd.moellmann@t-online.de
Subject: Re: Why do we spend time on Emacs on Guile?
Date: Fri, 23 Aug 2002 09:02:43 +0200 [thread overview]
Message-ID: <y9lofbuoy5o.fsf@sams.informatik.uni-tuebingen.de> (raw)
In-Reply-To: <m3ptwhocyt.fsf@loiso.podval.org> (Sam Steingold's message of "17 Aug 2002 09:02:18 -0400")
>>>>> "Sam" == Sam Steingold <sds@gnu.org> writes:
>> * In message <200208170450.g7H4oRf08568@wijiji.santafe.edu>
>> * On the subject of "Re: Why do we spend time on Emacs on Guile?"
>> * Sent on Fri, 16 Aug 2002 22:50:27 -0600 (MDT)
>> * Honorable Richard Stallman <rms@gnu.org> writes:
Sam> >
>> Guile is the standard extensibility package of the GNU Project, All
>> GNU packages that include an interpreter for extensibility are
>> supposed to use Guile. It is inconsistent for Emacs not to support
>> Guile.
Sam> Supporting Guile via compilation into Common Lisp is _much_ easier.
Sam> I.e., re-hosting Emacs on CLISP and making CLISP able to load Emacs
Sam> Lisp (done already) and Guile (should be very easy).
Jonathan Rees's Pseudoscheme did this many years ago, but the support
sure wasn't complete. I'd also be surprise if this were "very" easy:
you at least need to take care of hygienic macros (possible) and
CALL-WITH-CURRENT-CONTINUATION (ermh, ..., difficult).
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
prev parent reply other threads:[~2002-08-23 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86y9b8awuv.fsf@gerd.free-bsd.org>
2002-08-16 9:34 ` Why do we spend time on Emacs on Guile? Kim F. Storm
2002-08-16 16:36 ` Thien-Thi Nguyen
2002-08-16 22:46 ` Werner LEMBERG
2002-08-17 23:28 ` Thien-Thi Nguyen
2002-08-16 16:52 ` D. Goel
2002-08-16 18:02 ` Sam Steingold
2002-08-17 4:50 ` Richard Stallman
2002-08-17 13:02 ` Sam Steingold
2002-08-23 7:02 ` Michael Sperber [Mr. Preprocessor] [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y9lofbuoy5o.fsf@sams.informatik.uni-tuebingen.de \
--to=sperber@informatik.uni-tuebingen.de \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@t-online.de \
--cc=storm@cua.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).