public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: Keisuke Nishida <kxn30@po.cwru.edu>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: Emacs Scheme interface
Date: Tue, 28 Mar 2000 04:01:00 -0000	[thread overview]
Message-ID: <87n1njuww0.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <m3ln33ege5.fsf@kei.cwru.edu>

Keisuke Nishida <kxn30@po.cwru.edu> writes:

> It is easy to define point so that (point) returns a number,

And I think it should be defined that way.

> but mixing both normal imported functions and other special
> versions such as the (point) mentioned above may be very
> confusing.

If a Lisp reference is needed, one can call
(lisp-eval '(current-global-map)).

> Some functions can be easily imported by always converting return
> values to Scheme objects.  Some may be difficult because modifying
> the Lisp value is essential (e.g., keymaps).

If Emacs Scheme treated keymaps as opaque objects like XEmacs
does, that would be easier to solve.  But I suppose RMS wouldn't
approve that.

> Some requires defining new Scheme object in onder to get proper
> processing (e.g., buffers).

That's right.  They should probably also be associated with GOOPS
classes.

> People may define a new module (emacs api) (or whatever)
> and put new definitions in it.

IIRC, SCWM keeps its modules under (app scwm ...).  Perhaps Emacs
modules should be (app emacs ...).

> Unfortunately, I don't have enough time to work on this for a while.
> But let's start discussing.

I would really like thread support in Emacs Scheme.  Multiple
threads should be able to process different buffers at the same
time.  Perhaps the "current buffer" should be thread-local.

  reply	other threads:[~2000-03-28  4:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27 22:51 Keisuke Nishida
2000-03-28  4:01 ` Kalle Olavi Niemitalo [this message]
2000-03-28 10:27   ` Keisuke Nishida
2000-03-28 11:37     ` Ken Raeburn
2000-03-28 23:06     ` Kalle Olavi Niemitalo
2000-03-29 16:57       ` Keisuke Nishida
2000-03-28 11:43 ` Kalle Olavi Niemitalo
2000-03-28 12:23   ` Keisuke Nishida
2000-03-29  2:33     ` Kalle Olavi Niemitalo
2000-03-29 17:09       ` Keisuke Nishida
2000-04-30 12:08         ` Kalle Olavi Niemitalo
2000-03-31 17:48 ` Keisuke Nishida
2000-03-31 22:42   ` Klaus Schilling
2000-04-01  9:02     ` 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=87n1njuww0.fsf@PC486.Niemitalo.LAN \
    --to=tosi@stekt.oulu.fi \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=kxn30@po.cwru.edu \
    /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).