public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: raeburn@raeburn.org
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: guile-emacs-0.1 released
Date: Sun, 07 Jan 2001 09:13:00 -0000	[thread overview]
Message-ID: <200101071713.KAA18087@aztec.santafe.edu> (raw)
In-Reply-To: <tx1k8j1aov2.fsf@raeburn.org>

I am responding to messages that got buried during the year.
Please forgive me for taking so long to respond.

You wrote:
    >       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 responded:

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

You responded:

    Which "normal ways of writing code"?

It occurs to me now that there's more than one way of interpreting
what you originally said.  So I think the useful thing for me to do
is explain what I'm concerned about.

    If people want to write elisp, it'll work just fine, with the expected
    dynamic bindings and buffer-local variables and so on.

    If people want to write Scheme to extend an application -- be it GNU
    Emacs or GNU ld or whatever -- I think it should be Scheme, not
    "Scheme except maybe for dynamic bindings if you're running Emacs".

The Scheme language certainly should not be changed, so variables
should ordinarily be lexical as usual in Scheme.  And these lexical
variables would have nothing to do with Emacs buffer-local bindings.

But whatever mechanism people use in Scheme to make and access
dynamically scoped variables, it should be integrated smoothly with
Emacs buffer-local and frame-local bindings when you use it in Emacs.

  reply	other threads:[~2001-01-07  9:13 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
2000-03-17  2:10     ` Ken Raeburn
2001-01-07  9:13       ` Richard Stallman [this message]
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:
  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=200101071713.KAA18087@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=raeburn@raeburn.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).