From mboxrd@z Thu Jan 1 00:00:00 1970 From: lars@nocrew.org (Lars Brinkhoff) Date: Sun, 26 Feb 2017 19:32:46 +0100 Subject: [TUHS] Un-released/internal/special UNIX versions/ports during the years? In-Reply-To: <008701d2904d$29d56c60$7d804520$@ronnatalie.com> (Ron Natalie's message of "Sun, 26 Feb 2017 11:27:01 -0500") References: <20170226123956.DBD3C18C088@mercury.lcs.mit.edu> <58b2ec12.PWETi07hYb+bxrO0%schily@schily.net> <13D1D81F-F878-4D23-922A-279AADF29CFE@tfeb.org> <58b2f9c8.N21HJWDG1ABXGZ/w%schily@schily.net> <008701d2904d$29d56c60$7d804520$@ronnatalie.com> Message-ID: <86d1e4reep.fsf@molnjunk.nocrew.org> "Ron Natalie" writes: > > I'd have to check the chronology but I'm fairly sure that EINE > > predates Gosling Emacs by several years: I'd assume that either EINE > > is where Gosling got the idea, or that it was just obvious, since > > Emacs came from an environment where implementing things in Lisp was > > not a strange idea, to put it rather mildly. > Tim is right. EINE predates Gosling's EMACS by a few years. Of course, > it uses LISP as an extension language not because they thought that would be > novel but since the whole thing was implemented in LISP to begin with (much > as you could extend the TECO EMACS with more TECO). RMS credits Multics Emacs with the idea to use Lisp as the extension language: The language that you build your extensions on shouldn't be thought of as a programming language in afterthought; it should be designed as a programming language. In fact, we discovered that the best programming language for that purpose was Lisp. It was Bernie Greenberg, who discovered that it was. He wrote a version of Emacs in Multics MacLisp, and he wrote his commands in MacLisp in a straightforward fashion. The editor itself was written entirely in Lisp. Multics Emacs proved to be a success great programming new editing commands was so convenient that even the secretaries in his office started learning how to use it. https://www.gnu.org/gnu/rms-lisp.html