Lesson plan
MicroEMACS
MicroEMACS is a small, portable Emacs-like text editor originally written by Dave Conroy in 1985, and further developed by Daniel M. Lawrence (1958–2010 ) and was maintained by him. MicroEMACS has been ported to many operating systems, including CP/M, MS-DOS, Microsoft Windows, VMS, Atari ST, AmigaOS, OS-9, NeXTSTEP, and various Unix-like operating systems. Variants of MicroEMACS also exist, such as mg, a more GNU Emacs-compatible editor. Many relationships to contemporary editors can also be found in MicroEMACS. The vi clone vile was derived from an older version of MicroEMACS. University of Washington's simple text editor Pico was based on MicroEMACS 3.6. Pico's featureset and interface would later be emulated in the free software clone GNU nano due to its ambiguous licensing terms. Linus Torvalds, creator of Linux, has been a user of MicroEMACS since his days as a student at the University of Helsinki. Torvalds also maintains a fork called uEmacs/Pk, based on MicroEMACS 3.9e.
Article summary
MicroEMACS is a small, portable Emacs-like text editor originally written by Dave Conroy in 1985, and further developed by Daniel M. Lawrence (1958–2010 ) and was maintained by him. MicroEMACS has been ported to many operating systems, including CP/M, MS-DOS, Microsoft Windows, VMS, Atari ST, AmigaOS, OS-9, NeXTSTEP, and various Unix-like operating systems. Variants of MicroEMACS also exist, such as mg, a more GNU Emacs-compatible editor. Many relationships to contemporary editors can also be found in MicroEMACS. The vi clone vile was derived from an older version of MicroEMACS. University of Washington's simple text editor Pico was based on MicroEMACS 3.6. Pico's featureset and interface would later be emulated in the free software clone GNU nano due to its ambiguous licensing terms. Linus Torvalds, creator of Linux, has been a user of MicroEMACS since his days as a student at the University of Helsinki. Torvalds also maintains a fork called uEmacs/Pk, based on MicroEMACS 3.9e.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.