14 Nov
2021
14 Nov
'21
1:04 p.m.
On 2021-11-12 22:07, Paul Koning wrote:
Correct. It's about GnuEmacs. And yes, that is the major painpoint in
porting it. Every port needs to be able to create a runnable image on
disk from current memory.
But there is a version for Arm64 for the M1 now. I have it on my machine.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Nov 12, 2021, at 3:49 PM, Thomas DeBellis
<tommytimesharing at gmail.com> wrote:
I'm not 100% sure, but I don't believe that ITS/Tops-20/TENEX Emacs quite does
this. It is built on top of TECO, which you will recall as a language that is so terse
that it looks like line noise. I don't think it's a very big stretch to compare
it a byte code interpreter.
I do not recall that the EMACS libraries that are loaded are not quite compiled. They
have all the comments and unnecessary white space stripped out, which would, of course
speed execution.
gnuEmacs does a similar thing for the LISP code; it's still interpreted as I recall.
On 11/12/21 10:59 AM, Johnny Billquist wrote:
> RMS kept the idea alive in Emacs, where even today you fire up the core system, load
all kind of libraries, and then you do a memory dump, which is the runnable Emacs image.
>
> JOhnny
I think Johnny was talking about current Emacs. That might explain why it's hard to
port -- for example, there is a Mac version (AquaMacs) but no Arm64 (Apple M1 chip)
version because of the trickery associated with the dump machinery.