Jump to content

Multics Emacs

From Wikipedia, the free encyclopedia
Multics Emacs
Original author(s)Bernard Greenberg
Developer(s)Honeywell
Initial release1978; 46 years ago (1978)
Written inMaclisp
Operating systemMultics
Available inEnglish
TypeText editor

Multics Emacs is an early implementation of the Emacs text editor.[1] It was written in Maclisp by Bernard Greenberg at Honeywell's Cambridge Information Systems Lab in 1978, as a successor to the original 1976 TECO implementation of Emacs and a precursor of later GNU Emacs.[2]

It has been claimed to be the first version of Emacs to be written in the Lisp programming language,[3] although the same claim has also been made for the Lisp Machine editors EINE and ZWEI, also written in the late 1970s. As well as the editor itself being written in Lisp, user-supplied extensions were also written in Lisp. The choice of Lisp provided more extensibility than ever before, and has been followed by most subsequent Emacs implementations.[4]

Rather than using TECO's gap buffer representation for the text being edited, it used a doubly linked list of lines of text.[5]

References

[edit]
  1. ^ Stallman, Richard M. (1981), "EMACS: the extensible, customizable self-documenting display editor", Proceedings of the ACM SIGPLAN SIGOA Symposium on Text Manipulation, doi:10.1145/800209.806466, hdl:1721.1/5736
  2. ^ Finseth, Craig A. (2012), The Craft of Text Editing: Emacs for the Modern World, Springer, p. 210, ISBN 9781461231882
  3. ^ Seibel, Peter (2006), Practical Common Lisp, Apress, p. xxi, ISBN 9781430200178
  4. ^ Greenberg, Bernard S. (April 8, 1996), "Multics Emacs: The History, Design and Implementation", Multicians
  5. ^ Strandh, Robert; Villeneuve, Matthieu; Moore, Timothy (2004), "Flexichain: An editable sequence and its gap-buffer implementation" (PDF), Proceedings of the Lisp and Scheme Workshop
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy