public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: Jim Blandy <jimb@red-bean.com>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: guile-emacs GC (was special forms)
Date: Wed, 15 Mar 2000 15:14:00 -0000	[thread overview]
Message-ID: <m3vh2n7rlz.fsf@kei.cwru.edu> (raw)
In-Reply-To: <m34sa79a6q.fsf@savonarola.red-bean.com>

Jim Blandy <jimb@red-bean.com> writes:

> Honestly, this doesn't seem like a good idea.  There are zillions of
> useful Emacs Lisp functions that are part of Emacs right now, and it
> would be a fatal mistake to push a design which doesn't encourage the
> Lisp and Scheme worlds to share data freely.
> 
> The best approach is to change Emacs Lisp to use Guile objects.  That
> is, Fcons (if I remember correctly) should call SCM_NEWCELL, and so
> on.  That way, the two languages operate on a common GC, and can share
> data freely.

I know that it is the right way; however, it takes time.  People and I
do not want to wait that long.  See Ken Raeburn's web page.  It counts
only two hundreds of accesses.  Most people are interested in the editor
which they CAN use without many problems.  I guess that is one reason
why many people have not been interested in merging Guile with Emacs.
I do not like this situation.  I could write a editor that at least
worked fine with Guile.  And I could advertise it with some interesting
facilities such as the GNOME/GTK+ interface.  Then, more people will
come here (I believe).

I do not mean that I am discouraging people from using Scheme data from
Lisp programs.  I just mean it is not that time.  I understand there are
so many useful Elisp programs (including mine), so I encourage people to
use them from Scheme programs.  But the other side is not necessary true
at this moment.  If there are so many people who want to use Scheme data
from Lisp programs, they will do so by replacing the Lisp evaluator with
Guile.  I just think, that is not my work.

> Ken Raeburn has already done a lot of this work.  You really should
> look at his patches.

Yes, I did (about a half year ago), and I appreciate his work.  So I am
not going to do the same work as his.  I intentionally choose a different
approach.  When more and more people get interested in Guile Emacs, that
is the end of my approach and the time to switch to his approach.  If
there were more people who worked on Guile-based Emacs, I did not need
to do this now.

  reply	other threads:[~2000-03-15 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-14 12:46 special forms (save-excursion) Kalle Olavi Niemitalo
2000-03-14 13:32 ` Keisuke Nishida
2000-03-14 14:11 ` Keisuke Nishida
2000-03-14 14:17   ` Keisuke Nishida
2000-03-15  0:34   ` Kalle Olavi Niemitalo
2000-03-15  3:32     ` Keisuke Nishida
2000-03-15  5:11       ` Kalle Olavi Niemitalo
2000-03-15  5:43         ` Keisuke Nishida
2000-03-15  6:12           ` Kalle Olavi Niemitalo
2000-03-15 11:37             ` guile-emacs GC (was special forms) Kalle Olavi Niemitalo
2000-03-15 12:18               ` Keisuke Nishida
2000-03-15 13:48                 ` Jim Blandy
2000-03-15 15:14                   ` Keisuke Nishida [this message]
2000-03-15 11:30           ` special forms (save-excursion) Kalle Olavi Niemitalo
2000-03-15 12:42             ` Keisuke Nishida

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vh2n7rlz.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=jimb@red-bean.com \
    /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).