public inbox for
 help / color / mirror / Atom feed
From: Richard Stallman <>
Subject: Re: guile-emacs-0.1 released
Date: Thu, 16 Mar 2000 18:50:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

      Symbols might be converted without waiting for
    strings to be done, but the interaction of Lisp dynamic bindings and
    buffer- and frame-local bindings and Scheme lexical bindings needs to
    be worked out.  (IMHO, Scheme code should see Scheme behavior unless
    it requests access to the current Lisp environment.

I don't think so.  That is not a useful behavior in the context of
Emacs.  To get useful results, we need to make the normal ways of
writing code access the local bindings of Emacs.

    And then there's variables restricted to specific types, and with
    side-effects in the C code.

These variables are just an implementation method, not a feature users
depend on.  I'm sure we could manage to implement the code that uses
these variables in some other way, if that will simplify matters by
avoiding the need for a special feature for such variables.

  parent reply	other threads:[~2000-03-16 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13 15:11 Keisuke Nishida
2000-03-14 12:46 ` guileapi.x problems [patch] Kalle Olavi Niemitalo
2000-03-14 13:20   ` Keisuke Nishida
2000-03-15 21:11   ` Ken Raeburn
2000-03-16  4:29     ` Kalle Olavi Niemitalo
2000-03-16  8:55       ` Keisuke Nishida
2000-03-16 16:57         ` Kalle Olavi Niemitalo
2000-03-17  9:55           ` Keisuke Nishida
2000-03-15 21:07 ` guile-emacs-0.1 released Ken Raeburn
2000-03-16 12:29   ` Keisuke Nishida
2000-03-16 18:50   ` Richard Stallman [this message]
2000-03-17  2:10     ` Ken Raeburn
2001-01-07  9:13       ` Richard Stallman
2001-01-07 13:28         ` 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:

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

  git send-email \ \ \ \ \ \

* 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).