Emacs

Not to be confused with eMac.
This article is about the class of text editors. For the most popular current example, see GNU Emacs.
emacs

Editing multiple Dired buffers in GNU Emacs
Developer(s) Richard Stallman, Guy L. Steele, Jr.
Initial release 1976, 39–40 years ago[1]
Written in Lisp, C
Operating system TECO, cross-platform, Unix-like
Type Text editor

Emacs /ˈiːmæks/ and its derivatives are a family of text editors that are characterized by their extensibility. The manual for the most widely used variant, GNU Emacs, describes it as "the extensible, customizable, self-documenting, real-time display editor".[2] Development of the first Emacs began in the mid-1970s and continues actively as of 2016.

Emacs has over 2,000 built-in commands and allows the user to combine these commands into macros to automate work. Emacs Lisp provides a deep extension capability allowing users and developers to write new commands using a dialect of the Lisp programming language. Extensions have been written to manage email, files, outlines, and RSS feeds.[3] Some users find they can do almost all their work from within Emacs, not just editing text.[4]

The original EMACS was written in 1976 by Richard Stallman and Guy L. Steele, Jr. as a set of Editor MACroS for the TECO editor.[5][6][7][8] It was inspired by the ideas of the TECO-macro editors TECMAC and TMACS.[9]

The most popular, and most ported, version of Emacs is GNU Emacs, which was created by Stallman for the GNU Project.[10] XEmacs is a variant that branched from GNU Emacs in 1991. Both GNU Emacs and XEmacs use Emacs Lisp and are for the most part compatible with each other.

Emacs is, along with vi, one of the two main contenders in the traditional editor wars of Unix culture. Both are among the oldest application programs still in use.

History

Editing C source code in GNU Emacs
Editing and compiling C++ code from GNU Emacs

Emacs development began during the 1970s at the MIT AI Lab, whose PDP-6 and PDP-10 computers used the Incompatible Timesharing System (ITS) operating system that featured a default line editor known as Tape Editor and Corrector (TECO). Unlike most modern text editors, TECO used separate modes in which the user would either add text, edit existing text, or display the document. One could not place characters directly into a document by typing them into TECO, but would instead enter a character ('i') in the TECO command language telling it to switch to input mode, enter the required characters, during which time the edited text was not displayed on the screen, and finally enter a character (<esc>) to switch the editor back to command mode. (A similar technique was used to allow overtyping.) This behavior is similar to that of the program ed.

Richard Stallman visited the Stanford AI Lab in 1972 or 1974 and saw the lab's E editor, written by Fred Wright.[11] He was impressed by the editor's intuitive WYSIWYG (What You See Is What You Get) behavior, which has since become the default behavior of most modern text editors. He returned to MIT where Carl Mikkelsen, a hacker at the AI Lab, had added to TECO a combined display/editing mode called Control-R that allowed the screen display to be updated each time the user entered a keystroke. Stallman reimplemented this mode to run efficiently and then added a macro feature to the TECO display-editing mode that allowed the user to redefine any keystroke to run a TECO program.[8]

E had another feature that TECO lacked: random-access editing. TECO was a page-sequential editor that was designed for editing paper tape on the PDP-1 and typically allowed editing on only one page at a time, in the order of the pages in the file. Instead of adopting E's approach of structuring the file for page-random access on disk, Stallman modified TECO to handle large buffers more efficiently and changed its file-management method to read, edit, and write the entire file as a single buffer. Almost all modern editors use this approach.

The new version of TECO quickly became popular at the AI Lab and soon accumulated a large collection of custom macros whose names often ended in MAC or MACS, which stood for macro. Two years later, Guy Steele took on the project of unifying the overly diverse macros into a single set.[12] Steele and Stallman's finished implementation included facilities for extending and documenting the new macro set.[8] The resulting system was called EMACS, which stood for Editing MACroS or, alternatively, E with MACroS. Stallman picked the name Emacs "because <E> was not in use as an abbreviation on ITS at the time."[13] An apocryphal hacker koan alleges that the program was named after Emack & Bolio's, a popular Cambridge ice cream store.[14] The first operational EMACS system existed in late 1976.[15]

Stallman saw a problem in too much customization and de facto forking and set certain conditions for usage. He later wrote:[15]

