Commit cd6e7ded authored by adriana's avatar adriana

Initial revision

parent ad13daa491d8
john s jacobs anderson
<h1>XEmacs Screenshots</h1>
<p>This area of exists so XEmacs users can show
off the amazing amounts of customization possible with
XEmacs. If you've got a screenshot of XEmacs that you think
the world needs to see, send the location to
<a href=""></a>
(Please don't email images without checking.)
<li>Robin S. Socha: several shots from
<a href="">
Robin's XEmacs settings page</a> and
<a href="">
Robin's Gnus settings page</a>, showing an html
editting mode, a TeX editting mode, and Gnus, a news and
mail reading application that runs within XEmacs.
<br>Open in this window:
<a href="">[1]</a>
<a href="">[2]</a>
<a href="">[3]</a>
<a href="">[4]</a>
<a href="">[5]</a>
<a href="">[6]</a>
<a href="">[7]</a>
<br>Open in new window:
<a href="" target="new">[1]</a>
<a href="" target="new">[2]</a>
<a href="" target="new">[3]</a>
<a href="" target="new">[4]</a>
<a href="" target="new">[5]</a>
<a href="" target="new">[6]</a>
<a href="" target="new">[7]</a>
<li>Stephen Tse: a nice shot showing a Mule-enabled XEmacs running
<a href="">eicq</a>,
Stephen's ICQ client that runs within XEmacs.
<br>Open in this window:
<a href="">[1]</a>
<br>Open in new window:
<a href="" target="new">[1]</a>
<li>Didier Verna: a pair of shots, showing Gnus and a
customization buffer. Nice use of pixmap backgrounds!
<br>Open in this window:
<a href="Images/gnus.png">[1]</a>
<a href="Images/custom.png">[2]</a>
<br>Open in new window:
<a href="Images/gnus.png" target="new">[1]</a>
<a href="Images/custom.png" target="new">[2]</a>
<li>Charles G Waldman: a nice shot showcasing pixmap
backgrounds,multiple frames with multiple windows, and a
customized vm.
<br>Open in this window:
<a href="">[1]</a>
<br>Open in new window:
<a href="" target="new">[1]</a>
<br>Instructions for duplicating the customization are
available <a href="">at
Charles's site</a>.
XEmacs vs. GNU Emacs
<h1>XEmacs vs. GNU Emacs</h1>
<P>There are currently irreconcilable differences in the views
about technical, programming, design and organizational
matters between RMS and the XEmacs development team which
provide little hope for a merge to take place in the
short-term future.
<P>If you have a comment to add regarding the merge, it is a
good idea to avoid posting to the newsgroups, because of the
very heated flamewars that often result. Mail your questions
<a HREF=""></A>
<A HREF=""></A>.
<h2>Difference between XEmacs and GNU Emacs 19, from the XEmacs Point of View</h2>
<p>In XEmacs 20, characters are first-class objects.
Characters can be converted to integers, but are not integers.
FSF 19, XEmacs 19, and Mule represent them as integers.
<p>In XEmacs, events are first-class objects. FSF 19
represents them as integers, which obscures the differences
between a key gesture and the ancient ASCII code used to
represent a particular overlapping subset of them.
<p>In XEmacs, keymaps are first-class opaque objects. FSF 19
represents them as complicated combinations of association
lists and vectors. If you use the advertised functional
interface to manipulation of keymaps, the same code will work
in XEmacs, Emacs 18, and GNU Emacs 19; if your code depends on
the underlying implementation of keymaps, it will not.
<p>XEmacs uses "extents" to represent all non-textual aspects
of buffers; FSF 19 uses two distinct objects, "text
properties" and "overlays", which divide up the functionality
between them. Extents are a superset of the functionality of
the two FSF data types. The full FSF 19 interface to text
properties and overlays is supported in XEmacs (with extents
being the underlying representation).
<p>Extents can be made to be copied into strings, and thus
restored by kill and yank. Thus, one can specify this
behavior on either "extents" or "text properties", whereas in
FSF 19 text properties always have this behavior and overlays
never do.
<p>Many more packages are provided standard with XEmacs than
with FSF 19.
<p>Images of arbitrary size can be embedded in a buffer.
<p>Variable width fonts work.
<p>The height of a line is the height of the tallest font on
that line, instead of all lines having the same height.
<p>XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls,
which makes it be a more well-behaved X citizen (and also
improves portability). A result of this is that it is
possible to include other Xt "Widgets" in the XEmacs window.
Also, XEmacs understands the standard Xt command-line
<p>XEmacs provides support for ToolTalk on systems that have
<p>XEmacs can ask questions using popup dialog boxes. Any
command executed from a menu will ask yes/no questions with
dialog boxes, while commands executed via the keyboard will
use the minibuffer.
<p>XEmacs has a built-in toolbar. Four toolbars can actually
be configured: top, bottom, left, and right toolbars.
<p>XEmacs has vertical and horizontal scrollbars. Unlike in
FSF 19 (which provides a primitive form of vertical
scrollbar), these are true toolkit scrollbars. A look-alike
Motif scrollbar is provided for those who don't have
Motif. (Even for those who do, the look-alike may be
preferable as it is faster.)
<p>If you're running on a machine with audio hardware, you can
specify sound files for XEmacs to play instead of the default
X beep. See the documentation of the function load-sound-file
and the variable sound-alist.
<p>An XEmacs frame can be placed within an "external client
widget" managed by another application. This allows an
application to use an XEmacs frame as its text pane rather
than the standard Text widget that is provided with Motif or
Athena. XEmacs supports Motif applications, generic Xt
(e.g. Athena) applications, and raw Xlib applications.
<h2>The FSF Point of View</h2>
<p><A HREF="">Richard Stallman</A> writes:
<P>XEmacs is GNU software because it's a modified version of a
GNU program. And it is GNU software because the FSF is the
copyright holder for most of it, and therefore the legal
responsibility for protecting its free status falls on us
whether we want it or not. This is why the term "GNU XEmacs"
is legitimate.
<P>But in another sense it is not GNU software, because we
can't use XEmacs in the GNU system: using it would mean paying
a price in terms of our ability to enforce the GPL. Some of
the people who have worked on XEmacs have not provided, and
have not asked other contributors to provide, the legal papers
to help us enforce the GPL. I have managed to get legal
papers for some parts myself, but most of the XEmacs
developers have not helped me get them.
XEmacs was possible because free software means that anyone can change
it and distribute a modified version. I have no regrets about
establishing this freedom for Emacs. Everyone should have the freedom
to change any program, and this is not limited to changes that the
original author likes.
<P>Many people have taken advantage of the freedom to change
GNU Emacs, over the last decade. Most of them were willing to
cooperate on integrating their changes into Emacs. XEmacs
arose as a separate forked version because some of the
developers--starting with Zawinski--were unwilling to do that.
<P>People should have the freedom to decide what to work on,
including the freedom to compete with the GNU project, but
it's a shame when they make that choice. The whole community
loses when someone chooses competition rather than
<P>But this is worse than competition--it is unfair
competition. The XEmacs developers can and do copy code they
like from Emacs. If I could copy the code I like from XEmacs
in the same way, at least the rivalry would be fair. But I
can't do that't, because substantial parts of XEmacs don't
have legal papers, or don't have known authors.
<P>As long as we cannot use XEmacs in the GNU system, the GNU
project has to make sure that Emacs is not left behind. In
other words, we have to behave like rivals too, even though we
wish there were no rivalry. When XEmacs developers try to
persuade people to use, test, fix and enhance XEmacs instead
of Emacs, the GNU project can't sit still; we need them to
use, test, fix and enhance Emacs instead.
<P>There is good code in XEmacs, which I'd be happy to have in
a merged Emacs any day. But I cannot copy it out of XEmacs
myself because of the uncertain authorship and/or lack of
legal papers.
<P>This problem could probably be resolved, at least for large
parts of XEmacs, with substantial help from the authors of
that code. Otherwise, the GNU project has to write or find
replacements for it.
<P>I invite people who like Emacs, and want the best possible
version of Emacs to be available for use in the GNU system, to
help in one way or the other.
<p><b>Sources:</b> <a href="">FAQ</a>
item 1.0.5, and XEmacs 21.0 NEWS file
Year 2000 Statement
john s jacobs anderson, reworking old content with no author listed
<h1>Year 2000 Statement</h1>
<p> As far as we know, XEmacs is year 2000 compliant. Our
position on year 2000 compliance is the same as the
<a href="">position of
the Free Software Foundation.</a>
<p> Although the XEmacs Development team offers no guarantee
that there will be no year 2000 bugs, there have been actual
tests to back up our feeling that XEmacs will work across the
year 2000 transition. A member of the XEmacs community has
built XEmacs on a post-2000 `time machine', and the resulting
executables have performed correctly both on post-2000 and
pre-2000 machines.
<p> Those interested in formal year 2000 support for XEmacs
should contact
<a href=""></a>.
Created by XEmacs
<h1>Created with XEmacs</h1>
<img src="Images/cbx.jpg" alt="Created with XEmacs!" height="54" width="150">
<img src="Images/cbxSmall.jpg" alt="Created with XEmacs!" height="36" width="100">
<p>Do you use XEmacs to build your websites? Would you like to
be listed as a <a href="About/created.html#list">Created with XEmacs site</a>?
Just follow these steps:
<ol type="1">
<li>Download the one of the above badges. Please don't link
directly to the images on!
<li>Put the image on your site. Please link the image back
to this page if possible.
<li>Send mail to <a href=""></a>
with the URL where the logo is displayed, and your site will
be added to <a href="About/created.html#list">the list</a>.
<h1><a name="list">Sites that have been Created with XEmacs</a></h1>
<li><a href=""></a>
<li><a href="">GeneHack</a>
<li><a href="">interhack</a>
<li><a href=""></a>
<li><a href="">Colin and Marleny Rafferty</a>
<li><a href="">Electronic CAD &amp; Reliability Group</a>
<li><a href="">Cafe Eccellente</a>
<li><a href="">Monadnock Linux Users Group</a>
<li><a href="">R. J. Bruce</a>
<li><a href="">U.S.D.A. Southwest Watershed Research Center</a>
<li><a href="">Rado Faletic's home page</a>
<li><a href="">RKBA</a>
<li><a href="">White Dragon Website</a>
<li><a href="">Curtis Consulting</a>
<li><a href=""></a>
<li><a href="">La Esquina del Ping&uuml;ino (The Penguin's Place)</a>
<li><a href="">Kentucky Council of Teachers of English</a>
<li><a href="">Jochen-Kpper</a>
<li><a href="">rt_com</a>
<li><a href="">Survit's Home Page</a>
<li><a href="">Autohaus Kl&ouml;k &amp; Str&ouml;hle GmbH</a>
<li><a href="">eicq - An XEmacs ICQ Client</a>
<li><a href=""></a>
<li><a href="">Salman Ahmed's home page</a>
<li><a href="">monochromatic dot net</a>
<li><a href="">Erik's Masonic Journey</a>
History of XEmacs
john s jacobs anderson, stealing content from the FAQ
<h1>The History of XEmacs</h1>
<P>An alternative to GNU Emacs, XEmacs was originally based on
an early alpha version of FSF's version 19, and has diverged
quite a bit since then. XEmacs was known as Lucid Emacs
through version 19.10. Almost all features of GNU Emacs are
supported in XEmacs. The maintainers of XEmacs actively track
changes to GNU Emacs while also working to add new features.
<p>More information about the current and past developers of
XEmacs, as well as some information about the history of
XEmacs development is available within XEmacs by selecting
<strong>'About XEmacs...' </strong> from the
<strong>Help</strong> menu. Detailed information is available
in the <a href="News/">NEWS files</a> from each release.
<p><b>Source:</b> <a href="">FAQ</a> item 1.0.1
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment