unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#41985: ELisp
       [not found] <1016225996.1163221.1592726018504.ref@mail.yahoo.com>
@ 2020-06-21  7:53 ` Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
       [not found]   ` <mailman.211.1592754723.2574.bug-gnu-emacs@gnu.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2020-06-21  7:53 UTC (permalink / raw)
  To: 41985

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 1021 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#41985: ELisp
       [not found]   ` <mailman.211.1592754723.2574.bug-gnu-emacs@gnu.org>
@ 2020-06-21 17:41     ` Alan Mackenzie
  2020-07-24 13:48       ` Stefan Kangas
  0 siblings, 1 reply; 3+ messages in thread
From: Alan Mackenzie @ 2020-06-21 17:41 UTC (permalink / raw)
  To: Andrew Goh; +Cc: 41985

In article <mailman.211.1592754723.2574.bug-gnu-emacs@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).






^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#41985: ELisp
  2020-06-21 17:41     ` Alan Mackenzie
@ 2020-07-24 13:48       ` Stefan Kangas
  0 siblings, 0 replies; 3+ messages in thread
From: Stefan Kangas @ 2020-07-24 13:48 UTC (permalink / raw)
  To: Alan Mackenzie, Andrew Goh; +Cc: 41985

tags 41985 + notabug wontfix
close 41985
thanks

Alan Mackenzie <acm@muc.de> writes:

> In article <mailman.211.1592754723.2574.bug-gnu-emacs@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





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-07-24 13:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1016225996.1163221.1592726018504.ref@mail.yahoo.com>
2020-06-21  7:53 ` bug#41985: ELisp Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <mailman.211.1592754723.2574.bug-gnu-emacs@gnu.org>
2020-06-21 17:41     ` Alan Mackenzie
2020-07-24 13:48       ` Stefan Kangas

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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