"EMACS was distributed on a basis of communal sharing, which means all improvements must be given back to me to be incorporated and distributed."

The original Emacs, like TECO, ran only on the PDP-10 running ITS. Its behavior was sufficiently different from that of TECO that it could be considered a text editor in its own right, and it quickly became the standard editing program on ITS. Mike McMahon ported Emacs from ITS to the Tenex and TOPS-20 operating systems. Other contributors to early versions of Emacs include Kent Pitman, Earl Killian, and Eugene Ciccarelli. By 1979, Emacs was the main editor used in MIT's AI lab and its Computer Science lab.[16]

Other early implementations

In the following years, programmers wrote a variety of Emacs-like editors for other computer systems. These included EINE (EINE Is Not EMACS) and ZWEI[17] (ZWEI Was EINE Initially), which were written for the Lisp machine by Mike McMahon and Daniel Weinreb, and Sine (Sine Is Not Eine),[18] which was written by Owen Theodore Anderson. Weinreb's EINE was the first Emacs written in Lisp. In 1978, Bernard Greenberg wrote Multics Emacs almost entirely in Multics Lisp at Honeywell's Cambridge Information Systems Lab. Multics Emacs was later maintained by Richard Soley, who went on to develop the NILE Emacs-like editor for the NIL Project, and by Barry Margolin. Many versions of Emacs, including GNU Emacs, would later adopt Lisp as an extension language.

James Gosling, who would later invent NeWS and the Java programming language, wrote Gosling Emacs in 1981. The first Emacs-like editor to run on Unix, Gosling Emacs was written in C and used Mocklisp, a language with Lisp-like syntax, as an extension language.

GNU Emacs

Main article: GNU Emacs
GNU Emacs running in a text console
GNU Emacs running on Microsoft Windows

Richard Stallman began work on GNU Emacs in 1984 to produce a free software alternative to the proprietary Gosling Emacs. GNU Emacs was initially based on Gosling Emacs, but Stallman's replacement of its Mocklisp interpreter with a true Lisp interpreter required that nearly all of its code be rewritten. This became the first program released by the nascent GNU Project. GNU Emacs is written in C and provides Emacs Lisp, also implemented in C, as an extension language. Version 13, the first public release, was made on March 20, 1985. The first widely distributed version of GNU Emacs was version 15.34, released later in 1985. Early versions of GNU Emacs were numbered as 1.x.x, with the initial digit denoting the version of the C core. The 1 was dropped after version 1.12, as it was thought that the major number would never change, and thus the numbering skipped from 1 to 13.[19] In September 2014, it was announced on the GNU emacs-devel mailing list that GNU Emacs would adopt a rapid release strategy and version numbers would increment more quickly in the future.[20]

GNU Emacs was later ported to Unix. It offered more features than Gosling Emacs, in particular a full-featured Lisp as its extension language, and soon replaced Gosling Emacs as the de facto Unix Emacs editor. Markus Hess exploited a security flaw in GNU Emacs' email subsystem in his 1986 cracking spree in which he gained superuser access to Unix computers.[21]

GNU Emacs development was relatively closed until 1999 and was used as an example of the Cathedral development style in The Cathedral and the Bazaar. The project has since adopted a public development mailing list and anonymous CVS access. Development took place in a single CVS trunk until 2008 and was then switched to the Bazaar DVCS. On November 11, 2014, development was moved to Git.[22]

Richard Stallman has remained the principal maintainer of GNU Emacs, but he has stepped back from the role at times. Stefan Monnier and Chong Yidong have overseen maintenance since 2008.[23] As of early 2014, GNU Emacs has had 579 individual commiters throughout its history.[24]

XEmacs

Main article: XEmacs
XEmacs 21.5 on GNU/Linux

Lucid Emacs, based on an early alpha version of GNU Emacs 19, was developed beginning in 1991 by Jamie Zawinski and others at Lucid Inc. One of the best-known early forks in free software development occurred when the codebases of the two Emacs versions diverged and the separate development teams ceased efforts to merge them back into a single program.[25] Lucid Emacs has since been renamed XEmacs and remains the second most popular variety of Emacs, after GNU Emacs. XEmacs development has slowed, with the most recent stable version 21.4.22 released in January 2009 (while a beta was released in 2013), while GNU Emacs has implemented many formerly XEmacs-only features. This has led some users to proclaim XEmacs' death.[26]

