Štěpán Němec writes:
On Mon, Jul 25, 2011 at 01:52:14PM +0900, Stephen J. Turnbull wrote:
[thank you for the GPL & Elisp information]
You're welcome.
> Mike (Sperber)'s student did some work on implementing Emacs
Lisp in
> Scheme48, which would get us partway there.[1]
I know about that, but as I said, I don't really see the point of
reimplementing Elisp. You wouldn't want to use most of the existing
Elisp code anyway, both for copyright/licence
Ah, but *if* we have a non-Emacs-derived implementation of the
"facilities", then those facilities become de facto part of the
language, and the "just interprets data as a language" part of the FAQ
means that there are no copyright/license issues.
and quality reasons,
Agreed. Nevertheless, most of those programs are quite useful in
daily editing, even if equally inadequate to the task of providing a
robust general-purpose programming environment "with batteries included".
and a dynamic-scope-only[1], slow, module-less scripting language
like Elisp is not up to the task, in any case (as can well be seen
on the current state of Emacs, too)...
I think we disagree on what "the task" is. I use XEmacs daily and am
(mostly) quite satisfied with it.
Indeed, I would like to see Emacs (well, *X*Emacs ;-) become a
scripting and programming environment to surpass the P languages. I
suppose that is "the task" you have in mind. But I don't consider
that to be a primary task of current Emacs development, nor do I
consider the inability of Emacs to provide such an environment likely
to kill any of the Emacsen any time soon.
...right, and not desirable anyway, for the reasons listed.
> so the most plausible route would be a Schemacs core engine, based on
> a libre-licensed Scheme, combined with UI and API derived from
> (SX|X)?Emacs, with the whole work licensed under GPL.
Why would it have to be GPL-licensed?
*Derived* means using code from those projects, which would be
gradually replaced over time, the way the BSD guys wrote libedit to
make it possible to write code that users could link to libreadline
even if projects can't distribute it that way. To the extent that the
core expanded and new applications or rewrites of old ones were done
in Scheme, it would be possible to have a partial but very useful
distribution under libre terms.
Another possibility would be to reimplement only the text types
(buffers and strings), and leave everything else up to a brand new
display engine. Jamie Zawinski's suggestion is targeting HTML,
leaving redisplay up to your browser. :-)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta