From: Per Bothner <per@bothner.com>
To: Rafik Naccache [TNTeam] <rafik@tnteam.rocks>, kawa@sourceware.org
Subject: Re: RE : Re: What is the Development Environment of Choice for Kawa?
Date: Thu, 18 Feb 2016 22:38:00 -0000 [thread overview]
Message-ID: <56C647D1.9090100@bothner.com> (raw)
In-Reply-To: <56C64490.8090204@tnteam.rocks>
On 02/18/2016 02:24 PM, Rafik Naccache [TNTeam] wrote:
> Actually, scheme's kinda most accomplished tooling on emacs is Geiser : http://www.nongnu.org/geiser/
The following is promising:
"In particular, Geiser expects [a REPL] to support namespaces in the form of a module system, and to provide
a well-defined way to establish the REPL’s current namespace (or module), as well as the current file’s module (or namespace)."
It's good that Geiser is namespace/module-friendly.
There is a feature-request:
https://github.com/jaor/geiser/issues/55
A comment states:
Very loosely, this won't work as expected, apparently:
(eval '(...) my-module-environment)
Not sure what that refers to. Kawa (as of 2.0) does support environment-specifiers
to the eval procedure, but perhaps not quite in the way Geiser wants.
> I shall maybe hack on it drawing inspiration from what has been implemented for guile, chicken and racket...
That would be great.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-02-18 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
2016-02-18 21:18 ` Per Bothner
2016-02-18 21:22 ` mikel evins
2016-02-18 22:24 ` RE : " Rafik
2016-02-18 22:38 ` Per Bothner [this message]
2016-02-19 0:09 ` Alex Shinn
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=56C647D1.9090100@bothner.com \
--to=per@bothner.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).