Other forks of GNU Emacs

Other forks, less known than XEmacs, include:

Various Emacs editors

The mg tiny Emacs-like editor in OpenBSD 5.3. Editing Ruby source code
Zmacs, an Emacs for Lisp machines

In the past, projects aimed at producing small versions of Emacs proliferated. GNU Emacs was initially targeted at computers with a 32-bit flat address space and at least 1 MiB of RAM. Such computers were high end workstations in the 1980s, and this left a need for smaller reimplementations that would run on common personal computer hardware. In more recent times, small clones have been designed to fit on software installation disks.

Other projects aim to implement Emacs in a different dialect of Lisp or a different programming language altogether. Although not all are still actively maintained, these clones include:

Editors with Emacs emulation

Features

Emacs is primarily a text editor and is designed for manipulating pieces of text, although it is capable of formatting and printing documents like a word processor by interfacing with external programs such as LaTeX, Ghostscript or a web browser. Emacs provides commands to manipulate and differentially display semantic units of text such as words, sentences, paragraphs and source code constructs such as functions. It also features keyboard macros for performing user-defined batches of editing commands.

GNU Emacs is a real-time display editor, as its edits are displayed onscreen as they occur. This is standard behavior for modern text editors but EMACS was among the earliest to implement this functionality instead of having to issue a separate command to insert new edits into the existing text as in vi.

General architecture

Almost all of the functionality in Emacs, including basic editing operations such as the insertion of characters into a document, is achieved through scripts written in a dialect of the Lisp programming language. The dialect used in GNU Emacs is known as Emacs Lisp (ELisp). The ELisp layer sits atop a stable core of basic services and platform abstraction written in the C programming language. In this Lisp environment, variables and functions can be temporarily modified with no need to recompile or restart Emacs.

Emacs operates on buffers containing text with additional attributes; every buffer maintains its own point (cursor location) and mark (another location, delimiting the selected region together with the point), the name of the file it is visiting (if applicable) and the set of active modes (exactly one major mode and any number of minor modes), which control editor behaviour through variables. Elisp code can be executed interactively through named commands, which can be bound to key presses or accessed by name; some commands evaluate arbitrary Elisp code from buffers (e.g. eval-region or eval-buffer).

Buffers are displayed in windows, which are tiled portions of the terminal screen or the GUI window (called a frame in Emacs terms; multiple frames are possible). Unless configured otherwise, windows include scroll bars, line numbers, a header line at the top (usually displaying the buffer title or filename) and a mode line at the bottom (usually listing the active modes and point position of the buffer).

Multiple windows can be opened onto the same buffer, for example to see different parts of a long text, and multiple buffers can share the same text, for example to take advantage of different major modes in a mixed-language file. The mode can also be changed manually as needed with M-x <mode name>.

Customizability

Portability

Emacs uses a layered architecture, with a Turing complete language running on top of a smaller central core. Because about three-fourths of the stock Emacs distribution (1266 of 1611 kLOC as of version 24.4) is written in the Elisp extension language , and the set of features implemented in Elisp code are automatically present once the C core (which implements the Elisp interpreter, weighing 247 kLOC as of 24.4) has been ported, porting Emacs to a new platform is considerably less difficult than porting an equivalent project consisting of native code only. Theoretically, only the core must be ported to the new platform; once the core is ported, the portions implemented in the language above that take minimal work to bring over.

Self-documenting

The first Emacs contained a help library that included documentation for every command, variable and internal function. Because of this, Emacs proponents described the software as self-documenting in that it presents the user with information on its normal features and its current state. Each function includes a documentation string that is displayed to the user on request, a practice that subsequently spread to programming languages including Lisp, Java, Perl, and Python. This help system can take users to the actual code for each function, whether from a built-in library or an added third-party library.

Emacs also has a built-in tutorial. Emacs displays instructions for performing simple editing commands and invoking the tutorial when it is launched with no file to edit. The tutorial is by Stuart Cracraft and Richard Stallman.

Culture

Church of Emacs

Main article: Editor war
Richard Stallman as St IGNUcius, a saint in the Church of Emacs

