History of Emacs and XEmacs

25 March 2007

Last time we looked how to get Emacs. Before you get bogged down in information, open Emacs and type into the box. See how far you can get without reading anything.

Emacs and Emacsen

Versions of Emacs-type editors have been going around for over 30 years. In the 1970s, people like Richard Stallman invented concepts such as live interactive editing and inline help that are common in all programs now. The standard Emacs today is GNU Emacs. The second most common is XEmacs. There are a load of smaller versions, as well as some defunct versions, but these are the important ones. Why two main versions? For purely arbitrary historical reasons.

A little bed time story

By 1991, there had not been a new version of Emacs for a few years, and the FSF was extremely slow at bringing out version 19, and a company called Lucid tried to get GNU Emacs out of the door to satisfy its own customers (it sold a set of development tools). Lucid was willing to throw as many programmers and as much money at the problem as required, which turned out to be $200,000, which was a lot of money back then.

However, this was before Internet based collaboration facilities such as Sourceforge existed, so the large fast-moving team of people at Lucid had trouble getting the very small team at the Free Software Foundation to understand the code they were making, not least because the main FSF Emacs maintainer to this point now worked for Lucid, and the new fulltime maintainer at the FSF had not yet got familar with the Emacs codebase.

This was not the only problem, the FSF were not willing to use any externally produced code unless Richard Stallman had worked through and edited it himself, while Lucid had commercial pressures to get its development tools out of the door. This was not the last time in the open source world that there has been conflict between more academic computer scientists who want architectural perfection and commercial companies who need to make a release. This is just one of those things that happens in the real world.

Lucid went ahead and shipped the version of Emacs that it had, which it assumed would be very similar to the next GNU Emacs, and that everyone would all come back together around the same codebase. Over time it dawned that this was not going to happen, and then the FSF eventually came out with their own different version of Emacs 19, rejecting most of the Lucid improvements.

All the king's horses...

So for a while in the early 1990s, Lucid Emacs, was almost the main Emacs, and was far more feature complete than GNU Emacs, not least because it made it really easy for anyone to get involved and improve the editor. It still has 2-3 releases per year while GNU Emacs takes a couple of years to get one release out.

Lucid Emacs was soon renamed XEmacs as a condition for SUN providing full- time developers. X as in generic, e.g. 'brand X', rather than the trademarked 'Lucid'. (Nothing to do with X windows, at the point Lucid Emacs became XEmacs, still not that many people were using X Windows, especially among mainframe users and other hardcore Unix people - the key Emacs users).

So now we are in the mid-1990s and Lucid, which had been a major name in the Lisp era, never really made the transition into the C++ market which became dominated by Borland, Microsoft, etc, or the Java market which was just beginning. It disappeared from the scene before the Web and Apache would bring very high-level languages back in to fashion.

By the turn of the millennium, GNU Emacs had caught up with XEmacs, with open online development and so on, but too much water had passed under the bridge, and with the rise of lots of other programs, having more than one Emacs does not seem that strange. More strange than two word processors, as Emacs is a development platform and a Lisp interpreter as well as an editor, but there are so many more computer users now, and far more contributors.

For most users, the two versions are essentially the same, although each has its own strengths, for example, GNU Emacs has fantastic Unicode support, while XEmacs has some small performance gains. From here on in, the difference is irrelevant, I will just say 'Emacs' to cover them both.

Funnily enough, some of the hackers from the fork period would become famous elsewhere, Marc Andreessen who wrote another early Emacs fork (Epoch) would go on to write Mosaic, which would later be bought by Microsoft and rebranded as Internet Explorer, while Jamie Zawinski, one of the first major XEmacs hackers, wrote much of Netscape Navigator, and was also involved in the early Mozilla. He now runs his own nightclub in San Francisco (complete with public Linux terminals) and maintains XScreenSaver.

What do you have to say?

Show Editing Help


About

Hello, my name is Zeth, I'll be your host here.

Command Line Warriors is about taking control of your own technology, it looks at our experiences of computing; especially using GNU/Linux, the Python programming language, the command-line and issues such as techno-ethics, best practices and whatever is cool now. If you take control of your technology then you are a Warrior too!

This site is your site too which means that you can contribute and get involved. You can leave comments using the facility provided. For me, the comments and discussions are by far the best part of the site. So please do have your say!

Latest Discussions

Nui

July 18, 2008
Hmm, this would be more persuasive as an argument with some evidence. I am a happy admin of Windows and a novice user of Linux, so I have taken the ...
Give Linux a chance

Paddy3118

July 18, 2008
Hi, I too work with Electronic Design Automation tools, where Tcl is used extensively. I tend to only occasionally have to write in Tcl and so find the TclTutor utility: ...
Python and TCL

Cliff Wells

July 17, 2008
I personally cannot live without the Web Developer extension or Firebug. Unfortunately these are probably both among the more difficult to port extensions. Given how poorly Firefox functions on Linux ...
Will Epiphany be able to compete with Firefox's extensions?

making money on the internet

July 17, 2008
[url=http://www.divinecaroline.com/public/user/profile?user_id=83997]extra money 101waystoincome.com[/url]
A year after my 2007 predictions - the score card

Leatherjackets99

July 16, 2008
New Style in Leather Jackets For Man and Woman at http://www.Leatherjackets99.com They Offer Free Shipment Worldwide.
Email Syntax Check in Python

Åke Forslund

July 13, 2008
I'm pretty much a novice in both of these languages but I find them both easy to use and preform the tasks I give them. However I rarely use them ...
Python and TCL

Christopher Thoday

July 12, 2008
A single test is not sufficient to give you confidence that the algorithm is working. You should make 'number' an argument of 'main' so that you can test some boundary ...
Python and TCL

paul21

July 10, 2008
Shame on Mozilla. They should make developers specify the extension license before hosting it. They should show the license next to download button as well.
Are your Firefox extensions proprietary software?

Tris

July 8, 2008
Justin - You say they had not heard of Linux? That doesn't sound very professional to me!
Give Linux a chance

michael

July 8, 2008
what about Galeon? in Gnome i use Galeon mostly. it is fast and stable and has a nice portal with search masks for Debian, FSF, Freshmeat and so on. wtf ...
Will Epiphany be able to compete with Firefox's extensions?

vermin

July 7, 2008
> Eventually, after a bit of digging and Googling, I found their Toolbar-License... You simply found the license of the StumbleUpon Toolbar for Internet Explorer. This is another product, much ...
Are your Firefox extensions proprietary software?

Andrew West

July 6, 2008
Both the Python and the Tcl example could do with error checking. While at first this may not seem on topic with the post I think it better shows the ...
Python and TCL

Kurushiyama

June 30, 2008
XML is no replacement for SGML, it's a subset.
An Introduction to ReStructuredText