GNU bug report logs - #41985
ELisp

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41985 in the body.
You can then email your comments to 41985 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andrew Goh <andrewgoh95 <at> yahoo.com.sg>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: ELisp
Date: Sun, 21 Jun 2020 07:53:38 +0000 (UTC)

[Message part 1 (text/plain, inline)]

Hi GNU Emacs Team,
I wonder if the GNU Emacs Team had thought of replacing the ELisp scripting language with that from newLisp.  I took a look at newLisp documentation and must say its very easy.  Anyway, I didn't run the newLisp installer as Windows Defender blocked the download from executing. The only place where I will run newLisp code is "newLisp in a browser."
Regards,
Andrew Goh S M

[Message part 2 (text/html, inline)]

Message #8 received at 41985 <at> debbugs.gnu.org (full text, mbox):

From: Alan Mackenzie <acm <at> muc.de>
To: Andrew Goh <andrewgoh95 <at> yahoo.com.sg>
Cc: 41985 <at> debbugs.gnu.org
Subject: Re: bug#41985: ELisp
Date: 21 Jun 2020 17:41:28 -0000

In article <mailman.211.1592754723.2574.bug-gnu-emacs <at> gnu.org> you wrote:
> Hi GNU Emacs Team,

> I wonder if the GNU Emacs Team had thought of replacing the ELisp
> scripting language with that from newLisp.?

Hardly.

> I took a look at newLisp documentation and must say its very easy.

But it won't include facilities for manipulating editing things like
buffers.  It would take a lot of work to replicate these in newLisp.

Also, there's around 1.7 million lines of Emacs Lisp code in the Emacs
core.  That's a lot of code to have to convert.

> Anyway, I didn't run the newLisp installer as Windows Defender blocked
> the download from executing. The only place where I will run newLisp
> code is "newLisp in a browser."

Well, there's another reason.  You'd likely have less trouble running on
GNU/Linux.

> Regards, Andrew Goh S M

-- 
Alan Mackenzie (Nuremberg, Germany).

Message #11 received at 41985 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Alan Mackenzie <acm <at> muc.de>, Andrew Goh <andrewgoh95 <at> yahoo.com.sg>
Cc: 41985 <at> debbugs.gnu.org
Subject: Re: bug#41985: ELisp
Date: Fri, 24 Jul 2020 06:48:41 -0700

tags 41985 + notabug wontfix
close 41985
thanks

Alan Mackenzie <acm <at> muc.de> writes:

> In article <mailman.211.1592754723.2574.bug-gnu-emacs <at> gnu.org> you wrote:
>> Hi GNU Emacs Team,
>
>> I wonder if the GNU Emacs Team had thought of replacing the ELisp
>> scripting language with that from newLisp.?
>
> Hardly.
>
>> I took a look at newLisp documentation and must say its very easy.
>
> But it won't include facilities for manipulating editing things like
> buffers.  It would take a lot of work to replicate these in newLisp.
>
> Also, there's around 1.7 million lines of Emacs Lisp code in the Emacs
> core.  That's a lot of code to have to convert.

It is very unlikely that we will rewrite Emacs in newLisp.

I'm therefore closing this bug.

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.