The Church of Emacs, formed by Richard Stallman, is a parody religion created for Emacs users.[39] While it refers to vi as the editor of the beast (vi-vi-vi being 6-6-6 in Roman numerals), it does not oppose the use of vi; rather, it calls proprietary software anathema. ("Using a free version of vi is not a sin but a penance."[40]) The Church of Emacs has its own newsgroup, alt.religion.emacs,[41] that has posts purporting to support this parody religion. Supporters of vi have created an opposing Cult of vi, argued by some Emacs users to be an attempt to "ape their betters".

Stallman has jokingly referred to himself as St IGNUcius, a saint in the Church of Emacs.[42]

Emacs pinky

There is folklore attributing repetitive strain injury to Emacs' strong dependence on modified keys called Emacs pinky,[43] although there is no scientific evidence for Emacs causing more such problems than other keyboard-heavy computer programs.

Users have addressed this through various approaches. Some users recommend simply using the two Control keys on typical PC keyboards like Shift keys while touch typing to avoid overly straining the left pinky.[44] Software-side methods include:[45]

Hardware solutions include special keyboards such as Kinesis's Contoured Keyboard, which places the modifier keys where they can easily be operated by the thumb, or the Microsoft Natural keyboard, whose large modifier keys are placed symmetrically on both sides of the keyboard and can be pressed with the palm of the hand.[43] Foot pedals can also be used.

The Emacs pinky is a relatively recent development. The Space-cadet keyboard on which Emacs was developed had oversized Control keys that were adjacent to the space bar and were easy to reach with the thumb.[53]

Vim advocates often cite Emacs pinky as a reason to switch, although some Vim users transpose their mode change key with the caps lock key for similar reasons.[54]

Terminology

The word emacs is sometimes pluralized as emacsen, by analogy with boxen and VAXen.[55]

See also

Notes

