Commits

Anonymous committed 31642a4

Import FAQ again

  • Participants
  • Parent commits 5d7c243
  • Branches adriana
  • Tags re-import-as-FAQ

Comments (0)

Files changed (116)

FAQ/alvin.jpeg

Added
New image

FAQ/c-mode.gif

Added
New image

FAQ/cthomp.gif

Added
New image

FAQ/cthomp.jpeg

Added
New image

FAQ/cy_ball.gif

Added
New image

FAQ/ediff.gif

Added
New image

FAQ/emacs-xemacs.txt

+I'd like rms to:
+
+
+(Steven Turnbull)
+find a term that differs Emacs from XEmacs, but does not imply XEmacs
+as a deviant version.  
+
+Emphasize that the FSF development team are willing to make use of
+patches to XEmacs-beta as long as the authors have signed the legal
+papers.
+
+Aknowledge the work by Steven L. Baur and others in getting
+signatures.
+
+(Hrvoje Niksic)
+
+Aknowledge the effort by the XEmacs Development team, deny "hating"
+it.
+
+
+
+
+
+ /* --- COMMON TO ALL ARTICLES --- */
+
+BODY { margin-left: 8%; margin-right: 5%;   
+       text-align: left; background: white none; color: black }
+
+
+DFN  { font-style: italic }
+
+CODE { color: #0000AA; background: white none; }
+
+H1,H2,H3,H4,H5,H6 { font-family: Arial, Helvetica, Sans-Serif;
+                    text-align: left }
+
+H1   {  padding-top: 3em;  font-size: 200% } /* Overrides above rule as it appears below it */
+
+.subtitle { text-align: center; font-size: 60% }
+
+H2   { padding-top: 2em }
+
+H3   { padding-top: 1em }
+
+DT   { font-weight: bold }
+
+.uferdig   { color: #AA0000     } /* Used for parts not yet finished */
+
+P.center   { text-align: center }
+P.contents { text-align: center; padding-bottom: 2em }
+P.note     { background: white none; color: #AA0000; font-weight: bold }
+
+DL        { margin-left: 5% }
+DT        { font-weight: bold }
+DD        { padding-bottom: 0.7em }
+
+PRE       { background: white none; color: #0000AA }
+
+A:link    { background: white none; color: #0000EE }
+A:visited { background: white none; color: #551A8B }
+
+HR        { padding-top: 1em }
+
+ADDRESS   { text-align: left; font-size: small; font-style: italic }
+
+DIV.partof     { font-size: small; text-align: right }
+
+#problemstilling { margin-left: 4%; margin-right: 4%; font-style: italic }
+
+BLOCKQUOTE { margin-left: 5%; font-style: italic }
+
+P.origin   { text-align: right; margin-left: 10% }
+
+P.termdef  { margin-left: 10%; margin-right: 10%;
+             background-color: #f5dcb3; border-width: 1px;
+             padding: 15px }
+
+/* --- ONLY FOR THE CSS INTRO --- */
+
+LI.serif      { font-family: serif      }
+LI.sans-serif { font-family: sans-serif }
+LI.fantasy    { font-family: fantasy    }
+LI.monospace  { font-family: monospace  }
+LI.cursive    { font-family: cursive    }

FAQ/fixed.gif

Added
New image

FAQ/gnus-topics.gif

Added
New image

FAQ/gnuscape.jpg

Added
New image

FAQ/grad_blu.gif

Added
New image

FAQ/hniksic.jpeg

Added
New image

FAQ/hwg.gif

Added
New image

FAQ/index.content

+%title%
+Frequently asked questions about XEmacs
+
+%author%
+Sandra Wambold
+
+%main%
+
+<!--
+Go to the first, previous, <A HREF="xemacs-faq_2.html">next</A>, <A HREF="xemacs-faq_8.html">last</A> section, <A HREF="xemacs-faq_toc.html">table of contents</A>.
+<P><HR><P>
+-->
+
+<H1><A NAME="SEC1" HREF="faq/xemacs-faq_toc.html#TOC1">Introduction</A></H1>
+<P>
+This is the guide to the XEmacs Frequently Asked Questions list--a
+compendium of questions and answers pertaining to one of the finest
+programs ever written.  It is much more than just a Text Editor.
+</P>
+<P>
+This FAQ is freely redistributable.  I take no liability for the
+correctness and safety of any procedures or advice given here.  This
+FAQ is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.
+</P>
+<P>
+If you have a Web browser, the official hypertext version is at
+</P>
+<P>
+<A HREF="http://www.xemacs.org/faq/xemacs-faq.html">http://www.xemacs.org/faq/xemacs-faq.html</A>.
+</P>
+<P>
+This version is somewhat nicer than the unofficial hypertext versions
+that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
+archives.
+</P>
+<P>
+This document is available in several different formats:
+<UL>
+<LI>
+<A HREF="faq/xemacs-faq.txt">As a single ASCII file</A>, produced by
+<CODE>makeinfo --no-headers</CODE>
+<LI>
+<A HREF="faq/xemacs-faq.dvi">As a .dvi file</A>, as used with
+<A HREF="http://www.tug.org">TeX.</A>
+<!--
+<LI>
+As a PostScript file <A HREF="xemacs-faq-a4.ps">in A4 format</A>,
+as well as in <A HREF="xemacs-faq-letter.ps">letter format</A>
+-->
+<LI>
+In html format, <A HREF="faq/xemacs-faq_2.html">split by chapter</A>, or in
+<A HREF="faq/xemacs-faq.html">one monolithic</A> document.
+<LI>
+The canonical version of the FAQ is the texinfo document
+<A HREF="faq/xemacs-faq.texi">man/xemacs-faq.texi</A>.
+<!--
+You'll need
+<A HREF="mswindows-faq.texi">man/mswindows-faq.texi</A> as well.
+-->
+</UL>
+<!--
+<P><HR><P>
+Go to the first, previous, <A HREF="faq/xemacs-faq_2.html">next</A>, <A HREF="xemacs-faq_8.html">last</A> section, <A HREF="xemacs-faq_toc.html">table of contents</A>.
+>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
+<HTML>
+<HEAD>
+<!-- This HTML file has been created by texi2html 1.52
+     from /usr/local/src/xemacs-20/man/xemacs-faq.texi on 4 May 1999 -->
+
+<TITLE>Frequently asked questions about XEmacs - Introduction</TITLE>
+<LINK REL=StyleSheet HREF="faq.css" TYPE="text/css" MEDIA=screen>
+<LINK REL="next"     HREF="xemacs-faq_2.html">
+<LINK REL="contents" HREF="xemacs-faq_toc.html">
+</HEAD>
+<BODY>
+<p>
+<a href="http://www.xemacs.org">
+<img src="xemacs.gif" width="388" height="145" border="0" alt="[XEmacs Logo]">
+</a>
+</p>
+Go to the first, previous, <A HREF="xemacs-faq_2.html">next</A>, <A HREF="xemacs-faq_8.html">last</A> section, <A HREF="xemacs-faq_toc.html">table of contents</A>.
+<P><HR><P>
+
+
+<H1><A NAME="SEC1" HREF="xemacs-faq_toc.html#TOC1">Introduction</A></H1>
+
+<P>
+This is the guide to the XEmacs Frequently Asked Questions list--a
+compendium of questions and answers pertaining to one of the finest
+programs ever written.  It is much more than just a Text Editor.
+
+</P>
+<P>
+This FAQ is freely redistributable.  I take no liability for the
+correctness and safety of any procedures or advice given here.  This
+FAQ is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.
+
+</P>
+<P>
+If you have a Web browser, the official hypertext version is at
+
+</P>
+<P>
+<A HREF="http://www.xemacs.org/faq/xemacs-faq.html">http://www.xemacs.org/faq/xemacs-faq.html</A>.
+
+</P>
+<P>
+This version is somewhat nicer than the unofficial hypertext versions
+that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
+archives.
+
+</P>
+
+
+<P>
+This document is available in several different formats:
+
+<UL>
+<LI>
+
+<A HREF="xemacs-faq.txt">As a single ASCII file</A>, produced by
+<CODE>makeinfo --no-headers</CODE>
+<LI>
+
+<A HREF="xemacs-faq.dvi">As a .dvi file</A>, as used with
+<A HREF="http://www.tug.org">TeX.</A>
+<!--
+<LI>
+
+As a PostScript file <A HREF="xemacs-faq-a4.ps">in A4 format</A>,
+as well as in <A HREF="xemacs-faq-letter.ps">letter format</A>
+-->
+<LI>
+
+In html format, <A HREF="xemacs-faq_2.html">split by chapter</A>, or in
+<A HREF="xemacs-faq.html">one monolithic</A> document.
+<LI>
+
+The canonical version of the FAQ is the texinfo document
+<A HREF="xemacs-faq.texi">man/xemacs-faq.texi</A>.
+<!--
+You'll need
+<A HREF="mswindows-faq.texi">man/mswindows-faq.texi</A> as well.
+-->
+
+</UL>
+
+</P>
+
+<P><HR><P>
+Go to the first, previous, <A HREF="xemacs-faq_2.html">next</A>, <A HREF="xemacs-faq_8.html">last</A> section, <A HREF="xemacs-faq_toc.html">table of contents</A>.
+</BODY>
+</HTML>

FAQ/iu.jpg

Added
New image

FAQ/jwz.gif

Added
New image

FAQ/lcylarrw.gif

Added
New image

FAQ/left-purple.gif

Added
New image

FAQ/mrb.jpeg

Added
New image

FAQ/new.gif

Added
New image

FAQ/old/XEmacs-FAQ-changes.html

+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//2.0">
+<HTML>
+<HEAD>
+<TITLE>Changes to the XEmacs FAQ for the Month of June 1996</TITLE>
+</HEAD>
+<BODY>
+<H1>Changes to the XEmacs FAQ for the Month of June 1996</H1>
+<H2>Modified Questions</H2>
+<OL>
+<LI> <A HREF="xemacs-faq.html#Q1_4_1">Q1.4.1</A> June 11 (Finding sample.emacs,
+and determining where the XEmacs etc directory is)
+<LI> <A HREF="xemacs-installation.html#Q2_1_1">Q2.1.1</A> June 11 and June 17
+(Crash reporting hints)
+<LI> <A HREF="xemacs-installation.html#Q2_1_2">Q2.1.2</A> June 11 (Viewing
+Minibuffer error messages in a buffer)
+<LI> <A HREF="xemacs-installation.html#Q2_1_8">Q2.1.8</A> June 11 (Retitled
+<SAMP>got (wrong-type-argument color-instance-p nil) and I don't know
+why!</SAMP>)
+<LI> <A HREF="xemacs-customization.html#Q3_0_2">Q3.0.2</A> June 11
+(eval-expression keybinding)
+<LI> <A HREF="xemacs-customization.html#Q3_0_4">Q3.0.4</A> June 5 (Adding
+directories to load-path)
+<LI> <A HREF="xemacs-customization.html#Q3_1_8">Q3.1.8</A> June 5 (Starting
+XEmacs iconic)
+<LI> <A HREF="xemacs-customization.html#Q3_2_4">Q3.2.4</A> June 11 (XEmacs
+and the global colormap)
+<LI> <A HREF="xemacs-customization.html#Q3_3_1">Q3.3.1</A> June 11 (Making
+the modeline go away)
+<LI> <A HREF="xemacs-customization.html#Q3_4_1">Q3.4.1</A> June 11 (Multi-
+headed displays)
+<LI> <A HREF="xemacs-customization.html#Q3_5_4">Q3.5.4</A> June 11 (Globally
+binding Delete)
+<LI> <A HREF="xemacs-customization.html#Q3_5_8">Q3.5.8</A> June 11 (Binding
+[ delete-forward ])
+<LI> <A HREF="xemacs-customization.html#Q3_5_9">Q3.5.9</A> June 11 (Making
+Delete key delete forwards)
+<LI> <A HREF="xemacs-customization.html#Q3_5_10">Q3.5.10</A> June 11 (Sticky
+modifier keys)
+<LI> <A HREF="xemacs-customization.html#Q3_8_1">Q3.8.1</A> June 11 (Making
+the menubar go away)
+p<LI> <A HREF="xemacs-customization.html#Q3_8_5">Q3.8.5</A> June 11 (Making
+the toolbar go away to a key binding)[ <STRONG>Warning</STRONG> ]
+<LI> <A HREF="xemacs-customization.html#Q3_8_6">Q3.8.6</A> June 11 (Making
+the toolbar go away)[ <STRONG>Warning</STRONG> ]
+<LI> <A HREF="xemacs-customization.html#Q3_9_1">Q3.9.1</A> June 11 (Making
+the scrollbar go away)
+<LI> <A HREF="xemacs-customization.html#Q3_10_1">Q3.10.1</A> June 11 (Changing
+selection highlight)
+<LI> <A HREF="xemacs-customization.html#Q3_10_2">Q3.10.2</A> June 11 (Automatic
+deletion of selection when you start typing)
+<LI> <A HREF="xemacs-customization.html#Q3_10_3">Q3.10.3</A> June 11 (Isearch
+highlighting)
+<LI> <A HREF="xemacs-customization.html#Q3_10_4">Q3.10.4</A> June 11 (Turning
+off <KBD>C-x C-p</KBD> highlighting).
+<LI> <A HREF="xemacs-subsystems.html#Q4_2_1">Q4.2.1</A> June 6 (Gnus FAQ URL)
+<LI> <A HREF="xemacs-subsystems.html#Q4_3_4">Q4.3.4</A> June 8 (Netscape
+Movemail -vs- XEmacs Movemail)
+<LI> <A HREF="xemacs-miscellaneous.html#Q5_3_9">Q5.3.9</A> June 11 (Abbrev
+mode explanation)
+</OL>
+<H2>New Questions</H2>
+<OL>
+<LI> <A HREF="xemacs-faq.html#Q1_3_5">Q1.3.5</A> June 13 (Explanation of
+non-English input methods)
+<LI> <A HREF="xemacs-faq.html#Q1_3_6">Q1.3.6</A> June 13 (MULE coding
+standards)
+<LI> <A HREF="xemacs-faq.html#Q1_4_3">Q1.4.3</A> June 6 (XEmacs tutorial locations)
+<LI> <A HREF="xemacs-faq.html#Q1_4_4">Q1.4.4</A> June 6 (Writing a simple interactive function)
+<LI> <A HREF="xemacs-faq.html#Q1_4_5">Q1.4.5</A> June 6 (Binding a function to a key)
+<LI> <A HREF="xemacs-faq.html#Q1_4_6">Q1.4.6</A> June 7 (Functions &amp; Macros)
+<LI> <A HREF="xemacs-installation.html#Q2_0_6">Q2.0.6</A> June 11 (Help with
+strange crashes)
+<LI> <A HREF="xemacs-installation.html#Q2_0_7">Q2.0.7</A> June 15 (Libraries
+in non-standard locations)
+<LI> <A HREF="xemacs-installation.html#Q2_0_8">Q2.0.8</A> June 16 (Where is
+_h_errno?)
+<LI> <A HREF="xemacs-installation.html#Q2_1_9">Q2.1.9</A> June 11 (XEmacs
+-vs- OpenWindows 3.0 X server)
+<LI> <A HREF="xemacs-installation.html#Q2_1_10">Q2.1.10</A> June 11 (Warnings
+from incorrect key modifiers)
+<LI> <A HREF="xemacs-installation.html#Q2_1_11">Q2.1.11</A> June 12 (YAM of
+the old <CODE>set-text-properties</CODE> problem)
+<LI> <A HREF="xemacs-installation.html#Q2_1_12">Q2.1.12</A> June 13 (DEC OSF1
+C Compiler Optimization bugs)
+<LI> <A HREF="xemacs-installation.html#Q2_1_13">Q2.1.13</A> June 16
+(Create_process problems on HP/UX 10.10)
+<LI> <A HREF="xemacs-installation.html#Q2_1_14">Q2.1.14</A> June 17 (Problems
+with <KBD>C-g</KBD>)
+<LI> <A HREF="xemacs-installation.html#Q2_1_15">Q2.1.15</A> June 17 (Detailed
+hints on debugging problems in XEmacs)
+<LI> <A HREF="xemacs-customization.html#Q3_2_5">Q3.2.5</A> June 11 (Tty
+colors)
+<LI> <A HREF="xemacs-customization.html#Q3_10_5">Q3.10.5</A> June 11 (Selection
+disappears when paging through buffer and reaching the end).
+<LI> <A HREF="xemacs-subsystems.html#Q4_0_10">Q4.0.10</A> June 17 (Limiting
+VM to a single frame).
+<LI> <A HREF="xemacs-subsystems.html#Q4_1_2">Q4.1.2</A> June 11 (Running
+W3 from behind a firewall).
+<LI> <A HREF="xemacs-subsystems.html#Q4_2_3">Q4.2.3</A> June 17 (Limiting
+Gnus to a single frame).
+<LI> <A HREF="xemacs-subsystems.html#Q4_7_2">Q4.7.2</A> June 11 (Emacs Lisp
+Spreadsheets anyone?)
+<LI> <A HREF="xemacs-miscellaneous.html#Q5_0_16">Q5.0.16</A> June 9 (Auto
+Show Mode)
+</OL>
+<H2>Deleted Questions</H2>
+<H2>Other Changes</H2>
+<OL>
+<LI> Added toolbar document linkage (June 6)
+<LI> Added graphical navigational buttons for trailing-edge browsers (June 7)
+</OL>
+</HTML>

FAQ/old/index.html

+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//2.0">
+<HTML>
+<HEAD>
+<TITLE>XEmacs Editor FAQ [1/6]</TITLE>
+<!-- Created by: Andreas Kaempf,  2-Dec-1997 -->
+<!-- Changed by: Andreas Kaempf, 03-Jul-1997 -->
+<LINK REV=MADE HREF="mailto:steve@altair.xemacs.org">
+<LINK REL=Next HREF="xemacs-installation.html">
+<META NAME="description" CONTENT="Frequently Asked Questions about XEmacs the Text Editor">
+<META NAME="keywords" CONTENT="XEmacs,X Windows,GNU,Emacs,Text Editors,FAQ">
+</HEAD>
+<BODY>
+<A HREF="http://www.eff.org/blueribbon.html">
+<IMG SRC="rib_bar_wh.gif" ALT=""></A>
+<A HREF="xemacs-installation.html"><IMG SRC="right-purple.gif" ALT=""></A>
+<BR>
+<A HREF="http://www.xemacs.org/">
+<IMG SRC="xemacs.gif" ALT=""></A>
+<H1>XEmacs FAQ [1/6]</H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: ">Introduction</H2>
+<P>
+This is the guide to the XEmacs Frequently Asked Questions list it is 
+a compendium of questions and answers pertaining to one of the finest
+programs ever written.  It is much more than just a Text Editor.
+<P>
+Learning XEmacs is a lifelong activity.  I've been using Emacs for
+over a decade now, and I'm still discovering new features.  Therefore
+this document cannot be complete.  Instead it is aimed at the person
+who is either considering XEmacs for their own use, or has just
+obtained it and is wondering what to do next.  It is also useful as a
+reference to available resources.
+<P>
+The previous maintainer of the FAQ was Anthony Rossini
+&lt;rossini@stat.sc.edu&gt;, who started it, after getting tired of
+hearing JWZ complain about repeatedly having to answer questions.
+Ben Wing &lt;ben@666.com&gt; and Chuck Thompson &lt;cthomp@xemacs.org&gt;, the
+principal authors of XEmacs, then took over and Ben did a massive update
+reorganizing the whole thing.  At which point Anthony took back over, but
+then had to give it up again .  Some of the other contributors to this
+FAQ are listed later in this document.
+<P>
+The previous version was converted to hypertext format, and edited by 
+Steven L. Baur &lt;steve@altair.xemacs.org&gt;.  
+<P>
+Since Steve Baur is so busy putting out multiple versions of XEmacs I
+have taken on the task of maintaining the FAQ.  I use XEmacs on a daily
+basis and I wanted to give something back to the community that has made
+XEmacs possible.  If you notice any errors or items which should be
+added or amended to this FAQ please send email to Andreas Kaempf
+&lt;andreas@sccon.com&gt;. Include XEmacs FAQ on the Subject: line.
+<P>
+This FAQ is freely redistributable.  I take no liability for the
+correctness and safety of any procedures or advice given
+here.  This FAQ is distributed in the hope that it will
+be useful, but WITHOUT ANY WARRANTY; without even the
+implied warranty of MERCHANTABILITY or FITNESS FOR A
+PARTICULAR PURPOSE.
+<P>
+If you have a Web browser, the official hypertext version is at:
+<A HREF="http://www.sccon.com/~andreas/xemacs-faq.html">&lt;http://www.sccon.com/~andreas/xemacs-faq.html&gt;</A>,
+and also at:
+<A HREF="http://www.xemacs.org/faq/xemacs-faq.html">&lt;http://www.xemacs.org/faq/xemacs-faq.html&gt;</A>.
+This version is much nicer than the unofficial hypertext
+versions that are archived at Utrecht, Oxford, Smart Pages,
+and other FAQ archives.
+<P>
+Changes this month:<BR>
+<P>
+This file was last modified on Feburary 23, 1998.
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: "><A NAME="Roadmap">Roadmap</A></H2>
+<UL>
+<LI> <A HREF="#xemacs">Introduction, Policy, Credits.</A><IMG SRC="lcylarrw.gif" ALT="[You are here]">
+<UL>
+<LI> <A HREF="#introduction">1.0 Introduction</A>
+<UL>
+<LI><A HREF="#Q1_0_1">Q1.0.1</A> What is XEmacs?
+<LI><A HREF="#Q1_0_2">Q1.0.2</A> What is the current version of XEmacs?
+<LI><A HREF="#Q1_0_3">Q1.0.3</A> Where can I find it?
+<LI><A HREF="#Q1_0_4">Q1.0.4</A> Why Another Version of Emacs
+<LI><A hREF="#Q1_0_5">Q1.0.5</A> Why Haven't XEmacs and GNU Emacs Merged?
+<LI><A HREF="#Q1_0_6">Q1.0.6</A> Where can I get help?
+<LI><A HREF="#Q1_0_7">Q1.0.7</A> Where is the mailing list archived?
+<LI><A HREF="#Q1_0_8">Q1.0.8</A> How do you pronounce XEmacs?
+<LI><A HREF="#Q1_0_9">Q1.0.9</A> What does XEmacs look like?
+<LI><A HREF="#Q1_0_10">Q1.0.10</A> Is there a port of XEmacs to Microsoft ('95 or NT)?
+<LI><A HREF="#Q1_0_11">Q1.0.11</A> Is there a port of XEmacs to the Macintosh?
+<LI><A HREF="#Q1_0_12">Q1.0.12</A> Is there a port of XEmacs to NextStep?
+<LI><A HREF="#Q1_0_13">Q1.0.13</A> Is there a port of XEmacs to OS/2?
+<LI><A HREF="#Q1_0_14">Q1.0.14</A> Where can I obtain a printed copy of the XEmacs users manual?
+</UL>
+<LI> <A HREF="#policy">1.1 Policies</A>
+<UL>
+<LI><A HREF="#Q1_1_1">Q1.1.1</A> What is the FAQ editorial policy?
+<LI><A HREF="#Q1_1_2">Q1.1.2</A> How do I become a Beta Tester?
+<LI><A HREF="#Q1_1_3">Q1.1.3</A> How do I contribute to XEmacs itself?
+</UL>
+<LI> <A HREF="#credits">1.2 Credits</A>
+<UL>
+<LI><A HREF="#Q1_2_1">Q1.2.1</A> Who wrote XEmacs?
+<LI><A HREF="#Q1_2_2">Q1.2.2</A> Who contributed to this version of the FAQ?
+<LI><A HREF="#Q1_2_3">Q1.2.3</A> Who contributed to the FAQ in the past?
+</UL>
+<LI> <A HREF="#internationalization">1.3 Internationalization</A>
+<UL>
+<LI><A HREF="#Q1_3_1">Q1.3.1</A> What is the status of XEmacs v20?
+<LI><A HREF="#Q1_3_2">Q1.3.2</A> What is the status of Asian-language support, aka <VAR>MULE</VAR>?
+<LI><A HREF="#Q1_3_3">Q1.3.3</A> I speak a language that uses a lot of non-ASCII characters. How do I type them in?
+<LI><A HREF="#Q1_3_4">Q1.3.4</A> Can I get the messages output by XEmacs to come out in a different language?
+<LI><A HREF="#Q1_3_5">Q1.3.5</A> Please explain the various input methods in MULE/XEmacs 20.0
+<LI><A HREF="#Q1_3_6">Q1.3.6</A> How do I portably code for MULE/XEmacs 20.0?
+<LI><A HREF="#Q1_3_7">Q1.3.7</A> How about Cyrillic Modes?
+</UL>
+<LI> <A HREF="#backup">1.4 Getting Started, Backing up & Recovery</A>
+<UL>
+<LI><A HREF="#Q1_4_1">Q1.4.1</A> What is a <VAR>.emacs</VAR> and is there one I can look at so I can build my own?
+<LI><A HREF="#Q1_4_2">Q1.4.2</A> Can I use the same <VAR>.emacs</VAR> with the other Emacs?
+<LI><A HREF="#Q1_4_3">Q1.4.3</A> Any good XEmacs tutorials around?
+<LI><A HREF="#Q1_4_4">Q1.4.4</A> May I see an example of an XEmacs Lisp function that does something with text near the cursor?
+<LI><A HREF="#Q1_4_5">Q1.4.5</A> And how do I bind it to a key?
+<LI><A HREF="#Q1_4_6">Q1.4.6</A> What's the difference between a macro and a function?
+<LI><A HREF="#Q1_4_7">Q1.4.7</A> How come options saved with 19.13 don't work with 19.14 or later?
+</UL>
+</UL>
+<LI> <A HREF="xemacs-installation.html#Roadmap">Installation and Trouble Shooting</A>
+<LI> <A HREF="xemacs-customization.html#Roadmap">Customization and Options</A>
+<LI> <A HREF="xemacs-subsystems.html#Roadmap">Major Subsystems</A>
+<LI> <A HREF="xemacs-miscellaneous.html#Roadmap">Miscellaneous</A>
+<LI> <A HREF="xemacs-current.html#Roadmap">Current Events</A>
+</UL>
+<HR>
+<H1><IMG SRC="rd_ball.gif" ALT="">
+<A NAME="introduction">1.0 Introduction</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_1">Q1.0.1  What is XEmacs?</A></H2>
+An alternative to GNU Emacs, 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.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_2">Q1.0.2  What is the current version of XEmacs?</A></H2>
+   The current stable version of XEmacs is 20.3, released in December, 1997.
+<P>
+   The next feature release will be XEmacs 20.4.
+<P>
+   XEmacs 19.16 was the last release of v19, released in November, 1997,
+which was also the last version without international language support.
+<P>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_3">Q1.0.3  Where can I find it?</A></H2>
+The canonical source and binaries is found via anonymous FTP at
+<A HREF="ftp://ftp.xemacs.org/pub/xemacs/">
+&lt;ftp://ftp.xemacs.org:/pub/xemacs/&gt;</A>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_4">Q1.0.4  Why Another Version of Emacs</A></H2>
+For a detailed description of the differences between GNU Emacs and
+XEmacs and a detailed history of XEmacs, check out the
+<A HREF="http://www.xemacs.org/NEWS.html">
+&lt;http://www.xemacs.org/NEWS.html&gt;</A> file.  However,
+here is a list of some of the reasons why we think you might consider
+using it:
+<UL>
+<LI> It looks nicer.
+<LI> The XEmacs maintainers are generally more receptive to suggestions than
+the GNU Emacs maintainers.
+<LI> Many more bundled packages than GNU Emacs
+<LI> Binaries are available for many common operating systems.
+<LI> Face support on TTY's.
+<LI> A built-in toolbar.
+<LI> Better Motif compliance.
+<LI> Some internationalization support (full MULE support starting with 20.0).
+<LI> Variable-width fonts.
+<LI> Variable-height lines.
+<LI> Marginal annotations.
+<LI> ToolTalk support.
+<LI> XEmacs can be used as an Xt widget, and can be embedded within another
+application.
+<LI> Horizontal and vertical scrollbars (using real toolkit scrollbars)
+<LI> Better APIs (and performance) for attaching fonts, colors, and other
+properties to text.
+<LI> The ability to embed arbitrary graphics in a buffer.
+<LI> Completely compatible (at the C level) with the Xt-based toolkits.
+<LI> First production Web Browser supporting Style Sheets
+</UL>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_5">Q1.0.5  Why Haven't XEmacs and GNU Emacs Merged?</A></H2>
+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 to <A HREF="mailto:xemacs-beta@xemacs.org">&lt;xemacs-beta@xemacs.org&gt;</A> and<A HREF="mailto:bug-gnu-emacs@prep.ai.mit.edu">&lt;bug-gnu-emacs@prep.ai.mit.edu&gt;</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_6">Q1.0.6  Where can I get help?</A></H2>
+Probably the easiest way, if everything is installed, is to use info, by
+pressing <CODE>C-h i</CODE>, or selecting <EM>Emacs Info</EM> from the
+Help Menu.
+Also, <CODE>M-x apropos</CODE> will look for commands for you.
+<P>
+Try reading this FAQ, examining the regular GNU Emacs FAQ (which can be
+found with the Emacs 19 distribution) as well as at
+<A HREF="http://www.eecs.nwu.edu/emacs/faq/">
+&lt;http://www.eecs.nwu.edu/emacs/faq/&gt;</A>
+and reading the Usenet group
+<A HREF="news:comp.emacs.xemacs">comp.emacs.xemacs</A>.
+If that does not help, try posting your
+question to <A HREF="news:comp.emacs.xemacs">comp.emacs.xemacs</A>.
+Please <STRONG>Do Not</STRONG> post XEmacs related questions to
+<A HREF="news:gnu.emacs.help">gnu.emacs.help</A>.
+<P>
+If you cannot post or read
+Usenet news, there is a corresponding mailing list which is available.
+It can be subscribed to by sending a message with a subject of
+<VAR>subscribe</VAR> to
+<A HREF="mailto:xemacs-request@xemacs.org">xemacs-request@xemacs.org</A>
+for subscription information and 
+<A HREF="mailto:xemacs@xemacs.org">xemacs@xemacs.org</A>
+to send messages to the list.
+<P>
+To cancel a subscription, <STRONG>you must</STRONG> use the
+xemacs-request address.  Send a message with a subject of
+<VAR>unsubscribe</VAR> to be removed.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_7">Q1.0.7  Where is the mailing list archived?</A></H2>
+The mailing list is archived in the directory
+<A HREF="ftp://ftp.xemacs.org/pub/mlists/">
+&lt;ftp://ftp.xemacs.org:/pub/xemacs/mlists/&gt;</A>.
+<P>
+However, this archive is out of date.  The current mailing list
+server supports an `archive' feature, which may be utilized.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_8">Q1.0.8  How do you pronounce XEmacs?</A></H2>
+I pronounce it <SAMP>Eks eemax</SAMP>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_9">Q1.0.9  What does XEmacs look like?</A></H2>
+Here are some Screen Snapshots:
+<UL>
+<LI> <A HREF="splash.gif">The Splash Screen</A>
+<LI> <A HREF="c-mode.gif">C Mode</A>
+<LI> <A HREF="sample.emacs.gif">Emacs Lisp Mode</A>
+<LI> <A HREF="wingpsgml-mode.gif">Wing-enhanced Psgml Mode</A>
+<LI> W3, the Web Browser (Two snapshots courtesy of William Perry 
+&lt;wmperry@monolith.spry.com&gt;).
+<OL>
+   <LI> <A HREF="gnuscape.jpg">W3 Home Page</A>
+   <LI> <A HREF="hwg.gif">HTML Writers Guild</A>
+   <LI> <A HREF="iu.jpg">University of Indiana</A>
+</OL>
+<LI> <A HREF="gnus-topics.gif">Gnus 5, the News and Mail Reader</A>
+<LI> <A HREF="vm.gif">VM, the Mail Reader</A>
+<LI> <A HREF="ediff.gif">Ediff (File Differences)</A>
+</UL>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_10">Q1.0.10  Is there a port of XEmacs to Microsoft ('95 or NT)?</A></H2>
+   Thanks to efforts of many people, coordinated by David Hobley <A
+HREF="mailto:davidh@wr.com.au">&lt;davidh@wr.com.au&gt;</A> and Marc
+Paquette <A HREF="mailto:marcpa@cam.org">&lt;marcpa@cam.org&gt;</A>,
+beta versions of XEmacs now run on 32-bit Windows platforms (NT and
+95).  The current betas require having an X server to run XEmacs;
+however, a native NT/95 port is in alpha.
+<P>
+   The NT development is now coordinated by a mailing list at <A
+HREF="mailto:xemacs-nt@xemacs.org">&lt;xemacs-nt@xemacs.org&gt;</A>.
+If you are willing to contribute or want to follow the progress, mail
+to <A
+HREF="mailto:xemacs-nt-request@xemacs.org">&lt;xemacs-nt-request@xemacs.org&gt;</A>
+to subscribe.
+ <P>
+   Furthermore, Altrasoft is seeking corporate and government sponsors
+to help fund a fully native port of XEmacs to Windows 95 and NT using
+full-time, senior-level staff working under a professionally managed
+project structure.
+<P>
+See <A HREF="http://www.altrasoft.com/">&lt;http://www.altrasoft.com/&gt;</A>
+for more details or contact Altrasoft directly at 1-888-ALTSOFT.
+<P>
+The closest is <EM>Win-Emacs</EM>, which is based on Lucid
+Emacs 19.6.  Available from <A HREF="http://www.pearlsoft.com/">
+&lt;http://www.pearlsoft.com/&gt;</A>.
+<P>
+There's a port of GNU Emacs (not XEmacs) at<BR>
+<A HREF="http://www.cs.washington.edu/homes/voelker/ntemacs.html">
+&lt;http://www.cs.washington.edu/homes/voelker/ntemacs.html&gt;</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_11">Q1.0.11  Is there a port of XEmacs to the Macintosh?</A></H2>
+There has been a port to the MachTen environment of XEmacs 19.13, but no
+patches have been submitted to the maintainers to get this in the mainstream
+distribution.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_12">Q1.0.12  Is there a port of XEmacs to NextStep?</A></H2>
+Carl Edman, apparently no longer at &lt;cedman@princeton.edu&gt;,
+did the port of FSF Emacs to NeXTstep and
+expressed interest in doing the XEmacs port, but never went any farther.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_13">Q1.0.13  Is there a port of XEmacs to OS/2?</A></H2>
+No, and there is no news of anyone working on it.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_0_14">Q1.0.14 Where can I obtain a printed copy of the XEmacs users manual? </A></H2>
+   InfoDock Associates, a firm specializing in Emacs-related support and
+development, will be maintaining the XEmacs user manual.  The firm plans
+to begin publishing printed copies of the manual soon.
+<P>
+       Web:     <A HREF="http://www.xemacs.com">&lt;http://www.xemacs.com&gt;</A>
+<P>       E-mail:  <A HREF="mailto:info@xemacs.com">&lt;info@xemacs.com&gt;</A>
+<P>       Tel:     +1 408 243 3300
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="policy">1.1 Policy</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_1_1">Q1.1.1  What is the FAQ editorial policy?</A></H2>
+The FAQ is actively maintained and modified regularly.  All links should
+be up to date.
+<P>
+Changes are displayed on a monthly basis.  <EM>Months</EM>, for this
+purpose are defined as the 5th of the month through the 5th of the month.
+Preexisting questions that have been changed are marked as such.  Brand
+new questions are tagged.
+<P>
+All submissions are welcome.  E-mail submissions to Andreas Kaempf
+<A HREF="mailto:andreas@sccon.com">&lt;andreas@sccon.com&gt;</A>.
+Please make sure that <EM>XEmacs FAQ</EM> appears on the Subject: line.
+If you think you have a better way of
+answering a question, or think a question should be included, I'd
+like to hear about it.
+Questions and answers included into the FAQ
+will be edited for spelling and grammar, and will be attributed.  Answers
+appearing without attribution are either from versions of the FAQ
+dated before May
+1996, or are from one of the four people listed at the top of this
+document.  Answers quoted from Usenet news articles will always be
+attributed, regardless of the author.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_1_2">Q1.1.2  How do I become a Beta Tester?</A></H2>
+Send an email message to <A HREF="mailto:xemacs-beta-request@xemacs.org">
+&lt;xemacs-beta-request@xemacs.org&gt;</A> with a subject line of subscribe.
+<P>
+Be prepared to get your hands dirty, as beta testers are expected to
+identify problems as best they can.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_1_3">Q1.1.3  How do I contribute to XEmacs itself?</A></H2>
+Ben Wing &lt;ben@666.com&gt; writes:
+<P>
+BTW if you have a wish list of things that you want added, you have
+to speak up about it!  More specifically, you can do the following
+if you want a feature added (in increasing order of usefulness):
+<UL>
+<LI> Make a posting about a feature you want added
+<LI> Become a beta tester and make more postings about those same features
+<LI> Convince us that you're going to use the features in some cool and
+useful way
+<LI> Come up with a clear and well-thought-out API concerning the features
+<LI> Write the code to implement a feature and send us a patch
+</UL>
+(not that we're necessarily requiring you to write the code, but we
+can always hope :)
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="credits">1.2 Credits</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_2_1">Q1.2.1  Who wrote XEmacs?</A></H2>
+XEmacs is the result of the time and effort of many people.
+The developers responsible for the 19.15/20.0 release are:
+<UL>
+<LI> Martin Buchholz &lt;mrb@eng.sun.com&gt;
+<LI> Steve Baur &lt;steve@altair.xemacs.org&gt;
+</UL>
+The developers responsible for the 19.14 release are:
+<UL>
+<LI> Chuck Thompson &lt;cthomp@xemacs.org&gt;
+<IMG SRC="cthomp.gif" ALIGN=BOTTOM ALT="[Picture of Chuck Thompson]">
+<P> Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible for
+XEmacs becoming a widely distributed program over the Internet.
+<LI> Ben Wing &lt;ben@666.com&gt;
+<IMG SRC="wing.gif" ALIGN=BOTTOM ALT="[Picture of Ben Wing]">
+</UL>
+Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10,
+the last release actually named Lucid Emacs.  Richard Mlynarik
+was crucial to most of those releases.
+<UL>
+<LI> Jamie Zawinski &lt;jwz@netscape.com&gt;
+<IMG SRC="jwz.gif" ALIGN=BOTTOM ALT="[Picture of Jamie Zawinski]">
+<LI> Richard Mlynarik &lt;mly@adoc.xerox.com&gt;
+</UL>
+Along with many other contributors, partially enumerated in the
+<VAR>About XEmacs</VAR> option in the Help menu.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_2_2">Q1.2.2  Who contributed to this version of the FAQ?</A></H2>
+The following people contributed valuable suggestions to building this
+version of the FAQ (listed in alphabetical order):
+<UL>
+<LI> <A HREF="mailto:steve@miranova.com">
+Steven L Baur &lt;steve@miranova.com&gt;</A>
+<LI> <A HREF="mailto:hniksic@srce.hr">
+Hrvoje Niksic &lt;hniksic@srce.hr&gt;</A>
+</UL>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_2_3">Q1.2.3  Who contributed to the FAQ in the past?</A></H2>
+This is only a partial list, as many names were lost in a hard disk crash
+some time ago.
+<UL>
+<LI> <A HREF="mailto:abraham@dina.kvl.dk">
+Per Abrahamsen &lt;abraham@dina.kvl.dk&gt;</A>
+<LI> <A HREF="mailto:vladimir@cs.ualberta.ca">
+Vladimir Alexiev &lt;vladimir@cs.ualberta.ca&gt;</A>
+<LI> <A HREF="mailto:binge@aloft.att.com">
+Curtis.N.Bingham &lt;binge@aloft.att.com&gt;</A>
+<LI> <A HREF="mailto:Martin.Buchholz@sun.com"> 
+Martin Buchholz &lt;Martin.Buchholz@sun.com&gt;</A>
+<LI> <A HREF="mailto:rjc@cogsci.ed.ac.uk"<LI>
+Richard Caley &lt;rjc@cogsci.ed.ac.uk&gt;</A>
+<LI> <A HREF="mailto:briand@iccom.com">
+Brian Denheyer &lt;briand@iccom.com&gt;</A>
+<LI> <A HREF="mailto:wgd@martigny.ai.mit.edu">
+William G. Dubuque &lt;wgd@martigny.ai.mit.edu&gt;</A>
+<LI> <A HREF="mailto:eeide@cs.utah.edu">
+Eric Eide &lt;eeide@cs.utah.edu&gt;</A>
+<LI> <A HREF="mailto:fcg@philabs.Philips.COM">
+&lt;fcg@philabs.Philips.COM&gt;</A>
+<LI> <A HREF="mailto:cflatter@nrao.edu">
+Chris Flatters &lt;cflatter@nrao.edu&gt;</A>
+<LI> <A HREF="mailto:ginsparg@adra.com">
+Evelyn Ginsparg &lt;ginsparg@adra.com&gt;</A>
+<LI> <A HREF="mailto:gutschk@ESCHER.UNI-MUENSTER.DE">
+Markus Gutschke &lt;gutschk@ESCHER.UNI-MUENSTER.DE&gt;</A>
+<LI> <A HREF="mailto:hall@aplcenmp.apl.jhu.edu">
+Marty Hall &lt;hall@aplcenmp.apl.jhu.edu&gt;</A>
+<LI> <A HREF="mailto:dak@fsnif.neuroinformatik.ruhr-uni-bochum.de">
+David Kastrup &lt;dak@fsnif.neuroinformatik.ruhr-uni-bochum.de&gt;</A>
+<LI> <A HREF="mailto:nataliek@rd.scitec.com.au">
+Natalie Kershaw &lt;nataliek@rd.scitec.com.au&gt;</A>
+<LI> <A HREF="mailto:arup+@cmu.edu">
+Arup Mukherjee &lt;arup+@cmu.edu&gt;</A>
+<LI> <A HREF="mailto:nickel@prz.tu-berlin.de">
+Juergen Nickelsen &lt;nickel@prz.tu-berlin.de&gt;</A>
+<LI> <A HREF="mailto:powell@csl.ncsa.uiuc.edu">
+Kevin R. Powell &lt;powell@csl.ncsa.uiuc.edu&gt;</A>
+<LI> <A HREF="mailto:stig@hackvan.com">
+Stig &lt;stig@hackvan.com&gt;</A>
+<LI> <A HREF="mailto:turner@lanl.gov">
+John Turner &lt;turner@lanl.gov&gt;</A>
+<LI> <A HREF="mailto:DvdS@eden.com">
+David Vanderschel &lt;DvdS@eden.com&gt;</A>
+<LI> <A HREF="mailto:ave@niksula.hut.fi">
+Aki Vehtari &lt;ave@niksula.hut.fi&gt;</A>
+</UL>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="internationalization">1.3 Internationalization</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_1">Q1.3.1 What is the status of XEmacs v20?</A></H2>
+
+   XEmacs v20 is the version of XEmacs that includes MULE
+(Asian-language) support.  XEmacs 20.0 was released in February 1997,
+followed by XEmacs 20.2 in May and XEmacs 20.3 in November.  When
+compiled without MULE support, 20.3 is approximately as stable as
+19.16, and probably faster (due to additional optimization work.)
+<P>
+  As of XEmacs 20.3, version 20 is <strong>the</strong> supported
+version of XEmacs.  This means that 19.16 will optionally receive
+stability fixes (if any), but that all the real development work will
+be done on the v20 tree.  
+<P>
+   The incompatible changes in XEmacs 20 include the additional
+byte-codes, new primitive data types (<var>character</var>,
+<var>char-table</var>, and <var>range-table</var>).  This means that the
+character-integer equivalence inherent to all the previous Emacs and
+XEmacs releases no longer applies.
+<P>
+   However, to avoid breaking old code, many functions that should
+normally accept characters work with integers, and vice versa.  For more
+information, see the Lisp reference manual.  Here is a relevant excerpt,
+for your convenience.
+<P>
+       In XEmacs version 19, and in all versions of FSF GNU Emacs, a
+     "character" in XEmacs Lisp is nothing more than an integer.  This
+     is yet another holdover from XEmacs Lisp's derivation from
+     vintage-1980 Lisps; modern versions of Lisp consider this
+     equivalence a bad idea, and have separate character types.  In
+     XEmacs version 20, the modern convention is followed, and
+     characters are their own primitive types. (This change was
+     necessary in order for MULE, i.e. Asian-language, support to be
+     correctly implemented.)
+<P>
+     Even in XEmacs version 20, remnants of the equivalence between
+     characters and integers still exist; this is termed the "char-int
+     confoundance disease".  In particular, many functions such as </var>eq</var>,
+     <var>equal</var>, and <var>memq</var> have equivalent functions (<var>old-eq</var>,
+     <var>old-equal</var>, <var>old-memq</var>, etc.) that pretend like characters are
+     integers are the same.  Byte code compiled under any version 19
+     Emacs will have all such functions mapped to their <var>old-</var>
+     equivalents when the byte code is read into XEmacs 20.  This is to
+     preserve compatibility - Emacs 19 converts all constant characters
+     to the equivalent integer during byte-compilation, and thus there
+     is no other way to preserve byte-code compatibility even if the
+     code has specifically been written with the distinction between
+     characters and integers in mind.
+<P>
+     Every character has an equivalent integer, called the "character
+     code".  For example, the character <var>A</var> is represented as the
+     integer 65, following the standard ASCII representation of
+     characters.  If XEmacs was not compiled with MULE support, the
+     range of this integer will always be 0 to 255 - eight bits, or one
+     byte. (Integers outside this range are accepted but silently
+     truncated; however, you should most decidedly <strong>not</strong> rely on this,
+     because it will not work under XEmacs with MULE support.)  When
+     MULE support is present, the range of character codes is much
+     larger. (Currently, 19 bits are used.)
+<P>
+     FSF GNU Emacs uses kludgy character codes above 255 to represent
+     keyboard input of ASCII characters in combination with certain
+     modifiers.  XEmacs does not use this (a more general mechanism is
+     used that does not distinguish between ASCII keys and other keys),
+     so you will never find character codes above 255 in a non-MULE
+     XEmacs.
+<P>
+     Individual characters are not often used in programs.  It is far
+     more common to work with <strong>strings</strong>, which are sequences composed of
+     characters.
+
+
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_2">Q1.3.2 What is the status of Asian-language support, aka <VAR>MULE</VAR>?</A></H2>
+   The MULE support works OK but still needs a fair amount of work
+before it's really solid.  We could definitely use some help here, esp.
+people who speak Japanese and will use XEmacs/MULE to work with
+Japanese and have some experience with E-Lisp.
+<P>
+   As the fundings on Mule have stopped, Mule part of XEmacs is
+currently looking for a full-time maintainer.  If you can provide help
+here, or are willing to fund the work, please mail to <A HREF="mailto:xemacs-beta@xemacs.org">&lt;xemacs-beta@xemacs.org&gt;</A>.
+
+If you can help out here, please see <A HREF="#Q1_1_2">Q1.1.2</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_3">Q1.3.3 I speak a language that uses a lot of non-ASCII characters. How do I type them in?</A></H2>
+See <A HREF="xemacs-customization.html#Q3_5_7">Q3.5.7</A> in part 3 of this
+FAQ.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_4">Q1.3.4 Can I get the messages output by XEmacs to come out in a different language?</A></H2>
+The message-catalog support has mostly been written but doesn't
+currently work.  The first release of XEmacs 20 will <EM>not</EM> support it.
+However, menubar localization <EM>does</EM> work, even in 19.14.
+To enable it, add to
+your <VAR>Emacs</VAR> file entries like this:
+<PRE>
+Emacs*XlwMenu.resourceLabels: True
+Emacs*XlwMenu.file.labelString: Fichier
+Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster &ouml;ffnen
+</PRE>
+The name of the resource is derived from the non-localized entry by
+removing punctuation and capitalizing as above.
+Martin Buchholz
+<A HREF="mailto:Martin.Buchholz@sun.com">&lt;Martin.Buchholz@sun.com&gt;</A>
+is working on adding support for Asian language menubar localization
+to XEmacs 20.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_5">Q1.3.5 Please explain the various input methods in MULE/XEmacs 20.0</A></H2>
+MORIOKA Tomohiko &lt;morioka@jaist.ac.jp&gt; writes:<BR>
+Original Mule supports following input methods: Wnn4, Wnn6, Canna,
+SJ3 and XIM. Interfaces for Wnn and SJ3 uses the <VAR>egg</VAR> user
+interface. Interface for Canna does not use <VAR>egg</VAR>. I don't know about
+XIM. It is to support ATOK, of course, it may work for another
+servers.
+<P>
+Wnn supports Japanese, Chinese and Korean. It is made by OMRON and
+Ky&#244;to university. It is a powerful and complex system.  Wnn4 is free and
+Wnn6 is not free.
+<P>
+Canna supports only Japanese. It is made by NEC. It is a simple and
+powerful system. Canna uses only grammar (Wnn uses grammar and
+probability between words), so I think Wnn is cleverer than Canna,
+however Canna users made a good grammar and dictionary. So for standard
+modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
+version of Canna is free (now there is a Microsoft Windows version).
+<P>
+SJ3 supports only Japanese. It is made by Sony.
+<P>
+XIM supports was made to use ATOK (a major input method in personal
+computer world).  XIM is the standard for accessing input methods
+bundled in Japanese versions of Solaris.  (XEmacs 20 will support XIM
+input).
+<P>
+Egg consists of following parts:
+<OL>
+<LI>Input character Translation System (ITS) layer.
+It translates ASCII inputs to Kana/PinYin/Hangul characters.
+<LI>Kana/PinYin/Hangul to Kanji transfer layer.
+It is interface layer for network Kana-Kanji server (Wnn
+and Sj3).
+</OL> 
+These input methods are modal, namely there are mode, alphabet mode
+and Kana-Kanji transfer mode. However there are mode-less input
+methods for Egg and Canna. <EM>Boiled-egg</EM> is a mode-less input method
+running on Egg. For Canna, <VAR>canna.el</VAR> has a tiny boiled-egg like
+command, <CODE>(canna-boil)</CODE>, and there are some boiled-egg
+like utilities.
+<P> 
+In addition, it was planned to make an abstraction for all transfer
+type input methods. However authors of input methods are busy, so
+maybe this plan is stopped. Perhaps after Mule merged FSF Emacs will
+be released, it will be continued.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_6">Q1.3.6 How do I portably code for MULE/XEmacs 20.0?</A></H2>
+MORIOKA Tomohiko &lt;morioka@jaist.ac.jp&gt; writes:<BR>
+MULE and XEmacs are quite different. So the application implementor must
+write separate code for these mule variants.
+<P>
+MULE and the next version of Emacs are similar but the symbols are very
+different -- requiring separate code as well.
+<P>
+Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds
+of emacs variants... (;_;)
+<P>
+I'm shocked, so I wrote a wrapper package called <VAR>emu</VAR> to 
+provide a common interface.
+<P>
+I have the following suggestions about dealing with mule
+variants:
+<OL>
+<LI> <CODE>(featurep 'mule)</CODE> is <CODE>t</CODE> on all mule variants
+<LI> <CODE>(boundp 'MULE)</CODE> is <CODE>t</CODE> on only MULE.  Maybe
+the next version of Emacs will not have this symbol.
+<LI> MULE has a variable <CODE>mule-version</CODE>.
+Perhaps the next version of Emacs will have this variable as well.
+</OL>
+<P>
+Following is a sample to distinguish mule variants:
+<PRE>
+(if (featurep 'mule)
+    (cond ((boundp 'MULE)
+           ;; for original Mule
+           )
+	  ((string-match "XEmacs" emacs-version)
+	   ;; for XEmacs with Mule
+	   )
+	  (t
+	   ;; for next version of Emacs
+	   ))
+  ;; for old emacs variants
+  )
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_3_7">Q1.3.7 How about Cyrillic Modes?</A></H2>
+Ilya Zakharevich &lt;ilya@math.ohio-state.edu&gt; writes:
+<P>
+There is a cyrillic mode in the file <VAR>mysetup.zip</VAR> in
+<A HREF="ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/">
+&lt;ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/&gt;</A>.
+<P>
+Dima Barsky &lt;d.barsky@ee.surrey.ac.uk&gt; writes:
+<P>
+There is another cyrillic mode for both GNU Emacs and XEmacs by Dmitrii
+(Mitya) Manin &lt;manin@camelot.mssm.edu&gt; at<BR>
+<A HREF="http://camelot.mssm.edu/~manin/cyr.el">&lt;http://camelot.mssm.edu/~manin/cyr.el&gt;</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="backup">1.4 Getting Started, Backing up & Recovery</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_1">Q1.4.1 What is a <VAR>.emacs</VAR> and is there one I can look at so I can build my own?</A></H2>
+The <VAR>.emacs</VAR> file is used to customize XEmacs to your tastes.  No
+two are alike, nor are they expected to be alike, but that's the point.  The
+XEmacs distribution contains an excellent starter example in the etc
+directory called <VAR>sample.emacs</VAR>.  Copy this file from there to
+your home directory and rename it <VAR>.emacs</VAR>.  Then edit it to suit.
+<P>
+Starting with 19.14, you may bring the <VAR>sample.emacs</VAR> into 
+an XEmacs buffer by selecting Help-&gt;Sample .emacs from the menubar.  
+To determine the location of the <VAR>etc</VAR> directory type the 
+command <KBD>C-h v data-directory RET</KBD>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_2">Q1.4.2 Can I use the same <VAR>.emacs</VAR> with the other Emacs?</A></H2>
+Yes.  The sample <VAR>.emacs</VAR> included in the XEmacs distribution
+will show you how to handle different versions and flavors of Emacs.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_3">Q1.4.3 Any good tutorials around?</A></H2>
+There's the XEmacs tutorial available from the Help Menu, or by typing
+<KBD>C-h t</KBD>.
+<P>
+There's an Emacs Lisp tutorial at:<BR>
+<A HREF="ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz">
+&lt;ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz&gt;</A>.
+<P>
+Erik Sundermann &lt;erik@petaxp.rug.ac.be&gt; has made a tutorial web page
+at <A HREF="http://petaxp.rug.ac.be/~erik/xemacs/">
+&lt;http://petaxp.rug.ac.be/~erik/xemacs/&gt;</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_4">Q1.4.4 May I see an example of an XEmacs Lisp function that does something with text near the cursor?</A></H2>
+The following function does a little bit of everything useful.  It does
+something with the prefix argument, it examines the text around the cursor,
+and it's interactive so it may be bound to a key.
+It inserts copies of the current word the cursor is sitting on at the
+cursor.  If you give it a prefix argument:
+<KBD>C-u 3 M-x double-word</KBD>
+then it will insert 3 copies.
+<P>
+<PRE>
+(defun double-word (count)
+       "Insert a copy of the current word underneath the cursor"
+       (interactive "*p")
+       (let (here there string)
+         (save-excursion
+           (forward-word -1)
+           (setq here (point))
+           (forward-word 1)
+           (setq there (point))
+           (setq string (buffer-substring here there)))
+         (while (>= count 1)
+           (insert string)
+           (decf count))))
+</PRE>
+The best way to see what is going on here is to let XEmacs tell you.
+Put the code into an XEmacs buffer, and do a <KBD>C-h f</KBD> with the
+cursor sitting just to
+the right of the function you want explained.  Eg.  move the cursor to
+the SPACE between <SAMP>interactive</SAMP> and <SAMP>"*p"</SAMP> and hit
+<KBD>C-h f</KBD> to see
+what the function <CODE>interactive</CODE> does.  Doing this will tell you
+that the <VAR>*</VAR> requires a writable buffer, and <VAR>p</VAR> converts
+the prefix argument to a number, and <CODE>interactive</CODE> allows
+you to execute the command with <KBD>M-x</KBD>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_5">Q1.4.5 And how do I bind it to a key?</A></H2>
+To bind to a key do:
+<PRE>
+(global-set-key "\C-cd" 'double-word)
+</PRE>
+Or interactively, <KBD>M-x global-set-key</KBD> and follow the prompts.
+<P>
+Jari Aalto has written a guide to Emacs keys binding, available at<BR>
+<A HREF="ftp://cs.uta.fi/pub/ssjaaa/ema-keys.gui">
+&lt;ftp://cs.uta.fi/pub/ssjaaa/ema-keys.gui&gt;</A>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_6">Q1.4.6 What's the difference between a macro and a function?</A></H2>
+Quoting from the Lisp Reference (a.k.a <EM>lispref</EM>) Manual:
+<P>
+<EM>Macros</EM> enable you to define new control constructs and other
+language features.  A macro is defined much like a function, but
+instead of telling how to compute a value, it tells how to compute
+another Lisp expression which will in turn compute the value.  We call
+this expression the <VAR>expansion</VAR> of the macro.
+<P>
+Macros can do this because they operate on the unevaluated
+expressions for the arguments, not on the argument values as functions
+do.  They can therefore construct an expansion containing these
+argument expressions or parts of them.
+<P>
+Do not confuse the two terms with "keyboard macros", which are
+another matter, entirely.  A keyboard macro is a key bound to several
+other keys.  Refer to manual for details.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q1_4_7">Q1.4.7 How come options saved with 19.13 don't work with 19.14 or later?</A></H2>
+There's a problem with options of the form:
+<PRE>
+(add-spec-list-to-specifier (face-property 'searchm-field 'font)
+                            '((global (nil))))
+</PRE>
+saved by a 19.13 XEmacs that causes a 19.14 XEmacs grief.  You must delete
+these options.  XEmacs 19.14 and later no longer writes the options directly 
+to <VAR>.emacs</VAR> which should allow us to deal with version
+incompatibilities better in the future.
+<P>
+Options saved under XEmacs 19.13 are protected by code that specifically
+requires a version 19 XEmacs.  This won't be a problem unless you're testing
+XEmacs v20.  You should consider changing the code to read:
+<PRE>
+(cond
+ ((and (string-match "XEmacs" emacs-version)
+       (boundp 'emacs-major-version)
+       (or (and (= emacs-major-version 19)
+                (>= emacs-minor-version 12))
+           (>= emacs-major-version 20)))
+ ...
+</PRE>
+<HR>
+<P>
+This FAQ is Copyright &copy; 1998 by various people and edited by 
+Andreas Kaempf. Please send comments, and suggestions to Andreas Kaempf
+<A HREF="mailto:andreas@sccon.com">&lt;andreas@sccon.com&gt;</A>.
+<P>
+<A HREF="xemacs-installation.html">
+<IMG SRC="right-purple.gif" ALT=" Part 2 =>"></A>
+</BODY>
+</HTML>
+

FAQ/old/xemacs-current.html

+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//2.0">
+<HTML>
+<HEAD>
+<TITLE>XEmacs Editor FAQ [6/6]</TITLE>
+<LINK REV=MADE HREF="mailto:andreas@sccon.com">
+<LINK REL="Home" HREF="xemacs-faq.html">
+</HEAD>
+<BODY>
+<A HREF="http://www.eff.org/blueribbon.html">
+<IMG SRC="rib_bar_wh.gif" ALT=""></A>
+<A HREF="xemacs-miscellaneous.html"><IMG SRC="left-purple.gif" ALT=""></A>
+<BR>
+<A HREF="http://www.xemacs.org/"><IMG SRC="xemacs.gif" ALT=""></A>
+<H1>XEmacs FAQ [6/6]</H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: ">Introduction</H2>
+<P>
+This is part 6 of the XEmacs Frequently Asked Questions list.  This
+section will change monthly, and contains any interesting items that have
+transpired over the previous month.  If you are reading this from the
+XEmacs distribution, please see the version on the Web or archived at the
+various FAQ FTP sites, as this file is surely out of date.
+<P>
+If you have a Web browser, the official hypertext version is at:
+<A HREF="http://www.sccon.com/~andreas/xemacs-current.html">&lt;URL:http://www.sccon.com/~andreas/xemacs-current.html&gt;</A>,
+and also at:
+<A HREF="http://www.xemacs.org/faq/xemacs-miscellaneous.html">&lt;URL:http://www.xemacs.org/faq/xemacs-miscellaneous.html&gt;</A>.
+This version is much nicer than the unofficial hypertext
+versions that are archived at Utrecht, Oxford, Smart Pages,
+and other FAQ archives.
+<P>
+This file was last modified on Feburary 23, 1998.
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: "><A NAME="Roadmap">Roadmap</A></H2>
+<OL>
+<LI> <A HREF="xemacs-faq.html#Roadmap">Introduction, policy, credits.</A>
+<LI> <A HREF="xemacs-installation.html#Roadmap">Installation and Trouble Shooting</A>
+<LI> <A HREF="xemacs-customization.html#Roadmap">Customization and Options</A>
+<LI> <A HREF="xemacs-subsystems.html#Roadmap">Major Subsystems</A>
+<LI> <A HREF="xemacs-miscellaneous.html#Roadmap">Miscellaneous</A>
+<LI> <A HREF="#Roadmap">Current Events</A><IMG SRC="lcylarrw.gif" ALT="[You are here]">
+<UL>
+<LI> <A HREF="#Q6_0_1">Q6.0.1</A> What is new in 20.2?
+<LI> <A HREF="#Q6_0_1">Q6.0.1</A> What is new in 20.3?
+<LI> <A HREF="#Q6_0_1">Q6.0.1</A> Procedural Changes in XEmacs development
+</UL>
+</OL>
+<HR>
+<H1><IMG SRC="rd_ball.gif"
+ALT=""><A NAME="modes">Current Events</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q6_0_1">Q6.0.1 What is new in 20.2?</A></H2>
+<P>
+The biggest changes in 20.2 include intergration of EFS (the next
+generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
+major mode for editing Tex and LaTeX, and a lot of other stuff).  Many
+bugs from 20.0 have been fixed for this release.  20.2 also contains a
+new system for customizing XEmacs options, invoked via <KBD>M-x customize</KBD>.
+<P>
+XEmacs 20.2 is the development release (20.0 was beta), and is no longer
+considered unstable.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q6_0_2">Q6.0.2 What is new in 20.3?</A></H2>
+<P>
+XEmacs release 20.3 is planned for autumn 1997.  It will likely contain
+a much smaller amount of code for basic functionality, with all the
+popular Lisp packages being available in the form of easy-to-install
+add-ons.
+<P>
+Other input methods (such as skk) will be made available for Mule, as
+well as more user-level documentation.
+<P>
+Many new features are planned, such as multiple TTY frames, support for
+Autoconf 2, synches with Emacs 20.1, and more; much of this is already
+running in various beta versions.  Ask at
+<A HREF="mailto:xemacs-beta-request@xemacs.org">xemacs-beta-request@xemacs.org</A>
+ for more details.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q6_0_3">Q6.0.3 Procedural changes in XEmacs development.</A></H2>
+<OL>
+<LI> Discussion about the development of XEmacs occurs on the xemacs-beta
+mailing list.  Subscriptions to this list will now be fully automated
+instead of being handled by hand.  Send a mail message to
+<A HREF="mailto:xemacs-beta-request@xemacs.org">xemacs-beta-request@xemacs.org</A> with a subject of subscribe to join the list.  Please note this is a
+developers mailing list for people who have an active interest in the
+development process.
+<LI> Due to the long development cycle in between releases, it has been decided
+that intermediate versions will be made available in source only form for
+the truly interested.  
+<LI> No further XEmacs 19 feature releases are planned.  XEmacs 19.16 will
+consist of 19.15 plus the collected bugfixes, and will probably be the
+final version of XEmacs 19.
+<LI> As of December 1996, Steve Baur &lt;steve@altair.xemacs.org&gt; has
+become the lead maintainer of XEmacs.
+</OL>
+<HR>
+<P>
+This FAQ is Copyright &copy; 1998 by various people, and edited by Andreas Kaempf.
+Please send comments, and suggestions to Andreas Kaempf
+<A HREF="mailto:andreas@sccon.com">&lt;andreas@sccon.com&gt;</A>.
+<P>
+<A HREF="xemacs-miscellaneous.html"><IMG SRC="left-purple.gif" ALT="<= Part 5"></A>
+</BODY>
+</HTML>

FAQ/old/xemacs-customization.html

+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//2.0">
+<HTML>
+<HEAD>
+<TITLE>XEmacs Editor FAQ [3/6]</TITLE>
+<LINK REV=MADE HREF="mailto:andreas@sccon.com">
+<LINK REL="Home" HREF="xemacs-faq.html">
+<LINK REL="Next" HREF="xemacs-subsystems.html">
+</HEAD>
+<BODY>
+<A HREF="http://www.eff.org/blueribbon.html">
+<IMG SRC="rib_bar_wh.gif" ALT=""></A>
+<A HREF="xemacs-installation.html"><IMG SRC="left-purple.gif" ALT=""></A>
+<A HREF="xemacs-subsystems.html"><IMG SRC="right-purple.gif" ALT=""></A>
+<BR>
+<A HREF="http://www.xemacs.org/">
+<IMG SRC="xemacs.gif" ALT=""></A>
+<H1>XEmacs FAQ [3/6]</H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: ">Introduction</H2>
+<P>
+This is part 3 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to Customization and screen settings.
+<P>
+If you have a Web browser, the official hypertext version is at:
+<A HREF="http://www.sccon.com/~andreas/xemacs-customization.html">&lt;URL:http://www.sccon.com/~andreas/xemacs-installation.html&gt;</A>,
+and also at:
+<A HREF="http://www.xemacs.org/faq/xemacs-customization.html">&lt;URL:http://www.xemacs.org/faq/xemacs-customization.html&gt;</A>.
+This version is much nicer than the unofficial hypertext
+versions that are archived at Utrecht, Oxford, Smart Pages,
+and other FAQ archives.
+<P>
+Changes this month:<BR>
+<P>
+This file was last modified on Feburary 23, 1998.
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="rd_ball.gif" ALT="Subject: "><A NAME="Roadmap">Roadmap</A></H2>
+<OL>
+<LI> <A HREF="xemacs-faq.html#Roadmap">Introduction, policy, credits.</A>
+<LI> <A HREF="xemacs-installation.html#Roadmap">Installation and Trouble Shooting</A>
+<LI> <A HREF="#customization">Customization and Options</A><IMG SRC="lcylarrw.gif" ALT="[You are here]">
+<UL>
+<LI> <A HREF="#customization">3.0 Customization -- Emacs Lisp and <VAR>.emacs</VAR></A>
+<UL>
+<LI><A HREF="#Q3_0_1">Q3.0.1</A> What version of Emacs am I running?
+<LI><A HREF="#Q3_0_2">Q3.0.2</A> How can I evaluate Emacs-Lisp expressions without switching to the <VAR>*scratch*</VAR> buffer?
+<LI><A HREF="#Q3_0_3">Q3.0.3</A> <CODE>(setq tab-width 6)</CODE> behaves oddly
+<LI><A HREF="#Q3_0_4">Q3.0.4</A> How can I add directories to the <VAR>load-path</VAR>?
+<LI><A HREF="#Q3_0_5">Q3.0.5</A> How to check if a lisp function is defined?
+<LI><A HREF="#Q3_0_6">Q3.0.6</A> Can I force the output of <CODE>(face-list)</CODE> to a buffer other than the minibuffer since it is too wide to fit?
+<LI><A HREF="#Q3_0_7">Q3.0.7</A> My font selections don't get saved when I do a <EM>Save Options</EM>
+<LI><A HREF="#Q3_0_8">Q3.0.8</A> How do I make a single minibuffer frame?
+</UL>
+<LI> <A HREF="#x-windows">3.1 X Window System &amp; Resources</A>
+<UL>
+<LI><A HREF="#Q3_1_1">Q3.1.1</A> Where is a list of X resources?
+<LI><A HREF="#Q3_1_2">Q3.1.2</A> How can I detect a color display?
+<LI><A HREF="#Q3_1_3">Q3.1.3</A> `(set-screen-width)' worked in 19.6, but not in 19.13?
+<LI><A HREF="#Q3_1_4">Q3.1.4</A> Specifiying `Emacs*EmacsScreen.geometry' in `.emacs' does not work in 19.15?
+<LI><A HREF="#Q3_1_5">Q3.1.5</A> How can I get the icon to just say <SAMP>XEmacs</SAMP>?
+<LI><A HREF="#Q3_1_6">Q3.1.6</A> How can I have the window title area display the full path?
+<LI><A HREF="#Q3_1_7">Q3.1.7</A> `xemacs -name junk' doesn't work?
+<LI><A HREF="#Q3_1_8">Q3.1.8</A> When I start up XEmacs using <EM>-iconic</EM> it doesn't work right.
+</UL>
+<LI> <A HREF="#fonts">3.2 Textual Fonts &amp; Colors</A>
+<UL>
+<LI><A HREF="#Q3_2_1">Q3.2.1</A> How can I set color options from `.emacs'?
+<LI><A HREF="#Q3_2_2">Q3.2.2</A> How do I set the text, menu and modeline fonts?
+<LI><A HREF="#Q3_2_3">Q3.2.3</A> How can I set the background/foreground colors when highlighting a region?
+<LI><A HREF="#Q3_2_4">Q3.2.4</A> How can I limit color map usage?
+<LI><A HREF="#Q3_2_5">Q3.2.5</A> My tty supports color, but XEmacs doesn't use them
+<LI> <A HREF="#modeline">3.3 The Modeline</A>
+<LI><A HREF="#Q3_3.1">Q3.3.1</A> How can I make the modeline go away?
+<LI><A HREF="#Q3_3_2">Q3.3.2</A> How do you have XEmacs display the line or column number in the modeline?
+<LI><A HREF="#Q3_3_3">Q3.3.3</A> How do I get XEmacs to put the time of day on the modeline?
+<LI><A HREF="#Q3_3_4">Q3.3.4</A> How do I turn off current chapter from AUC-TeX modeline?
+<LI><A HREF="#Q3_3_5">Q3.3.5</A> How can one change the color of the modeline based on the mode used?
+<LI><A HREF="#Q3_3_6">Q3.3.6</A> [This question intentionally left blank]
+</UL>
+<LI> <A HREF="#multidev">3.4 Multiple Device Support</A>
+<UL>
+<LI><A HREF="#Q3_4_1">Q3.4.1</A> How do I open a frame on another screen of my multi-headed display?
+<LI><A HREF="#Q3_4_2">Q3.4.2</A> Can I really connect to a running XEmacs after calling up over a modem?  How do I do it?
+</UL>
+<LI> <A HREF="#keyboard">3.5 The Keyboard</A>
+<UL>
+<LI><A HREF="#Q3_5_1">Q3.5.1</A> How can I bind complex functions (or macros) to keys?
+<LI><A HREF="#Q3_5_2">Q3.5.2</A> How can I stop the down-arrow-key from adding empty lines at the bottom of my buffers?
+<LI><A HREF="#Q3_5_3">Q3.5.3</A> How do I bind C-. and C-; to scroll one line up and down?
+<LI><A HREF="#Q3_5_4">Q3.5.4</A> Globally binding <KBD>Delete</KBD>?
+<LI><A HREF="#Q3_5_5">Q3.5.5</A> Scrolling one line at a time
+<LI><A HREF="#Q3_5_6">Q3.5.6</A> How to map <KBD>Help</KBD> key alone on Sun type4 keyboard?
+<LI><A HREF="#Q3_5_7">Q3.5.7</A> How can you type in special characters in XEmacs?
+<LI><A HREF="#Q3_5_8">Q3.5.8</A> Why does <CODE>(define-key global-map [ delete-forward ] 'delete-char)</CODE> complain?
+<LI><A HREF="#Q3_5_9">Q3.5.9</A> How do I make the Delete key delete forward?
+<LI><A HREF="#Q3_5_10">Q3.5.10</A> Can I turn on <EM>sticky modifier</EM> keys?
+</UL>
+<LI> <A HREF="#cursor">3.6 The Cursor</A>
+<UL>
+<LI><A HREF="#Q3_6_1">Q3.6.1</A> Is there a way to make the bar cursor a little thicker?
+<LI><A HREF="#Q3_6_2">Q3.6.2</A> Is there a way to get back the <EM>block</EM> cursor?
+<LI><A HREF="#Q3_6_3">Q3.6.3</A> Can I make the cursor blink?
+</UL>
+<LI> <A HREF="#mouse">3.7 The Mouse and Highlighting</A>
+<UL>
+<LI><A HREF="#Q3_7_1">Q3.7.1</A> How can I turn off Mouse pasting?
+<LI><A HREF="#Q3_7_2">Q3.7.2</A> How do I set control/meta/etc modifiers on mouse buttons?
+<LI><A HREF="#Q3_7_3">Q3.7.3</A> Clicking the left button does not do anything in buffer list.
+<LI><A HREF="#Q3_7_4">Q3.7.4</A> How can I get a list of buffers to popup when I hit button 3 on the mouse?
+<LI><A HREF="#Q3_7_5">Q3.7.5</A> Why does cut-and-paste not work between XEmacs and a cmdtool?
+<LI><A HREF="#Q3_7_6">Q3.7.6</A> How I can set XEmacs up so that it pastes where the text cursor is?
+<LI><A HREF="#Q3_7_7">Q3.7.7</A> How do I select a rectangular region?
+<LI><A HREF="#Q3_7_8">Q3.7.8</A> Why does <KBD>M-w</KBD> take so long?
+</UL>
+<LI> <A HREF="#menubar">3.8 The Menubar and Toolbar</A>
+<UL>
+<LI><A HREF="#Q3_8_1">Q3.8.1</A> How do I get rid of the menu (or menubar)?
+<LI><A HREF="#Q3_8_2">Q3.8.2</A> Can I customize the basic menubar?
+<LI><A HREF="#Q3_8_3">Q3.8.3</A> How do I control how many buffers are listed in the menu <EM>Buffers</EM> list?
+<LI><A HREF="#Q3_8_4">Q3.8.4</A> Resources like `Emacs*menubar*font' are not working?
+<LI><A HREF="#Q3_8_5">Q3.8.5</A> How can I bind a key to a function to toggle the toolbar?
+</UL>
+<LI> <A HREF="#scrollbars">3.9 Scrollbars</A>
+<UL>
+<LI><A HREF="#Q3_9_1">Q3.9.1</A> How can I disable the scrollbar?
+<LI><A HREF="#Q3_9_2">Q3.9.2</A> How can one use resources to change scrollbar colors?
+<LI><A HREF="#Q3_9_3">Q3.9.3</A> Moving the scrollbar can move the point; can I disable this?
+<LI><A HREF="#Q3_9_4">Q3.9.4</A> How can I get automatic horizontal scrolling?
+</UL>
+<LI> <A HREF="#highlighting">3.10 Text Selections</A>
+<UL>
+<LI><A HREF="#Q3_10_1">Q3.10.1</A> How can I turn off or change highlighted selections?
+<LI><A HREF="#Q3_10_2">Q3.10.2</A> How do I get that typing on an active region removes it?
+<LI><A HREF="#Q3_10_3">Q3.10.3</A> Can I turn off the highlight during isearch?
+<LI><A HREF="#Q3_10_4">Q3.10.4</A> How do I turn off highlighting after <KBD>C-x C-p</KBD> (mark-page).</A></H2>
+<LI><A HREF="#Q3_10_5">Q3.10.5</A> The region disappears when I hit the end of buffer while scrolling.
+</UL>
+</UL>
+<LI> <A HREF="xemacs-subsystems.html#Roadmap">Major Subsystems</A>
+<LI> <A HREF="xemacs-miscellaneous.html#Roadmap">Miscellaneous</A>
+<LI> <A HREF="xemacs-current.html#Roadmap">Current Events</A>
+</OL>
+<HR>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="customization">3.0 Customization -- Emacs Lisp and <VAR>.emacs</VAR></A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_1">Q3.0.1  What version of Emacs am I running?</A></H2>
+How can <EM>.emacs</EM> determine which of the family of Emacsen I am using?
+<P>
+To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
+XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the 
+example given in <EM>etc/sample.emacs</EM>.  There are other nifty things in 
+there as well!
+<P>
+For all new code, a simple
+<PRE>
+(defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
+</PRE>
+is all you really need to do.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_2">Q3.0.2  How can I evaluate Emacs-Lisp expressions without switching to the <VAR>*scratch*</VAR> buffer?</A></H2>
+   I know I can evaluate Elisp expressions from <VAR>*scratch*</VAR> buffer with
+<CODE>C-j</CODE> after the expression.  How do I do it from another buffer?
+<P>
+   Press <CODE>M-:</CODE>  (the default binding of <CODE>eval-expression</CODE>), and enter the expression to the minibuffer.  In XEmacs prior to 19.15
+<CODE>eval-expression</CODE> used to be a disabled command by default.  
+<P>
+If this is the case, upgrade your XEmacs.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_3">Q3.0.3  <CODE>(setq tab-width 6)</CODE> behaves oddly</A></H2>
+If you put <CODE>(setq tab-width 6)</CODE> in your <VAR>.emacs</VAR>
+file it does not work!  Is there a reason for this?
+If you do it at the EVAL prompt it works fine!! How strange.
+<P>
+Use <CODE>setq-default</CODE> instead,
+since <VAR>tab-width</VAR> is all-buffer-local.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_4">Q3.0.4  How can I add directories to the <VAR>load-path</VAR>?</A></H2>
+Here are two ways to do that, one that puts your directories at the front of
+the load-path, the other at the end:
+<PRE>
+     ;;; Add things at the beginning of the load-path, do not add
+     ;;; duplicate directories:
+     (pushnew "bar" load-path :test 'equal)
+     
+     (pushnew "foo" load-path :test 'equal)
+     
+     ;;; Add things at the end, unconditionally
+     (setq load-path (nconc load-path '("foo" "bar")))
+</PRE>
+keith (k.p.) hanlan &lt;keithh@nortel.ca&gt; writes:<BR>
+<P>
+To add directories using Unix shell metacharacters use
+<CODE>expand-file-name</CODE> like this:
+<PRE>
+(setq load-path (cons (expand-file-name "~keithh/.emacsdir") load-path))
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_5">Q3.0.5  How to check if a lisp function is defined?</A></H2>
+Use the following elisp:
+<PRE>
+(fboundp 'foo)
+</PRE>
+<P>
+It's almost always a mistake to test
+<VAR>emacs-version</VAR> or any similar variables.
+<P>
+Instead, use feature-tests, such as
+<CODE>featurep</CODE> or <CODE>boundp</CODE> or <CODE>fboundp</CODE>, or
+even simple behavioural tests, eg.
+<PRE>
+(defvar foo-old-losing-code-p 
+  (condition-case nil (progn (losing-code t) nil)
+   (wrong-number-of-arguments t)))
+</PRE>
+<P>
+There is an incredible amount of broken code out there which could
+work much better more often in more places if it did the above instead
+of trying to divine its environment from the value of one variable.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_6">Q3.0.6 Can I force the output of <CODE>(face-list)</CODE> to a buffer other than the minibuffer since it is too wide to fit?</A></H2>
+   It would be good having it in a buffer, as the output of
+<VAR>(face-list)</VAR> is too wide to fit to a minibuffer.
+<P>
+   Evaluate the expression in the <VAR>*scratch*</VAR> buffer with point after
+the rightmost paren and typing <KBD>C-j</KBD>.
+<P>
+   If the minibuffer smallness is the only problem you encounter, you
+can simply press <KBD>C-h l</KBD> to get the former minibuffer contents in a
+buffer.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_7">Q3.0.7 My font selections don't get saved when I do a <EM>Save Options</EM></A></H2>
+For XEmacs 19.14 and previous:
+<P>
+John Mann &lt;mannj@ll.mit.edu&gt; writes:<BR>
+<P>
+You have to go to Options-&gt;Menubar Appearance and unselect
+<VAR>Frame-Local Font Menu</VAR>.  If this option is selected, font changes
+are only applied to the <STRONG>current</STRONG> frame and do
+<STRONG>not</STRONG> get saved when you save options.
+<P>
+For XEmacs 19.15 and later:
+<P>
+Implement the above as well as set the following in your `.emacs'
+<PRE>
+     (setq options-save-faces 't)
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_0_8">Q3.0.8 How do I get a single minibuffer frame?</A></H2>
+Vinnie Shelton &lt;shelton@icd.teradyne.com&gt; writes:<BR>
+<PRE>
+(setq initial-frame-plist '(minibuffer nil))
+(setq default-frame-plist '(minibuffer nil))
+(setq default-minibuffer-frame
+      (make-frame
+	'(minibuffer only
+                     width 86
+                     height 1
+                     menubar-visible-p nil
+                     default-toolbar-visible-p nil
+                     name "minibuffer"
+                     top -2
+                     left -2
+                     has-modeline-p nil)))
+(frame-notice-user-settings)
+</PRE>
+<P>
+<STRONG>NOTE:</STRONG> The single minibuffer frame may not be to everyone's
+taste, and there any number of other XEmacs options settings that may make
+it difficult or inconvenient to use.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="x-windows">3.1 X Window System &amp; Resources</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_1">Q3.1.1  Where is a list of X resources?</A></H2>
+Search through the <VAR>NEWS</VAR> file for <EM>X Resources</EM>.
+A fairly comprehensive list is given after it.
+<P>
+In addition, an <VAR>app-defaults</VAR> file is supplied,
+<VAR>etc/Emacs.ad</VAR>,
+listing the defaults.  The file <VAR>etc/sample.Xdefaults</VAR> gives a set
+of defaults that you might consider.  It is essentially the same as
+<VAR>etc/Emacs.ad</VAR> but some entries are slightly altered.  Be careful
+about installing the contents of this file into your <VAR>.Xdefaults</VAR>
+or <VAR>.Xresources</VAR> file if you use GNU Emacs under X11 as well.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_2">Q3.1.2  How can I detect a color display?</A></H2>
+You can test the return value of the function
+<EM>(device-class)</EM>, as in:
+<PRE>
+(when (eq (device-class) 'color)
+  (set-face-foreground  'font-lock-comment-face "Grey")
+  (set-face-foreground  'font-lock-string-face  "Red")
+  ....
+  )
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_3">Q3.1.3 `(set-screen-width)' worked in 19.6, but not in 19.13?</A></H2> 
+In Lucid Emacs 19.6 I did <CODE>(set-screen-width <VAR>characters</VAR>)</CODE> and <CODE>(set-screen-height <VAR>lines</VAR>)</CODE> in my <VAR>.emacs</VAR> instead of specifying <SAMP>Emacs*EmacsScreen.geometry</SAMP> in my <VAR>.Xdefaults</VAR> but this does not work in XEmacs 19.13.
+<P>
+These two functions now take frame arguments:
+<PRE>
+(set-frame-width (selected-frame) <VAR>characters</VAR>)
+(set-frame-height (selected-frame) <VAR>lines</VAR>)
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_4">Q3.1.4 Specifiying `Emacs*EmacsScreen.geometry' in `.emacs' does not work in 19.15? </A></H2>
+In XEmacs 19.11 I specified <SAMP>Emacs*EmacsScreen.geometry</SAMP> in my <VAR>.emacs</VAR> but this does not work in XEmacs 19.15.
+<P>
+We have switched from using the term 'screen' to using the term <EM>frame</EM>.
+<P>
+The correct entry for your <VAR>.Xdefaults</VAR> is now:
+<PRE>
+Emacs*EmacsFrame.geometry
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_5">Q3.1.5 How can I get the icon to just say <SAMP>XEmacs</SAMP></A></H2>
+I'd like the icon to just say `XEmacs', and not include the name of
+the current file in it.
+<P>
+Add the following line to your <VAR>.emacs</VAR>:
+<PRE>
+(setq frame-icon-title-format "XEmacs")
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_6">Q3.1.6 How can I have the window title area display the full path?</A></H2>
+I'd like to have the window title area display the full
+directory/name of the current buffer file and not just the name.
+<P>
+Add the following line to your <VAR>.emacs</VAR>:
+<PRE>
+(setq frame-title-format "%S: %f")
+</PRE>
+A more sophisticated title might be:
+<PRE>
+(setq frame-title-format
+  '("%S: " (buffer-file-name "%f" (dired-directory dired-directory "%b"))))
+</PRE>
+That is, use the file name, or the dired-directory, or the buffer name.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_7">Q3.1.7 `xemacs -name junk' doesn't work?</A></H2>
+When I run <SAMP>xterm -name junk</SAMP> I get an xterm whose class name according to xprop, is <SAMP>junk</SAMP>.  This is the way it's supposed to work, I think.  When I run <SAMP>xemacs -name junk</SAMP> the class name is not set to <SAMP>junk</SAMP>.  It's still <SAMP>emacs</SAMP>.  What does <SAMP>xemacs -name</SAMP> really do?  The reason I ask is that my window manager (fvwm) will make a window sticky and I use XEmacs to read my mail.  I want that XEmacs window to be sticky, without having to use the window manager's function to set the window sticky.  What gives?
+<P>
+<SAMP>xemacs -name</SAMP> sets the application name for the program (that is,
+the thing which normally comes from <CODE>argv[0]</CODE>).
+Using <SAMP>-name</SAMP>
+is the same as making a copy of the executable with that new name.  The
+WM_CLASS property on each frame is set to the frame-name, and the
+application-class.  So, if you did <SAMP>xemacs -name FOO</SAMP> and then
+created a frame named <SAMP>BAR</SAMP>, you'd get an X window with WM_CLASS =
+<SAMP>( "BAR", "Emacs")</SAMP>.  However, the resource hierarchy for this
+widget would be
+<PRE>
+Name:    FOO   .shell             .container   .BAR
+Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+</PRE>
+instead of the default
+<PRE>
+Name:    xemacs.shell             .container   .emacs
+Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+</PRE>
+It is arguable that the first element of WM_CLASS should be set to the
+application-name instead of the frame-name, but I think that's less
+flexible, since it does not give you the ability to have multiple
+frames with different WM_CLASS properties.  Another possibility would
+be for the default frame name to come from the application name instead
+of simply being <SAMP>emacs</SAMP>.  However, at this point, making that
+change would be troublesome: it would mean that many users would have to
+make yet another change to their resource files (since the default
+frame name would suddenly change from <SAMP>emacs</SAMP>
+to <SAMP>xemacs</SAMP>, or
+whatever the executable happened to be named), so we'd rather avoid it.
+<P>
+To make a frame with a particular name use:
+<PRE>
+(make-frame '((name . "the-name")))
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_1_8">Q3.1.8 When I start up XEmacs using <EM>-iconic</EM> it doesn't work right.</A></H2>
+Using <EM>-unmapped</EM> on the command line, and setting the
+<VAR>initiallyUnmapped</VAR> X Resource don't seem to help 
+much either ...
+<P>
+Ben Wing &lt;ben@666.com&gt; writes:<BR>
+Ugh, this stuff is such an incredible mess that I've about given up
+getting it to work.  The principal problem is numerous window-manager
+bugs ...
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="fonts">3.2 Textual Fonts &amp; Colors</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_2_1">Q3.2.1 How can I set color options from `.emacs'?</A></H2>
+How can I set the most commonly used color options from my <VAR>.emacs</VAR> instead of from my <VAR>.Xdefaults</VAR>?
+<P>
+Like this:
+<PRE>
+(set-face-background 'default      "bisque")     ; frame background
+(set-face-foreground 'default      "black")      ; normal text
+(set-face-background 'zmacs-region "red")        ; When selecting w/
+                                                 ; mouse 
+(set-face-foreground 'zmacs-region "yellow")
+(set-face-font       'default      "*courier-bold-r*120-100-100*")
+(set-face-background 'highlight    "blue")       ; Ie when selecting buffers 
+(set-face-foreground 'highlight    "yellow")
+(set-face-background 'modeline     "blue")       ; Line at bottom of buffer
+(set-face-foreground 'modeline     "white")
+(set-face-font       'modeline     "*bold-r-normal*140-100-100*")
+(set-face-background 'isearch      "yellow")     ; When highlighting while
+                                                 ; searching		 
+(set-face-foreground 'isearch      "red")
+(setq x-pointer-foreground-color   "black")      ; Adds to bg color,
+                                                 ; so keep black
+(setq x-pointer-background-color   "blue")       ; This is color you really
+                                                 ; want ptr/crsr
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_2_2">Q3.2.2 How do I set the text, menu and modeline fonts?</A></H2>
+Note that you should use <EM>Emacs.</EM> and not <EM>Emacs*</EM> when
+setting face values.
+<P>
+In <VAR>.Xdefaults</VAR>:
+<PRE>
+Emacs.default.attributeFont:  -*-*-medium-r-*-*-*-120-*-*-m-*-*-* 
+Emacs*menubar*font:           fixed
+Emacs.modeline.attributeFont: fixed
+</PRE>
+<P>
+This is confusing because modeline is a face, and can be found listed
+with all faces in the current mode by using
+<KBD>M-x set-face-font (enter) ?</KBD>.
+It uses the face specification of <EM>attributeFont</EM>, while menubar is a
+normal X thing that uses the specification <EM>font</EM>.  With Motif it may be
+necessary to use <EM>fontList</EM> instead of <EM>font</EM>.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_2_3">Q3.2.3 How can I set the background/foreground colors when highlighting a region?</A></H2>
+You can change the face <VAR>zmacs-region</VAR> either in your
+<VAR>.Xdefaults</VAR>:
+<PRE>
+Emacs.zmacs-region.attributeForeground: firebrick
+Emacs.zmacs-region.attributeBackground: lightseagreen
+</PRE>
+or in your <VAR>.emacs</VAR>:
+<PRE>
+(set-face-background 'zmacs-region "red")   
+(set-face-foreground 'zmacs-region "yellow")
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_2_4">Q3.2.4 How can I limit color map usage?</A></H2>
+I'm using Netscape (or another color grabber like XEmacs);
+is there anyway to limit the number of available colors in the color map?
+<P>
+XEmacs 19.13 didn't have such a mechanism (unlike netscape, or other
+color-hogs).  One solution is to start XEmacs prior to netscape, since
+this will prevent Netscape from grabbing all colors (but Netscape will
+complain).   You can use the flags for Netscape, like -mono, -ncols &lt;#&gt;
+or -install  (for mono, limiting to &lt;#&gt; colors, or for using a private
+color map).  Since Netscape will take the entire colormap and never release
+it, the only reasonable way to run it is with <EM>-install</EM>.
+<P>
+If you have the money, another solution would be to use a truecolor or
+direct color video.
+<P>
+Starting with XEmacs 19.14, XEmacs will use the closest available color
+if the colormap is full, so it's O.K. now to start Netscape first.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_2_5">Q3.2.5 My tty supports color, but XEmacs doesn't use them</A></H2>
+XEmacs tries to automatically determine whether your tty supports
+color, but sometimes guesses wrong.  In that case, you can make
+XEmacs Do The Right Thing using this Lisp code:
+<PRE>
+(if (eq 'tty (device-type))
+    (set-device-class nil 'color))
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H1><IMG SRC="rd_ball.gif" ALT=""><A NAME="modeline">3.3 The Modeline</A></H1>
+<BR>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_3.1">Q3.3.1 How can I make the modeline go away?</A></H2>
+<PRE>
+(set-specifier has-modeline-p nil)
+</PRE>
+<P>
+Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if you
+haven't liked or used the modeline in the past, you might want to try the 
+new version out.
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_3_2">Q3.3.2 How do you have XEmacs display the line number in the modeline?</A></H2>
+Add the following line to your <VAR>.emacs</VAR> file to display the line
+number:
+<PRE>
+(setq line-number-mode t)
+</PRE>
+<P>
+Use the following to display the column number:
+<PRE>
+(setq display-column-mode t)
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_3_3">Q3.3.3 How do I get XEmacs to put the time of day on the modeline?</A></H2>
+<PRE>
+(display-time)
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_3_4">Q3.3.4 How do I turn off current chapter from AUC-TeX modeline?</A></H2> 
+With AUC-TeX, fast typing is hard because the current chapter/section/... is given in the modeline.  How can I turn this off?
+<P>
+It's not auc-tex, it comes from <CODE>func-menu</CODE> in
+<VAR>func-menu.el</VAR>.
+Add this code to your <VAR>.emacs</VAR> to turn it off:
+<PRE>
+(setq fume-display-in-modeline-p nil)
+</PRE>
+Or just add a hook to <CODE>TeX-mode-hook</CODE> to turn it off only for TeX
+mode. 
+<PRE>
+(add-hook 'TeX-mode-hook '(lambda () (setq fume-display-in-modeline-p nil)))
+</PRE>
+<P>
+David Hughes &lt;dhughes@origin-at.co.uk&gt; writes:
+<P>
+If you have 19.14 or later, try this instead; you'll still get the
+function name displayed in the modeline, but it won't attempt to keep 
+track when you modify the file. To refresh when it gets out of synch, you 
+simply need click on the <EM>Rescan Buffer</EM> option in the function-menu.
+<PRE>
+(setq-default fume-auto-rescan-buffer-p nil)
+</PRE>
+<H2><IMG SRC="grad_blu.gif" ALT="------------------------------"></H2>
+<H2><IMG SRC="cy_ball.gif" ALT="Subject: "><A NAME="Q3_3_5">Q3.3.5 How can one change the color of the modeline based on the mode used?</A></H2>
+You can use something like the following:
+<PRE>
+(add-hook 'lisp-mode-hook 
+        '(lambda () (set-face-background 'modeline "red" (current-buffer))
+                    (set-face-foreground 'modeline "yellow" (current-buffer))))
+</PRE>
+<P>
+Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
+colors change from the default set in your <VAR>.emacs</VAR>.  The change
+will only be made in the buffer you just entered (which contains the
+Lisp file you are editing) and will not affect the modeline colors
+anywhere else.