References

  1. ↑ "Emacs Timeline". Retrieved 11 August 2015.
  2. ↑ "GNU Emacs Manual". GNU Emacs Manual. FSF. Retrieved 24 November 2012.
  3. ↑ "Introducing Elfeed, an Emacs Web Feed Reader".
  4. ↑ "A Guided Tour of Emacs". Some users find that they can do almost all of their work from within Emacs.
  5. ↑ Bernard S. Greenberg. "Multics Emacs: The History, Design and Implementation".
  6. ↑ "GNU Emacs FAQ".
  7. ↑ Jamie Zawinski. "Emacs Timeline".
  8. 1 2 3 Adrienne G. Thompson. "MACSimizing TECO".
  9. ↑ "A history of Emacs". XEmacs Internals Manual. 2006-12-11. Retrieved 2007-08-22.
  10. ↑ Allombert, Bill. "Debian Popularity Contest". Editors report. Debian. Retrieved 22 November 2011.
  11. ↑ Arthur Samuel (March 1980). "Essential E" (PDF). Retrieved 2011-08-01.
  12. ↑ "EMACS vs. vi: The endless geek 'holy war'". "EMACS as such actually started out as a standards project," emails Guy Steele
  13. ↑ Richard M., Stallman. "The EMACS Full-Screen Editor". Retrieved 2007-09-14.
  14. ↑ "A cocky novice once said to Stallman: 'I can guess why the editor is called Emacs, but why is the justifier called Bolio?'. Stallman replied forcefully, Names are but names, Emack & Bolio's is the name of a popular ice cream shop in Boston town. Neither of these men had anything to do with the software.' His question answered, yet unanswered, the novice turned to go, but Stallman called to him, 'Neither Emacs nor Bolio had anything to do with the ice cream shop, either.'"
  15. 1 2 Stallman, Richard (March 26, 1981). EMACS: The Extensible, Customizable, Self-Documenting, Display Editor (PDF) (Technical report). MIT AI Lab. AI Memo 519a. Retrieved 2011-01-07.
  16. ↑ Leigh Klotz (2007-08-29). "email quoted in "Be Careful What You Joke About"". The New York Times. Retrieved 2010-05-01.
  17. ↑ "Comment by ZWEI's author Dan Weinreb". I wrote the second Emacs ever: the Lisp machine implementation, whose spec was "do what Stallman's PDP-10 (original) Emacs does", and then progressed from there. There's just a whole LOT of it. It took me and Mike McMahon endless hours to implement so many commands to make ZWEI/Zmacs.
  18. ↑ Owen Theodore Anderson (January 1979). "The Design and Implementation of a Display-Oriented Editor Writing System" (PDF). Retrieved 2012-09-09.
  19. ↑ "A History of Emacs".
  20. ↑ "emacs-devel msg 00872 (2014-09-29)". In retrospect 24.3 should have been named 25.1 and 24.4 should have been named 26.1. The .N thingy should really be kept only for bug-fix releases and neither of 24.3, 24.4, nor the previously planned 24.5 are bug-fix releases.
  21. ↑ Stoll, Clifford (1988). "Stalking the wily hacker". Communications of the ACM 31 (5): 484–497. doi:10.1145/42411.42412
  22. ↑ "New Git repository is up.".
  23. ↑ "Re: Looking for a new Emacs maintainer or team". gnu.org Mailing List. Retrieved 2008-02-23.; see also "Stallman on handing over GNU Emacs, its future and the importance of nomenclature"
  24. ↑ "Ugliest…repository…conversion…ever". twenty-nine years of continuous development by no fewer than 579 people
  25. ↑ Stephen J., Turnbull. "XEmacs vs. GNU Emacs". Retrieved 2012-10-02.
  26. ↑ "XEmacs is Dead. Long Live XEmacs!".
  27. ↑ FrontPage - Meadow Wiki
  28. ↑ "SXEmacs Website". Sxemacs.org. 2009-10-11. Retrieved 2009-11-08.
  29. ↑ "NotGNU Emacs Editor (Author's Official Download Site)". Notgnu.org. 2004-01-15. Retrieved 2009-11-08.
  30. ↑ "Zile home page".
  31. ↑ "QEmacs Homepage". Fabrice.bellard.free.fr. Retrieved 2009-11-08.
  32. ↑ "Lugaru Software Homepage".
  33. ↑ Christian Jullien. (1986). "EmACT on sourceforge". Christian Jullien. Retrieved 31 December 2011.
  34. ↑ "AMACS source".
  35. ↑ "apple2.org".
  36. ↑ "Cocoa text system".
  37. ↑ "SublemacsPro plugin for Sublime Text".
  38. ↑ "Init file".
  39. ↑ "Saint IGNUcius - Richard Stallman". Retrieved 29 January 2015.
  40. ↑ "The unabridged selective transcript of Richard M Stallman's talk at the ANU". Retrieved 29 January 2015.
  41. ↑ alt.religion.emacs newsgroup
  42. ↑ Saint IGNUcius - Richard Stallman
  43. 1 2 "How To Avoid The Emacs Pinky Problem". Xahlee.org. Retrieved 2009-11-08.
  44. ↑ "Emacs: Why You Should Not Swap {Caps Lock, Control} Keys". In touch typing, modifiers comes in pairs, such as ⇧ Shift key. The accepted ergonomic way to press modifier combinations is using one hand to press the modifier key and the other to press the letter key. Using 2 hands avoids single-hand straining its muscle.
  45. ↑ "EmacsWiki: Repeated Strain Injury". Retrieved 29 January 2015.
  46. ↑ "Moving The Ctrl Key". EmacsWiki. Last edited 2009-09-26 17:40 UTC by asdf (diff). Retrieved 2009-11-08. Check date values in: |date= (help)
  47. ↑ "ErgoEmacs". Retrieved 2014-04-28.
  48. ↑ "EmacsWiki: Ace Jump". Retrieved 29 January 2015.
  49. ↑ "Spacemacs". Retrieved 2015-04-20.
  50. ↑ BayleShanks (2009-10-07). "Sticky Modifiers". EmacsWiki. Retrieved 2009-11-08.
  51. ↑ "Viper Mode". EmacsWiki. Last edited 2009-07-19 22:39 UTC by AaronHawley (diff). Retrieved 2009-11-08. Check date values in: |date= (help)
  52. ↑ "At Home Modifier by Evdev". Retrieved 2015-04-14.
  53. ↑ "Why Emacs's Keyboard Shortcuts are Painful".
  54. ↑ "VimとEmacsのあいだで小指痛を叫んだけもの" (in Japanese). 2007-10-14.
  55. ↑ "VAXen". Catb.org. Retrieved 2009-11-08.

External links

Wikiquote has quotations related to: Emacs
Wikimedia Commons has media related to Emacs.
Wikibooks has more on the topic of: Emacs
This article is issued from Wikipedia - version of the Friday, May 06, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.