X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=man%2Fxemacs-faq.texi;h=404f85394f8f739eaf9290f08bec05c1ec979c3f;hb=8c147c0df83b61f902b930c7d8cefffd36025cd2;hp=ef0b785655033e2e1a0ed810f0f1f36072792231;hpb=b73e352f264e9da0a00159dc29f318305cbe8636;p=chise%2Fxemacs-chise.git.1

diff --git a/man/xemacs-faq.texi b/man/xemacs-faq.texi
index ef0b785..404f853 100644
--- a/man/xemacs-faq.texi
+++ b/man/xemacs-faq.texi
@@ -1,4 +1,4 @@
-\input texinfo.tex      @c -*-texinfo-*-
+\input texinfo.tex      @c -*- mode: texinfo; coding: iso-2022-8 -*-
 @c %**start of header
 @setfilename ../info/xemacs-faq.info
 @settitle Frequently asked questions about XEmacs
@@ -7,48 +7,143 @@
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 1999/12/07 03:11:46 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/10/14 02:11:49 $
 @sp 1
-@author Tony Rossini <arossini@@stat.sc.edu>
 @author Ben Wing <ben@@xemacs.org>
+@author Tony Rossini <rossini@@u.washington.edu>
 @author Chuck Thompson <cthomp@@xemacs.org>
 @author Steve Baur <steve@@xemacs.org>
 @author Andreas Kaempf <andreas@@sccon.com>
 @author Christian Nyb@o{} <chr@@mediascience.no>
-@author Sandra Wambold <wambold@@pobox.com>
+@author Sandra Wambold <wambold@@xemacs.org>
 @page
 @end titlepage
 
 @ifinfo
 @dircategory XEmacs Editor
 @direntry
-* FAQ: (xemacs-faq).		XEmacs FAQ.
+* FAQ: (xemacs-faq).            XEmacs FAQ.
 @end direntry
 @end ifinfo
 
+@ignore
+ *****************************************
+ ***** To update the menus and nodes *****
+ *****************************************
+
+First, the first argument to @node (the name itself) needs to be correct.
+Use a macro if necessary to update the @node names from the
+@unnumberedsubsec commands.  Also note that the command we're about to
+run will not correctly fix up the part of the menu to the right of a ::.
+It will leave existing text in place but not change anything.  If you
+make a lot of changes and want to update this semi-automatically, use
+M-x occur to pick out all @unnumberedsubsec lines then do some editing
+magic to coerce them into the right format and cut and paste as necessary:
+
+1. M-x occur @unnumberedsubsec
+2. <select a rectangle including all text before the Q#.#.#>
+3. C-x r t *<space>
+4. go to the top and use the following macro to get the indentation right.
+ 
+(setq last-kbd-macro (read-kbd-macro
+"C-s : RET : <right> M-x indent- to- column RET 14 RET <home> <down>"))
+
+5. Cut and paste the menus into the detailmenu at the top and
+   individual menus at the top of the appropriate chapters. (#### I
+   wonder, does texinfo-master-menu generate the detailmenu from the
+   individual menus or vice-versa or neither?)
+
+Then,
+
+6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
+   and nodes.  However, it appears that even though it tries to
+   preserve the existing menu structure as much as possible, it
+   doesn't do a perfect job.  It messes up in at least two ways: The
+   indentation in the part of the main menu above the detailmenu will
+   be screwed up, and the #.0 titles will be removed from both the
+   detailmenu and the individual chapter menus.  In addition,
+   sometimes random things get screwed up in individual parts of the
+   menus.  Therefore:
+
+   1. Use the Lisp line below to get the spacing correct for the Q#.#.#
+   menu entries.
+
+(set (make-local-variable 'texinfo-column-for-description) 14)
+
+   2. Copy the whole detailmenu beforehand.
+   3. Run C-u C-c C-u m to fix up the nodes.
+   4. Run `fix-main-menu' and `fix-omitted-menu-lines'.
+   5. Check the new detailmenu carefully to see if anything is screwed up
+      compared to the old detailmenu you copied.
+   6. If so, paste back the appropriate sections and fix up the corresponding
+      part of the chapter-specific menu.
+
+(defun fix-main-menu ()
+  (interactive)
+  (save-restriction
+    (let (p q)
+      (goto-char (point-min))
+      (re-search-forward "^@menu")
+      (setq p (match-beginning 0))
+      (re-search-forward "^$")
+      (setq q (match-end 0))
+      (narrow-to-region p q)
+      (goto-char p)
+      (while (search-forward "::  " nil t)
+        (indent-to-column 26)))))
+
+(defun fix-omitted-menu-lines ()
+  (interactive)
+  (save-excursion
+    (loop for x from 1 to 10 do
+      (goto-char (point-min))
+      (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x))
+      (let ((line (match-string 1)))
+	(re-search-backward "^@menu")
+	(forward-line 1)
+	(unless (looking-at "[0-9]+.0:")
+	  (insert line)
+	  (insert "\n"))
+	(goto-char (point-min))
+	(re-search-forward "^@menu")
+	(search-forward (format "Q%d.0.1:" x))
+	(forward-line -1)
+	(unless (looking-at "[0-9]+.0:")
+	  (insert "\n")
+	  (insert line))))))
+
+ *****************************************
+ *****            Other work         *****
+ *****************************************
+
+When you've rearranged and renumbered a bunch of nodes, you can get
+the numbers agreeing again.  The macro below assumes that the
+unnumberedsubsec number is correct, and fixes up the node to agree.
+Only the first part of the node is fixed and the other parts may still
+be wrong; but they will be fixed as part of
+@code{texinfo-master-menu}.
+
+(setq last-kbd-macro (read-kbd-macro
+"<f1> unnumberedsubsec SPC RET C-s : RET <left> C-x C-x <f3> <home> <up> <C-right> <right> C-s , RET <left> C-x C-x <f4> <home> 2*<down>"))
+@end ignore
+
+
 @node Top, Introduction, (dir), (dir)
 @top XEmacs FAQ
-@unnumbered Introduction
 
 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.
+programs ever written.  XEmacs is much more than just a Text Editor.
 
-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.
+This FAQ is freely redistributable.  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.
 
 If you have a Web browser, the official hypertext version is at
 @iftex
 @*
 @end iftex
-@uref{http://www.xemacs.org/faq/xemacs-faq.html}.
-
-This version is somewhat nicer than the unofficial hypertext versions
-that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
-archives.
+@uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
 
 @ifset CANONICAL
 @html
@@ -73,7 +168,7 @@ The canonical version of the FAQ is the texinfo document
 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
 download the faq} in info format, and install it in @file{<XEmacs
 library directory>/info/}. For example in
-@file{/usr/local/lib/xemacs-20.4/info/}.
+@file{/usr/local/lib/xemacs-21.4/info/}.
 
 @end itemize
 
@@ -84,333 +179,392 @@ library directory>/info/}. For example in
 @c end ifset points to CANONICAL
 
 @menu
-* Introduction::        Introduction, Policy, Credits.
-* Installation::        Installation and Trouble Shooting.
-* Customization::       Customization and Options.
-* Subsystems::          Major Subsystems.
-* Miscellaneous::       The Miscellaneous Stuff.
-* MS Windows::          XEmacs on Microsoft Windows.
-* Current Events::      What the Future Holds.
+* Introduction::          Introduction, Policy, Credits.
+* Installation::          Installation and Troubleshooting.
+* Editing::               Editing Functions.
+* Display::               Display Functions.
+* External Subsystems::   Interfacing with the OS and External Devices.
+* Internet::              Connecting to the Internet.
+* Advanced::              Advanced Customization Using XEmacs Lisp.
+* Other Packages::        Other External Packages.
+* Current Events::        What the Future Holds.
+* Legacy Versions::       New information about old XEmacsen.
 
 @detailmenu
-
  --- The Detailed Node Listing ---
 
-Introduction, Policy, Credits
-
-* Q1.0.1::      What is XEmacs?
-* Q1.0.2::      What is the current version of XEmacs?
-* Q1.0.3::      Where can I find it?
-* Q1.0.4::      Why Another Version of Emacs?
-* Q1.0.5::      Why Haven't XEmacs and GNU Emacs Merged?
-* Q1.0.6::      Where can I get help?
-* Q1.0.7::      Where is the mailing list archived?
-* Q1.0.8::      How do you pronounce XEmacs?
-* Q1.0.9::      What does XEmacs look like?
-* Q1.0.10::     Is there a port of XEmacs to Microsoft ('95 or NT)?
-* Q1.0.11::     Is there a port of XEmacs to the Macintosh?
-* Q1.0.12::     Is there a port of XEmacs to NextStep?
-* Q1.0.13::     Is there a port of XEmacs to OS/2?
-* Q1.0.14::     Where can I get a printed copy of the XEmacs users manual?
-
-Policies:
-* Q1.1.1::      What is the FAQ editorial policy?
-* Q1.1.2::      How do I become a Beta Tester?
-* Q1.1.3::      How do I contribute to XEmacs itself?
-
-Credits:
-* Q1.2.1::      Who wrote XEmacs?
-* Q1.2.2::      Who contributed to this version of the FAQ?
-* Q1.2.3::      Who contributed to the FAQ in the past?
-
-Internationalization:
-* Q1.3.1::      What is the status of XEmacs v20?
-* Q1.3.2::      What is the status of Asian-language support, aka @var{mule}?
-* Q1.3.3::      How do I type non-ASCII characters?
-* Q1.3.4::      Can XEmacs messages come out in a different language?
-* Q1.3.5::      Please explain the various input methods in MULE/XEmacs 20.0
-* Q1.3.6::      How do I portably code for MULE/XEmacs 20.0?
-* Q1.3.7::      How about Cyrillic Modes?
-
-Getting Started:
-* Q1.4.1::      What is a @file{.emacs} and is there a sample one?
-* Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
-* Q1.4.3::      Any good XEmacs tutorials around?
-* Q1.4.4::      May I see an example of a useful XEmacs Lisp function?
-* Q1.4.5::      And how do I bind it to a key?
-* Q1.4.6::      What's the difference between a macro and a function?
-* Q1.4.7::      Why options saved with 19.13 don't work with 19.14 or later?
-
-Installation and Trouble Shooting
-
-* Q2.0.1::      Running XEmacs without installing.
-* Q2.0.2::      XEmacs is too big.
-* Q2.0.3::      Compiling XEmacs with Netaudio.
-* Q2.0.4::      Problems with Linux and ncurses.
-* Q2.0.5::      Do I need X11 to run XEmacs?
-* Q2.0.6::      I'm having strange crashes.  What do I do?
-* Q2.0.7::      Libraries in non-standard locations.
-* Q2.0.8::      can't resolve symbol _h_errno
-* Q2.0.9::      Where do I find external libraries?
-* Q2.0.10::     After I run configure I find a coredump, is something wrong?
-* Q2.0.11::     XEmacs can't resolve host names.
-* Q2.0.12::     Why can't I strip XEmacs?
-* Q2.0.13::     Can't link XEmacs on Solaris with Gcc.
-* Q2.0.14::     Make on HP/UX 9 fails after linking temacs
-
-Trouble Shooting:
-* Q2.1.1::      XEmacs just crashed on me!
-* Q2.1.2::      Cryptic Minibuffer messages.
-* Q2.1.3::      Translation Table Syntax messages at Startup.
-* Q2.1.4::      Startup warnings about deducing proper fonts?
-* Q2.1.5::      XEmacs cannot connect to my X Terminal.
-* Q2.1.6::      XEmacs just locked up my Linux X server.
-* Q2.1.7::      HP Alt key as Meta.
-* Q2.1.8::      got (wrong-type-argument color-instance-p nil)!
-* Q2.1.9::      XEmacs causes my OpenWindows 3.0 server to crash.
-* Q2.1.10::     Warnings from incorrect key modifiers.
-* Q2.1.11::     Can't instantiate image error... in toolbar
-* Q2.1.12::     Regular Expression Problems on DEC OSF1.
-* Q2.1.13::     HP/UX 10.10 and @code{create_process} failure
-* Q2.1.14::     @kbd{C-g} doesn't work for me.  Is it broken?
-* Q2.1.15::     How to debug an XEmacs problem with a debugger.
-* Q2.1.16::     XEmacs crashes in @code{strcat} on HP/UX 10.
-* Q2.1.17::     @samp{Marker does not point anywhere}.
-* Q2.1.18::     19.14 hangs on HP/UX 10.10.
-* Q2.1.19::     XEmacs does not follow the local timezone.
-* Q2.1.20::     @samp{Symbol's function definition is void: hkey-help-show.}
-* Q2.1.21::     Every so often the XEmacs frame freezes.
-* Q2.1.22::     XEmacs seems to take a really long time to do some things.
-* Q2.1.23::     Movemail on Linux does not work for XEmacs 19.15 and later.
-
-Customization and Options
-
-* Q3.0.1::      What version of Emacs am I running?
-* Q3.0.2::      How do I evaluate Elisp expressions?
-* Q3.0.3::      @code{(setq tab-width 6)} behaves oddly.
-* Q3.0.4::      How can I add directories to the @code{load-path}?
-* Q3.0.5::      How to check if a lisp function is defined?
-* Q3.0.6::      Can I force the output of @code{(face-list)} to a buffer?
-* Q3.0.7::      Font selections don't get saved after @code{Save Options}.
-* Q3.0.8::      How do I make a single minibuffer frame?
-* Q3.0.9::      What is @code{Customize}?
-
-X Window System & Resources:
-* Q3.1.1::      Where is a list of X resources?
-* Q3.1.2::      How can I detect a color display?
-* Q3.1.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
-* Q3.1.4::      Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
-* Q3.1.5::      How can I get the icon to just say @samp{XEmacs}?
-* Q3.1.6::      How can I have the window title area display the full path?
-* Q3.1.7::      @samp{xemacs -name junk} doesn't work?
-* Q3.1.8::      @samp{-iconic} doesn't work.
-
-Textual Fonts & Colors:
-* Q3.2.1::      How can I set color options from @file{.emacs}?
-* Q3.2.2::      How do I set the text, menu and modeline fonts?
-* Q3.2.3::      How can I set the colors when highlighting a region?
-* Q3.2.4::      How can I limit color map usage?
-* Q3.2.5::      My tty supports color, but XEmacs doesn't use them.
-* Q3.2.6::      Can I have pixmap backgrounds in XEmacs?
-
-The Modeline:
-* Q3.3.1::      How can I make the modeline go away?
-* Q3.3.2::      How do you have XEmacs display the line number in the modeline?
-* Q3.3.3::      How do I get XEmacs to put the time of day on the modeline?
-* Q3.3.4::      How do I turn off current chapter from AUC TeX modeline?
-* Q3.3.5::      How can one change the modeline color based on the mode used?
-
-Multiple Device Support:
-* Q3.4.1::      How do I open a frame on another screen of my multi-headed display?
-* Q3.4.2::      Can I really connect to a running XEmacs after calling up over a modem?  How?
-
-The Keyboard:
-* Q3.5.1::      How can I bind complex functions (or macros) to keys?
-* Q3.5.2::      How can I stop down-arrow from adding empty lines to the bottom of my buffers?
-* Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
-* Q3.5.4::      Globally binding @kbd{Delete}?
-* Q3.5.5::      Scrolling one line at a time.
-* Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
-* Q3.5.7::      How can you type in special characters in XEmacs?
-* Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
-* Q3.5.9::      How do I make the Delete key delete forward?
-* Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
-* Q3.5.11::     How do I map the arrow keys?
-
-The Cursor:
-* Q3.6.1::      Is there a way to make the bar cursor thicker?
-* Q3.6.2::      Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
-* Q3.6.3::      Can I make the cursor blink?
-
-The Mouse and Highlighting:
-* Q3.7.1::      How can I turn off Mouse pasting?
-* Q3.7.2::      How do I set control/meta/etc modifiers on mouse buttons?
-* Q3.7.3::      Clicking the left button does not do anything in buffer list.
-* Q3.7.4::      How can I get a list of buffers when I hit mouse button 3?
-* Q3.7.5::      Why does cut-and-paste not work between XEmacs and a cmdtool?
-* Q3.7.6::      How I can set XEmacs up so that it pastes where the text cursor is?
-* Q3.7.7::      How do I select a rectangular region?
-* Q3.7.8::      Why does @kbd{M-w} take so long?
-
-The Menubar and Toolbar:
-* Q3.8.1::      How do I get rid of the menu (or menubar)?
-* Q3.8.2::      Can I customize the basic menubar?
-* Q3.8.3::      How do I control how many buffers are listed in the menu @code{Buffers} list?
-* Q3.8.4::      Resources like @code{Emacs*menubar*font} are not working?
-* Q3.8.5::      How can I bind a key to a function to toggle the toolbar?
-
-Scrollbars:
-* Q3.9.1::      How can I disable the scrollbar?
-* Q3.9.2::      How can one use resources to change scrollbar colors?
-* Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
-* Q3.9.4::      How can I get automatic horizontal scrolling?
-
-Text Selections:
-* Q3.10.1::     How can I turn off or change highlighted selections?
-* Q3.10.2::     How do I get that typing on an active region removes it?
-* Q3.10.3::     Can I turn off the highlight during isearch?
-* Q3.10.4::     How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
-* Q3.10.5::     The region disappears when I hit the end of buffer while scrolling.
-
-Major Subsystems
-
-* Q4.0.1::      How do I set up VM to retrieve remote mail using POP?
-* Q4.0.2::      How do I get VM to filter mail for me?
-* Q4.0.3::      How can I get VM to automatically check for new mail?
-* Q4.0.4::      [This question intentionally left blank]
-* Q4.0.5::      How do I get my outgoing mail archived?
-* Q4.0.6::      I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
-* Q4.0.7::      Is there a mailing list or FAQ for VM?
-* Q4.0.8::      Remote mail reading with VM.
-* Q4.0.9::      rmail or VM gets an error incorporating new mail.
-* Q4.0.10::     How do I make VM stay in a single frame?
-* Q4.0.11::     How do I make VM or mh-e display graphical smilies?
-* Q4.0.12::     Customization of VM not covered in the manual or here.
-
-Web browsing with W3:
-* Q4.1.1::      What is W3?
-* Q4.1.2::      How do I run W3 from behind a firewall?
-* Q4.1.3::      Is it true that W3 supports style sheets and tables?
-
-Reading Netnews and Mail with Gnus:
-* Q4.2.1::      GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
-* Q4.2.2::      [This question intentionally left blank]
-* Q4.2.3::      How do I make Gnus stay within a single frame?
-* Q4.2.4::      How do I customize the From: line?
-
-Other Mail & News:
-* Q4.3.1::      How can I read and/or compose MIME messages?
-* Q4.3.2::      What is TM and where do I get it?
-* Q4.3.3::      Why isn't this @code{movemail} program working?
-* Q4.3.4::      Movemail is also distributed by Netscape?  Can that cause problems?
-* Q4.3.5::      Where do I find pstogif (required by tm)?
-
-Sparcworks, EOS, and WorkShop:
-* Q4.4.1::      What is SPARCworks, EOS, and WorkShop
-* Q4.4.2::      How do I start the Sun Workshop support in XEmacs 21?
-
-Energize:
-* Q4.5.1::      What is/was Energize?
-
-Infodock:
-* Q4.6.1::      What is Infodock?
-
-Other Unbundled Packages:
-* Q4.7.1::      What is AUC TeX?  Where do you get it?
-* Q4.7.2::      Are there any Emacs Lisp Spreadsheets?
-* Q4.7.3::      Byte compiling AUC TeX on XEmacs 19.14
-* Q4.7.4::      Problems installing AUC TeX
-* Q4.7.5::      Is there a reason for an Emacs package not to be included in XEmacs?
-* Q4.7.6::      Is there a MatLab mode?
-
-The Miscellaneous Stuff
-
-* Q5.0.1::      How can I do source code highlighting using font-lock?
-* Q5.0.2::      I do not like cc-mode.  How do I use the old c-mode?
-* Q5.0.3::      How do I get @samp{More} Syntax Highlighting on by default?
-* Q5.0.4::      How can I enable auto-indent?
-* Q5.0.5::      How can I get XEmacs to come up in text/auto-fill mode by default?
-* Q5.0.6::      How do I start up a second shell buffer?
-* Q5.0.7::      Telnet from shell filters too much.
-* Q5.0.8::      Why does edt emulation not work?
-* Q5.0.9::      How can I emulate VI and use it as my default mode?
-* Q5.0.10::     [This question intentionally left blank]
-* Q5.0.11::     Filladapt doesn't work in 19.15?
-* Q5.0.12::     How do I disable gnuserv from opening a new frame?
-* Q5.0.13::     How do I start gnuserv so that each subsequent XEmacs is a client?
-* Q5.0.14::     Strange things are happening in Shell Mode.
-* Q5.0.15::     Where do I get the latest CC Mode?
-* Q5.0.16::     I find auto-show-mode disconcerting.  How do I turn it off?
-* Q5.0.17::     How can I get two instances of info?
-* Q5.0.18::     I upgraded to XEmacs 19.14 and gnuserv stopped working
-* Q5.0.19::     Is there something better than LaTeX mode?
-* Q5.0.20::     Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
-
-Emacs Lisp Programming Techniques:
-* Q5.1.1::      The difference in key sequences between XEmacs and GNU Emacs?
-* Q5.1.2::      Can I generate "fake" keyboard events?
-* Q5.1.3::      Could you explain @code{read-kbd-macro} in more detail?
-* Q5.1.4::      What is the performance hit of @code{let}?
-* Q5.1.5::      What is the recommended use of @code{setq}?
-* Q5.1.6::      What is the typical misuse of @code{setq} ?
-* Q5.1.7::      I like the the @code{do} form of cl, does it slow things down?
-* Q5.1.8::      I like recursion, does it slow things down?
-* Q5.1.9::      How do I put a glyph as annotation in a buffer?
-* Q5.1.10::     @code{map-extents} won't traverse all of my extents!
-* Q5.1.11::     My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
-
-Sound:
-* Q5.2.1::      How do I turn off the sound?
-* Q5.2.2::      How do I get funky sounds instead of a boring beep?
-* Q5.2.3::      What's NAS, how do I get it?
-* Q5.2.4::      Sunsite sounds don't play.
-
-Miscellaneous:
-* Q5.3.1::      How do you make XEmacs indent CL if-clauses correctly?
-* Q5.3.2::      Fontifying hangs when editing a postscript file.
-* Q5.3.3::      How can I print WYSIWYG a font-locked buffer?
-* Q5.3.4::      Getting @kbd{M-x lpr} to work with postscript printer.
-* Q5.3.5::      How do I specify the paths that XEmacs uses for finding files?
-* Q5.3.6::      [This question intentionally left blank]
-* Q5.3.7::      Can I have the end of the buffer delimited in some way?
-* Q5.3.8::      How do I insert today's date into a buffer?
-* Q5.3.9::      Are only certain syntactic character classes available for abbrevs?
-* Q5.3.10::     How can I get those oh-so-neat X-Face lines?
-* Q5.3.11::     How do I add new Info directories?
-* Q5.3.12::     What do I need to change to make printing work?
-
-XEmacs on MS Windows
-
-General Info:
-* Q6.0.1::	What is the status of the XEmacs port to Windows?
-* Q6.0.2::	What flavors of MS Windows are supported?
-* Q6.0.3::	Are binary kits available?
-* Q6.0.4::	Does XEmacs on MS Windows require an X server to run?
-
-Building XEmacs on MS Windows:
-* Q6.1.1::	I decided to run with X.  Where do I get an X server?
-* Q6.1.2::	What compiler do I need to compile XEmacs?
-* Q6.1.3::	How do I compile for the native port?
-* Q6.1.4::	How do I compile for the X port?
-* Q6.1.5::	How do I compile for Cygnus' Cygwin?
-* Q6.1.6::	What do I need for Cygwin?
-
-Customization and User Interface:
-* Q6.2.1::	How will the port cope with differences in the Windows user interface?
-* Q6.2.2::	How do I change fonts in XEmacs on MS Windows?
-* Q6.2.3::	Where do I put my @file{.emacs} file?
-
-Miscellaneous:
-* Q6.3.1::	Will XEmacs rename all the win32-* symbols to w32-*?
-* Q6.3.2::	What are the differences between the various MS Windows emacsen?
-* Q6.3.3::	What is the porting team doing at the moment?
-
-Current Events:
-
-* Q7.0.1::      What is new in 20.2?
-* Q7.0.2::      What is new in 20.3?
-* Q7.0.3::      What is new in 20.4?
-* Q7.0.4::      Procedural changes in XEmacs development.
+1 Introduction, Policy, Credits
+
+1.0: What is XEmacs?
+* Q1.0.1::    What is XEmacs?
+* Q1.0.2::    What is the current version of XEmacs?
+* Q1.0.3::    How do you pronounce XEmacs?
+* Q1.0.4::    What does XEmacs look like?
+* Q1.0.5::    Who wrote XEmacs?
+* Q1.0.6::    Who wrote the FAQ?
+
+1.1: Getting XEmacs
+* Q1.1.1::    Where can I find XEmacs?
+* Q1.1.2::    Are binaries available?
+* Q1.1.3::    How do I get the bleeding-edge sources?
+* Q1.1.4::    Where can I obtain a printed copy of the XEmacs User's Manual?
+
+1.2: Versions for Different Operating Systems
+* Q1.2.1::    Do I need X11 to run XEmacs?
+* Q1.2.2::    What versions of Unix does XEmacs run on?
+* Q1.2.3::    Is there a port of XEmacs to Microsoft Windows?
+* Q1.2.4::    Can I build XEmacs on MS Windows with X support?  Do I need to?
+* Q1.2.5::    What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q1.2.6::    What are the differences between the various MS Windows emacsen?
+* Q1.2.7::    How does the port cope with differences in the Windows user interface?
+* Q1.2.8::    Is there a port of XEmacs to the Macintosh?
+* Q1.2.9::    Is there a port of XEmacs to MS-DOS?
+* Q1.2.10::   Is there a port of XEmacs to OS/2?
+* Q1.2.11::   Is there a port of XEmacs to NextStep?
+* Q1.2.12::   Is there a port of XEmacs to VMS?
+
+1.3: Getting Started
+* Q1.3.1::    What is an @file{init.el} or @file{.emacs} and is there a sample one?
+* Q1.3.2::    Where do I put my @file{init.el} file?
+* Q1.3.3::    Can I use the same @file{init.el} with the other Emacs?
+* Q1.3.4::    Any good XEmacs tutorials around?
+* Q1.3.5::    May I see an example of a useful XEmacs Lisp function?
+* Q1.3.6::    And how do I bind it to a key?
+* Q1.3.7::    What's the difference between a macro and a function?
+* Q1.3.8::    What is @code{Custom}?
+
+1.4: Getting Help
+* Q1.4.1::    Where can I get help?
+* Q1.4.2::    Which mailing lists are there?
+* Q1.4.3::    Where are the mailing lists archived?
+* Q1.4.4::    How can I get two instances of info?
+* Q1.4.5::    How do I add new Info directories?
+
+1.5: Contributing to XEmacs
+* Q1.5.1::    How do I submit changes to the FAQ?
+* Q1.5.2::    How do I become a beta tester?
+* Q1.5.3::    How do I contribute to XEmacs itself?
+* Q1.5.4::    How do I get started developing XEmacs?
+* Q1.5.5::    What's the basic layout of the code?
+
+1.6: Politics (XEmacs vs. GNU Emacs)
+* Q1.6.1::    What is GNU Emacs?
+* Q1.6.2::    How does XEmacs differ from GNU Emacs?
+* Q1.6.3::    How much does XEmacs differ?
+* Q1.6.4::    Is XEmacs "GNU"?
+* Q1.6.5::    What is the correct way to refer to XEmacs and GNU Emacs?
+* Q1.6.6::    Why haven't XEmacs and GNU Emacs merged?
+
+1.7: External Packages
+* Q1.7.1::    What is the package system?
+* Q1.7.2::    Which external packages are there?
+* Q1.7.3::    Do I need to have the packages to run XEmacs? 
+* Q1.7.4::    Is there a way to find which package has particular functionality?
+
+1.8: Internationalization
+* Q1.8.1::    What is the status of internationalization support aka MULE (including Asian language support)?
+* Q1.8.2::    How can I help with internationalization?
+* Q1.8.3::    How do I type non-ASCII characters?
+* Q1.8.4::    Can XEmacs messages come out in a different language?
+* Q1.8.5::    Please explain the various input methods in MULE/XEmacs
+* Q1.8.6::    How do I portably code for MULE/XEmacs?
+* Q1.8.7::    How about Cyrillic modes?
+* Q1.8.8::    Does XEmacs support Unicode?
+* Q1.8.9::    How does XEmacs display Unicode?
+
+2 Installation and Troubleshooting
+
+2.0: Installation (General)
+* Q2.0.1::    How do I build and install XEmacs?
+* Q2.0.2::    Where do I find external libraries?
+* Q2.0.3::    How do I specify the paths that XEmacs uses for finding files?
+* Q2.0.4::    Running XEmacs without installing
+* Q2.0.5::    XEmacs is too big
+
+2.1: Package Installation
+* Q2.1.1::    How do I install the packages?
+* Q2.1.2::    Can I install the packages individually?
+* Q2.1.3::    Can I install the packages automatically?
+* Q2.1.4::    Can I upgrade or remove packages?
+* Q2.1.5::    Which packages to install?
+* Q2.1.6::    Can you describe the package location process in more detail?
+* Q2.1.7::    EFS fails with "500 AUTH not understood"
+
+2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
+* Q2.2.1::    Libraries in non-standard locations
+* Q2.2.2::    Why can't I strip XEmacs?
+* Q2.2.3::    X11/bitmaps/gray (or other X11-related file) not found.
+
+2.3: Windows Installation (Windows, Cygwin, MinGW)
+* Q2.3.1::    What exactly are all the different ways to build XEmacs under Windows?
+* Q2.3.2::    What compiler/libraries do I need to compile XEmacs?
+* Q2.3.3::    How do I compile the native port?
+* Q2.3.4::    What do I need for Cygwin?
+* Q2.3.5::    How do I compile under Cygwin?
+* Q2.3.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+* Q2.3.7::    How do I compile with X support?
+* Q2.3.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
+
+2.4: General Troubleshooting
+* Q2.4.1::    How do I deal with bugs or with problems building, installing, or running?
+* Q2.4.2::    Help!  XEmacs just crashed on me!
+* Q2.4.3::    XEmacs crashes and I compiled it myself.
+* Q2.4.4::    How to debug an XEmacs problem with a debugger
+* Q2.4.5::    I get a cryptic error message when trying to do something.
+* Q2.4.6::    XEmacs hangs when I try to do something.
+* Q2.4.7::    I get an error message when XEmacs is running in batch mode.
+* Q2.4.8::    The keyboard or mouse is not working properly, or I have some other event-related problem.
+* Q2.4.9::    @kbd{C-g} doesn't work for me.  Is it broken?
+* Q2.4.10::   How do I debug process-related problems?
+* Q2.4.11::   XEmacs is outputting lots of X errors.
+* Q2.4.12::   After upgrading, XEmacs won't do `foo' any more!
+
+2.5: Startup-Related Problems
+* Q2.5.1::    XEmacs cannot connect to my X Terminal!
+* Q2.5.2::    Startup problems related to paths or package locations.
+* Q2.5.3::    XEmacs won't start without network.
+* Q2.5.4::    Startup warnings about deducing proper fonts?
+* Q2.5.5::    Warnings from incorrect key modifiers.
+* Q2.5.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+
+3 Editing Functions
+
+3.0: The Keyboard
+* Q3.0.1::    How can I customize the keyboard?
+* Q3.0.2::    How can I bind complex functions (or macros) to keys?
+* Q3.0.3::    How do I bind C-. and C-; to scroll one line up and down?
+* Q3.0.4::    Globally binding @kbd{Delete}?
+* Q3.0.5::    How to map @kbd{Help} key alone on Sun type4 keyboard?
+* Q3.0.6::    How can you type in special characters in XEmacs?
+* Q3.0.7::    Can I turn on @dfn{sticky} modifier keys?
+* Q3.0.8::    How do I map the arrow keys?
+* Q3.0.9::    HP Alt key as Meta.
+* Q3.0.10::   Why does edt emulation not work?
+* Q3.0.11::   How can I emulate VI and use it as my default mode?
+
+3.1: The Mouse
+* Q3.1.1::    How can I turn off Mouse pasting?
+* Q3.1.2::    How do I set control/meta/etc modifiers on mouse buttons?
+* Q3.1.3::    Clicking the left button does not do anything in buffer list.
+* Q3.1.4::    How can I get a list of buffers when I hit mouse button 3?
+* Q3.1.5::    How can I set XEmacs up so that it pastes where the text cursor is?
+
+3.2: Buffers, Text Editing
+* Q3.2.1::    Can I have the end of the buffer delimited in some way?
+* Q3.2.2::    How do I insert today's date into a buffer?
+* Q3.2.3::    How do I get a single minibuffer frame?
+* Q3.2.4::    How can I enable auto-indent and/or Filladapt?
+* Q3.2.5::    How can I get XEmacs to come up in text/auto-fill mode by default?
+
+3.3: Text Selections
+* Q3.3.1::    How do I select a rectangular region?
+* Q3.3.2::    How can I turn off or change highlighted selections?
+* Q3.3.3::    How do I cause typing on an active region to remove it?
+* Q3.3.4::    Can I turn off the highlight during isearch?
+* Q3.3.5::    Why is killing so slow?
+* Q3.3.6::    Why does @kbd{M-w} take so long?
+
+3.4: Editing Source Code
+* Q3.4.1::    I do not like cc-mode.  How do I use the old c-mode?
+* Q3.4.2::    How do you make XEmacs indent CL if-clauses correctly?
+
+4 Display Functions
+
+4.0: Textual Fonts and Colors
+* Q4.0.1::    How do I specify a font?
+* Q4.0.2::    How do I set the text, menu and modeline fonts?
+* Q4.0.3::    How can I set color options from @file{init.el}?
+* Q4.0.4::    How can I set the colors when highlighting a region?
+* Q4.0.5::    How can I limit color map usage?
+* Q4.0.6::    My tty supports color, but XEmacs doesn't use them.
+* Q4.0.7::    Can I have pixmap backgrounds in XEmacs?
+* Q4.0.8::    How do I display non-ASCII characters?
+* Q4.0.9::    Font selections in don't get saved after @code{Save Options}.
+
+4.1: Syntax Highlighting (Font Lock)
+* Q4.1.1::    How can I do source code highlighting using font-lock?
+* Q4.1.2::    How do I get @samp{More} Syntax Highlighting on by default?
+
+4.2: The Modeline
+* Q4.2.1::    How can I make the modeline go away?
+* Q4.2.2::    How do you have XEmacs display the line number in the modeline?
+* Q4.2.3::    How do I get XEmacs to put the time of day on the modeline?
+* Q4.2.4::    How can I change the modeline color based on the mode used?
+
+4.3: The Cursor
+* Q4.3.1::    Is there a way to make the bar cursor thicker?
+* Q4.3.2::    Is there a way to get back the block cursor?
+* Q4.3.3::    Can I make the cursor blink?
+
+4.4: The Menubar
+* Q4.4.1::    How do I get rid of the menubar?
+* Q4.4.2::    How can I customize the menubar?
+* Q4.4.3::    How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
+* Q4.4.4::    How do I control how many buffers are listed in the menu @code{Buffers List}?
+* Q4.4.5::    Resources like @code{Emacs*menubar*font} are not working?
+
+4.5: The Toolbar
+* Q4.5.1::    How do I get rid of the toolbar?
+* Q4.5.2::    How can I customize the toolbar?
+* Q4.5.3::    How can I bind a key to a function to toggle the toolbar?
+* Q4.5.4::    @samp{Can't instantiate image error...} in toolbar
+
+4.6: Scrollbars and Scrolling
+* Q4.6.1::    How can I disable the scrollbar?
+* Q4.6.2::    How can I change the scrollbar width?
+* Q4.6.3::    How can I use resources to change scrollbar colors?
+* Q4.6.4::    Moving the scrollbar can move the point; can I disable this?
+* Q4.6.5::    Scrolling one line at a time.
+* Q4.6.6::    How can I turn off automatic horizontal scrolling in specific modes?
+* Q4.6.7::    I find auto-show-mode disconcerting.  How do I turn it off?
+
+4.7: The Gutter Tabs, The Progress Bar, Widgets
+* Q4.7.1::    How can I disable the gutter tabs?
+* Q4.7.2::    How can I disable the progress bar?
+* Q4.7.3::    There are bugs in the gutter or widgets.
+* Q4.7.4::    How can I customize the gutter or gutter tabs?
+
+5 Interfacing with the Operating System and External Devices
+
+5.0: X Window System and Resources
+* Q5.0.1::    Where is a list of X resources?
+* Q5.0.2::    How can I detect a color display?
+* Q5.0.3::    How can I get the icon to just say @samp{XEmacs}?
+* Q5.0.4::    How can I have the window title area display the full path?
+* Q5.0.5::    @samp{xemacs -name junk} doesn't work?
+* Q5.0.6::    @samp{-iconic} doesn't work.
+
+5.1: Microsoft Windows
+* Q5.1.1::    Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
+* Q5.1.2::    How do I get Windows Explorer to associate a file type with XEmacs?
+
+5.2: Printing
+* Q5.2.1::    What do I need to change to make printing work?
+* Q5.2.2::    How can I print WYSIWYG a font-locked buffer?
+* Q5.2.3::    Getting @kbd{M-x lpr} to work with postscript printer.
+* Q5.2.4::    Can you print under MS Windows?
+
+5.3: Sound
+* Q5.3.1::    How do I turn off the sound?
+* Q5.3.2::    How do I get funky sounds instead of a boring beep?
+* Q5.3.3::    What are NAS and ESD (EsounD)?
+* Q5.3.4::    Sunsite sounds don't play.
+
+5.4: Running an Interior Shell, Invoking Subprocesses
+* Q5.4.1::    What is an interior shell?
+* Q5.4.2::    How do I start up a second shell buffer?
+* Q5.4.3::    Telnet from shell filters too much
+* Q5.4.4::    Strange things are happening in Shell Mode.
+* Q5.4.5::    XEmacs complains "No such file or directory, diff"
+* Q5.4.6::    Cygwin error "fork_copy: linked dll/bss pass 0 failed"
+
+5.5: Multiple Device Support
+* Q5.5.1::    How do I open a frame on another screen of my multi-headed display?
+* Q5.5.2::    Can I really connect to a running XEmacs after calling up over a modem?  How?
+* Q5.5.3::    How do I disable gnuserv from opening a new frame?
+* Q5.5.4::    How do I start gnuserv so that each subsequent XEmacs is a client?
+* Q5.5.5::    Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
+
+6 Connecting to the Internet
+
+6.0: General Mail and News
+* Q6.0.1::    What are the various packages for reading mail?
+* Q6.0.2::    How can I send mail?
+* Q6.0.3::    How do I get my outgoing mail archived?
+* Q6.0.4::    How can I read and/or compose MIME messages?
+* Q6.0.5::    How do I customize the From line?
+* Q6.0.6::    How do I get my MUA to filter mail for me?
+* Q6.0.7::    Remote mail reading with an MUA.
+* Q6.0.8::    An MUA gets an error incorporating new mail.
+* Q6.0.9::    Why isn't @file{movemail} working?
+* Q6.0.10::   How do I make my MUA display graphical smilies?
+* Q6.0.11::   How can I get those oh-so-neat X-Face lines?
+
+6.1: Reading Mail with VM
+* Q6.1.1::    How do I set up VM to retrieve mail from a remote site using POP?
+* Q6.1.2::    How can I get VM to automatically check for new mail?
+* Q6.1.3::    I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
+* Q6.1.4::    Is there a mailing list or FAQ for VM?
+* Q6.1.5::    How do I make VM stay in a single frame?
+* Q6.1.6::    Customization of VM not covered in the manual, or here.
+
+6.2: Reading Netnews and Mail with Gnus
+* Q6.2.1::    GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
+* Q6.2.2::    How do I make Gnus stay within a single frame?
+
+6.3: FTP Access
+* Q6.3.1::    Can I edit files on other hosts?
+* Q6.3.2::    What is EFS?
+
+6.4: Web Browsing with W3
+* Q6.4.1::    What is W3?
+* Q6.4.2::    How do I run W3 from behind a firewall?
+* Q6.4.3::    Is it true that W3 supports style sheets and tables?
+
+7 Advanced Customization Using XEmacs Lisp
+
+7.0: Emacs Lisp and @file{init.el}
+* Q7.0.1::    What version of Emacs am I running?
+* Q7.0.2::    How can I evaluate Emacs-Lisp expressions?
+* Q7.0.3::    @code{(setq tab-width 6)} behaves oddly.
+* Q7.0.4::    How can I add directories to the @code{load-path}?
+* Q7.0.5::    How to check if a lisp function is defined?
+* Q7.0.6::    Can I force the output of @code{(face-list)} to a buffer?
+
+7.1: Emacs Lisp Programming Techniques
+* Q7.1.1::    What is the difference in key sequences between XEmacs and GNU Emacs?
+* Q7.1.2::    Can I generate "fake" keyboard events?
+* Q7.1.3::    Could you explain @code{read-kbd-macro} in more detail?
+* Q7.1.4::    What is the performance hit of @code{let}?
+* Q7.1.5::    What is the recommended use of @code{setq}?
+* Q7.1.6::    What is the typical misuse of @code{setq}?
+* Q7.1.7::    I like the @code{do} form of cl, does it slow things down?
+* Q7.1.8::    I like recursion, does it slow things down?
+* Q7.1.9::    How do I put a glyph as annotation in a buffer?
+* Q7.1.10::   @code{map-extents} won't traverse all of my extents!
+* Q7.1.11::   My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
+
+7.2: Mathematics
+* Q7.2.1::    What are bignums, ratios, and bigfloats in Lisp?
+* Q7.2.2::    XEmacs segfaults when I use very big numbers!
+* Q7.2.3::    Bignums are really slow!
+* Q7.2.4::    Equal bignums don't compare as equal!  What gives?
+
+8 Other External Packages
+
+8.0: TeX
+* Q8.0.1::    Is there something better than LaTeX mode?
+* Q8.0.2::    What is AUCTeX?  Where do you get it?
+* Q8.0.3::    Problems installing AUCTeX.
+* Q8.0.4::    How do I turn off current chapter from AUCTeX modeline?
+
+8.1: Other Unbundled Packages
+* Q8.1.1::    Is there a reason for an Emacs package not to be included in XEmacs?
+* Q8.1.2::    Are there any Emacs Lisp Spreadsheets?
+* Q8.1.3::    Is there a MatLab mode?
+
+8.2: Environments Built Around XEmacs
+* Q8.2.1::    What are SPARCworks, EOS, and WorkShop?
+* Q8.2.2::    How do I start the Sun Workshop support in XEmacs 21?
+* Q8.2.3::    What is/was Energize?
+* Q8.2.4::    What is Infodock?
+
+9 What the Future Holds
+
+9.0: Changes
+* Q9.0.1::    What new features will be in XEmacs soon?
+* Q9.0.2::    What's new in XEmacs 21.4?
+* Q9.0.3::    What's new in XEmacs 21.1?
+* Q9.0.4::    What's new in XEmacs 20.4?
+* Q9.0.5::    What's new in XEmacs 20.3?
+* Q9.0.6::    What's new in XEmacs 20.2?
+
+10 New information about old XEmacsen
+
+10.0: XEmacs 21.1
+* Q10.0.1::   Gnus 5.10 won't display smileys in XEmacs 21.1.
+* Q10.0.2::   XEmacs won't start on Windows in XEmacs 21.1.
+
 @end detailmenu
 @end menu
 
@@ -424,460 +578,403 @@ 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.
 
-The previous maintainer of the FAQ was @email{rossini@@stat.sc.edu,
-Anthony Rossini}, who started it, after getting tired of hearing JWZ
-complain about repeatedly having to answer questions.
-@email{ben@@xemacs.org, Ben Wing} and @email{cthomp@@xemacs.org, Chuck
-Thompson}, 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.
+The previous maintainer of the FAQ was
+@email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
+it, after getting tired of hearing JWZ complain about repeatedly
+having to answer questions.  @email{ben@@xemacs.org, Ben Wing} then
+took over and did a massive update reorganizing the whole thing.  At
+this 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.
 
 The previous version was converted to hypertext format, and edited by
 @email{steve@@xemacs.org, Steven L. Baur}.  It was converted back to
-texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}.
+texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}.  The FAQ was then
+maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
+on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
 
-The FAQ was then maintained by @email{andreas@@sccon.com, Andreas
-Kaempf}, who passed it on to @email{faq@@xemacs.org, Christian
-Nyb@o{}}, the current FAQ maintainer.
+The current version of the FAQ has been heavily redone by
+@email{ben@@xemacs.org, Ben Wing}.
 
 If you notice any errors or items which should be added or amended to
-this FAQ please send email to @email{faq@@xemacs.org, Christian
-Nyb@o{}}. Include @samp{XEmacs FAQ} on the Subject: line.
+this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
+Include @samp{XEmacs FAQ} on the Subject: line.
 
 @menu
-Introduction:
-* Q1.0.1::      What is XEmacs?
-* Q1.0.2::      What is the current version of XEmacs?
-* Q1.0.3::      Where can I find it?
-* Q1.0.4::      Why Another Version of Emacs?
-* Q1.0.5::      Why Haven't XEmacs and GNU Emacs Merged?
-* Q1.0.6::      Where can I get help?
-* Q1.0.7::      Where is the mailing list archived?
-* Q1.0.8::      How do you pronounce XEmacs?
-* Q1.0.9::      What does XEmacs look like?
-* Q1.0.10::     Is there a port of XEmacs to Microsoft ('95 or NT)?
-* Q1.0.11::     Is there a port of XEmacs to the Macintosh?
-* Q1.0.12::     Is there a port of XEmacs to NextStep?
-* Q1.0.13::     Is there a port of XEmacs to OS/2?
-* Q1.0.14::     Where can I get a printed copy of the XEmacs users manual?
-
-Policies:
-* Q1.1.1::      What is the FAQ editorial policy?
-* Q1.1.2::      How do I become a Beta Tester?
-* Q1.1.3::      How do I contribute to XEmacs itself?
-
-Credits:
-* Q1.2.1::      Who wrote XEmacs?
-* Q1.2.2::      Who contributed to this version of the FAQ?
-* Q1.2.3::      Who contributed to the FAQ in the past?
-
-Internationalization:
-* Q1.3.1::      What is the status of XEmacs v20?
-* Q1.3.2::      What is the status of Asian-language support, aka @var{mule}?
-* Q1.3.3::      How do I type non-ASCII characters?
-* Q1.3.4::      Can XEmacs messages come out in a different language?
-* Q1.3.5::      Please explain the various input methods in MULE/XEmacs 20.0
-* Q1.3.6::      How do I portably code for MULE/XEmacs 20.0?
-* Q1.3.7::      How about Cyrillic Modes?
-
-Getting Started:
-* Q1.4.1::      What is a @file{.emacs} and is there a sample one?
-* Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
-* Q1.4.3::      Any good XEmacs tutorials around?
-* Q1.4.4::      May I see an example of a useful XEmacs Lisp function?
-* Q1.4.5::      And how do I bind it to a key?
-* Q1.4.6::      What's the difference between a macro and a function?
-* Q1.4.7::      Why options saved with 19.13 don't work with 19.14 or later?
+1.0: What is XEmacs?
+* Q1.0.1::    What is XEmacs?
+* Q1.0.2::    What is the current version of XEmacs?
+* Q1.0.3::    How do you pronounce XEmacs?
+* Q1.0.4::    What does XEmacs look like?
+* Q1.0.5::    Who wrote XEmacs?
+* Q1.0.6::    Who wrote the FAQ?
+
+1.1: Getting XEmacs
+* Q1.1.1::    Where can I find XEmacs?
+* Q1.1.2::    Are binaries available?
+* Q1.1.3::    How do I get the bleeding-edge sources?
+* Q1.1.4::    Where can I obtain a printed copy of the XEmacs User's Manual?
+
+1.2: Versions for Different Operating Systems
+* Q1.2.1::    Do I need X11 to run XEmacs?
+* Q1.2.2::    What versions of Unix does XEmacs run on?
+* Q1.2.3::    Is there a port of XEmacs to Microsoft Windows?
+* Q1.2.4::    Can I build XEmacs on MS Windows with X support?  Do I need to?
+* Q1.2.5::    What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q1.2.6::    What are the differences between the various MS Windows emacsen?
+* Q1.2.7::    How does the port cope with differences in the Windows user interface?
+* Q1.2.8::    Is there a port of XEmacs to the Macintosh?
+* Q1.2.9::    Is there a port of XEmacs to MS-DOS?
+* Q1.2.10::   Is there a port of XEmacs to OS/2?
+* Q1.2.11::   Is there a port of XEmacs to NextStep?
+* Q1.2.12::   Is there a port of XEmacs to VMS?
+
+1.3: Getting Started
+* Q1.3.1::    What is an @file{init.el} or @file{.emacs} and is there a sample one?
+* Q1.3.2::    Where do I put my @file{init.el} file?
+* Q1.3.3::    Can I use the same @file{init.el} with the other Emacs?
+* Q1.3.4::    Any good XEmacs tutorials around?
+* Q1.3.5::    May I see an example of a useful XEmacs Lisp function?
+* Q1.3.6::    And how do I bind it to a key?
+* Q1.3.7::    What's the difference between a macro and a function?
+* Q1.3.8::    What is @code{Custom}?
+
+1.4: Getting Help
+* Q1.4.1::    Where can I get help?
+* Q1.4.2::    Which mailing lists are there?
+* Q1.4.3::    Where are the mailing lists archived?
+* Q1.4.4::    How can I get two instances of info?
+* Q1.4.5::    How do I add new Info directories?
+
+1.5: Contributing to XEmacs
+* Q1.5.1::    How do I submit changes to the FAQ?
+* Q1.5.2::    How do I become a beta tester?
+* Q1.5.3::    How do I contribute to XEmacs itself?
+* Q1.5.4::    How do I get started developing XEmacs?
+* Q1.5.5::    What's the basic layout of the code?
+
+1.6: Politics (XEmacs vs. GNU Emacs)
+* Q1.6.1::    What is GNU Emacs?
+* Q1.6.2::    How does XEmacs differ from GNU Emacs?
+* Q1.6.3::    How much does XEmacs differ?
+* Q1.6.4::    Is XEmacs "GNU"?
+* Q1.6.5::    What is the correct way to refer to XEmacs and GNU Emacs?
+* Q1.6.6::    Why haven't XEmacs and GNU Emacs merged?
+
+1.7: External Packages
+* Q1.7.1::    What is the package system?
+* Q1.7.2::    Which external packages are there?
+* Q1.7.3::    Do I need to have the packages to run XEmacs? 
+* Q1.7.4::    Is there a way to find which package has particular functionality?
+
+1.8: Internationalization
+* Q1.8.1::    What is the status of internationalization support aka MULE (including Asian language support)?
+* Q1.8.2::    How can I help with internationalization?
+* Q1.8.3::    How do I type non-ASCII characters?
+* Q1.8.4::    Can XEmacs messages come out in a different language?
+* Q1.8.5::    Please explain the various input methods in MULE/XEmacs
+* Q1.8.6::    How do I portably code for MULE/XEmacs?
+* Q1.8.7::    How about Cyrillic modes?
+* Q1.8.8::    Does XEmacs support Unicode?
+* Q1.8.9::    How does XEmacs display Unicode?
 @end menu
 
+@unnumberedsec 1.0: What is XEmacs?
+
 @node Q1.0.1, Q1.0.2, Introduction, Introduction
-@unnumberedsec 1.0: Introduction
 @unnumberedsubsec Q1.0.1: What is XEmacs?
 
-
-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.
+XEmacs is a powerful, highly customizable open source text editor and
+application development system, with full GUI support.  It is
+protected under the GNU Public License and related to other versions
+of Emacs, in particular GNU Emacs.  Its emphasis is on modern
+graphical user interface support and an open software development
+model, similar to Linux.  XEmacs has an active development community
+numbering in the hundreds (and thousands of active beta testers on top
+of this), and runs on all versions of MS Windows, on Mac OS X, on
+Linux, and on nearly every other version of Unix in existence.
+Support for XEmacs has been supplied by Sun Microsystems, University
+of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
+Corporation, BeOpen, and others, as well as the unpaid time of a great
+number of individual developers.
 
 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
 
-XEmacs 21.1.8 is the current stable version of XEmacs.
+XEmacs versions 21.4.* are releases made from the current stable
+sources.  XEmacs versions 21.5.* (which will be released as 22.0) are
+releases made from the development sources.  Check at
+@uref{http://www.xemacs.org} for the current minor version.  XEmacs
+versions 21.1.* were the previous stable releases, now retired.
 
-XEmacs 20.4 is a minor upgrade from 20.3, containing many bugfixes. It
-was released in February 1998.
+XEmacs 20.4, released in February 1998, was the last release of v20.
 
-XEmacs 19.16 was the last release of v19, released in November, 1997,
-which was also the last version without international language support.
+XEmacs 19.16, released in November, 1997. was the last release of v19,
+and was also the last version without international language support.
 
 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
-@unnumberedsubsec Q1.0.3: Where can I find it?
-
-The canonical source and binaries can be found via anonymous FTP at:
+@unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
 
-@example
-@uref{ftp://ftp.xemacs.org/pub/xemacs/}
-@end example
+The most common pronounciation is @samp{Eks eemax}.
 
 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
-@unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
+@unnumberedsubsec Q1.0.4: What does XEmacs look like?
 
-For a detailed description of the differences between GNU Emacs and
-XEmacs and a detailed history of XEmacs, check out the
-@example
-@uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
-@end example
+Screen snapshots are available at
+@uref{http://www.xemacs.org/About/Screenshots/index.html}
+as part of the XEmacs website.
 
-However, here is a list of some of the reasons why we think you might
-consider using it:
+@node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
+@unnumberedsubsec Q1.0.5: Who wrote XEmacs?
 
-@itemize @bullet
-@item
-It looks nicer.
+XEmacs is the result of the time and effort of many people, and the
+active developers have changed over time.  There are two major
+components of the XEmacs effort -- writing the code itself and providing
+all the support work (testing the code, releasing beta and final
+versions, handling patches, reading bug reports, maintaining the web
+site, managing the mailing lists, etc. etc.).  Neither component would
+work without the other.
 
-@item
-The XEmacs maintainers are generally more receptive to suggestions than
-the GNU Emacs maintainers.
+@subheading CODING
 
-@item
-Many more bundled packages than GNU Emacs
+The primary code contributor over the years has been Ben Wing (active
+since late 1992).  Between 1991 and 1995, large amounts of coding was
+contributed by Jamie Zawinski and Chuck Thompson.  Many other people
+have authored major subsystems or otherwise contributed large amounts of
+code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
+Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
+Mlynarik, Stig, William Perry and plenty of others.
 
-@item
-Binaries are available for many common operating systems.
+Primary XEmacs-specific subsystems and their authors:
 
+@table @asis
+@item Objects
+@itemize @minus
 @item
-Face support on TTY's.
-
+Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
 @item
-A built-in toolbar.
-
+Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
 @item
-Better Motif compliance.
-
+Portable dumper, object descriptions: Olivier Galibert
 @item
-Some internationalization support (including full MULE support, if
-compiled with it.)
-
+KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
 @item
-Variable-width fonts.
-
+Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
 @item
-Variable-height lines.
-
+Profiling: Ben Wing
 @item
-Marginal annotations.
-
+Some byte-compilation and hash-table improvements: Martin Buchholz
 @item
-ToolTalk support.
+Bignum: Jerry James
+@end itemize
 
+@item Internationalization/Mule
+@itemize @minus
 @item
-XEmacs can be used as an Xt widget, and can be embedded within another
-application.
+mostly Ben Wing; many ideas for future work, Stephen Turnbull
+@end itemize
 
+@item I/O
+@itemize @minus
 @item
-Horizontal and vertical scrollbars (using real toolkit scrollbars).
-
+Basic event/event-stream implementation: Jamie Zawinski
 @item
-Better APIs (and performance) for attaching fonts, colors, and other
-properties to text.
-
+Most event work since 1994: Ben Wing
 @item
-The ability to embed arbitrary graphics in a buffer.
-
+Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
 @item
-Completely compatible (at the C level) with the Xt-based toolkits.
-
+Process method abstraction, Windows process work: Kirill Katsnelson
+@item
+Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
 @item
-First production Web Browser supporting Style Sheets.
+Lstreams: Ben Wing
 @end itemize
 
-@node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
-@unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
-
-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.
-
-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 @email{xemacs-beta@@xemacs.org} and
-@email{bug-gnu-emacs@@prep.ai.mit.edu}.
-
-@node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
-@unnumberedsubsec Q1.0.6: Where can I get help?
-
-Probably the easiest way, if everything is installed, is to use Info, by
-pressing @kbd{C-h i}, or selecting @code{Manuals->Info} from the
-Help Menu.  @kbd{M-x apropos} can be used to look for particular commands.
-
-For items not found in the manual, try reading this FAQ
-@comment , examining the regular GNU Emacs FAQ (which can be
-@comment found with the Emacs 19 distribution) as well as at
-@comment @uref{http://www.eecs.nwu.edu/emacs/faq/}
-and reading the Usenet group comp.emacs.xemacs.
-
-If you choose to post to a newsgroup, @strong{please use
-comp.emacs.xemacs}.  Please do not post XEmacs related questions to
-gnu.emacs.help.
-
-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
-to @email{xemacs-request@@xemacs.org} with @samp{subscribe} in the
-body of the message.  Send to the list at @email{xemacs@@xemacs.org}.
-list.  To cancel a subscription, you @strong{must} use the
-xemacs-request address.  Send a message with a subject of
-@samp{unsubscribe} to be removed.
-
-@node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
-@unnumberedsubsec Q1.0.7: Where is the mailing list archived?
-
-The archives can be found at @uref{http://www.xemacs.org/Lists/Archive}
-
-@node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
-@unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
-
-The most common pronounciation is @samp{Eks eemax}.
-
-@node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
-@unnumberedsubsec Q1.0.9: What does XEmacs look like?
-
-Screen snapshots are available in the WWW version of the FAQ.
-@example
-@uref{http://www.xemacs.org/faq/xemacs-faq.html}
-@end example
-
-@node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
-@unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
-
-Yes, @xref{MS Windows}.
-
-@comment Thanks to efforts of many people, coordinated by
-@comment @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
-@comment Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
-@comment (NT and 95).  The current betas require having an X server to run
-@comment XEmacs; however, a native NT/95 port is in alpha, thanks to
-@comment @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
-@comment 
-@comment Although some features are still unimplemented, XEmacs 21.0 will support
-@comment MS-Windows.
-@comment 
-@comment The NT development is now coordinated by a mailing list at
-@comment @email{xemacs-nt@@xemacs.org}.
-@comment 
-@comment If you are willing to contribute or want to follow the progress, mail to
-@comment @iftex
-@comment @*
-@comment @end iftex
-@comment @email{xemacs-nt-request@@xemacs.org} to subscribe.
-@comment 
-@comment Furthermore, Altrasoft is seeking corporate and government sponsors to
-@comment help fund a fully native port of XEmacs to Windows 95 and NT using
-@comment full-time, senior-level staff working under a professionally managed
-@comment project structure.  See @uref{http://www.altrasoft.com/, the Altrasoft
-@comment web site} for more details
-@comment or contact Altrasoft directly at 1-888-ALTSOFT.
-@comment 
-@comment 
-@comment The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
-@comment Emacs 19.6.  Available from @uref{http://www.pearlsoft.com/}.
-@comment 
-@comment There's a port of GNU Emacs (not XEmacs) at
-@comment @example
-@comment @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
-@comment @end example
-
-@node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
-@unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
-@c changed
-
-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.
-
-For the MacOS, there is a port of
-@uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
-
-@node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
-@unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
-
-Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
-the port of GNU Emacs to NeXTstep and expressed interest in doing the
-XEmacs port, but never went any farther.
-
-@node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
-@unnumberedsubsec Q1.0.13: Is there a port of XEmacs to OS/2?
-
-No, and there is no news of anyone working on it.
-
-@node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
-@unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
-
-Pre-printed manuals are not available.  If you are familiar with 
-TeX, you can generate your own manual from the XEmacs sources.
-
-HTML and Postscript versions of XEmacs manuals may be available from the
-XEmacs web site in the future.
-
-
-@node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
-@unnumberedsec 1.1: Policies
-@unnumberedsubsec Q1.1.1: What is the FAQ editorial policy?
+@item Display
+@itemize @minus
+@item
+Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
+@item
+Glyphs: mostly Ben Wing
+@item
+Specifiers: Ben Wing
+@item
+Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
+@item
+Widgets: Andy Piper
+@item
+JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
+@item
+Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
+@item
+Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
+@item
+Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
+@item
+Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
+@item
+Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
+@item
+Toolbars: implementation, chuck, much interface work, Ben Wing
+@item
+Gutters, tabs: andy piper
+@end itemize
 
-The FAQ is actively maintained and modified regularly.  All links should
-be up to date.  All submissions are welcome.  E-mail submissions to
-@email{faq@@xemacs.org, XEmacs FAQ maintainers}.
+@item Device subsystems
+@itemize @minus
+@item
+X Windows: Jamie Zawinksi, Ben Wing, others
+@item
+GTK: William Perry, Malcolm Purvis
+@item
+MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
+@item
+TTY: Chuck Thompson, Ben Wing
+@item
+Cygwin: Andy Piper
+@end itemize
 
-Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
-If you think you have a better way of answering a question, or think a
-question should be included, we'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.
+@item Misc
+@itemize @minus
+@item
+Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
+@item
+Most initialization-related code: Ben Wing
+@item
+Internals manual, much of Lisp manual: Ben Wing
+@item
+FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
+@end itemize
+@end table
 
-@node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
-@unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
+@subheading SUPPORT
 
-Send an email message to @email{xemacs-beta-request@@xemacs.org} with
-the line @samp{subscribe} in the body of the message.
+Currently, support duties are handled by many different people.
 
-Be prepared to get your hands dirty, as beta testers are expected to
-identify problems as best they can.
+Release managers have been
 
-@node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
-@unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
+@itemize @minus
+@item
+Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present)
+@item
+Vin Shelton (Mar 1997 - Jan 2001, May 2003 - present, 19.16, 21.1.3 -
+21.1.14, 21.4.13 - present)
+@item
+Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
+@item
+Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1)
+@item
+Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
+@item
+Andy Piper (December 1998, 21.2.6)
+@item
+Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
+@item
+Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
+@end itemize
 
-Ben Wing @email{ben@@xemacs.org} writes:
+The recent overlapping dates are intentional, since two or three trees
+are maintained simultaneously at any point.
 
-@quotation
-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):
+Other major support work:
 
-@itemize @bullet
+@itemize @minus
 @item
-Make a posting about a feature you want added.
-
+Adrian Aichner wrote and maintains the web site.
 @item
-Become a beta tester and make more postings about those same features.
-
+Stephen Turnbull has produced many of the beta and semi-stable releases
+and has attempted to be the "face" of XEmacs on the newsgroups and
+mailing lists.
 @item
-Convince us that you're going to use the features in some cool and
-useful way.
-
+Steve Youngs currently produces the beta releases (???).
 @item
-Come up with a clear and well-thought-out API concerning the features.
-
+Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
+maintaining the packages.
 @item
-Write the code to implement a feature and send us a patch.
+Vin Shelton maintains the stable releases.
+@item
+Testing - #### Norbert, Adrian, ???
 @end itemize
 
-(not that we're necessarily requiring you to write the code, but we can
-always hope :)
-@end quotation
-
-@node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
-@unnumberedsec 1.2: Credits
-@unnumberedsubsec Q1.2.1: Who wrote XEmacs?
-
-XEmacs is the result of the time and effort of many people.  The
-developers responsible for the 19.16/20.x releases are:
+Portraits and email of some of the major developers:
 
 @itemize @bullet
-@item @email{martin@@xemacs.org, Martin Buchholz}
-@ifhtml
-<br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
-@end ifhtml
-
-
-@item @email{steve@@xemacs.org, Steve Baur}
+@item @email{andy@@xemacs.org, Andy Piper}
+@html
+<br><img src="piper.png" alt="Portrait of Andy Piper"><br>
+@end html
 
-@ifhtml
-<br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
-@end ifhtml
+@item @email{ben@@xemacs.org, Ben Wing}
+@html
+<br><img src="ben.png" alt="Portrait of Ben Wing"><br>
+@end html
 
+@item @email{cthomp@@xemacs.org, Chuck Thompson}
+@html
+<br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
+@end html
 
 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
 
-@ifhtml
-<br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
-@end ifhtml
-
-@end itemize
+@html
+<br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
+@end html
 
-The developers responsible for the 19.14 release are:
+@item @email{jwz@@jwz.org, Jamie Zawinski}
+@html
+<br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
+@end html
 
-@itemize @bullet
-@item @email{cthomp@@xemacs.org, Chuck Thompson}
-@ifhtml
-<br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
-@end ifhtml
+@item @email{martin@@xemacs.org, Martin Buchholz}
+@html
+<br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
+@end html
 
-Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
-for XEmacs becoming a widely distributed program over the Internet.
+@item @email{mly@@adoc.xerox.com, Richard Mlynarik}
+@html
+<br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
+@end html
 
-@item @email{ben@@xemacs.org, Ben Wing}
-@ifhtml
-<br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
-@end ifhtml
+@item @email{stephen@@xemacs.org, Stephen Turnbull}
 
+@item @email{steve@@xemacs.org, Steve Baur}
+@html
+<br><img src="slb.png" alt="Portrait of Steve Baur"><br>
+@end html
 @end itemize
 
+Many other people have contributed to XEmacs; this is partially
+enumerated in the @samp{About XEmacs} option in the Help menu.
 
-@itemize @bullet
-@item @email{jwz@@jwz.org, Jamie Zawinski}
-@ifhtml
-<br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
-@end ifhtml
-
-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.
-
-@item @email{mly@@adoc.xerox.com, Richard Mlynarik}
-@end itemize
-
-Along with many other contributors, partially enumerated in the
-@samp{About XEmacs} option in the Help menu.
+@node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
+@unnumberedsubsec Q1.0.6: Who wrote the FAQ?
 
-@node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
-@unnumberedsubsec Q1.2.2: Who contributed to this version of the FAQ?
+The current version of this FAQ was created by @email{ben@@xemacs.org,
+Ben Wing}.
 
-The following people contributed valuable suggestions to building this
-version of the FAQ (listed in alphabetical order):
+Previous contributors to the FAQ include
 
 @itemize @bullet
 @item @email{steve@@xemacs.org, SL Baur}
 
 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
 
-@item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
-
-@end itemize
-
-@node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
-@unnumberedsubsec Q1.2.3: Who contributed to the FAQ in the past?
-
-This is only a partial list, as many names were lost in a hard disk
-crash some time ago.
-
-@itemize @bullet
 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
 
+@item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
+
 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
 
 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
 
+@item @email{daku@@nortel.ca, Mark Daku}
+
 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
 
 @item @email{eeide@@cs.utah.edu, Eric Eide}
 
+@item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
+
 @item @email{cflatter@@nrao.edu, Chris Flatters}
 
 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
@@ -901,286 +998,453 @@ crash some time ago.
 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
 @end itemize
 
-@node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
-@unnumberedsec 1.3: Internationalization
-@unnumberedsubsec Q1.3.1: What is the status of XEmacs v20?
+@unnumberedsec 1.1: Getting XEmacs
 
-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, XEmacs 20.3 in November and XEmacs 20.4 in February 1998.  When compiled without MULE
-support, 20.4 is approximately as stable as 19.16, and probably faster
-(due to additional optimization work.)
+@node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
+@unnumberedsubsec Q1.1.1: Where can I find XEmacs?
 
-As of XEmacs 20.3, version 20 is @emph{the} 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.
+To download XEmacs, visit the XEmacs WWW page at
+@uref{http://www.xemacs.org/Download/}.  The most up-to-date list of
+distribution sites can always be found there.  Try to pick a site that
+is networkologically close to you.  If you know of other mirrors of
+the XEmacs archives, please send e-mail to
+@uref{mailto:webmaster@@xemacs.org} and we will list them here as well.
 
-The incompatible changes in XEmacs 20 include the additional byte-codes,
-new primitive data types (@code{character}, @code{char-table}, and
-@code{range-table}).  This means that the character-integer equivalence
-inherent to all the previous Emacs and XEmacs releases no longer
-applies.
+The canonical distribution point is ftp.xemacs.org, available either
+through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP
+(@uref{ftp://ftp.xemacs.org/pub/xemacs/}).
 
-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.
+@node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
+@unnumberedsubsec Q1.1.2: Are binaries available?
+
+MS Windows binaries are available at
+@uref{http://www.xemacs.org/Download/win32/} for the native versions
+of 21.4 and 21.1.  Cygwin binaries are now available as part of the
+standard Cygwin installation process.  XEmacs also comes pre-built as
+part of many Linux distributions, such as Red Hat and SuSE.
+
+Otherwise, you will need to build XEmacs yourself or get your system
+administrator to do it.  Generally, this is not a difficult process
+under Unix and Mac OS X, as XEmacs has been tested under all of the
+common Unix versions and under Mac OS X and comes with an extensive
+configure script that is able to automatically detect most aspects of
+the configuration of your particular system.
+
+@node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
+@unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
+
+If you are interested in developing XEmacs, or getting the absolutely most
+recent, up-to-the-moment, bleeding-edge source code, you can directly
+access the master CVS source tree (read-only, of course, until you ask for
+and are granted permission to directly modify portions of the source tree)
+at cvs.xemacs.org.  Directions on how to access the source tree are located
+at @uref{http://www.xemacs.org/Develop/cvsaccess.html}.
+
+Nightly CVS snapshots are available at
+@uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
+
+@node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
+@unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual?
+
+Pre-printed manuals are not available.  If you are familiar with
+TeX, you can generate your own manual from the XEmacs sources.
 
-@quotation
-  In XEmacs version 19, and in all versions of FSF GNU Emacs, a
-@dfn{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 @sc{mule},
-i.e. Asian-language, support to be correctly implemented.)
-
-  Even in XEmacs version 20, remnants of the equivalence between
-characters and integers still exist; this is termed the @dfn{char-int
-confoundance disease}.  In particular, many functions such as @code{eq},
-@code{equal}, and @code{memq} have equivalent functions (@code{old-eq},
-@code{old-equal}, @code{old-memq}, 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 @code{old-} 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.
-
-  Every character has an equivalent integer, called the @dfn{character
-code}.  For example, the character @kbd{A} is represented as the
-@w{integer 65}, following the standard @sc{ascii} representation of
-characters.  If XEmacs was not compiled with @sc{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 @emph{not} rely on this, because it
-will not work under XEmacs with @sc{mule} support.)  When @sc{mule}
-support is present, the range of character codes is much
-larger. (Currently, 19 bits are used.)
-
-  FSF GNU Emacs uses kludgy character codes above 255 to represent
-keyboard input of @sc{ascii} characters in combination with certain
-modifiers.  XEmacs does not use this (a more general mechanism is
-used that does not distinguish between @sc{ascii} keys and other
-keys), so you will never find character codes above 255 in a
-non-@sc{mule} XEmacs.
-
-  Individual characters are not often used in programs.  It is far more
-common to work with @emph{strings}, which are sequences composed of
-characters.
-@end quotation
+HTML and Postscript versions of XEmacs manuals are available from the
+XEmacs web site at
+@uref{http://www.xemacs.org/Documentation/index.html}.
 
-@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
-@unnumberedsubsec Q1.3.2: What is the status of Asian-language support, aka MULE?
+@unnumberedsec 1.2: Versions for Different Operating Systems
 
-MULE support is now available for UNIX versions of XEmacs.  
+@node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
+@unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs?
 
-If you would like to help, you may want to join the
-@email{xemacs-mule@@xemacs.org} mailing list.  Especially needed are
-people who speak/write languages other than English, who are willing to
-use XEmacs/MULE regularly, and have some experience with Elisp.
+No.  The name @dfn{XEmacs} is unfortunate in the sense that it is
+@strong{not} an X Window System-only version of Emacs.  XEmacs has
+full color support on a color-capable character terminal.
 
-@xref{Q1.1.2}.
+@node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
+@unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
 
-@node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
-@unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
+XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD,
+OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably
+others.  It should work on all versions of Unix created in the last 10
+years or so, perhaps with a bit of work on more obscure platforms to
+correct bit-rot.  It uses a sophisticated configuration system to
+auto-detect zillions of features that are implemented differently in
+different versions of Unix, so it will probably work on your vendor's
+version, possibly with a bit of tweaking, even if we've never heard of
+it.
 
-See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
+For problems with particular machines and versions of Unix, see the
+@file{PROBLEMS} file.
 
-@node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
-@unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
+Much effort has gone into making XEmacs work on as many different
+machines, configurations, and compilers as possible.
 
-The message-catalog support has mostly been written but doesn't
-currently work.  The first release of XEmacs 20 will @emph{not} support
-it.  However, menubar localization @emph{does} work, even in 19.14.  To
-enable it, add to your @file{Emacs} file entries like this:
+Much effort has gone into making XEmacs 64-bit clean.
+
+Much effort has gone into removing system-specific code, and replacing
+such code with autodetection at configure time.
+
+The XEmacs core should build "out of the box" on most Unix-like systems.
+
+XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix
+configurations as of 2001-02-10:
 
 @example
-Emacs*XlwMenu.resourceLabels:			True
-Emacs*XlwMenu.file.labelString:	        	Fichier
-Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster offnen
+alphaev56-dec-osf4.0e (both Compaq C and gcc)
+i386-unknown-freebsd4.2
+i386-unknown-netbsdelf1.5
+i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
+i686-pc-linux-gnu
+hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
+mips-sgi-irix6.5 (both MIPSpro cc and gcc)
+rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
+sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
+sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
+sparc-sun-sunos4.1.4 (gcc)
 @end example
 
-The name of the resource is derived from the non-localized entry by
-removing punctuation and capitalizing as above.
+Some systems have a dual mode 32-bit/64-bit compiler.  On most of these,
+XEmacs requires the @samp{--pdump} (in XEmacs 21.5,
+@samp{--enable-pdump}) configure option to build correctly with the
+64-bit version of the compiler.
 
-@node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
-@unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
+@example
+mips-sgi-irix6.5, CC="gcc -mabi=64"
+mips-sgi-irix6.5, CC="cc -64"
+rs6000-ibm-aix4.3.0.0, CC="cc -q64"
+@end example
 
-@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
+On most of these systems, XEmacs also builds with a C++ compiler,
+but not "out of the box".  This feature is only for use by the
+maintainers.
+
+XEmacs 21.2 is known @emph{not} to work on any machines with m680x0
+processors.  Sorry, all you sun3 and Unix PC nostalgia buffs out there.
+
+VMS has never been supported by XEmacs.  In fact, all the old VMS code
+inherited from Emacs has been removed.  Sorry, all you VMS fans out there.
+
+@node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
+@unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
+
+Yes.  Beginning with release 21.0, XEmacs has worked under MS Windows
+and is fully-featured and actively developed.  A group of dedicated
+developers actively maintains and improves the Windows-specific
+portions of the code.  Some of the core developers, in fact, use
+Windows as their only development environment, and some features, such
+as printing, actually work better on Windows than native Unix and Mac
+OS X.  The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
+to that effort (please use the -request address to
+subscribe). (Despite its name, XEmacs actually works on all versions
+of Windows.)
+
+The list name is misleading, as XEmacs supports and has been compiled on
+Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
+XP, and all newer versions of Windows.  The MS Windows-specific code is
+based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
+MS-DOS.
+
+XEmacs also supports the Cygwin and MinGW development and runtime
+environments, where it also uses native Windows code for graphical
+features.  In addition, under Cygwin it is possible to compile XEmacs
+to use an X server (and XFree86 is available as part of the standard
+Cygwin installation).
+
+@node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
+@unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support?  Do I need to?
+
+Yes, you can, but no you do not need to.  In fact, we recommend that you
+use a native-GUI version unless you have a specific need for an X
+version.
+
+@node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
+@unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
+
+To answer the second part of the question: No, you, you don't need
+Cygwin or MinGW to build or to run XEmacs.  But if you have them and
+want to use them, XEmacs supports these environments.
+
+(One important reason to support Cygwin is that it lets the MS Windows
+developers test out their code in a Unix environment without actually
+having to have a Unix machine around.  For this reason alone, Cygwin
+support is likely to remain supported for a long time in XEmacs.  Same
+goes for the X support under Cygwin, for the same reasons.  MinGW
+support, on the other hand, depends on volunteers to keep it up to date;
+but this is generally not hard.)
+
+Cygwin is a set of tools providing Unix-like API on top of Win32.
+It makes it easy to port large Unix programs without significant
+changes to their source code.  It is a development environment as well
+as a runtime environment.
+
+When built with Cygwin, XEmacs supports all display types -- TTY, X &
+Win32 GUI, and can be built with support for all three simultaneously.
+If you build with Win32 GUI support then the Cygwin version uses the
+majority of the Windows-specific code, which is mostly related to
+display.  If you want to build with X support you need X libraries (and
+an X server to display XEmacs on); see @ref{Q2.3.7}.  TTY and Win32 GUI
+require no additional libraries beyond what comes standard with Cygwin.
+
+The advantages of the Cygwin version are that it integrates well with
+the Cygwin environment for existing Cygwin users; uses configure so
+building with different features is very easy; and actively supports X &
+TTY.  Furthermore, the entire Cygwin environment and compiler are free,
+whereas Visual C++ costs money.
+
+The disadvantage is that it requires the whole Cygwin environment,
+whereas the native port requires only a suitable MS Windows compiler.
+Also, it follows the Unix filesystem and process model very closely
+(some will undoubtedly view this as an advantage).
+
+See @uref{http://www.cygwin.com/} for more information on
+Cygwin.
+
+MinGW is a collection of header files and import libraries that allow
+one to use GCC under the Cygwin environment to compile and produce
+exactly the same native Win32 programs that you can using Visual C++.
+Programs compiled with MinGW make use of the standard Microsoft runtime
+library @file{MSVCRT.DLL}, present on all Windows systems, and look,
+feel, and act like a standard Visual-C-produced application. (The only
+difference is the compiler.) This means that, unlike a
+standardly-compiled Cygwin application, no extra runtime support
+(e.g. Cygwin's @file{cygwin1.dll}) is required.  This, along with the
+fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
+environment, for those die-hard Unix hackers out there), is the main
+advantage of MinGW.  It is also potentially faster than Cygwin because
+it has less overhead when calling Windows, but you lose the POSIX
+emulation layer, which makes Unix programs harder to port. (But this is
+irrelevant for XEmacs since it's already ported to Win32.)
+
+See @uref{http://www.mingw.org/} for more information on MinGW.
+
+@node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
+@unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
 
-@quotation
-Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
-and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
-interface. Interface for Canna does not use @samp{egg}. I don't know
-about XIM. It is to support ATOK, of course, it may work for another
-servers.
+XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
+Could you briefly explain the differences between them?
 
-Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
-university. It is a powerful and complex system.  Wnn4 is free and Wnn6
-is not free.
+Here is a recount of various Emacs versions running on MS Windows:
 
-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).
+@itemize @bullet
 
-SJ3 supports only Japanese. It is made by Sony.  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).
+@item
+XEmacs
 
-Egg consists of following parts:
+@itemize @minus
 
-@enumerate
 @item
-Input character Translation System (ITS) layer.
-It translates ASCII inputs to Kana/PinYin/Hangul characters.
+Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
+in such a way to allow clean support of multiple window systems.  At
+this time the TTY support was added, making X and TTY the first two
+"window systems" supported by XEmacs.  The 19.12 design is the basis for
+the current native MS Windows code.
 
 @item
-Kana/PinYin/Hangul to Kanji transfer layer.
-It is interface layer for network Kana-Kanji server (Wnn and Sj3).
-@end enumerate
-
-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.  @samp{Boiled-egg} is a mode-less input method running on
-Egg.  For Canna, @samp{canna.el} has a tiny boiled-egg like command,
-@code{(canna-boil)}, and there are some boiled-egg like utilities.  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 GNU Emacs will be released,
-it will be continued.
-@end quotation
+Some time during 1997, David Hobley (soon joined by Marc Paquette)
+imported some of the NT-specific portions of GNU Emacs, making XEmacs
+with X support compile under Windows NT, and creating the "X" port.
 
-@node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
-@unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs 20?
+@item
+Several months later, Jonathan Harris sent out initial patches to use
+the Win32 API, thus creating the native port.  Since then, various
+people have contributed, including Kirill M. Katsnelson (contributed
+support for menubars, subprocesses and network, as well as loads of
+other code), Andy Piper (ported XEmacs to Cygwin environment,
+contributed Windows unexec, Windows-specific glyphs and toolbars code,
+and more), Ben Wing (loads of improvements; primary MS Windows developer
+since 2000), Jeff Sparkes (contributed scrollbars support) and many
+others.
+@end itemize
 
-@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
+@item
+NT Emacs
 
-@quotation
-MULE and XEmacs are quite different. So the application
-implementor must write separate code for these mule variants.
+@itemize @minus
 
-MULE and the next version of Emacs are similar but the symbols are very
-different---requiring separate code as well.
+@item
+NT Emacs was an early version of GNU Emacs 19 modified to compile and
+run under MS Windows 95 and NT using the native Win32 API.  It was
+written by Geoff Voelker, and has long since been incorporated into
+the mainline GNU Emacs distribution.
+@end itemize
 
-Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
-emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
-@code{emu} to provide a common interface.
+@item
+Win-Emacs
 
-I have the following suggestions about dealing with mule variants:
+@itemize @minus
 
-@itemize @bullet
 @item
-@code{(featurep 'mule)} @code{t} on all mule variants
+Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
+compatibility libraries.  Win-Emacs was written by Ben Wing.  The MS
+Windows code never made it back to Lucid Emacs, and its creator (Pearl
+Software) has long since gone out of business.
+@end itemize
 
 @item
-@code{(boundp 'MULE)} is @code{t} on only MULE.  Maybe the next version
-of Emacs will not have this symbol.
+GNU Emacs for DOS
+
+@itemize @minus
 
 @item
-MULE has a variable @code{mule-version}.  Perhaps the next version of
-Emacs will have this variable as well.
+GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
+port of GCC).  Such an Emacs is heavily underfeatured, because it does
+not support long file names, lacks proper subprocesses support, and
+is far too big compared with typical DOS editors.
 @end itemize
 
-Following is a sample to distinguish mule variants:
+@item
+GNU Emacs compiled with Win32
 
-@lisp
-(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
-  )
-@end lisp
-@end quotation
+@itemize @minus
 
-@node Q1.3.7, Q1.4.1, Q1.3.6, Introduction
-@unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
+@item
+Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
+under MS Windows using the DJGPP compiler and X libraries.  The result
+is very similar to GNU Emacs compiled under MS DOS, only it works
+somewhat better because it runs in 32-bit mode, makes use of all the
+system memory, supports long file names, etc.
+@end itemize
 
-@email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
+@end itemize
 
-@quotation
-There is a cyrillic mode in the file @file{mysetup.zip} in
-@iftex
-@*
-@end iftex
-@uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}.  This is a
-modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
-which can be obtained from
-@end quotation
+@node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
+@unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
+
+The XEmacs (and Emacs in general) user interface is pretty different
+from what is expected of a typical MS Windows program.  How does the MS
+Windows port cope with it?
+
+As a general rule, we follow native MS Windows conventions as much as
+possible.  21.4 is a fairly complete Windows application, supporting
+native printing, system file dialog boxes, tool tips, etc.  In cases
+where there's a clear UI conflict, we currently use normal Unix XEmacs
+behavior by default, but make sure the MS Windows "look and feel" (mark
+via shift-arrow, self-inserting deletes region, Alt selects menu items,
+etc.) is easily configurable (respectively: using the variable
+@code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
+the default in these versions], or the @file{pc-select} package; using
+the @file{pending-del} package; and setting the variable
+@code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
+In fact, if you use the sample @file{init.el} file as your init file,
+you will get all these behaviors automatically turned on.
+
+In future versions, some of these features might be turned on by
+default in the MS Windows environment.
 
-@uref{http://ftpsearch.ntnu.no/?query=russian.el.Z}.
-@c dead link above
+@node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
+@unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
 
-@email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
+Yes.
 
-@quotation
-There is another cyrillic mode for both GNU Emacs and XEmacs by
-@email{manin@@camelot.mssm.edu, Dmitrii
-(Mitya) Manin} at
-@iftex
+XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
+will not feel very much like a Mac application as it has no Mac-specific
+code in it.
 
-@end iftex
-@uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
-@c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
-@c Changed to russian host instead
-@end quotation
+There is also a port of XEmacs 19.14 that works on all recent versions
+of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
+Pitts Jarvis} (recently deceased).  It runs in an equivalent of TTY
+mode only (one single Macintosh window, 25 colors), but has a large
+number of Mac-specific additions.  It's available at
+@uref{http://homepage.mac.com/pjarvis/xemacs.html}.
 
-@email{rebecca.ore@@op.net, Rebecca Ore} writes:
+@node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
+@unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
 
-@quotation
-The fullest resource I found on Russian language use (in and out of
-XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
-@end quotation
+No.  We have never supported running on MS-DOS or Windows 3.1, and in
+fact have long since deleted all MS-DOS-related code.  We're not
+particularly interested in patches for these platforms, as they would
+introduce huge amounts of code clutter due to the woefully
+underfeatured nature of these systems. (See GNU Emacs for a port to
+MS-DOS.)
+
+@node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
+@unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
 
-@node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
-@unnumberedsec 1.4: Getting Started, Backing up & Recovery
-@unnumberedsubsec Q1.4.1: What is a @file{.emacs} and is there a sample one?
+No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
+working on it.
 
-The @file{.emacs} 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 @file{sample.emacs}.  Copy this file from there to your
-home directory and rename it @file{.emacs}.  Then edit it to suit.
+@node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
+@unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep?
+
+Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
+the port of GNU Emacs to NeXTstep and expressed interest in doing the
+XEmacs port, but never went any farther.
 
-Starting with 19.14, you may bring the @file{sample.emacs} into an
-XEmacs buffer by selecting @samp{Help->Sample .emacs} from the menubar.
-To determine the location of the @file{etc} directory type the command
+@node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
+@unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS?
+
+VMS has never been supported by XEmacs.  In fact, all the old VMS code
+inherited from GNU Emacs has been removed.  Sorry, all you VMS fans
+out there.
+
+@unnumberedsec 1.3: Getting Started
+
+@node Q1.3.1, Q1.3.2, Q1.2.12, Introduction
+@unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
+
+The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
+your tastes.  Starting in 21.4, the preferred location for the init file
+is @file{~/.xemacs/init.el}; in previous versions, it was
+@file{~/.emacs}.  21.4 still accepts the old location, but the first
+time you run it, it will ask to migrate your file to the new location.
+If you answer yes, the file will be moved, and a "compatibility"
+@file{.emacs} file will be placed in the old location so that you can
+still run older versions of XEmacs, and versions of GNU Emacs, which
+expect the old location.  The @file{.emacs} file present is just a stub
+that loads the real file in @file{~/.xemacs/init.el}.
+
+No two init files are alike, nor are they expected to be alike, but
+that's the point.  The XEmacs distribution contains an excellent starter
+example in the @file{etc/} directory called @file{sample.init.el}
+(starting in 21.4) or @file{sample.emacs} in older versions.  Copy this
+file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
+@file{~/.emacs} in older versions, where @samp{~} means your home
+directory, of course.  Then edit it to suit.
+
+You may bring the @file{sample.init.el} or @file{sample.emacs} file into
+an XEmacs buffer from the menubar. (The menu entry for it is always
+under the @samp{Help} menu, but its location under that has changed in
+various versions.  Recently, look under the @samp{Samples} submenu.)  To
+determine the location of the @file{etc/} directory type the command
 @kbd{C-h v data-directory @key{RET}}.
 
-@node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
-@unnumberedsubsec Q1.4.2: Can I use the same @file{.emacs} with the other Emacs?
+@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
+@unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file?
 
-Yes.  The sample @file{.emacs} included in the XEmacs distribution will
-show you how to handle different versions and flavors of Emacs.
+@file{init.el} is the name of the init file starting with 21.4, and is
+located in the subdirectory @file{.xemacs/} of your home directory.  In
+prior versions, the init file is called @file{.emacs} and is located in
+your home directory.
 
-@node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
-@unnumberedsubsec Q1.4.3: Any good tutorials around?
+Your home directory under Windows is determined by the @samp{HOME}
+environment variable.  If this is not set, it defaults to @samp{C:\}.
+To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
+select @samp{Control Panel->System->Advanced->Environment Variables...}
+under Windows NT/2000.
+
+@node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
+@unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs?
+
+Yes.  The sample @file{init.el} included in the XEmacs
+distribution will show you how to handle different versions and flavors
+of Emacs.
+
+@node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
+@unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
 
 There's the XEmacs tutorial available from the Help Menu under
-@samp{Basics->Tutorials}, or by typing @kbd{C-h t}. To check whether
+@samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
 the first letters of your preferred language, then type @key{RET}.
 
 @comment There's an Emacs Lisp tutorial at
-@comment 
+@comment
 @comment @example
 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
 @comment @end example
-@comment 
+@comment
 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
 @comment page at
 @comment @iftex
@@ -1188,8 +1452,8 @@ the first letters of your preferred language, then type @key{RET}.
 @comment @end iftex
 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
 
-@node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
-@unnumberedsubsec Q1.4.4: May I see an example of a useful XEmacs Lisp function?
+@node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
+@unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
 
 The following function does a little bit of everything useful.  It does
 something with the prefix argument, it examines the text around the
@@ -1223,8 +1487,8 @@ this will tell you that the @code{*} requires a writable buffer, and
 @code{p} converts the prefix argument to a number, and
 @code{interactive} allows you to execute the command with @kbd{M-x}.
 
-@node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
-@unnumberedsubsec Q1.4.5: And how do I bind it to a key?
+@node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
+@unnumberedsubsec Q1.3.6: And how do I bind it to a key?
 
 To bind to a key do:
 
@@ -1234,8 +1498,8 @@ To bind to a key do:
 
 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
 
-@node Q1.4.6, Q1.4.7, Q1.4.5, Introduction
-@unnumberedsubsec Q1.4.6: What's the difference between a macro and a function?
+@node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
+@unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
 
 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
 
@@ -1254,4151 +1518,5903 @@ Do not confuse the two terms with @dfn{keyboard macros}, which are
 another matter, entirely.  A keyboard macro is a key bound to several
 other keys.  Refer to manual for details.
 
-@node Q1.4.7, , Q1.4.6, Introduction
-@unnumberedsubsec Q1.4.7: How come options saved with 19.13 don't work with 19.14 or later?
+@node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
+@unnumberedsubsec Q1.3.8: What is @code{Custom}?
 
-There's a problem with options of the form:
+@code{Custom} is a system for customizing XEmacs options.
 
-@lisp
-(add-spec-list-to-specifier (face-property 'searchm-field 'font)
-                            '((global (nil))))
-@end lisp
+You can access @code{Advanced (Customize)} from the @code{Options} menu
+or invoking one of customize commands by typing eg.
+@kbd{M-x customize}, @kbd{M-x customize-face},
+@kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
 
-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 write the
-options directly to @file{.emacs} which should allow us to deal with
-version incompatibilities better in the future.
+There is also new @samp{browser} mode for Customize.
+Try it out with @kbd{M-x customize-browse}
 
-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
-using XEmacs v20.  You should consider changing the code to read:
+@unnumberedsec 1.4: Getting Help
 
-@lisp
-(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)))
-  ...
-  ))
-@end lisp
+@node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
+@unnumberedsubsec Q1.4.1: Where can I get help?
 
-@node Installation, Customization, Introduction, Top
-@unnumbered 2 Installation and Trouble Shooting
+Probably the easiest way, if everything is installed, is to use Info, by
+pressing @kbd{C-h i}, or looking for an Info item on the
+Help Menu.  @kbd{M-x apropos} can be used to look for particular commands.
 
-This is part 2 of the XEmacs Frequently Asked Questions list.  This
-section is devoted to Installation, Maintenance and Trouble Shooting.
+For items not found in the manual, try reading this FAQ
+and reading the Usenet group comp.emacs.xemacs.
 
-@menu
-Installation:
-* Q2.0.1::      Running XEmacs without installing.
-* Q2.0.2::      XEmacs is too big.
-* Q2.0.3::      Compiling XEmacs with Netaudio.
-* Q2.0.4::      Problems with Linux and ncurses.
-* Q2.0.5::      Do I need X11 to run XEmacs?
-* Q2.0.6::      I'm having strange crashes.  What do I do?
-* Q2.0.7::      Libraries in non-standard locations.
-* Q2.0.8::      can't resolve symbol _h_errno
-* Q2.0.9::      Where do I find external libraries?
-* Q2.0.10::     After I run configure I find a coredump, is something wrong?
-* Q2.0.11::     XEmacs can't resolve host names.
-* Q2.0.12::     Why can't I strip XEmacs?
-* Q2.0.13::     Can't link XEmacs on Solaris with Gcc.
-* Q2.0.14::     Make on HP/UX 9 fails after linking temacs
-
-Trouble Shooting:
-* Q2.1.1::      XEmacs just crashed on me!
-* Q2.1.2::      Cryptic Minibuffer messages.
-* Q2.1.3::      Translation Table Syntax messages at Startup.
-* Q2.1.4::      Startup warnings about deducing proper fonts?
-* Q2.1.5::      XEmacs cannot connect to my X Terminal.
-* Q2.1.6::      XEmacs just locked up my Linux X server.
-* Q2.1.7::      HP Alt key as Meta.
-* Q2.1.8::      got (wrong-type-argument color-instance-p nil)!
-* Q2.1.9::      XEmacs causes my OpenWindows 3.0 server to crash.
-* Q2.1.10::     Warnings from incorrect key modifiers.
-* Q2.1.11::     Can't instantiate image error... in toolbar
-* Q2.1.12::     Regular Expression Problems on DEC OSF1.
-* Q2.1.13::     HP/UX 10.10 and @code{create_process} failure
-* Q2.1.14::     @kbd{C-g} doesn't work for me.  Is it broken?
-* Q2.1.15::     How to debug an XEmacs problem with a debugger.
-* Q2.1.16::     XEmacs crashes in @code{strcat} on HP/UX 10.
-* Q2.1.17::     @samp{Marker does not point anywhere}.
-* Q2.1.18::     19.14 hangs on HP/UX 10.10.
-* Q2.1.19::     XEmacs does not follow the local timezone.
-* Q2.1.20::     @samp{Symbol's function definition is void: hkey-help-show.}
-* Q2.1.21::     Every so often the XEmacs frame freezes.
-* Q2.1.22::     XEmacs seems to take a really long time to do some things.
-* Q2.1.23::     Movemail on Linux does not work for XEmacs 19.15 and later.
-@end menu
+If you choose to post to a newsgroup, @strong{please use
+comp.emacs.xemacs}.  Please do not post XEmacs related questions to
+gnu.emacs.help.
 
-@node Q2.0.1, Q2.0.2, Installation, Installation
-@unnumberedsec 2.0: Installation
-@unnumberedsubsec Q2.0.1: Running XEmacs without installing
-The @file{INSTALL} file says that up to 108 MB of space is needed
-temporarily during installation!  How can I just try it out?
+If you cannot post or read Usenet news, there is a corresponding mailing
+list @email{xemacs-news@@xemacs.org} which is available.  It can be
+subscribed to via the Mailman Web interface or by sending mail to to
+@email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
+body of the message.  See also
+@uref{http://www.xemacs.org/Lists/#xemacs-news}.  To cancel a
+subscription, you may use the @email{xemacs-news-request@@xemacs.org}
+address or the Web interface.  Send a message with a subject of
+@samp{unsubscribe} to be removed.
 
-XEmacs will run in place without requiring installation and copying of
-the Lisp directories, and without having to specify a special build-time
-flag.  It's the copying of the Lisp directories that requires so much
-space.  XEmacs is largely written in Lisp.
+@node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
+@unnumberedsubsec Q1.4.2: Which mailing lists are there?
+
+For complete, up-to-date info on the lists and how to subscribe, see
+@uref{http://www.xemacs.org/Lists/}.
+
+@table @samp
+
+@item comp.emacs.xemacs
+is a Usenet newsgroup
+for XEmacs users to discuss problems and issues that arise
+for them.  It's not generally an appropriate place to ask
+about apparent bugs (use @samp{xemacs-beta}), or future plans
+(use @samp{xemacs-design}).
+
+@item xemacs-announce
+is a read-only, low
+volume list for announcements concerning the XEmacs project
+and new releases of the XEmacs software.
+
+@item xemacs-beta
+is an open list for bug reports about beta versions of XEmacs.  This
+includes the bug reports themselves, by both users and developers, as
+well as queries, follow-ups, and discussions further determining their
+nature and status.  This is the primary channel for this kind of
+discussion; related code changes will usually not be applied until
+they have been discussed here.  When such discussions touch on
+significant changes to the code (in particular, structural changes),
+or on changes to API's or external functionality, they should be moved
+to @samp{xemacs-design}.  Requests and proposals for non-bug-related
+changes do not belong on @samp{xemacs-beta}, and should be sent to
+@samp{xemacs-design} instead.
+
+@item xemacs-beta-ja
+is an open list for bug
+reports and design discussion related to Mule features,
+including Japanese handling, in beta versions of XEmacs.
+Japanese is the preferred language of discussion.  For most
+timely presentation to reviewers, please consider sending
+appropriate discussion to @samp{xemacs-mule} or
+@samp{xemacs-design} in English when convenient for
+the participants in discussion.  When possible, bug reports
+not related to Mule (including Japanese) should be reported on
+@samp{xemacs-beta} in English.
+
+@item xemacs-buildreports
+is an open list for
+submission of build-reports on beta versions of XEmacs. For
+information on what the build-reports should contain, please
+see the `etc/BETA' file which is included in each beta
+distribution.
+
+@item xemacs-cvs
+is a read-only list for notices
+and information on what has been committed to the XEmacs CVS
+trees, by whom, and for what.
+
+@item xemacs-design
+is an open list for
+discussing the design of XEmacs.  This includes discussion
+about planned and ongoing changes to functionality and API
+changes and additions as well as requests for them.  This is
+the primary channel for this kind of discussion; related code
+changes will usually not be applied until they have been
+discussed here.  This does not include bug reports, which go
+to @samp{xemacs-beta}.
+
+@item xemacs-mule
+is an open mailing list for
+discussion of International extensions to XEmacs including
+Mule, XIM, I18n issues, etc, and is not confined to
+developmental issues. This list is not restricted to
+English, postings in all languages are welcome.
+
+@item xemacs-news
+is an open list for discussion
+and bug reporting for XEmacs.  This mailing list is
+bi-directionally gatewayed with the USENET newsgroup
+comp.emacs.xemacs.
+
+@item xemacs-nt
+is a developers-only mailing
+list and is intended for people who wish to work actively on
+the porting of XEmacs to Microsoft Windows NT and Microsoft
+Windows '95.
+
+@item xemacs-patches
+is an open, moderated
+list for submission of patches to the XEmacs distribution
+and its packages. Anyone may subscribe or submit to
+xemacs-patches, but all submissions are reviewed by the list
+moderator before they are distributed to the
+list. Discussion is not appropriate on xemacs-patches.
+
+@item xemacs-users-ja
+is an open list for
+discussion and bug reporting for XEmacs.  Japanese is the
+preferred language of discussion.  It is not gated to
+comp.emacs.xemacs or the @samp{xemacs} list.  For
+fastest response, bugs not specifically related to Japanese
+or Mule features should be reported on
+@samp{xemacs-beta} (in English).
+
+@item xemacs-users-ru
+is an open list for
+discussion and bug reporting for XEmacs.  Russian is the
+preferred language of discussion.  It is not gated to
+comp.emacs.xemacs or the @samp{xemacs} list.  For
+fastest response, bugs not specifically related to Russian
+or Mule features should be reported on
+@samp{xemacs-beta} (in English).
+@end table
 
-A good method is to make a shell alias for xemacs:
+@node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
+@unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
 
-@example
-alias xemacs=/i/xemacs-20.2/src/xemacs
-@end example
+The archives can be found at @uref{http://list-archive.xemacs.org}
 
-(You will obviously use whatever directory you downloaded the source
-tree to instead of @file{/i/xemacs-20.2}).
+@node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
+@unnumberedsubsec Q1.4.4: How can I get two instances of info?
 
-This will let you run XEmacs without massive copying.
+Before 21.4, you can't.  The @code{info} package does not provide for
+multiple info buffers.  In 21.4, this should be fixed. #### how?
 
-@node Q2.0.2, Q2.0.3, Q2.0.1, Installation
-@unnumberedsubsec Q2.0.2: XEmacs is too big
+@node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
+@unnumberedsubsec Q1.4.5: How do I add new Info directories?
 
-Although this entry has been written for XEmacs 19.13, most of it still
-stands true.
+You use something like:
 
-@email{steve@@xemacs.org, Steve Baur} writes:
+@lisp
+(setq Info-directory-list (cons
+                           (expand-file-name "~/info")
+                           Info-default-directory-list))
+@end lisp
 
-@quotation
-The 45MB of space required by the installation directories can be
-reduced dramatically if desired.  Gzip all the .el files.  Remove all
-the packages you'll never want to use (or even ones you do like the two
-obsolete mailcrypts and Gnus 4 in 19.13).  Remove the TexInfo manuals.
-Remove the Info (and use just hardcopy versions of the manual).  Remove
-most of the stuff in etc.  Remove or gzip all the source code.  Gzip or
-remove the C source code.  Configure it so that copies are not made of
-the support lisp.  I'm not advocating any of these things, just pointing
-out ways to reduce the disk requirements if desired.
+@email{davidm@@prism.kla.com, David Masterson} writes:
 
-Now examine the space used by directory:
+@quotation
+Emacs Info and XEmacs Info do many things differently.  If you're trying to
+support a number of versions of Emacs, here are some notes to remember:
 
-@format
-0	/usr/local/bin/xemacs
-2048	/usr/local/bin/xemacs-19.13
+@enumerate
+@item
+Emacs Info scans @code{Info-directory-list} from right-to-left while
+XEmacs Info reads it from left-to-right, so append to the @emph{correct}
+end of the list.
 
-1546	/usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
-1158	/usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
-@end format
+@item
+Use @code{Info-default-directory-list} to initialize
+@code{Info-directory-list} @emph{if} it is available at startup, but not
+all Emacsen define it.
 
-You need to keep these.  XEmacs isn't stripped by default in
-installation, you should consider stripping.  That will save you about
-5MB right there.
+@item
+Emacs Info looks for a standard @file{dir} file in each of the
+directories scanned from #1 and magically concatenates them together.
 
-@format
-207	/usr/local/lib/xemacs-19.13/etc/w3
-122	/usr/local/lib/xemacs-19.13/etc/sounds
-18	/usr/local/lib/xemacs-19.13/etc/sparcworks
-159	/usr/local/lib/xemacs-19.13/etc/vm
-6	/usr/local/lib/xemacs-19.13/etc/e
-21	/usr/local/lib/xemacs-19.13/etc/eos
-172	/usr/local/lib/xemacs-19.13/etc/toolbar
-61	/usr/local/lib/xemacs-19.13/etc/ns
-43	/usr/local/lib/xemacs-19.13/etc/gnus
-@end format
+@item
+XEmacs Info looks for a @file{localdir} file (which consists of just the
+menu entries from a @file{dir} file) in each of the directories scanned
+from #1 (except the first), does a simple concatenation of them, and
+magically attaches the resulting list to the end of the menu in the
+@file{dir} file in the first directory.
+@end enumerate
 
-These are support directories for various packages.  In general they
-match a directory under ./xemacs-19.13/lib/xemacs-19.13/lisp/.  If you
-do not require the package, you may delete or gzip the support too.
+Another alternative is to convert the documentation to HTML with
+texi2html and read it from a web browser like Lynx or W3.
+@end quotation
 
-@format
-1959	/usr/local/lib/xemacs-19.13/etc
-175	/usr/local/lib/xemacs-19.13/lisp/bytecomp
-340	/usr/local/lib/xemacs-19.13/lisp/calendar
-342	/usr/local/lib/xemacs-19.13/lisp/comint
-517	/usr/local/lib/xemacs-19.13/lisp/dired
-42	/usr/local/lib/xemacs-19.13/lisp/electric
-212	/usr/local/lib/xemacs-19.13/lisp/emulators
-238	/usr/local/lib/xemacs-19.13/lisp/energize
-289	/usr/local/lib/xemacs-19.13/lisp/gnus
-457	/usr/local/lib/xemacs-19.13/lisp/ilisp
-1439	/usr/local/lib/xemacs-19.13/lisp/modes
-2276	/usr/local/lib/xemacs-19.13/lisp/packages
-1040	/usr/local/lib/xemacs-19.13/lisp/prim
-176	/usr/local/lib/xemacs-19.13/lisp/pcl-cvs
-154	/usr/local/lib/xemacs-19.13/lisp/rmail
-3	/usr/local/lib/xemacs-19.13/lisp/epoch
-45	/usr/local/lib/xemacs-19.13/lisp/term
-860	/usr/local/lib/xemacs-19.13/lisp/utils
-851	/usr/local/lib/xemacs-19.13/lisp/vm
-13	/usr/local/lib/xemacs-19.13/lisp/vms
-157	/usr/local/lib/xemacs-19.13/lisp/x11
-19	/usr/local/lib/xemacs-19.13/lisp/tooltalk
-14	/usr/local/lib/xemacs-19.13/lisp/sunpro
-291	/usr/local/lib/xemacs-19.13/lisp/games
-198	/usr/local/lib/xemacs-19.13/lisp/edebug
-619	/usr/local/lib/xemacs-19.13/lisp/w3
-229	/usr/local/lib/xemacs-19.13/lisp/eos
-55	/usr/local/lib/xemacs-19.13/lisp/iso
-59	/usr/local/lib/xemacs-19.13/lisp/mailcrypt
-187	/usr/local/lib/xemacs-19.13/lisp/eterm
-356	/usr/local/lib/xemacs-19.13/lisp/ediff
-408	/usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
-1262	/usr/local/lib/xemacs-19.13/lisp/hyperbole
-247	/usr/local/lib/xemacs-19.13/lisp/hm--html-menus
-161	/usr/local/lib/xemacs-19.13/lisp/mh-e
-299	/usr/local/lib/xemacs-19.13/lisp/viper
-53	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
-4	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib
-3	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib
-3	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib
-11	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
-53	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
-466	/usr/local/lib/xemacs-19.13/lisp/oobr
-14142	/usr/local/lib/xemacs-19.13/lisp
-@end format
+@unnumberedsec 1.5: Contributing to XEmacs
 
-These are all Emacs Lisp source code and bytecompiled object code.  You
-may safely gzip everything named *.el here.  You may remove any package
-you don't use.  @emph{Nothing bad will happen if you delete a package
-that you do not use}.  You must be sure you do not use it though, so be
-conservative at first.
+@node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
+@unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
 
-Possible candidates for deletion include w3 (newer versions exist, or
-you may just use Lynx or Netscape for web browsing), games, hyperbole,
-mh-e, hm--html-menus (better packages exist), vm, viper, oobr, gnus (new
-versions exist), etc.  Ask yourself, @emph{Do I ever want to use this
-package?}  If the answer is no, then it is a candidate for removal.
+The FAQ is actively maintained and modified regularly.  All links should
+be up to date.  Unfortunately, some of the information is out of date --
+a situation which the FAQ maintainer is working on.  All submissions are
+welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
+maintainers}.
 
-First, gzip all the .el files.  Then go about package by package and
-start gzipping the .elc files.  Then run XEmacs and do whatever it is
-you normally do.  If nothing bad happens, then delete the directory.  Be
-conservative about deleting directories, and it would be handy to have a
-backup tape around in case you get too zealous.
+Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
+If you think you have a better way of answering a question, or think a
+question should be included, we'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
+previous FAQ maintainers.  Answers quoted from Usenet news articles will
+always be attributed, regardless of the author.
 
-@file{prim}, @file{modes}, @file{packages}, and @file{utils} are four
-directories you definitely do @strong{not} want to delete, although
-certain packages can be removed from them if you do not use them.
+@node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
+@unnumberedsubsec Q1.5.2: How do I become a beta tester?
 
-@example
-1972	/usr/local/lib/xemacs-19.13/info
-@end example
+Send an email message to @email{xemacs-beta-request@@xemacs.org} with
+the line @samp{subscribe} in the body of the message.
 
-These are online texinfo sources.  You may either gzip them or remove
-them.  In either case, @kbd{C-h i} (info mode) will no longer work.
+Be prepared to get your hands dirty, as beta testers are expected to
+identify problems as best they can.
 
-@example
-20778	/usr/local/lib/xemacs-19.13
-@end example
+@node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
+@unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
 
-The 20MB achieved is less than half of what the full distribution takes up,
-@strong{and} can be achieved without deleting a single file.
-@end quotation
+It depends on the knowledge and time you possess.  If you are able, by
+all means become a beta tester (@pxref{Q1.5.2}).  If you are a
+programmer, try to build XEmacs and see if you can improve it.
 
-@email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} provides this procedure:
+Otherwise, you can still help by using XEmacs as your everyday editor
+(for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you
+find to the mailing list.
 
-@quotation
-Substitute @file{/usr/local/lib/} with the path where the xemacs tree is
-rooted, then use this script:
+Another area where we need help is the documentation: We need good
+documentation for building XEmacs and for using it.  This FAQ is a
+small step in that direction.
 
-@example
-#!/bin/sh
+Ben Wing @email{ben@@xemacs.org} writes:
 
-r=/usr/local/lib/xemacs-19.13/lisp
+@quotation
+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):
 
-cd $r ; rm -f cmpr ; touch cmpr
+@itemize @bullet
+@item
+Make a posting about a feature you want added.
 
-du -s .
+@item
+Become a beta tester and make more postings about those same features.
 
-for d in * ; do
-  if test -d $d ; then
-    cd $d
-    for f in *.el ; do
-#     compress (remove) only (ONLY) the sources that have a
-#     corresponding compiled file --- do not (DO NOT)
-#     touch other sources
-      if test -f $@{f@}c ; then gzip -v9 $f >> $r/cmpr ; fi
-    done
-    cd ..
-  fi
-done
+@item
+Convince us that you're going to use the features in some cool and
+useful way.
 
-du -s .
-@end example
+@item
+Come up with a clear and well-thought-out API concerning the features.
 
-A step beyond would be substituting @samp{rm -f} for @samp{gzip -v9},
-but you have to be desperate for removing the sources (remember that
-emacs can access compressed files transparently).
+@item
+Write the code to implement a feature and send us a patch.
+@end itemize
 
-Also, a good megabyte could easily be trimmed from the $r/../etc
-directory, e.g., the termcap files, some O+NEWS, others that I don't
-remember as well.
+(not that we're necessarily requiring you to write the code, but we can
+always hope :)
 @end quotation
 
-@quotation
-XEmacs 21.0 will unbundle the lisp hierarchy and allow the installer
-to choose exactly how much support code gets installed.
-@end quotation
+@node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
+@unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
 
-@node Q2.0.3, Q2.0.4, Q2.0.2, Installation
-@unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
+First, get yourself set up under CVS so that you can access the CVS
+repositories containing the XEmacs sources and the XEmacs packages.
 
-What is the best way to compile XEmacs with the netaudio system, since I
-have got the netaudio system compiled but installed at a weird place, I
-am not root.  Also in the READMEs it does not say anything about
-compiling with the audioserver?
+Next, set up your layout.  This is important, as a good layout will
+facilitate getting things done efficiently, while a bad layout will could
+lead to disaster, as you can't figure out which code is the most recent,
+which can be thrown away, etc.  We suggest the following layout: (feel free
+to make changes)
 
-You should only need to add some stuff to the configure command line.
-To tell it to compile in netaudio support: @samp{--with-sound=both}, or
-@samp{--with-sound=nas} if you don't want native sound support for some
-reason.) To tell it where to find the netaudio includes and libraries:
+@itemize @bullet
+@item
+Everything goes under @file{/src/xemacs} (use a different directory if
+you want).  From now, instead of saying @file{/src/xemacs}, we use
+@file{<xsrc-top>}, to make it easier in case someone picked a
+different directory.
 
-@example
---site-libraries=WHATEVER
---site-includes=WHATEVER
-@end example
+@item
+Package source is in @file{<xsrc-top>/package-src}.
 
-Then (fingers crossed) it should compile and it will use netaudio if you
-have a server running corresponding to the X server. The netaudio server
-has to be there when XEmacs starts. If the netaudio server goes away and
-another is run, XEmacs should cope (fingers crossed, error handling in
-netaudio isn't perfect).
+@item
+Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
+@file{<xsrc-top>/mule-packages}.
 
-BTW, netaudio has been renamed as it has a name clash with something
-else, so if you see references to NAS or Network Audio System, it's the
-same thing.  It also might be found at
-@uref{ftp://ftp.x.org/contrib/audio/nas/}.
+@item
+A "workspace" is a complete copy of the sources, in which you do work of
+a particular kind.  Workspaces can be differentiated by which branch of
+the source tree they extend off of -- usually either the stable or
+experimental, unless other branches have been created (for example, Ben
+created a branch for his Mule work because (1) the project was long-term
+and involved an enormous number of changes, (2) people wanted to be able
+to look at what his work in progress, and (3) he wanted to be able to
+check things in and in general use source-code control, since it was a
+long-term project).  Workspaces are also differentiated in what their
+purpose is -- general working workspace, workspace for particular
+projects, workspace keeping the latest copy of the code in one of the
+branches without mods, etc.
 
-@node Q2.0.4, Q2.0.5, Q2.0.3, Installation
-@unnumberedsubsec Q2.0.4: Problems with Linux and ncurses.
+@item
+Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
 
-On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
-5.2.18, XEmacs 20.0b20 is unable to open a tty device:
+@itemize @bullet
+@item
+@file{<xsrc-top>/working} (the workspace you're actively working on,
+periodically synched up with the latest trunk)
 
-@example
-src/xemacs -nw -q
-Initialization error:
-@iftex
-@*
-@end iftex
-Terminal type `xterm' undefined (or can't access database?)
-@end example
+@item
+@file{<xsrc-top>/stable} (for making changes to the stable version of
+XEmacs, which sits on a branch)
 
-@email{ben@@xemacs.org, Ben Wing} writes:
+@item
+@file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult
+task that's going to affect lots of source and take a long time, and
+so best done in its own workspace without the interference of other
+work you're doing.  Also, you can commit just this one large change,
+separate from all the other changes).
 
-@quotation
-Your ncurses configuration is messed up.  Your /usr/lib/terminfo is a
-bad pointer, perhaps to a CD-ROM that is not inserted.
-@end quotation
+@item
+@file{<xsrc-top>/latest} (a copy of the latest sources on the trunk,
+i.e. the experimental version of XEmacs, with no patches in it;
+either update it periodically, by hand, or set up a cron job to do it
+automatically).  Set it up so it can be built, and build it so you
+have a working XEmacs. (Building it might also go into the cron job.)
 
-@node Q2.0.5, Q2.0.6, Q2.0.4, Installation
-@unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
+This workspace serves a number of purposes:
+@enumerate
+@item
+You always have a recent version of XEmacs you can compare
+against when something you're working on breaks.  It's true
+that you can do this with cvs diff, but when you need to do
+some serious investigation, this method just fails.
+@item
+You (almost) always have a working, up-to-date executable that
+can be used when your executable is crashing and you need to
+keep developing it, or when you need an `xemacs' to build
+packages, etc.
+@item
+When creating new workspaces, you can just copy the `latest'
+workspace using GNU @code{cp -a}.  You have all the .elc's built,
+everything else probably configured, any spare files in place
+(e.g. some annoying xpm.dll under Windows, etc.).
+@end enumerate
 
-No.  The name @dfn{XEmacs} is unfortunate in the sense that it is
-@strong{not} an X Window System-only version of Emacs.  Starting with
-19.14 XEmacs has full color support on a color-capable character
-terminal.
+@item
+@file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but
+for the Stable branch of XEmacs, rather than the Experimental branch
+of XEmacs).  This may or may not be necessary depending on how much
+development you do of the stable branch.
+@end itemize
 
-@node Q2.0.6, Q2.0.7, Q2.0.5, Installation
-@unnumberedsubsec Q2.0.6: I'm having strange crashes.  What do I do?
+@item
+@file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
+web site.
 
-There have been a variety of reports of crashes due to compilers with
-buggy optimizers.  Please see the @file{PROBLEMS} file that comes with
-XEmacs to read what it says about your platform.
+@item
+@file{<xsrc-top>/in-patches} for patches received from email and saved
+to files.
 
-@node Q2.0.7, Q2.0.8, Q2.0.6, Installation
-@unnumberedsubsec Q2.0.7: Libraries in non-standard locations
+@item
+@file{<xsrc-top>/out-patches} for locally-generated patches to be sent
+to @email{xemacs-patches@@xemacs.org}.  Less useful now that the
+patcher util has been developed.
 
-I have x-faces, jpeg, xpm etc. all in different places.  I've tried
-space-separated, comma-separated, several --site-libraries, all to no
-avail.
+@item
+@file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with
+various configuration options turned off and on.  The scripts in
+xemacs-builds/ben (see below) can be used to automate building XEmacs
+workspaces with many different configuration options and automatically
+filtering out the normal output so that you see only the abnormal
+output.
 
-@example
---site-libraries='/path/one /path/two /path/etc'
-@end example
+@item
+@file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need
+to check out separately in CVS.  This contains scripts used for building
+XEmacs, automating and simplifying using CVS, etc.  Under various
+people's directories are their own build and other scripts.  The
+currently most-maintained scripts are under ben/, where there are easily
+configurable scripts that can be used to easily build any workspace
+(esp. if you've more or less followed the layout presented above)
+unattended, with one or more configuration states (there's a
+pre-determined list of the most useful, but it's easy to change).  The
+output is filtered and split up in various ways so that you can identify
+which output came from where, and you can see the output either full or
+with all "normal" output except occasional status messages filtered so
+that you only see the abnormal ones.
+@end itemize
+
+@node Q1.5.5, Q1.6.1, Q1.5.4, Introduction
+@unnumberedsubsec Q1.5.5: What's the basic layout of the code?
+
+The file @file{configure} is a shell script to acclimate XEmacs to the
+oddities of your processor and operating system.  It will create a
+file named @file{Makefile} (a script for the @file{make} program), which helps
+automate the process of building and installing emacs.  See INSTALL
+for more detailed information.
 
-@node Q2.0.8, Q2.0.9, Q2.0.7, Installation
-@unnumberedsubsec Q2.0.8: can't resolve symbol _h_errno
+The file @file{configure.in} is the input used by the autoconf program to
+construct the @file{configure} script.  Since XEmacs has configuration
+requirements that autoconf can't meet, @file{configure.in} uses an unholy
+marriage of custom-baked configuration code and autoconf macros; it
+may be wise to avoid rebuilding @file{configure} from @file{configure.in} when
+possible.
 
-You are using the Linux/ELF distribution of XEmacs 19.14, and your ELF
-libraries are out of date.  You have the following options:
+The file @file{Makefile.in} is a template used by @file{configure} to create
+@file{Makefile}.
+
+There are several subdirectories:
 
 @enumerate
 @item
-Upgrade your libc to at least 5.2.16 (better is 5.2.18, 5.3.12, or
-5.4.10).
-
+@file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
+primitives, the redisplay code, and some basic editing functions).
 @item
-Patch the XEmacs binary by replacing all occurrences of
-@samp{_h_errno^@@} with
-@iftex
-@*
-@end iftex
-@samp{h_errno^@@^@@}.  Any version of Emacs will
-suffice.  If you don't understand how to do this, don't do it.
-
+@file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else).
+@item
+@file{lib-src} holds the source code for some utility programs for use by
+or with XEmacs, like movemail and etags.
+@item
+@file{etc} holds miscellaneous architecture-independent data files
+XEmacs uses, like the tutorial text.  The contents of the @file{lisp},
+@file{info} and @file{man} subdirectories are architecture-independent too.
 @item
-Rebuild XEmacs yourself -- any working ELF version of libc should be
-O.K.
+@file{lwlib} holds the C code for the X toolkit objects used by XEmacs.
+@item
+@file{info} holds the Info documentation tree for XEmacs.
+@item
+@file{man} holds the source code for the XEmacs online documentation.
+@item
+@file{nt} holds files used compiling XEmacs under Microsoft Windows.
 @end enumerate
 
-@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
+@unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
 
-@quotation
-Why not use a Perl one-liner for No. 2?
+@node Q1.6.1, Q1.6.2, Q1.5.5, Introduction
+@unnumberedsubsec Q1.6.1: What is GNU Emacs?
+
+GNU Emacs and XEmacs are related open-source text editors.  Both
+derive from GNU Emacs version 18; the split between the two happened
+in 1991 (for comparison, the oldest versions of GNU Emacs date from
+1984).  For information on GNU Emacs, see
+@uref{http://www.gnu.org/software/emacs/emacs.html}.
 
+@node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
+@unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
+
+For a detailed description of the differences between GNU Emacs and
+XEmacs and a detailed history of XEmacs, check out the
 @example
-perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
-/usr/local/bin/xemacs-19.14
+@uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
 @end example
 
-NB: You @emph{must} patch @file{/usr/local/bin/xemacs-19.14}, and not
-@file{xemacs} because @file{xemacs} is a link to @file{xemacs-19.14};
-the Perl @samp{-i} option will cause unwanted side-effects if applied to
-a symbolic link.
-@end quotation
+@table @strong
+@item User-Visible Editing Features
+XEmacs in general tries hard to conform to exist user-interface
+standards, and to work "out-of-the-box" without the need for obscure
+customization changes.  GNU Emacs, particularly version 21, has gotten
+better about this (in many cases by copying the XEmacs behavior!), but
+still has some weirdnesses.  For example, the standard method of
+selecting text using the Shift key works out-of-the-box in XEmacs.
+
+XEmacs has a built-in toolbar. Four toolbars can actually be configured
+simultaneously: top, bottom, left, and right toolbars.
+
+XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 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.)
+
+XEmacs has buffer tabs along the top of the frame (although the
+position can be changed) that make it very easy to switch buffers.
+
+The menubar under XEmacs is better-designed, with more thought put into
+it.
+
+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.
+
+XEmacs under MS Windows provides uses the standard file-dialog box for
+opening and saving files.  Standard menu-accelerator behavior can easily
+be enabled using the Options menu, and integrates well into the existing
+keymap.
+
+XEmacs has (still experimental) support for widgets of various sorts --
+buttons, text boxes, sliders, progress bars, etc.  A progress bar is
+used in font lock to show the progress.
+
+Experimental support for drag-and-drop protocols is provided from
+XEmacs 21.
+
+@item General Platform Support
+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. XEmacs also supports the network sound protocols NAS and
+EsounD.
+
+XEmacs 21 supports database protocols with LISP bindings, currently
+including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
+
+XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
+servers directly, as well as through the X Input Method (XIM)
+protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
+support the Quail family of input methods (implemented in LISP) for many
+languages.
+
+XEmacs provides support for ToolTalk on systems that have
+it.
+
+@item Packaged LISP Libraries
+Many more packages are provided standard with XEmacs than with GNU Emacs
+19 or 20.
+
+XEmacs 21 supports an integrated package management system which uses
+EFS to download, then automatically install prebuilt LISP
+libraries. This allows XEmacs users much more straightforward access to
+the "latest and greatest" version of any given library.
+
+We are working on a standard method for enabling, disabling and
+otherwise controlling packages, which should make them very easy to use.
+
+@item LISP Programming
+From XEmacs 20 on, characters are a separate type. Characters can be
+converted to integers (and many integers can be converted to
+characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
+Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
+20 (incorporating Mule 3 and later Mule 4) represent them as integers.
+
+From XEmacs 20 on, the buffer is treated as an array of characters, and
+the representation of buffer text is not exposed to LISP. The GNU Emacs
+20 functions like buffer-as-multibyte are not supported.
+
+In XEmacs, events are first-class objects. GNU Emacs 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.
+
+In XEmacs, keymaps are first-class opaque objects. GNU Emacs 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, GNU Emacs 18, and GNU
+Emacs 19; if your code depends on the underlying implementation of
+keymaps, it will not.
+
+XEmacs uses "extents" to represent all non-textual aspects of buffers;
+GNU Emacs 19 uses two distinct objects, "text properties" and
+"overlays", which divide up the functionality between them. Extents are
+a superset of the union of the functionality of the two GNU Emacs data
+types. The full GNU Emacs 19 interface to text properties and overlays
+is supported in XEmacs (with extents being the underlying
+representation).
+
+Extents can be made to be copied into strings, and then restored, by
+kill and yank. Thus, one can specify this behavior on either "extents"
+or "text properties", whereas in GNU Emacs 19 text properties always
+have this behavior and overlays never do.
+
+@item Window System Programming Interface
+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
+arguments.
+
+XEmacs supports Motif applications, generic Xt (e.g. Athena)
+applications, and raw Xlib applications. An XEmacs variant which
+supports GTK+ is available (integration as an option in the XEmacs
+mainline is planned for XEmacs 22), although code to take advantage of
+the support is as yet scarce.
+
+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.
+
+@item Community Participation
+Joining the XEmacs development team is simple. Mail to
+@email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
+you want to be, of course. You're also welcome to just post
+development-related questions and bug reports.) The GNU Emacs
+development team and internal mailing lists are still by invitation
+only.
+
+The "bleeding edge" of mainline XEmacs development is available by
+anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
+module for the latest in GUI features!)
+
+Development and maintenance of Lisp libraries is separated from the core
+editor development at a fairly low level. This provides better
+modularization and a better division of responsibility between external
+library maintainers and the XEmacs core development team. Even for
+packages the size of Gnus, XEmacs users normally have access to a
+pre-built version within a few weeks of a major release, and minor
+updates often within days.
+
+CVS commit authority is broadly dispersed. Recognized maintainers of
+LISP libraries who are willing to maintain XEmacs packaged versions
+automatically qualify for CVS accounts for their packages.
+@end table
 
-@email{steve@@xemacs.org, SL Baur} writes:
+@node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
+@unnumberedsubsec Q1.6.3: How much does XEmacs differ?
 
-@quotation
-If you build against a recent libc-5.4 (late enough to have caused
-problems earlier in the beta cycle) and then run with an earlier version
-of libc, you get a
+RMS has asserted at times that XEmacs is merely a "patch" on top of
+GNU Emacs (@pxref{Q1.6.4}).  In fact, probably not more than 5% of the
+code, if that, remains unchanged, and nearly 14 years of work has gone
+into XEmacs at this point. (GNU Emacs itself is only than 20 years
+old, and thus XEmacs has existed as a separate product for over 2/3 of
+the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
+perhaps 65,000 more lines of C code than GNU Emacs 21.2.
 
-@example
-$ xemacs
-xemacs: can't resolve symbol '__malloc_hook'
-zsh: 7942 segmentation fault (core dumped)  xemacs
-@end example
+However, the XEmacs developers strive to keep their code compatible with
+GNU Emacs, especially on the Lisp level.  Much effort goes into
+"synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
+benefit from GNU Emacs development work. (In contrast, almost no code
+from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
+developers are instructed by RMS not to even look at XEmacs source code!
+This stems from self-imposed licensing restrictions on the part of GNU
+Emacs -- and almost certainly out of hostility, as well.)
+
+@node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
+@unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
 
-(Example binary compiled against libc-5.4.23 and run with libc-5.4.16).
+RMS insists on the term "GNU XEmacs" and maintains that
 
-The solution is to upgrade to at least libc-5.4.23.  Sigh.  Drat.
+@quotation
+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.
 @end quotation
 
-@node Q2.0.9, Q2.0.10, Q2.0.8, Installation
-@unnumberedsubsec Q2.0.9: Where do I find external libraries?
+In fact, FSF is @emph{not} the copyright holder for most of the code,
+as very little unmodified FSF code remains (@pxref{Q1.6.3}).
+
+Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
+to the XEmacs developers given RMS's hostility and general lack of
+interest in cooperation.  "GNU" software in general is part of the GNU
+Project, is distributed by it on their FTP site, and receives support
+(or at least cooperation), as well as implicit endorsement, from it.
+The GNU Project, however, has never supported XEmacs and never
+distributed XEmacs, and RMS's hostility is the farthest thing possible
+from an endorsement.  In fact, the GNU Project distributes a number of
+non-GNU software projects on the FSF web site, but again XEmacs is not
+one of them.
+
+@node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
+@unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
+
+Unfortunately even the naming of these two applications has become
+politicized.  Much of this stems from RMS, who has a history of
+politicizing similar issues. (Compare the controversy over "Lignux"
+and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
+Emacs" be used, which are neutral and acceptable to most people.  RMS,
+however, is not willing to accept these terms.  He insists that, if
+his product is called "GNU Emacs", then ours must be called "GNU
+XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other
+hand, if our product is to be called "XEmacs", as we prefer, then his
+product must simply be called "Emacs".  The intent of this seems
+clear: RMS wants to make sure the names reflect his view that his
+version is the "real" Emacs and ours is merely a derivative,
+second-class product (@pxref{Q1.6.3}).
+
+The XEmacs developers hope that you will use the neutral terms
+"XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
+the other hand, is a generic term for a class of programmable text
+editors with a similar look-and-feel, and usually a Lisp-based
+extension language.  These trace themselves back to early editors such
+as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
+internals, XEmacs Internals Manual}.
+
+We also call upon RMS, in the spirit of furthering cooperation, to
+stop politicizing this issue and use the neutral terms "XEmacs" and
+"GNU Emacs".  We have already acceded to RMS' wishes in this respect,
+and we expect him to do the same. (In the past, the XEmacs developers
+often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
+reference to GNU Emacs; these terms were apparently modeled after RMS'
+own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
+Emacs, produced by James Gosling.  RMS, however, considers such terms
+to be insulting, so we refrain from using them as much as possible in
+preference to GNU Emacs.)
+
+@node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
+@unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
 
-All external libraries used by XEmacs can be found at the XEmacs FTP
-site
-@iftex
-@*
-@end iftex
-@uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
+There are currently irreconcilable differences in the views about
+technical, programming, design, organizational and legal matters
+between Richard Stallman (RMS), the author and leader of the GNU Emacs
+project, and the XEmacs development team which provide little hope for
+a merge to take place in the short-term future.  There have been
+repeated attempts at merging by all of the major XEmacs developers,
+starting from the early days of Lucid Emacs (in 1991), but they have
+all failed.  RMS has very strong views about how GNU Emacs should be
+structured and how his project should be run, and during the repeated
+merge efforts has never demonstrated any realistic interest in
+sufficiently compromising or ceding control to allow a middle ground
+to be found.  The basic problem seems to be the very different goals
+of RMS and the XEmacs project.  The primary goals of the XEmacs
+project are technical and organizational -- we want to create the best
+editor possible, and to make it as easy as possible for people around
+the world to contribute.  The primary goals of RMS, on the other hand,
+are political, and GNU Emacs, and any potential merge efforts with
+XEmacs, are strictly subservient to these goals.  In fact, in many
+ways RMS sees GNU Emacs as the "poster child" of his aims, the one
+program in the GNU project that above all others must set an example
+to the world. (This has to do with the fact that GNU Emacs was the
+first program in the GNU project, and the only one that he is still
+personally involved with on a day-to-day basis.)  Given his goals, his
+position is completely reasonable -- but unfortunately, makes any
+merge impossible.
+
+From the XEmacs perspective, the most intractable issues appear to be
+legal and organizational, specifically:
 
-@c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
-@c This list is a pain in the you-know-what to keep in synch with the
-@c world.
-The canonical locations (at the time of this writing) are as follows:
+@itemize @bullet
+@item
+RMS requires "legal papers" to be signed for all contributions of code
+to GNU Emacs over 10 lines or so, transferring the copyright and all
+legal rights to the code to the Free Software Foundation.  XEmacs does
+not and has never required this, since it has the practical effect of
+discouraging individual and in particular corporate contributions --
+corporations will almost never sign away their legal rights to code
+since it makes it impossible to reuse the code in any product that
+whose license is not compatible with the GNU General Public License.
+Since RMS has shown no inclination to compromise on this issue, a
+merge would require that most of the existing XEmacs code would need
+to be thrown away and rewritten -- something the XEmacs developers are
+understandably reluctant to do.
 
-@table @asis
-@item JPEG
-@uref{ftp://ftp.uu.net/graphics/jpeg/}.  Version 6a is current.
-@c Check from host with legal IP address
-@item XPM
-@uref{ftp://ftp.x.org/contrib/libraries/}.  Version 3.4j is current.
-Older versions of this package are known to cause XEmacs crashes.
-
-@item TIFF
-@uref{ftp://ftp.sgi.com/graphics/tiff/}.  v3.4 is current.  The latest
-beta is v3.4b035.  There is a HOWTO here.
-
-@item PNG
-@uref{ftp://ftp.uu.net/graphics/png/}.  0.89c is current.  XEmacs
-requires a fairly recent version to avoid using temporary files.
-@c Check from host with legal IP address
-
-@uref{ftp://swrinde.nde.swri.edu/pub/png/src/}
-
-@item Compface
-@uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/}.  This library has
-been frozen for about 6 years, and is distributed without version
-numbers.  @emph{It should be compiled with the same options that X11 was
-compiled with on your system}.  The version of this library at
-XEmacs.org includes the @file{xbm2xface.pl} script, written by
-@email{stig@@hackvan.com}, which may be useful when generating your own xface.
-
-@item NAS
-@uref{ftp://ftp.x.org/contrib/audio/nas/}.
-Version 1.2p5 is current.  There is a FAQ here.
-@end table
+@item 
+A repeated stumbling block in the merge talks has been the issue of
+organizational control over the resulting product.  RMS has made it
+clear that he intends to have final say over design issues in a merged
+Emacs.  Unfortunately, RMS and the XEmacs developers have repeatedly
+clashed over design decisions, and RMS' insistence on getting his way
+in such disagreements was the very reason for the split in the first
+place.  This same issue has come up again and again in merge talks and
+we have never been able to come to a satisfactory resolution.  To the
+extent that RMS is willing to compromise at all, it appears to be of a
+purely political rather than technical nature -- "If we support this
+feature of yours, we also get to support this other feature of mine."
+The XEmacs developers cannot see how such a process would lead to
+anything but a mess of incompatible things hodgepodged together.
 
-@node Q2.0.10, Q2.0.11, Q2.0.9, Installation
-@unnumberedsubsec Q2.0.10: After I run configure I find a core dump, is something wrong?
+@item
+Because of the years of separate development, distinct and
+incompatible interfaces have developed and merging would be extremely
+difficult even with the above non-technical issues resolved.  The
+problem has been exacerbated by the issue of legal papers -- because
+XEmacs code is not "kosher" from RMS' perspective, he discourages
+developers from even looking at it out of legal concerns.  Although it
+is still possible to read the XEmacs documentation and run the
+program, the practical effect of this prohibition has been to strongly
+discourage code-sharing and cooperative development -- although a
+great deal of GNU Emacs code has been incorporated into XEmacs,
+practically none has gone the other direction.
+@end itemize
 
-Not necessarily.  If you have GNU sed 3.0 you should downgrade it to
-2.05.  From the @file{README} at prep.ai.mit.edu:
+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
+@email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
 
-@quotation
-sed 3.0 has been withdrawn from distribution.  It has major revisions,
-which mostly seem to be improvements; but it turns out to have bugs too
-which cause trouble in some common cases.
+@unnumberedsec 1.7: External Packages
 
-Tom Lord won't be able to work fixing the bugs until May.  So in the
-mean time, we've decided to withdraw sed 3.0 from distribution and make
-version 2.05 once again the recommended version.
-@end quotation
+@node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
+@unnumberedsubsec Q1.7.1: What is the package system?
 
-It has also been observed that the vfork test on Solaris will leave a
-core dump.
+In order to reduce the size and increase the maintainability of
+XEmacs, the majority of the Elisp packages that came with previous
+releases have been unbundled.  They have been replaced by the package
+system.  Each elisp add-on (or groups of them when they are small) now
+comes in its own tarball that contains a small search hierarchy.
 
-@node Q2.0.11, Q2.0.12, Q2.0.10, Installation
-@unnumberedsubsec Q2.0.11: XEmacs doesn't resolve hostnames.
+You select just the ones you need.  Install them by untarring them into
+the right place.  On startup XEmacs will find them, set up the load
+path correctly, install autoloads, etc, etc.
 
-This is the result of a long-standing problem with SunOS and the fact
-that stock SunOS systems do not ship with DNS resolver code in libc.
+@xref{Q2.1.1}, for more info on how to download and install the packages.
 
-@email{ckd@@loiosh.kei.com, Christopher Davis} writes:
+@node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
+@unnumberedsubsec Q1.7.2: Which external packages are there?
 
-@quotation
-That's correct [The SunOS 4.1.3 precompiled binaries don't do name
-lookup].  Since Sun figured that everyone used NIS to do name lookups
-(that DNS thing was apparently only a passing fad, right?), the stock
-SunOS 4.x systems don't have DNS-based name lookups in libc.
+@subheading Normal Packages
 
-This is also why Netscape ships two binaries for SunOS 4.1.x.
+A very broad collection of elisp packages.
 
-The best solution is to compile it yourself; the configure script will
-check to see if you've put DNS in the shared libc and will then proceed
-to link against the DNS resolver library code.
-@end quotation
+@table @asis
+@item Sun
+Support for Sparcworks.
 
-@node Q2.0.12, Q2.0.13, Q2.0.11, Installation
-@unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
+@item ada
+Ada language support.
 
-@email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
+@item apel
+A Portable Emacs Library.  Used by XEmacs MIME support.
 
-@quotation
-Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
-link gives you a bare-boned emacs (called temacs). temacs is then run,
-preloading some of the lisp files. The result is then dumped into a new
-executable, named xemacs, which will contain all of the preloaded lisp
-functions and data.
+@item auctex
+Basic TeX/LaTeX support.
 
-Now, during the dump itself, the executable (code+data+symbols) is
-written on disk using a special unexec() function. This function is
-obviously heavily system dependent. And on some systems, it leads to an
-executable which, although valid, cannot be stripped without damage. If
-memory serves, this is especially the case for AIX binaries. On other
-architecture it might work OK.
+@item bbdb
+The Big Brother Data Base: a rolodex-like database program.
 
-The Right Way to strip the emacs binary is to strip temacs prior to
-dumping xemacs. This will always work, although you can do that only if
-you install from sources (as temacs is @file{not} part of the binary
-kits).
-@end quotation
+@item build
+Build XEmacs from within (UNIX, Windows).
 
-@email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
+@item c-support
+Basic single-file add-ons for editing C code.
 
-@quotation
-Here is the trick:
+@item calc
+Emacs calculator.
 
-@enumerate
-@item
-[ ./configure; make ]
+@item calendar
+Calendar and diary support.
 
-@item
-rm src/xemacs
+@item cc-mode
+C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
 
-@item
-strip src/temacs
+@item clearcase
+New Clearcase Version Control for XEmacs (UNIX, Windows).
 
-@item
-make
+@item clearcase
+Support for the Clearcase version control system.
 
-@item
-cp src/xemacs /usr/local/bin/xemacs
+@item cookie
+"Fortune cookie"-style messages. Includes Spook (suspicious phrases) 
+and Yow (Zippy quotes).
 
-@item
-cp lib-src/DOC-19.16-XEmacs
-@iftex
-\ @*
-@end iftex
-/usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
-@end enumerate
-@end quotation
+@item crisp
+Crisp/Brief emulation.
 
-@node Q2.0.13, Q2.0.14, Q2.0.12, Installation
-@unnumberedsubsec Q2.0.13: Problems linking with Gcc on Solaris
+@item debug
+GUD, gdb, dbx debugging support.
 
-There are known difficulties linking with Gnu ld on Solaris.  A typical
-error message might look like:
+@item dictionary
+Interface to RFC2229 dictionary servers.
 
-@example
-unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
-fatal: relocation error:
-symbol not found: main: referenced in ../dynodump/dynodump.so
-@end example
+@item dired
+The DIRectory EDitor is for manipulating, and running commands on
+files in a directory.
 
-@email{martin@@xemacs.org, Martin Buchholz} writes:
+@item docbookide
+DocBook editing support.
 
-@quotation
-You need to specify @samp{-fno-gnu-linker} as part of your flags to pass
-to ld.  Future releases of XEmacs will try to do this automatically.
-@end quotation
+@item ecb
+Emacs source code browser.
 
-@node Q2.0.14, Q2.1.1, Q2.0.13, Installation
-@unnumberedsubsec Q2.0.14: Make on HP/UX 9 fails after linking temacs
+@item ecrypto
+Crypto functionality in Emacs Lisp.
 
-Problem when building xemacs-19.16 on hpux 9:
+@item edebug
+An Emacs Lisp debugger.
 
-@email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
+@item ediff
+Interface over GNU patch.
 
-@quotation
-make on hpux fails after linking temacs with a message:
+@item edit-utils
+Miscellaneous editor extensions, you probably need this.
 
-@example
-"make: don't know how to make .y."
-@end example
+@item edt
+DEC EDIT/EDT emulation.
 
-Solution: This is a problem with HP make revision 70.X.  Either use GNU
-make, or install PHCO_6552, which will bring make to revision
-72.24.1.17.
-@end quotation
+@item efs
+Treat files on remote systems the same as local files.
 
+@item eieio
+Enhanced Implementation of Emacs Interpreted Objects.
 
-@node Q2.1.1, Q2.1.2, Q2.0.14, Installation
-@unnumberedsec 2.1: Trouble Shooting
-@unnumberedsubsec Q2.1.1: Help!  XEmacs just crashed on me!
+@item elib
+Portable Emacs Lisp utilities library.
 
-First of all, don't panic.  Whenever XEmacs crashes, it tries extremely
-hard to auto-save all of your files before dying.  (The main time that
-this will not happen is if the machine physically lost power or if you
-killed the XEmacs process using @code{kill -9}).  The next time you try
-to edit those files, you will be informed that a more recent auto-save
-file exists.  You can use @kbd{M-x recover-file} to retrieve the
-auto-saved version of the file.
+@item emerge
+Another interface over GNU patch.
 
-Starting with 19.14, you may use the command @kbd{M-x recover-session}
-after a crash to pick up where you left off.
+@item erc
+ERC is an Emacs InternetRelayChat client.
 
-Now, XEmacs is not perfect, and there may occasionally be times, or
-particular sequences of actions, that cause it to crash.  If you can
-come up with a reproducible way of doing this (or even if you have a
-pretty good memory of exactly what you were doing at the time), the
-maintainers would be very interested in knowing about it.  Post a
-message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
-Please note that the @samp{crashes} address is exclusively for crash
-reports.
-
-If at all possible, include a stack backtrace of the core dump that was
-produced.  This shows where exactly things went wrong, and makes it much
-easier to diagnose problems.  To do this, you need to locate the core
-file (it's called @file{core}, and is usually sitting in the directory
-that you started XEmacs from, or your home directory if that other
-directory was not writable).  Then, go to that directory and execute a
-command like:
+@item escreen
+Multiple editing sessions withing a single frame (like screen).
 
-@example
-gdb `which xemacs` core
-@end example
+@item eshell
+Command shell implemented entirely in Emacs Lisp.
 
-and then issue the command @samp{where} to get the stack backtrace.  You
-might have to use @code{dbx} or some similar debugger in place of
-@code{gdb}.  If you don't have any such debugger available, complain to
-your system administrator.
+@item ess
+ESS: Emacs Speaks Statistics.
 
-It's possible that a core file didn't get produced, in which case you're
-out of luck.  Go complain to your system administrator and tell him not
-to disable core files by default.  Also @xref{Q2.1.15}, for tips and
-techniques for dealing with a debugger.
+@item eterm
+Terminal emulation.
 
-When making a problem report make sure that:
+@item eudc
+Emacs Unified Directory Client (LDAP, PH).
 
-@enumerate
-@item
-Report @strong{all} of the information output by XEmacs during the
-crash.
+@item footnote
+Footnoting in mail message editing modes.
 
-@item
-You mention what O/S & Hardware you are running XEmacs on.
+@item forms
+Forms editing support (obsolete, use Widget instead).
 
-@item
-What version of XEmacs you are running.
+@item fortran-modes
+Fortran support.
 
-@item
-What build options you are using.
+@item fortran-modes
+Fortran language support.
 
-@item
-If the problem is related to graphics, we will also need to know what
-version of the X Window System you are running, and what window manager
-you are using.
+@item frame-icon
+Set up mode-specific icons for each frame under XEmacs.
 
-@item
-If the problem happened on a tty, please include the terminal type.
-@end enumerate
+@item fsf-compat
+GNU Emacs compatibility files.
 
-@node Q2.1.2, Q2.1.3, Q2.1.1, Installation
-@unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
+@item games
+Tetris, Sokoban, and Snake.
 
-When I try to use some particular option of some particular package, I
-get a cryptic error in the minibuffer.
-
-If you can't figure out what's going on, select Options/General
-Options/Debug on Error from the Menubar and then try and make the error
-happen again.  This will give you a backtrace that may be enlightening.
-If not, try reading through this FAQ; if that fails, you could try
-posting to comp.emacs.xemacs (making sure to include the backtrace) and
-someone may be able to help.  If you can identify which Emacs lisp
-source file the error is coming from you can get a more detailed stack
-backtrace by doing the following:
+@item general-docs
+General documentation.  Presently, empty.
 
-@enumerate
-@item
-Visit the .el file in an XEmacs buffer.
+@item gnats
+XEmacs bug reports.
 
-@item
-Issue the command @kbd{M-x eval-current-buffer}.
+@item gnus
+The Gnus Newsreader and Mailreader.
 
-@item
-Reproduce the error.
-@end enumerate
+@item haskell-mode
+Haskell editing support.
 
-Depending on the version of XEmacs, you may either select Edit->Show
-Messages (19.13 and earlier) or Help->Recent Keystrokes/Messages (19.14
-and later) from the menubar to see the most recent messages.  This
-command is bound to @kbd{C-h l} by default.
+@item hm--html-menus
+HTML editing.
 
-@node Q2.1.3, Q2.1.4, Q2.1.2, Installation
-@unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
+@item hyperbole
+Hyperbole: The Everyday Info Manager.
 
-I get tons of translation table syntax error messages during startup.
-How do I get rid of them?
+@item ibuffer
+Advanced replacement for buffer-menu.
 
-There are two causes of this problem.  The first usually only strikes
-people using the prebuilt binaries.  The culprit in both cases is the
-file @file{XKeysymDB}.
+@item idlwave
+Editing and Shell mode for the Interactive Data Language.
 
-@itemize @bullet
-@item
-The binary cannot find the @file{XKeysymDB} file.  The location is
-hardcoded at compile time so if the system the binary was built on puts
-it a different place than your system does, you have problems.  To fix,
-set the environment variable @var{XKEYSYMDB} to the location of the
-@file{XKeysymDB} file on your system or to the location of the one
-included with XEmacs which should be at
-@iftex
-@*
-@end iftex
-@file{<xemacs_root_directory>/lib/xemacs-19.16/etc/XKeysymDB}.
+@item igrep
+Enhanced front-end for Grep.
 
-@item
-The binary is finding the XKeysymDB but it is out-of-date on your system
-and does not contain the necessary lines.  Either ask your system
-administrator to replace it with the one which comes with XEmacs (which
-is the stock R6 version and is backwards compatible) or set your
-@var{XKEYSYMDB} variable to the location of XEmacs's described above.
-@end itemize
+@item ilisp
+Front-end for interacting with Inferior Lisp (external lisps).
 
-@node Q2.1.4, Q2.1.5, Q2.1.3, Installation
-@unnumberedsubsec Q2.1.4: Startup warnings about deducing proper fonts?
+@item ispell
+Spell-checking with GNU ispell.
 
-How can I avoid the startup warnings about deducing proper fonts?
+@item jde
+Integrated Development Environment for Java.
 
-This is highly dependent on your installation, but try with the
-following font as your base font for XEmacs and see what it does:
+@item liece
+IRC (Internet Relay Chat) client for Emacs.  Note, this package is
+deprecated and will be removed, use riece instead.
 
-@format
--adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
-@end format
+@item mail-lib
+Fundamental lisp files for providing email support.
 
-More precisely, do the following in your resource file:
+@item mailcrypt
+Support for messaging encryption with PGP.
 
-@format
-Emacs.default.attributeFont: \
--adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
-@end format
+@item mew
+Messaging in an Emacs World; a MIME-based email program.
 
-If you just don't want to see the @samp{*Warnings*} buffer at startup
-time, you can set this:
+@item mh-e
+The XEmacs Interface to the MH Mail System.
 
-@lisp
-(setq display-warning-minimum-level 'error)
-@end lisp
+@item mine
+Elisp implementation of the game 'Minehunt'.
 
-The buffer still exists; it just isn't in your face.
+@item misc-games
+Other amusements and diversions.
 
-@node Q2.1.5, Q2.1.6, Q2.1.4, Installation
-@unnumberedsubsec Q2.1.5: XEmacs cannot connect to my X Terminal!
+@item mmm-mode
+Support for Multiple Major Modes within a single buffer.
 
-Help!  I can not get XEmacs to display on my Envizex X-terminal!
+@item net-utils
+Miscellaneous Networking Utilities.
 
-Try setting the @var{DISPLAY} variable using the numeric IP address of
-the host you are running XEmacs from.
+@item ocaml
+Objective Caml editing support.
 
-@node Q2.1.6, Q2.1.7, Q2.1.5, Installation
-@unnumberedsubsec Q2.1.6: XEmacs just locked up my Linux X server!
+@item oo-browser
+OO-Browser: The Multi-Language Object-Oriented Code Browser.
 
-There have been several reports of the X server locking up under Linux.
-In all reported cases removing speedo and scaled fonts from the font
-path corrected the problem.  This can be done with the command
-@code{xset}.
+@item ocaml
+Objective Caml editing support.
 
-It is possible that using a font server may also solve the problem.
+@item os-utils
+Miscellaneous single-file O/S utilities, for printing, archiving,
+compression, remote shells, etc.
 
-@node Q2.1.7, Q2.1.8, Q2.1.6, Installation
-@unnumberedsubsec Q2.1.7: HP Alt key as Meta.
+@item pc
+PC style interface emulation.
 
-How can I make XEmacs recognize the Alt key of my HP workstation as a
-Meta key?
+@item pcl-cvs
+CVS frontend.
 
-Put the following line into a file and load it with xmodmap(1) before
-starting XEmacs:
+@item pcomplete
+Provides programmatic completion.
 
-@example
-remove Mod1 = Mode_switch
-@end example
+@item perl-modes
+Perl support.
 
-@node Q2.1.8, Q2.1.9, Q2.1.7, Installation
-@unnumberedsubsec Q2.1.8: got (wrong-type-argument color-instance-p nil)
+@item pgg
+Emacs interface to various PGP implementations.
 
-@email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:
+@item prog-modes
+Support for various programming languages.
 
-@quotation
-I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
-get the following error. Has anyone seen anything like this? This
-doesn't occur on X11R5.
+@item ps-print
+Printing functions and utilities.
 
-@lisp
-Signalling:
-(error "got (wrong-type-argument color-instance-p nil)
-and I don't know why!")
-@end lisp
-@end quotation
+@item psgml
+Validated HTML/SGML editing.
 
-@email{map01kd@@gold.ac.uk, dinos} writes:
+@item psgml-dtds
+A collection of DTDs for psgml.  Note that this package is deprecated
+and will be removed in the future, most likely Q2/2003.  Instead of using
+this, you should install needed DTDs yourself.
 
-@quotation
-I think this is due to undefined resources; You need to define color
-backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
-like:
+@item python-modes
+Python language support.
 
-@example
-*Foreground:	Black	;everything will be of black on grey95,
-*Background:	Grey95	;unless otherwise specified.
-*cursorColor:	Red3	;red3 cursor with grey95 border.
-*pointerColor:	Red3	;red3 pointer with grey95 border.
-@end example
-@end quotation
+@item reftex
+Emacs support for LaTeX cross-references, citations.
 
-Natalie Kershaw adds:
+@item riece
+IRC (Internet Relay Chat) client for Emacs.
 
-@quotation
-What fixed the problem was adding some more colors to the X color
-database (copying the X11R5 colors over), and also defining the
-following resources:
+@item rmail
+An obsolete Emacs mailer.  If you do not already use it don't start.
 
-@example
-xemacs*cursorColor:    black
-xemacs*pointerColor:   black
-@end example
+@item ruby-modes
+Ruby support.
 
-With the new colors installed the problem still occurs if the above
-resources are not defined.
+@item sasl
+Simple Authentication and Security Layer (SASL) library.
 
-If the new colors are not present then an additional error occurs on
-XEmacs startup, which says @samp{Color Red3} not defined.
-@end quotation
+@item scheme
+Front-end support for Inferior Scheme.
 
-@node Q2.1.9, Q2.1.10, Q2.1.8, Installation
-@unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
+@item semantic
+Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
 
-The OpenWindows 3.0 server is incredibly buggy.  Your best bet is to
-replace it with one from the generic MIT X11 release.  You might also
-try disabling parts of your @file{.emacs}, like enabling background
-pixmaps.
+@item sgml
+SGML/Linuxdoc-SGML editing.
 
-@node Q2.1.10, Q2.1.11, Q2.1.9, Installation
-@unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
+@item sh-script
+Support for editing shell scripts.
 
-The following information comes from the @file{PROBLEMS} file that comes
-with XEmacs.
+@item sieve
+Manage Sieve email filtering scripts.
 
-If you're having troubles with HP/UX it is because HP/UX defines the
-modifiers wrong in X.  Here is a shell script to fix the problem; be
-sure that it is run after VUE configures the X server.
+@item slider
+User interface tool.
 
-@example
-#! /bin/sh
-xmodmap 2> /dev/null - << EOF
-keysym Alt_L = Meta_L
-keysym Alt_R = Meta_R
-EOF
+@item sml-mode
+SML editing support.
 
-xmodmap - << EOF
-clear mod1
-keysym Mode_switch = NoSymbol
-add mod1 = Meta_L
-keysym Meta_R = Mode_switch
-add mod2 = Mode_switch
-EOF
-@end example
+@item sounds-au
+XEmacs Sun sound files.
 
-@node Q2.1.11, Q2.1.12, Q2.1.10, Installation
-@unnumberedsubsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
-@c New
+@item sounds-wav
+XEmacs Microsoft sound files.
 
-@email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
+@item speedbar
+Provides a separate frame with convenient references.
 
-I just installed the XEmacs (20.4-2) RPMS that I downloaded from
-@uref{http://www.xemacs.org/}.  Everything works fine, except that when
-I place my mouse over the toolbar, it beeps and gives me this message:
+@item strokes
+Mouse enhancement utility.
 
-@example
- Can't instantiate image (probably cached):
- [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
- (16 16 <strange control characters> ...
-@end example
+@item supercite
+An Emacs citation tool for News & Mail messages.
 
-@email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
-@quotation
-This is problem specific to some Chips and Technologies video
-chips, when running XFree86.  Putting
+@item texinfo
+XEmacs TeXinfo support.
 
-@code{Option "sw_cursor"}
+@item text-modes
+Miscellaneous support for editing text files.
 
-in @file{XF86Config} gets rid of the problem.
-@end quotation
+@item textools
+Miscellaneous TeX support.
 
-@node Q2.1.12, Q2.1.13, Q2.1.11, Installation
-@unnumberedsubsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.
+@item time
+Display time & date on the modeline.
 
-I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
-would not run because it claimed the version number was incorrect
-although it was indeed OK. I traced the problem to the regular
-expression handler.
+@item tm
+Emacs MIME support. Not needed for gnus >= 5.8.0.
 
-@email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
+@item tooltalk
+Support for building with Tooltalk.
 
-@quotation
-Actually it's a DEC cc optimization bug that screws up the regexp
-handling in XEmacs.
+@item tpu
+DEC EDIT/TPU support.
 
-Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
-different sort of optimization) works fine.
-@end quotation
+@item tramp
+Remote shell-based file editing.  This is similar to EFS or Ange-FTP,
+but works with rsh/ssh and rcp/scp.
 
-See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
-build with the @samp{-migrate} flag:
+@item vc
+Version Control for Free systems.
 
-@example
-@uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
-@c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
-@c dead. And the directory `carney' is empty.
+@item vc-cc
+Version Control for ClearCase (UnFree) systems.
 
+@item vhdl
+Support for VHDL.
 
+@item view-process
+A Unix process browsing tool.
 
-@end example
+@item viper
+VI emulation support.
 
-NOTE: There have been a variety of other problems reported that are
-fixed in this fashion.
+@item vm
+An Emacs mailer.
 
-@node Q2.1.13, Q2.1.14, Q2.1.12, Installation
-@unnumberedsubsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
+@item w3
+A Web browser.
 
-@email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
+@item x-symbol
+Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
 
-@quotation
-With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
-@code{create_process} function fails. This breaks a lot of things
-(shell-mode, compile, ange-ftp, to name a few).
-@end quotation
+@item xemacs-base
+Fundamental XEmacs support, you almost certainly need this.
 
-@email{johnson@@dtc.hp.com, Phil Johnson} writes:
+@item xemacs-devel
+XEmacs Lisp developer support.  This package contains utilities for
+supporting Lisp development.  It is a single-file package so it may be 
+tailored.
 
-@quotation
-This is a problem specific to HP-UX 10.10.  It only occurs when XEmacs
-is compiled for shared libraries (the default), so you can work around
-it by compiling a statically-linked binary (run configure with
-@samp{--dynamic=no}).
+@item xlib
+Emacs interface to X server.
 
-I'm not sure whether the problem is with a particular shared library or
-if it's a kernel problem which crept into 10.10.
-@end quotation
+@item xslide
+XSL editing support.
 
-@email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
+@item xslt-process
+A minor mode for (X)Emacs which allows running an XSLT processor on a
+buffer.
 
-@quotation
-I had a few problems with 10.10. Apparently, some of them were solved by
-forcing a static link of libc (manually).
-@end quotation
+@item xwem
+X Emacs Window Manager.
 
-@node Q2.1.14, Q2.1.15, Q2.1.13, Installation
-@unnumberedsubsec Q2.1.14: @kbd{C-g} doesn't work for me.  Is it broken?
+@item zenirc
+ZENIRC IRC Client.
+@end table
 
-@email{ben@@xemacs.org, Ben Wing} writes:
+@subheading Mule Support (mule)
 
-@quotation
-@kbd{C-g} does work for most people in most circumstances.  If it
-doesn't, there are only two explanations:
+MULti-lingual Enhancement.  Support for world scripts such as
+Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
+To use these packages your XEmacs must be compiled with Mule
+support.
 
-@enumerate
-@item
-The code is wrapped with a binding of @code{inhibit-quit} to
-@code{t}.  @kbd{Ctrl-Shift-G} should still work, I think.
+@table @asis
+@item edict
+MULE: Lisp Interface to EDICT, Kanji Dictionary.
 
-@item
-SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
-@end enumerate
+@item egg-its
+MULE: Wnn (4.2 and 6) support.  SJ3 support.
 
-To test #2, try executing @code{(while t)} from the @samp{*scratch*}
-buffer.  If @kbd{C-g} doesn't interrupt, then you're seeing #2.
-@end quotation
+@item latin-unity
+MULE: find single ISO 8859 character set to encode a buffer.
 
-@email{terra@@diku.dk, Morten Welinder} writes:
+@item latin-unity
+Unify character sets in a buffer. When characters belong to disjoint
+character sets, this attempts to translate the characters so
+that they belong to one character set. If the buffer coding system is
+not sufficient, this suggests different coding systems.
 
-@quotation
-On some (but @emph{not} all) machines a hung XEmacs can be revived by
-@code{kill -FPE <pid>}.  This is a hack, of course, not a solution.
-This technique works on a Sun4 running 4.1.3_U1.  To see if it works for
-you, start another XEmacs and test with that first.  If you get a core
-dump the method doesn't work and if you get @samp{Arithmetic error} then
-it does.
-@end quotation
+@item leim
+MULE: Quail.  All non-English and non-Japanese language support.
 
-@node Q2.1.15, Q2.1.16, Q2.1.14, Installation
-@unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
+@item locale
+MULE: Localized menubars and localized splash screens.
 
-If XEmacs does crash on you, one of the most productive things you can
-do to help get the bug fixed is to poke around a bit with the debugger.
-Here are some hints:
+@item lookup
+Dictionary support. (This isn't an English dictionary program)
 
-@itemize @bullet
-@item
-First of all, if the crash is at all reproducible, consider very
-strongly recompiling your XEmacs with debugging symbols, with no
-optimization, and with the configure options @samp{--debug=yes} and
-@samp{--error-checking=all}.  This will make your XEmacs run somewhat
-slower but make it a lot more likely to catch the problem earlier
-(closer to its source), and a lot easier to determine what's going on
-with a debugger.
+@item mule-base
+MULE: Basic Mule support, required for building with Mule.
 
-@item
-If you're able to run XEmacs under a debugger and reproduce the crash
-(if it's inconvenient to do this because XEmacs is already running or is
-running in batch mode as part of a bunch of scripts, consider attaching
-to the existing process with your debugger; most debuggers let you do
-this by substituting the process ID for the core file when you invoke
-the debugger from the command line, or by using the @code{attach}
-command or something similar), here are some things you can do:
+@item mule-ucs
+MULE: Extended coding systems (including Unicode) for XEmacs.
 
-@item
-If XEmacs is hitting an assertion failure, put a breakpoint on
-@code{assert_failed()}.
+@item mule-ucs
+Extended coding systems (including Unicode) for XEmacs.
 
-@item
-If XEmacs is hitting some weird Lisp error that's causing it to crash
-(e.g. during startup), put a breakpoint on @code{signal_1()}---this is
-declared static in eval.c.
+@item skk
+Another Japanese Language Input Method.  Can be used without a
+separate process running as a dictionary server.
+@end table
 
-@item
-Internally, you will probably see lots of variables that hold objects of
-type @code{Lisp_Object}.  These are exactly what they appear to be,
-i.e. references to Lisp objects.  Printing them out with the debugger
-probably won't be too useful---you'll likely just see a number.  To
-decode them, do this:
+@node Q1.7.3, Q1.7.4, Q1.7.2, Introduction
+@unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs?
 
-@example
-call debug_print (OBJECT)
-@end example
+Strictly speaking, no.  XEmacs will build and install just fine without
+any packages installed.  However, only the most basic editing functions
+will be available with no packages installed, so installing packages is
+an essential part of making your installed XEmacs _useful_.
 
-where @var{OBJECT} is whatever you want to decode (it can be a variable,
-a function call, etc.).  This will print out a readable representation
-on the TTY from which the xemacs process was invoked.
+@node Q1.7.4, Q1.8.1, Q1.7.3, Introduction
+@unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality?
 
-@item
-If you want to get a Lisp backtrace showing the Lisp call
-stack, do this:
+If you want to find out which package contains the functionality you
+are looking for, use @kbd{M-x package-get-package-provider}, and give it a
+symbol that is likely to be in that package.  
+
+For example, if some code you want to use has a @code{(require 'thingatpt)}
+in it:
 
 @example
-call debug_backtrace ()
+	M-x package-get-package-provider RET thingatpt RET
 @end example
 
-@item
-Using @code{debug_print} and @code{debug_backtrace} has two
-disadvantages - it can only be used with a running xemacs process, and
-it cannot display the internal C structure of a Lisp Object.  Even if
-all you've got is a core dump, all is not lost.
-
-If you're using GDB, there are some macros in the file
-@file{src/gdbinit} in the XEmacs source distribution that should make it
-easier for you to decode Lisp objects.  Copy this file to
-@file{~/.gdbinit}, or @code{source} it from @file{~/.gdbinit}, and use
-the macros defined therein.  In particular, use the @code{pobj} macro to
-print the internal C representation of a lisp object.  This will work
-with a core file or not-yet-run executable.  The aliases @code{ldp} and
-@code{lbt} are provided for conveniently calling @code{debug_print} and
-@code{debug_backtrace}.
-
-If you are using Sun's @file{dbx} debugger, there is an equivalent file
-@file{src/dbxrc} to copy to or source from @file{~/.dbxrc}.
+which will return something like: @samp{(fsf-compat "1.08").}
 
-@item
-If you're using a debugger to get a C stack backtrace and you're seeing
-stack traces with some of the innermost frames mangled, it may be due to
-dynamic linking. (This happens especially under Linux.) Consider
-reconfiguring with @samp{--dynamic=no}.  Also, sometimes (again under
-Linux), stack backtraces of core dumps will have the frame where the
-fatal signal occurred mangled; if you can obtain a stack trace while
-running the XEmacs process under a debugger, the stack trace should be
-clean.
+@unnumberedsec 1.8: Internationalization
 
-@email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
-if dynamic linking and debugging is a problem on Linux.
+@node Q1.8.1, Q1.8.2, Q1.7.4, Introduction
+@unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
 
-@item
-If you're using a debugger to get a C stack backtrace and you're
-getting a completely mangled and bogus stack trace, it's probably due to
-one of the following:
+Both the stable and development versions of XEmacs include
+internationalization support (aka MULE).  MULE currently (21.4) works on
+UNIX and Linux systems.  It is possible to build with MULE on Windows
+systems, but if you really need MULE on Windows, it is recommended that
+you build and use the development (21.5) version, and deal with the
+instability of the development tree.  Binaries compiled without MULE
+support run faster than MULE capable XEmacsen.
 
-@enumerate a
-@item
-Your executable has been stripped.  Bad news.  Tell your sysadmin not to
-do this---it doesn't accomplish anything except to save a bit of disk
-space, and makes debugging much much harder.
+@node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
+@unnumberedsubsec Q1.8.2: How can I help with internationalization?
 
-@item
-Your stack is getting trashed.  Debugging this is hard; you have to do a
-binary-search type of narrowing down where the crash occurs, until you
-figure out exactly which line is causing the problem.  Of course, this
-only works if the bug is highly reproducible.
+If you would like to help, you may want to join the
+@email{xemacs-mule@@xemacs.org} mailing list.  Especially needed are
+people who speak/write languages other than English, who are willing to
+use XEmacs/MULE regularly, and have some experience with Elisp.
 
-@item
-If your stack trace has exactly one frame in it, with address 0x0, this
-could simply mean that XEmacs attempted to execute code at that address,
-e.g. through jumping to a null function pointer.  Unfortunately, under
-those circumstances, GDB under Linux doesn't know how to get a stack
-trace. (Yes, this is the third Linux-related problem I've mentioned.  I
-have no idea why GDB under Linux is so bogus.  Complain to the GDB
-authors, or to comp.os.linux.development.system).  Again, you'll have to
-use the narrowing-down process described above.
+Translations of the TUTORIAL and man page are welcome, and XEmacs does
+support multilingual menus, but we have few current translations.
 
-@item
-If you compiled 19.14 with @samp{--debug} (or by default in later
-versions), you will get a Lisp backtrace output when XEmacs crashes, so
-you'll have something useful.
+@xref{Q1.5.2, How do I become a Beta Tester?}.
 
-@end enumerate
+@node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
+@unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
 
-@item
-If you compile with the newer gcc variants gcc-2.8 or egcs, you will
-also need gdb 4.17.  Earlier releases of gdb can't handle the debug
-information generated by the newer compilers.
+@xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
+part 3 of this FAQ, for some simple methods that also work in non-MULE
+builds of XEmacs (but only for one-octet coded character sets, and
+mostly for ISO 8859/1).  Many of the methods available for Cyrillic
+(@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE.  MULE
+has more general capabilities.  @xref{Q1.8.5, Please explain the
+various input methods in MULE/XEmacs}.
 
-@item
-The above information on using @file{src/gdbinit} works for XEmacs-21.0
-and above.  For older versions of XEmacs, there are different
-@file{gdbinit} files provided in the @file{src} directory.  Use the one
-corresponding to the configure options used when building XEmacs.
+@xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
+display of non-ASCII characters.
 
-@end itemize
+@node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
+@unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
 
-@node Q2.1.16, Q2.1.17, Q2.1.15, Installation
-@unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
+The message-catalog support was written but is badly bit-rotted.  XEmacs
+20 and 21 did @emph{not} support it, and early releases of XEmacs 22
+will not either.
 
-From the problems database (through
-the former address http://support.mayfield.hp.com/):
+However, menubar localization @emph{does} work.  To enable it, add to
+your @file{Emacs} file entries like this:
 
 @example
-Problem Report: 5003302299
-Status:         Open
+Emacs*XlwMenu.resourceLabels:                   True
+Emacs*XlwMenu.file.labelString:                 Fichier
+Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster oeffnen
+@end example
 
-System/Model:   9000/700
-Product Name:   HPUX S800 10.0X
-Product Vers:   9245XB.10.00
+The name of the resource is derived from the non-localized entry by
+removing punctuation and capitalizing as above.
 
-Description: strcat(3C) may read beyond
-end of source string, can cause SIGSEGV
+@node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
+@unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
+
+Mule supports a wide variety of input methods.  There are three basic
+classes: Lisp implementations, generic platform support, and library
+interfaces.
+
+@emph{Lisp implementations} include Quail, which provides table-driven input
+methods for almost all the character sets that Mule supports (including
+all of the ISO 8859 family, the Indic languages, Thai, and so on), and
+SKK, for Japanese.  (SKK also supports an interface to an external
+"dictionary server" process.)  Quail supports both typical "dead-key"
+methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
+SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
+methods used for Asian ideographic languages like Chinese.
+
+Lisp implementations can be less powerful (but they are not perceptibly
+inefficient), and of course are not portable to non-Emacs applications.
+The incompatibility can be very annoying.  On the other hand, they
+require no special platform support or external libraries, so if you can
+display the characters, Mule can input them for you and you can edit,
+anywhere.
+
+@emph{Generic platform support} is currently limited to the X Input
+Method (XIM) framework, although support for MSIME (for MS Windows) is
+planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
+support is extremely desirable.  XIM is enabled at build time by use of
+the @samp{--with-xim} flag to @code{configure}.  For use of XIM, see
+your platform documentation.  However, normally the input method you use
+is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
+variables.
 
+Of course, input skills are portable across most applications.  However,
+especially in modern GUI systems the habit of using bucky bits has
+fallen into sad disuse, and many XIM systems are poorly configured for
+use with Emacs.  For example, the kinput2 input manager (a separate
+process providing an interface between Japanese dictionary servers such
+as Canna and Wnn, and the application) tends to gobble up keystrokes
+generating Meta characters.  This means that to edit while using an XIM
+input method, you must toggle the input method off every time you want
+to use @kbd{M-f}.  Your mileage may vary.
+
+@emph{Library interfaces} are most common for Japanese, although Wnn
+supports Chinese (traditional and simplified) and Korean.  There are
+Chinese and Korean input servers available, but we do not know of any
+patches for XEmacs to use them directly.  You can use them via
+IM-enabled terminals, by manipulating the terminal coding systems.  We
+describe only the Japanese-oriented systems here.  The advantage of
+these systems is that they are very powerful, and on platforms where
+they are available there is typically a wide range of applications that
+support them.  Thus your input skills are portable across applications.
+
+Mule provides built-in interfaces to the following input methods: Wnn4,
+Wnn6, Canna, and SJ3.  These can be configured at build time.  There are
+patches available (no URL, sorry) to support the SKK server, as well.
+Wnn and SJ3 use the @code{egg} user interface.  The interface for Canna
+is specialized to Canna.
 
-*** PROBLEM TEXT ***
-strcat(3C) may read beyond the source string onto an unmapped page,
-causing a segmentation violation.
-@end example
+Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
+University. It is a powerful and complex system.  Wnn4 is free and Wnn6
+is not.  Wnn uses grammatical hints and probability of word association,
+so in principle Wnn can be cleverer than other methods.
+
+Canna, made by NEC, supports only Japanese.  It is a simple and powerful
+system. Canna uses only grammar, but its grammar and dictionary are
+quite sophisticated.  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).
 
-@node Q2.1.17, Q2.1.18, Q2.1.16, Installation
-@unnumberedsubsec Q2.1.17: @samp{Marker does not point anywhere}
+SJ3, by Sony, supports only Japanese.
 
-As with other errors, set @code{debug-on-error} to @code{t} to get the
-backtrace when the error occurs.  Specifically, two problems have been
-reported (and fixed).
+Egg consists of following parts:
 
 @enumerate
 @item
-A problem with line-number-mode in XEmacs 19.14 affected a large number
-of other packages.  If you see this error message, turn off
-line-number-mode.
+Input character Translation System (ITS) layer.
+It translates ASCII inputs to Kana/PinYin/Hangul characters.
 
 @item
-A problem with some early versions of Gnus 5.4 caused this error.
-Upgrade your Gnus.
+Kana/PinYin/Hangul to Kanji transfer layer.
+The interface layer to network Kana-Kanji server (Wnn and Sj3).
 @end enumerate
 
-@node Q2.1.18, Q2.1.19, Q2.1.17, Installation
-@unnumberedsubsec Q2.1.18: 19.14 hangs on HP/UX 10.10.
+These input methods are modal.  They have a raw (alphabet) mode, a
+phonetic input mode, and Kana-Kanji transfer mode.  However there are
+mode-less input methods for Egg and Canna.  @samp{boiled-egg} is a
+mode-less input method running on Egg.  For Canna, @samp{canna.el} has a
+tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
+boiled-egg-like utilities.
 
-@email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
+Much of this information was provided by @email{morioka@@jaist.ac.jp,
+MORIOKA Tomohiko}.
 
-@quotation
-For the record, compiling on hpux 10.10 leads to a hang in Gnus when
-compiled with optimization on.
-
-I've just discovered that my hpux 10.01 binary was working less well
-than expected. In fact, on a 10.10 system, @code{(while t)} was not
-interrupted by @kbd{C-g}. I defined @code{BROKEN_SIGIO} and recompiled on
-10.10, and... the hang is now gone.
-
-As far as configure goes, this will be a bit tricky: @code{BROKEN_SIGIO}
-is needed on 10.10, but @strong{not} on 10.01: if I run my 10.01 binary
-on a 10.01 machine, without @code{BROKEN_SIGIO} being defined, @kbd{C-g}
-works as expected.
-@end quotation
+@node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
+@unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
 
-@email{cognot@@ensg.u-nancy.fr, Richard Cognot} adds:
+MULE has evolved rapidly over the last few years, and the original third
+party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
+different implementations.  The APIs also vary although recent versions
+of XEmacs have tended to converge to the GNU Emacs standard.
+
+MULE implementations are going to continue to evolve.  Both GNU Emacs
+and XEmacs are working hard on Unicode support, which will involve new
+APIs and probably variations on old ones.  For XEmacs 22, the old ISO
+2022-based system for recognizing encodings will be replaced by a much
+more flexible system, which should improve accuracy of automatic coding
+detections, but will also involve new APIs.
+
+@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
 
 @quotation
-Apparently somebody has found the reason why there is this
-@iftex
-@*
-@end iftex
-@samp{poll:
-interrupted...} message for each event.  For some reason, libcurses
-reimplements a @code{select()} system call, in a highly broken fashion.
-The fix is to add a -lc to the link line @emph{before} the
--lxcurses. XEmacs will then use the right version of @code{select()}.
-@end quotation
+The application implementor must write separate code for these mule
+variants.  [Please don't hesitate to report these variants to us; they
+are not, strictly speaking, bugs, but they give third-party developers
+the same kind of creepy-crawly feeling.  We'll do what we can. -- Ed.]
 
+MULE and the next version of Emacs are similar but the symbols are very
+different---requiring separate code as well.
 
-@email{af@@biomath.jussieu.fr, Alain Fauconnet} writes:
+Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
+emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
+@code{emu} to provide a common interface.  [There is an XEmacs package
+of APEL which provides much more comprehensive coverage.  Be careful,
+however; APEL has problems of its own. -- Ed.]
 
-@quotation
-The @emph{real} solution is to @emph{not} link -lcurses in!  I just
-changed -lcurses to -ltermcap in the Makefile and it fixed:
+I have the following suggestions about dealing with mule variants:
 
-@enumerate
+@itemize @bullet
 @item
-The @samp{poll: interrupted system call} message.
+@code{(featurep 'mule)} @code{t} on all mule variants
 
 @item
-A more serious problem I had discovered in the meantime, that is the
-fact that subprocess handling was seriously broken: subprocesses
-e.g. started by AUC TeX for TeX compilation of a buffer would
-@emph{hang}.  Actually they would wait forever for emacs to read the
-socket which connects stdout...
-@end enumerate
-@end quotation
+@code{(boundp 'MULE)} is @code{t} on only MULE.  Maybe the next version
+of Emacs will not have this symbol.
 
-@node Q2.1.19, Q2.1.20, Q2.1.18, Installation
-@unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
+@item
+MULE has a variable @code{mule-version}.  Perhaps the next version of
+Emacs will have this variable as well.
+@end itemize
 
-When using one of the prebuilt binaries many users have observed that
-XEmacs uses the timezone under which it was built, but not the timezone
-under which it is running.  The solution is to add:
+Following is a sample to distinguish mule variants:
 
 @lisp
-(set-time-zone-rule "MET")
+(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
+  )
 @end lisp
+@end quotation
 
-to your @file{.emacs} or the @file{site-start.el} file if you can.
-Replace @code{MET} with your local timezone.
-
-@node Q2.1.20, Q2.1.21, Q2.1.19, Installation
-@unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
+@node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
+@unnumberedsubsec Q1.8.7: How about Cyrillic modes?
 
-This is a problem with a partially loaded hyperbole.  Try adding:
+@email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
 
-@lisp
-(require 'hmouse-drv)
-@end lisp
+@quotation
+There is a cyrillic mode in the file @file{mysetup.zip} in
+@iftex
+@*
+@end iftex
+@uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}.  This is a
+modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
+which can be obtained from
+@end quotation
 
-where you load hyperbole and the problem should go away.
+@uref{http://www.math.uga.edu/~valery/russian.el}.
 
-@node Q2.1.21, Q2.1.22, Q2.1.20, Installation
-@unnumberedsubsec Q2.1.21: Every so often the XEmacs frame freezes
+@email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
 
-This problem has been fixed in 19.15, and was due to a not easily
-reproducible race condition.
+@quotation
+There is another cyrillic mode for both GNU Emacs and XEmacs by
+@email{manin@@camelot.mssm.edu, Dmitrii
+(Mitya) Manin} at
+@iftex
 
-@node Q2.1.22, Q2.1.23, Q2.1.21, Installation
-@unnumberedsubsec Q2.1.22: XEmacs seems to take a really long time to do some things
+@end iftex
+@uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
+@c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
+@c Changed to russian host instead
+@end quotation
 
-@email{dmoore@@ucsd.edu, David Moore} writes:
+@email{rebecca.ore@@op.net, Rebecca Ore} writes:
 
 @quotation
-Two things you can do:
+The fullest resource I found on Russian language use (in and out of
+XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
+@end quotation
 
-1) C level:
+@node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
+@unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
 
-When you see it going mad like this, you might want to use gdb from an
-'xterm' to attach to the running process and get a stack trace.  To do
-this just run:
+To get Unicode support, you need a Mule-enabled XEmacs.
+
+21.5 has internal support for Unicode and supports it fully, although we
+don't yet use it as the internal encoding.
+
+21.4 supports Unicode partially -- as an external encoding for files,
+processes, and terminals, but without font support.  @xref{Q1.8.9, How
+does XEmacs display Unicode?}.  To get Unicode support in 21.4,
+install Mule-UCS from packages in the usual way, and put
 
 @example
-gdb /path/to/xemacs/xemacs ####
+(require 'un-define)
+(set-coding-priority-list '(utf-8))
+(set-coding-category-system 'utf-8 'utf-8)
 @end example
 
-Where @code{####} is the process id of your xemacs, instead of
-specifying the core.  When gdb attaches, the xemacs will stop [1] and
-you can type `where' in gdb to get a stack trace as usual.  To get
-things moving again, you can just type `quit' in gdb.  It'll tell you
-the program is running and ask if you want to quit anyways.  Say 'y' and
-it'll quit and have your emacs continue from where it was at.
-
-2) Lisp level:
+in your init file to enable the UTF-8 coding system.  You may wish to
+view the documentation of @code{set-coding-priority-list} if you find
+that files that are not UTF-8 are being mis-recognized as UTF-8.
 
-Turn on debug-on-quit early on.  When you think things are going slow
-hit C-g and it may pop you in the debugger so you can see what routine
-is running.  Press `c' to get going again.
+Install standard national fonts (not Unicode fonts) for all character
+sets you use.  @xref{Q1.8.9, How does XEmacs display Unicode??}.
 
-debug-on-quit doesn't work if something's turned on inhibit-quit or in
-some other strange cases.
-@end quotation
+Mule-UCS also supports 16-bit forms of Unicode (UTF-16).  It does not
+support 31-bit forms of Unicode (UTF-32 or UCS-4).
 
-@node Q2.1.23,  , Q2.1.22, Installation
-@unnumberedsubsec Q2.1.23:  Movemail on Linux does not work for XEmacs 19.15 and later.
+@node Q1.8.9,  , Q1.8.8, Introduction
+@unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
 
-Movemail used to work fine in 19.14 but has stopped working in 19.15
-and 20.x.  I am using Linux.
+Mule doesn't have a Unicode charset internally, so there's nothing to
+bind a Unicode registry to.  It would not be straightforward to create,
+either, because Unicode is not ISO 2022-compatible.  You'd have to
+translate it to multiple 96x96 pages.
 
-@email{steve@@xemacs.org, SL Baur} writes:
+This means that Mule-UCS uses ordinary national fonts for display.  This
+is not really a problem, except for those languages that use the Unified
+Han characters.  The problem here is that Mule-UCS maps from Unicode
+code points to national character sets in a deterministic way.  By
+default, this means that Japanese fonts are tried first, then Chinese,
+then Korean.  To change the priority ordering, use the command
+`un-define-change-charset-order'.
 
-@quotation
-Movemail on Linux used to default to using flock file locking.  With
-19.15 and later versions it now defaults to using @code{.lock} file
-locking.  If this is not appropriate for your system, edit src/s/linux.h
-and uncomment the line that reads:
+It also means you can't use Unicode fonts directly, at least not without
+extreme hackery.  You can run -nw with (set-terminal-coding-system
+'utf-8) if you really want a Unicode font for some reason.
 
-@example
-#define MAIL_USE_FLOCK
-@end example
-@end quotation
+Real Unicode support will be introduced in XEmacs 22.0.
 
-@node Customization, Subsystems, Installation, Top
-@unnumbered 3 Customization and Options
+@node Installation, Editing, Introduction, Top
+@unnumbered 2 Installation and Troubleshooting
 
-This is part 3 of the XEmacs Frequently Asked Questions list.  This
-section is devoted to Customization and screen settings.
+This is part 2 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to Installation, Maintenance and Troubleshooting.
 
 @menu
-Customization---Emacs Lisp and @file{.emacs}:
-* Q3.0.1::      What version of Emacs am I running?
-* Q3.0.2::      How do I evaluate Elisp expressions?
-* Q3.0.3::      @code{(setq tab-width 6)} behaves oddly.
-* Q3.0.4::      How can I add directories to the @code{load-path}?
-* Q3.0.5::      How to check if a lisp function is defined?
-* Q3.0.6::      Can I force the output of @code{(face-list)} to a buffer?
-* Q3.0.7::      Font selections don't get saved after @code{Save Options}.
-* Q3.0.8::      How do I make a single minibuffer frame?
-* Q3.0.9::      What is @code{Customize}?
-
-X Window System & Resources:
-* Q3.1.1::      Where is a list of X resources?
-* Q3.1.2::      How can I detect a color display?
-* Q3.1.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
-* Q3.1.4::      Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
-* Q3.1.5::      How can I get the icon to just say @samp{XEmacs}?
-* Q3.1.6::      How can I have the window title area display the full path?
-* Q3.1.7::      @samp{xemacs -name junk} doesn't work?
-* Q3.1.8::      @samp{-iconic} doesn't work.
-
-Textual Fonts & Colors:
-* Q3.2.1::      How can I set color options from @file{.emacs}?
-* Q3.2.2::      How do I set the text, menu and modeline fonts?
-* Q3.2.3::      How can I set the colors when highlighting a region?
-* Q3.2.4::      How can I limit color map usage?
-* Q3.2.5::      My tty supports color, but XEmacs doesn't use them.
-* Q3.2.6::      Can I have pixmap backgrounds in XEmacs?
-
-The Modeline:
-* Q3.3.1::      How can I make the modeline go away?
-* Q3.3.2::      How do you have XEmacs display the line number in the modeline?
-* Q3.3.3::      How do I get XEmacs to put the time of day on the modeline?
-* Q3.3.4::      How do I turn off current chapter from AUC TeX modeline?
-* Q3.3.5::      How can one change the modeline color based on the mode used?
-
-3.4 Multiple Device Support:
-* Q3.4.1::      How do I open a frame on another screen of my multi-headed display?
-* Q3.4.2::      Can I really connect to a running XEmacs after calling up over a modem?  How?
-
-3.5 The Keyboard:
-* Q3.5.1::      How can I bind complex functions (or macros) to keys?
-* Q3.5.2::      How can I stop down-arrow from adding empty lines to the bottom of my buffers?
-* Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
-* Q3.5.4::      Globally binding @kbd{Delete}?
-* Q3.5.5::      Scrolling one line at a time.
-* Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
-* Q3.5.7::      How can you type in special characters in XEmacs?
-* Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
-* Q3.5.9::      How do I make the Delete key delete forward?
-* Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
-* Q3.5.11::     How do I map the arrow keys?
-
-The Cursor:
-* Q3.6.1::      Is there a way to make the bar cursor thicker?
-* Q3.6.2::      Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
-* Q3.6.3::      Can I make the cursor blink?
-
-The Mouse and Highlighting:
-* Q3.7.1::      How can I turn off Mouse pasting?
-* Q3.7.2::      How do I set control/meta/etc modifiers on mouse buttons?
-* Q3.7.3::      Clicking the left button does not do anything in buffer list.
-* Q3.7.4::      How can I get a list of buffers when I hit mouse button 3?
-* Q3.7.5::      Why does cut-and-paste not work between XEmacs and a cmdtool?
-* Q3.7.6::      How I can set XEmacs up so that it pastes where the text cursor is?
-* Q3.7.7::      How do I select a rectangular region?
-* Q3.7.8::      Why does @kbd{M-w} take so long?
-
-The Menubar and Toolbar:
-* Q3.8.1::      How do I get rid of the menu (or menubar)?
-* Q3.8.2::      Can I customize the basic menubar?
-* Q3.8.3::      How do I control how many buffers are listed in the menu @code{Buffers} list?
-* Q3.8.4::      Resources like @code{Emacs*menubar*font} are not working?
-* Q3.8.5::      How can I bind a key to a function to toggle the toolbar?
-
-Scrollbars:
-* Q3.9.1::      How can I disable the scrollbar?
-* Q3.9.2::      How can one use resources to change scrollbar colors?
-* Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
-* Q3.9.4::      How can I get automatic horizontal scrolling?
-
-Text Selections:
-* Q3.10.1::     How can I turn off or change highlighted selections?
-* Q3.10.2::     How do I get that typing on an active region removes it?
-* Q3.10.3::     Can I turn off the highlight during isearch?
-* Q3.10.4::     How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
-* Q3.10.5::     The region disappears when I hit the end of buffer while scrolling.
+2.0: Installation (General)
+* Q2.0.1::    How do I build and install XEmacs?
+* Q2.0.2::    Where do I find external libraries?
+* Q2.0.3::    How do I specify the paths that XEmacs uses for finding files?
+* Q2.0.4::    Running XEmacs without installing
+* Q2.0.5::    XEmacs is too big
+
+2.1: Package Installation
+* Q2.1.1::    How do I install the packages?
+* Q2.1.2::    Can I install the packages individually?
+* Q2.1.3::    Can I install the packages automatically?
+* Q2.1.4::    Can I upgrade or remove packages?
+* Q2.1.5::    Which packages to install?
+* Q2.1.6::    Can you describe the package location process in more detail?
+* Q2.1.7::    EFS fails with "500 AUTH not understood"
+
+2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
+* Q2.2.1::    Libraries in non-standard locations
+* Q2.2.2::    Why can't I strip XEmacs?
+* Q2.2.3::    X11/bitmaps/gray (or other X11-related file) not found.
+
+2.3: Windows Installation (Windows, Cygwin, MinGW)
+* Q2.3.1::    What exactly are all the different ways to build XEmacs under Windows?
+* Q2.3.2::    What compiler/libraries do I need to compile XEmacs?
+* Q2.3.3::    How do I compile the native port?
+* Q2.3.4::    What do I need for Cygwin?
+* Q2.3.5::    How do I compile under Cygwin?
+* Q2.3.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+* Q2.3.7::    How do I compile with X support?
+* Q2.3.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
+
+2.4: General Troubleshooting
+* Q2.4.1::    How do I deal with bugs or with problems building, installing, or running?
+* Q2.4.2::    Help!  XEmacs just crashed on me!
+* Q2.4.3::    XEmacs crashes and I compiled it myself.
+* Q2.4.4::    How to debug an XEmacs problem with a debugger
+* Q2.4.5::    I get a cryptic error message when trying to do something.
+* Q2.4.6::    XEmacs hangs when I try to do something.
+* Q2.4.7::    I get an error message when XEmacs is running in batch mode.
+* Q2.4.8::    The keyboard or mouse is not working properly, or I have some other event-related problem.
+* Q2.4.9::    @kbd{C-g} doesn't work for me.  Is it broken?
+* Q2.4.10::   How do I debug process-related problems?
+* Q2.4.11::   XEmacs is outputting lots of X errors.
+* Q2.4.12::   After upgrading, XEmacs won't do `foo' any more!
+
+2.5: Startup-Related Problems
+* Q2.5.1::    XEmacs cannot connect to my X Terminal!
+* Q2.5.2::    Startup problems related to paths or package locations.
+* Q2.5.3::    XEmacs won't start without network.
+* Q2.5.4::    Startup warnings about deducing proper fonts?
+* Q2.5.5::    Warnings from incorrect key modifiers.
+* Q2.5.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
 @end menu
 
-@node Q3.0.1, Q3.0.2, Customization, Customization
-@unnumberedsec 3.0: Customization -- Emacs Lisp and .emacs
-@unnumberedsubsec Q3.0.1: What version of Emacs am I running?
+@unnumberedsec 2.0: Installation (General)
 
-How can @file{.emacs} determine which of the family of Emacsen I am
-using?
+@node Q2.0.1, Q2.0.2, Installation, Installation
+@unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
 
-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 @file{etc/sample.emacs}.  There are other nifty things
-in there as well!
+See the file @file{etc/NEWS} for information on new features and other
+user-visible changes since the last version of XEmacs.
 
-For all new code, all you really need to do is:
+The file @file{INSTALL} in the top-level directory says how to bring
+up XEmacs on Unix and Cygwin, once you have loaded the entire subtree
+of this directory.
 
-@lisp
-(defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
-@end lisp
+See the file @file{nt/README} for instructions on building XEmacs for
+Microsoft Windows.
 
-@node Q3.0.2, Q3.0.3, Q3.0.1, Customization
-@unnumberedsubsec Q3.0.2: How can I evaluate Emacs-Lisp expressions?
+@xref{Q2.1.1}, for the installation of (essential) add on packages.
 
-I know I can evaluate Elisp expressions from @code{*scratch*} buffer
-with @kbd{C-j} after the expression.  How do I do it from another
-buffer?
+@node Q2.0.2, Q2.0.3, Q2.0.1, Installation
+@unnumberedsubsec Q2.0.2: Where do I find external libraries?
 
-Press @kbd{M-:} (the default binding of @code{eval-expression}), and
-enter the expression to the minibuffer.  In XEmacs prior to 19.15
-@code{eval-expression} used to be a disabled command by default.  If
-this is the case, upgrade your XEmacs.
+All external libraries used by XEmacs can be found on the XEmacs web
+site
+@iftex
+@*
+@end iftex
+@uref{http://www.xemacs.org/Download/optLibs.html}.
 
-@node Q3.0.3, Q3.0.4, Q3.0.2, Customization
-@unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
+The library versions available here are known to work with XEmacs.
+(Newer versions will probably work as well but we can't guarantee it.)
+We try to keep the libraries up-to-date but may not always succeed.
+Check the above page for the canonical locations of the external libraries,
+allowing you to download the latest, bleeding-edge versions.
 
-If you put @code{(setq tab-width 6)} in your @file{.emacs} file it does
-not work!  Is there a reason for this?  If you do it at the EVAL prompt
-it works fine!! How strange.
+@node Q2.0.3, Q2.0.4, Q2.0.2, Installation
+@unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files?
 
-Use @code{setq-default} instead, since @code{tab-width} is
-all-buffer-local.
+You can specify what paths to use by using a number of different flags
+when running configure.  See the section MAKE VARIABLES in the top-level
+file INSTALL in the XEmacs distribution for a listing of those flags.
 
-@node Q3.0.4, Q3.0.5, Q3.0.3, Customization
-@unnumberedsubsec Q3.0.4: How can I add directories to the @code{load-path}?
+Most of the time, however, the simplest fix is: @strong{do not} specify
+paths as you might for GNU Emacs.  XEmacs can generally determine the
+necessary paths dynamically at run time.  The only path that generally
+needs to be specified is the root directory to install into.  That can
+be specified by passing the @code{--prefix} flag to configure.  For a
+description of the XEmacs install tree, please consult the @file{NEWS}
+file.
 
-Here are two ways to do that, one that puts your directories at the
-front of the load-path, the other at the end:
+@node Q2.0.4, Q2.0.5, Q2.0.3, Installation
+@unnumberedsubsec Q2.0.4: Running XEmacs without installing
 
-@lisp
-;;; Add things at the beginning of the load-path, do not add
-;;; duplicate directories:
-(pushnew "bar" load-path :test 'equal)
+How can I just try XEmacs without installing it?
 
-(pushnew "foo" load-path :test 'equal)
+XEmacs will run in place without requiring installation and copying of
+the Lisp directories, and without having to specify a special build-time
+flag.  It's the copying of the Lisp directories that requires so much
+space.  XEmacs is largely written in Lisp.
 
-;;; Add things at the end, unconditionally
-(setq load-path (nconc load-path '("foo" "bar")))
-@end lisp
+A good method is to make a shell alias for xemacs:
 
-@email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
+@example
+alias xemacs=/src/xemacs-21.5/src/xemacs
+@end example
 
-@quotation
-To add directories using Unix shell metacharacters use
-@file{expand-file-name} like this:
+(You will obviously use whatever directory you downloaded the source
+tree to instead of @file{/src/xemacs-21.5}).
 
-@lisp
-(push (expand-file-name "~keithh/.emacsdir") load-path)
-@end lisp
-@end quotation
+This will let you run XEmacs without massive copying.
 
-@node Q3.0.5, Q3.0.6, Q3.0.4, Customization
-@unnumberedsubsec Q3.0.5: How to check if a lisp function is defined?
+@node Q2.0.5, Q2.1.1, Q2.0.4, Installation
+@unnumberedsubsec Q2.0.5: XEmacs is too big
 
-Use the following elisp:
+The space required by the installation directories can be
+reduced dramatically if desired.  Gzip all the .el files.  Remove all
+the packages you'll never want to use.  Remove the TexInfo manuals.
+Remove the Info (and use just hardcopy versions of the manual).  Remove
+most of the stuff in etc.  Remove or gzip all the source code.  Gzip or
+remove the C source code.  Configure it so that copies are not made of
+the support lisp.
 
-@lisp
-(fboundp 'foo)
-@end lisp
+These are all Emacs Lisp source code and bytecompiled object code.  You
+may safely gzip everything named *.el here.  You may remove any package
+you don't use.  @emph{Nothing bad will happen if you delete a package
+that you do not use}.  You must be sure you do not use it though, so be
+conservative at first.
 
-It's almost always a mistake to test @code{emacs-version} or any similar
-variables.
+Any package with the possible exceptions of xemacs-base, and EFS are
+candidates for removal.  Ask yourself, @emph{Do I ever want to use this
+package?}  If the answer is no, then it is a candidate for removal.
 
-Instead, use feature-tests, such as @code{featurep}, @code{boundp},
-@code{fboundp}, or even simple behavioral tests, eg.:
+First, gzip all the .el files.  Then go about package by package and
+start gzipping the .elc files.  Then run XEmacs and do whatever it is
+you normally do.  If nothing bad happens, then remove the package.  You
+can remove a package via the PUI interface 
+(@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
+you wish to delete, and then @kbd{x} to delete them.
 
-@lisp
-(defvar foo-old-losing-code-p
-  (condition-case nil (progn (losing-code t) nil)
-    (wrong-number-of-arguments t)))
-@end lisp
+Another method is to do @code{M-x package-get-delete-package}.
 
-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.
+@unnumberedsec 2.1: Package Installation
 
-@node Q3.0.6, Q3.0.7, Q3.0.5, Customization
-@unnumberedsubsec Q3.0.6: Can I force the output of @code{(face-list)} to a buffer?
+@node Q2.1.1, Q2.1.2, Q2.0.5, Installation
+@unnumberedsubsec Q2.1.1: How do I install the packages?
 
-It would be good having it in a buffer, as the output of
-@code{(face-list)} is too wide to fit to a minibuffer.
+There are three ways to install the packages.
 
-Evaluate the expression in the @samp{*scratch*} buffer with point after
-the rightmost paren and typing @kbd{C-j}.
+@enumerate
+@item
+Manually, all at once, using the 'Sumo Tarball'.
+@item
+Manually, using individual package tarballs.
+@item
+Automatically, using the package tools from XEmacs.
+@end enumerate
 
-If the minibuffer smallness is the only problem you encounter, you can
-simply press @kbd{C-h l} to get the former minibuffer contents in a
-buffer.
+If you don't want to mess with the packages, it is easiest to just
+grab them manually, all at once. (For the other two ways,
+@xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file
 
-@node Q3.0.7, Q3.0.8, Q3.0.6, Customization
-@unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
+@file{xemacs-sumo.tar.gz}
 
-For XEmacs 19.14 and previous:
+For an XEmacs compiled with Mule you also need
 
-@email{mannj@@ll.mit.edu, John Mann} writes:
+@file{xemacs-mule-sumo.tar.gz}
 
-@quotation
-You have to go to Options->Frame Appearance and unselect
-@samp{Frame-Local Font Menu}.  If this option is selected, font changes
-are only applied to the @emph{current} frame and do @emph{not} get saved
-when you save options.
-@end quotation
+These are in the @file{packages} directory on your XEmacs mirror
+archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
+mirrors.  N.B. They are called 'Sumo Tarballs' for good reason. They
+are currently about 19MB and 4.5MB (gzipped) respectively.
 
-For XEmacs 19.15 and later:
+Install them on Unix and Mac OS X using the shell/Terminal command
 
-Implement the above as well as set the following in your @file{.emacs}
+@code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
 
-@lisp
-(setq options-save-faces t)
-@end lisp
+Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
+@file{configure}, and defaults to @file{/usr/local}.
 
-@node Q3.0.8, Q3.0.9, Q3.0.7, Customization
-@unnumberedsubsec Q3.0.8: How do I get a single minibuffer frame?
+If you have GNU tar you can use:
 
-@email{acs@@acm.org, Vin Shelton} writes:
+@code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
 
-@lisp
-(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)
-@end lisp
+If you have the packages somewhere nonstandard and don't want to bother
+with @samp{$prefix} (for example, you're a developer and are compiling
+the packages yourself, and want your own private copy of everything),
+you can also directly specify this using @file{configure}.  To do this
+with 21.5 and above use the @samp{--with-package-prefix} parameter to
+specify the directory under which you untarred the above tarballs.
+Under 21.4 and previous you need to use @samp{--package-path}.  Using
+these options looks something like this:
 
-@strong{Please note:} 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.
+@example
+   configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
+@end example
 
-@node Q3.0.9, Q3.1.1, Q3.0.8, Customization
-@unnumberedsubsec Q3.0.9: What is @code{Customize}?
+Under Windows, you need to place the above @samp{tar.gz} files in the
+directory specified using the @samp{PACKAGE_PREFIX} value in
+@file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
+(To untar a @samp{tar.gz} file you will need to use a utility such as
+WinZip, unless you have Cygwin or a similar environment installed, in
+which case the above Unix shell command should work fine.) If you want
+the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
+
+Note that XEmacs finds the packages automatically anywhere underneath
+the directory tree where it expects to find the packages.  All you
+need to do is put stuff there; you don't need to run any program to
+tell XEmacs to find the packges, or do anything of that sort.
+
+However, XEmacs will only notice newly installed packages when it
+starts up, so you will have to restart if you are already running
+XEmacs.
 
-Starting with XEmacs 20.2 there is new system 'Customize' for customizing
-XEmacs options.
+For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
+Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
 
-You can access @code{Customize} from the @code{Options} menu
-or invoking one of customize commands by typing eg.
-@kbd{M-x customize}, @kbd{M-x customize-face},
-@kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
+As the Sumo tarballs are not regenerated as often as the individual
+packages, it is recommended that you use the automatic package tools
+afterwards to pick up any recent updates.
 
-Starting with XEmacs 20.3 there is also new `browser' mode for Customize.
-Try it out with @kbd{M-x customize-browse}
+@emph{NOTE}: For detailed information about how the package
+hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
+Reference Manual}.
 
-@node Q3.1.1, Q3.1.2, Q3.0.9, Customization
-@unnumberedsec 3.1: X Window System & Resources
-@unnumberedsubsec Q3.1.1: Where is a list of X resources?
+@node Q2.1.2, Q2.1.3, Q2.1.1, Installation
+@unnumberedsubsec Q2.1.2: Can I install the packages individually?
 
-Search through the @file{NEWS} file for @samp{X Resources}.  A fairly
-comprehensive list is given after it.
+Yes, you can download individual packages from the FTP site (@pxref{Q2.1.1}).  Since packages are automatically noticed at startup, you just have to put them in the right place.
 
-In addition, an @file{app-defaults} file is supplied,
-@file{etc/Emacs.ad} listing the defaults.  The file
-@file{etc/sample.Xdefaults} gives a set of defaults that you might
-consider.  It is essentially the same as @file{etc/Emacs.ad} but some
-entries are slightly altered.  Be careful about installing the contents
-of this file into your @file{.Xdefaults} or @file{.Xresources} file if
-you use GNU Emacs under X11 as well.
+Note: If you are upgrading packages already installed, it's best to
+remove the old package first (@pxref{Q2.1.4}).
 
-@node Q3.1.2, Q3.1.3, Q3.1.1, Customization
-@unnumberedsubsec Q3.1.2: How can I detect a color display?
+For example if we are installing the @samp{xemacs-base}
+package (version 1.48):
 
-You can test the return value of the function @code{(device-class)}, as
-in:
+@example
+   mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
+   cd $prefix/lib/xemacs/xemacs-packages RET
+   gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
+@end example
 
-@lisp
-(when (eq (device-class) 'color)
-  (set-face-foreground  'font-lock-comment-face "Grey")
-  (set-face-foreground  'font-lock-string-face  "Red")
-  ....
-  )
-@end lisp
+Or if you have GNU tar, the last step can be:
 
-@node Q3.1.3, Q3.1.4, Q3.1.2, Customization
-@unnumberedsubsec Q3.1.3: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
+@example
+   tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
+@end example
 
-In Lucid Emacs 19.6 I did @code{(set-screen-width @var{characters})} and
-@code{(set-screen-height @var{lines})} in my @file{.emacs} instead of
-specifying @code{Emacs*EmacsScreen.geometry} in my
-@iftex
-@*
-@end iftex
-@file{.Xdefaults} but
-this does not work in XEmacs 19.13.
+For MULE related packages, it is best to untar into the @samp{mule-packages}
+hierarchy, i.e. for the @samp{mule-base} package, version 1.37:
 
-These two functions now take frame arguments:
+@example
+   mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
+   cd $prefix/lib/xemacs/mule-packages RET
+   gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
+@end example
 
-@lisp
-(set-frame-width (selected-frame) @var{characters})
-(set-frame-height (selected-frame) @var{lines})
-@end lisp
+Or if you have GNU tar, the last step can be:
 
-@node Q3.1.4, Q3.1.5, Q3.1.3, Customization
-@unnumberedsubsec Q3.1.4: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
+@example
+   tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
+@end example
 
-In XEmacs 19.11 I specified @code{Emacs*EmacsScreen.geometry} in
-my @file{.emacs} but this does not work in XEmacs 19.15.
+@node Q2.1.3, Q2.1.4, Q2.1.2, Installation
+@unnumberedsubsec Q2.1.3: Can I install the packages automatically?
 
-We have switched from using the term @dfn{screen} to using the term
-@dfn{frame}.
+XEmacs comes with some tools to make the periodic updating and
+installing easier. It will notice if new packages or versions are
+available and will fetch them from the FTP site.
 
-The correct entry for your @file{.Xdefaults} is now:
+Unfortunately this requires that a few packages are already in place.
+You will have to install them by hand as above or use a SUMO tarball.
+This requirement will hopefully go away in the future. The packages
+you need are:
 
 @example
-Emacs*EmacsFrame.geometry
+   efs          - To fetch the files from the FTP site or mirrors.
+   xemacs-base  - Needed by efs.
 @end example
 
-@node Q3.1.5, Q3.1.6, Q3.1.4, Customization
-@unnumberedsubsec Q3.1.5: How can I get the icon to just say @samp{XEmacs}?
+and optionally:
 
-I'd like the icon to just say @samp{XEmacs}, and not include the name of
-the current file in it.
+@example
+   mailcrypt    - For PGP verification of the package-index file.
+@end example
 
-Add the following line to your @file{.emacs}:
+After installing these by hand, fire up XEmacs and follow these
+steps.
 
-@lisp
-(setq frame-icon-title-format "XEmacs")
-@end lisp
+@enumerate
+@item
+Choose a download site.
+@itemize @bullet
+@item
+via menu: Tools -> Packages -> Set Download Site 
+@item
+via keyb: M-x customize-variable RET package-get-remote RET
+(put in the details of remote host and directory)
+@end itemize
 
-@node Q3.1.6, Q3.1.7, Q3.1.5, Customization
-@unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
+If the package tarballs _AND_ the package-index file are in a
+local directory, you can: M-x pui-set-local-package-get-directory RET
 
-I'd like to have the window title area display the full directory/name
-of the current buffer file and not just the name.
+@item
+Obtain a list of packages and display the list in a buffer named
+"*Packages*".
+@itemize @bullet
+@item
+menu: Tools -> Packages -> List & Install
+@item
+keyb: M-x pui-list-packages RET
+@end itemize
 
-Add the following line to your @file{.emacs}:
+XEmacs will now connect to the remote site and download the
+latest package-index file.
 
-@lisp
-(setq frame-title-format "%S: %f")
-@end lisp
+The resulting buffer, "*Packages*" has brief instructions at the
+end of the buffer.
 
-A more sophisticated title might be:
+@item
+Choose the packages you wish to install.
+@itemize @bullet
+@item
+mouse: Click button 2 on the package name.
+@item
+keyb: RET on the package name
+@end itemize
 
-@lisp
-(setq frame-title-format
-      '("%S: " (buffer-file-name "%f"
-				 (dired-directory dired-directory "%b"))))
-@end lisp
+@item
+Make sure you have everything you need.
+@itemize @bullet
+@item
+menu: Packages -> Add Required
+@item
+keyb: r
+@end itemize
 
-That is, use the file name, or the dired-directory, or the buffer name.
+XEmacs will now search for packages that are required by the
+ones that you have chosen to install and offer to select
+those packages also.
 
-@node Q3.1.7, Q3.1.8, Q3.1.6, Customization
-@unnumberedsubsec Q3.1.7: @samp{xemacs -name junk} doesn't work?
+For novices and gurus alike, this step can save your bacon.
+It's easy to forget to install a critical package.
 
-When I run @samp{xterm -name junk}, I get an xterm whose class name
-according to xprop, is @samp{junk}.  This is the way it's supposed to
-work, I think.  When I run @samp{xemacs -name junk} the class name is
-not set to @samp{junk}.  It's still @samp{emacs}.  What does
-@samp{xemacs -name} 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?
+@item
+Download and install the packages.
+@itemize @bullet
+@item
+menu: Packages -> Install/Remove Selected
+@item
+keyb: x
+@end itemize
+@end enumerate
 
-@samp{xemacs -name} sets the application name for the program (that is,
-the thing which normally comes from @samp{argv[0]}).  Using @samp{-name}
-is the same as making a copy of the executable with that new name.  The
-@code{WM_CLASS} property on each frame is set to the frame-name, and the
-application-class.  So, if you did @samp{xemacs -name FOO} and then
-created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
-@code{( "BAR", "Emacs")}.  However, the resource hierarchy for this
-widget would be:
+@node Q2.1.4, Q2.1.5, Q2.1.3, Installation
+@unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
 
-@example
-Name:    FOO   .shell             .container   .BAR
-Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
-@end example
+As the exact files and their locations contained in a package may
+change it is recommended to remove a package first before installing a
+new version. In order to facilitate removal each package contains an
+pgkinfo/MANIFEST.pkgname file which list all the files belong to the
+package. M-x package-admin-delete-binary-package RET can be used to
+remove a package using this file.
 
-instead of the default
+Note that the interactive package tools included with XEmacs already do
+this for you.
 
-@example
-Name:    xemacs.shell             .container   .emacs
-Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
-@end example
+@node Q2.1.5, Q2.1.6, Q2.1.4, Installation
+@unnumberedsubsec Q2.1.5: Which packages to install?
 
+Unless you are an advanced user, just install everything.
 
-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}.  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} to @samp{xemacs}, or whatever
-the executable happened to be named), so we'd rather avoid it.
+If you really want to install only what's absolutely needed, a good
+minimal set of packages for XEmacs-latin1 would be
 
-To make a frame with a particular name use:
+@example
+xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
+edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
+text-modes, time, mailcrypt
+@end example
 
-@lisp
-(make-frame '((name . "the-name")))
-@end lisp
+If you are using the XEmacs package tools, don't forget to do:
 
-@node Q3.1.8, Q3.2.1, Q3.1.7, Customization
-@unnumberedsubsec Q3.1.8: @samp{-iconic} doesn't work.
+@example
+	Packages -> Add Required
+@end example
 
-When I start up XEmacs using @samp{-iconic} it doesn't work right.
-Using @samp{-unmapped} on the command line, and setting the
-@code{initiallyUnmapped} X Resource don't seem to help much either...
+To make sure you have everything that the packages you have chosen to
+install need.
 
-@email{ben@@xemacs.org, Ben Wing} writes:
+@xref{Q1.7.2}, for a description of the various packages.
 
-@quotation
-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...
-@end quotation
+@node Q2.1.6, Q2.1.7, Q2.1.5, Installation
+@unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail?
 
-@node Q3.2.1, Q3.2.2, Q3.1.8, Customization
-@unnumberedsec 3.2: Textual Fonts & Colors
-@unnumberedsubsec Q3.2.1: How can I set color options from @file{.emacs}?
+On startup XEmacs looks for packages in so-called package hierarchies.
+Normally, there are three system wide hierarchies, like this:
 
-How can I set the most commonly used color options from my @file{.emacs}
-instead of from my @file{.Xdefaults}?
+@example
+$prefix/lib/xemacs/xemacs-packages/
+     Normal packages go here.
 
-Like this:
+$prefix/lib/xemacs/mule-packages/
+     Mule packages go here and are only searched by MULE-enabled XEmacsen.
 
-@lisp
-(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
-@end lisp
+$prefix/lib/xemacs/site-packages/
+     Local and 3rd party packages go here.
+@end example
 
-@node Q3.2.2, Q3.2.3, Q3.2.1, Customization
-@unnumberedsubsec Q3.2.2: How do I set the text, menu and modeline fonts?
+This is what you get when you untar the SUMO tarballs under
+@file{$prefix/lib/xemacs}.
 
-Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
-setting face values.
+@file{$prefix} is specified using the @samp{--prefix} parameter to
+@file{configure}, and defaults to @file{usr/local}.
 
-In @file{.Xdefaults}:
+If the package path is not explicitly specified, XEmacs looks for the
+package directory @file{xemacs-packages} (and @file{mule-packages} and
+@file{site-packages}) first under @samp{~/.xemacs}, then for a sister
+directory @file{lib/xemacs-VERSION} of the directory in which the
+XEmacs executable is located, then for a sister directory
+@file{lib/xemacs}.  The XEmacs executable (under Unix at least) is
+installed by default in @file{/usr/local/bin}; this explains why
+XEmacs in its default installation will find packages that you put
+under @file{/usr/local/lib/xemacs}.
 
-@example
-Emacs.default.attributeFont:  -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
-Emacs*menubar*font:           fixed
-Emacs.modeline.attributeFont: fixed
-@end example
+You can specify where exactly XEmacs looks for packages by using the
+@samp{--with-package-prefix} or @samp{--with-package-path} parameters to
+@file{configure} (or the equivalent settings in @file{config.inc}, under
+Windows), or setting the @samp{EMACSPACKAGEPATH} environment variable
+(which has the same format as @samp{--with-package-path}).  @xref{Q2.1.1}.
 
-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) ?}.  It uses the face specification of @code{attributeFont},
-while menubar is a normal X thing that uses the specification
-@code{font}.  With Motif it may be necessary to use @code{fontList}
-instead of @code{font}.
+See @file{configure.usage} for more info about the format of these
+@file{configure} parameters.
 
-@node Q3.2.3, Q3.2.4, Q3.2.2, Customization
-@unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
+In addition to the system wide packages, each user can have his own
+packages installed under @file{~/.xemacs/}. If you want to install
+packages there using the interactive tools, you need to set
+@code{package-get-install-to-user-init-directory} to @code{t}.
 
-How can I set the background/foreground colors when highlighting a
-region?
+The site-packages hierarchy replaces the old @file{site-lisp}
+directory.  XEmacs no longer looks into a @file{site-lisp} directly by
+default.  A good place to put @file{site-start.el} would be in
+@file{$prefix/lib/xemacs/site-packages/lisp/}.
 
-You can change the face @code{zmacs-region} either in your
-@file{.Xdefaults}:
+@node Q2.1.7, Q2.2.1, Q2.1.6, Installation
+@unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
 
-@example
-Emacs.zmacs-region.attributeForeground: firebrick
-Emacs.zmacs-region.attributeBackground: lightseagreen
-@end example
+A typical error: FTP Error: USER request failed; 500 AUTH not understood.
 
-or in your @file{.emacs}:
+Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
+on comp.emacs.xemacs:
 
-@lisp
-(set-face-background 'zmacs-region "red")
-(set-face-foreground 'zmacs-region "yellow")
-@end lisp
+   tell your ftp client to not attempt AUTH authentication (or do not
+   use FTP servers that don't understand AUTH)
 
-@node Q3.2.4, Q3.2.5, Q3.2.3, Customization
-@unnumberedsubsec Q3.2.4: How can I limit color map usage?
+and notes that you need to add an element (often "-u") to
+`efs-ftp-program-args'.  Use M-x customize-variable, and verify the
+needed flag with `man ftp' or other local documentation.
 
-I'm using Netscape (or another color grabber like XEmacs);
-is there anyway to limit the number of available colors in the color map?
+@unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
 
-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 <#>
-or -install (for mono, limiting to <#> 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 @samp{-install}.
+@node Q2.2.1, Q2.2.2, Q2.1.7, Installation
+@unnumberedsubsec Q2.2.1: Libraries in non-standard locations
 
-If you have the money, another solution would be to use a truecolor or
-direct color video.
+If your libraries are in a non-standard location, you can specify the location
+using the following flags to @file{configure}.  Under 21.4 or earlier:
 
-Starting with XEmacs 19.14, XEmacs uses the closest available color if
-the colormap is full, so it's O.K. now to start Netscape first.
+@example
+--site-libraries=WHATEVER
+--site-includes=WHATEVER
+@end example
 
-@node Q3.2.5, Q3.2.6, Q3.2.4, Customization
-@unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
+Under 21.5 or later:
 
-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:
+@example
+--with-site-libraries=WHATEVER
+--with-site-includes=WHATEVER
+@end example
 
-@lisp
-(if (eq 'tty (device-type))
-    (set-device-class nil 'color))
-@end lisp
+If you have multiple paths to specify, use the following syntax:
 
-@node Q3.2.6, Q3.3.1, Q3.2.5, Customization
-@unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
-@c New
-@email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
+@example
+--site-libraries='/path/one /path/two /path/etc'
+@end example
 
-@quotation
-There are several ways to do it.  For example, you could specify a
-default pixmap image to use in your @file{~/.Xresources}, e.g.,
+If the libraries and headers reside in the directories @samp{lib} and
+@samp{include} of a common root (say @samp{/sw}) then both can be
+specified with a single option:
+
+@example
+--site-prefixes=WHATEVER
+@end example
 
+or for 21.5:
 
 @example
-  Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
+--with-site-prefixes=WHATEVER
 @end example
 
+@node Q2.2.2, Q2.2.3, Q2.2.1, Installation
+@unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
 
-and then reload ~/.Xresources and restart XEmacs.  Alternatively,
-since each face can have its own pixmap background, a better way
-would be to set a face's pixmap within your XEmacs init file, e.g.,
+@email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
 
-@lisp
-  (set-face-background-pixmap 'default "/path/to/image.xpm")
-  (set-face-background-pixmap 'bold    "/path/to/another_image.xpm")
-@end lisp
+@quotation
+Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
+link gives you a bare-boned emacs (called temacs). temacs is then run,
+preloading some of the lisp files. The result is then dumped into a new
+executable, named xemacs, which will contain all of the preloaded lisp
+functions and data.
 
-and so on.  You can also do this interactively via @kbd{M-x edit-faces}.
+Now, during the dump itself, the executable (code+data+symbols) is
+written on disk using a special unexec() function. This function is
+obviously heavily system dependent. And on some systems, it leads to an
+executable which, although valid, cannot be stripped without damage. If
+memory serves, this is especially the case for AIX binaries. On other
+architectures it might work OK.
 
+The Right Way to strip the emacs binary is to strip temacs prior to
+dumping xemacs. This will always work, although you can do that only if
+you install from sources (as temacs is @file{not} part of the binary
+kits).
 @end quotation
 
-@unnumberedsec 3.3: The Modeline
-@node Q3.3.1, Q3.3.2, Q3.2.6, Customization
-@unnumberedsubsec Q3.3.1: How can I make the modeline go away?
-
-@lisp
-(set-specifier has-modeline-p nil)
-@end lisp
+@email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
 
-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.
+@quotation
+Here is the trick:
 
-@node Q3.3.2, Q3.3.3, Q3.3.1, Customization
-@unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
+@enumerate
+@item
+[ ./configure; make ]
 
-Add the following line to your @file{.emacs} file to display the
-line number:
+@item
+rm src/xemacs
 
-@lisp
-(line-number-mode 1)
-@end lisp
+@item
+strip src/temacs
 
-Use the following to display the column number:
+@item
+make
 
-@lisp
-(column-number-mode 1)
-@end lisp
+@item
+cp src/xemacs /usr/local/bin/xemacs
 
-Or select from the @code{Options} menu
-@iftex
-@*
-@end iftex
-@code{Customize->Emacs->Editing->Basics->Line Number Mode}
-and/or
+@item
+cp lib-src/DOC-19.16-XEmacs
 @iftex
-@*
+\ @*
 @end iftex
-@code{Customize->Emacs->Editing->Basics->Column Number Mode}
+/usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
+@end enumerate
+@end quotation
 
-Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
+@node Q2.2.3, Q2.3.1, Q2.2.2, Installation
+@unnumberedsubsec Q2.2.3: X11/bitmaps/gray (or other X11-related file) not found.
+
+The X11R6 distribution was monolithic, but the X11R7 distribution is
+much more modular.  Many OS distributions omit these bitmaps (assuming
+nobody uses them, evidently).  Your OS distribution should have a
+developer's package containing these files, probably with a name
+containing the string "bitmap".  Known package names (you may need to
+add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu)
+and xorg-x11-xbitmaps (Fedora Core 5).
+
+@unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
+
+@node Q2.3.1, Q2.3.2, Q2.2.3, Installation
+@unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows?
+
+XEmacs can be built in several ways in the MS Windows environment.
+
+The standard way is what we call the "native" port.  It uses the Win32
+API and has no connection with X whatsoever -- it does not require X
+libraries to build, nor does it require an X server to run.  The native
+port is the most reliable version and provides the best graphical
+support.  Almost all development is geared towards this version, and
+there is little reason not to use it.
+
+The second way to build is the Cygwin port.  It takes advantage of
+Cygnus emulation library under Win32.  @xref{Q1.2.5, What are Cygwin
+and MinGW, and do I need them to run XEmacs?}, for more information.
+
+A third way is the MinGW port.  It uses the Cygwin environment to
+build but does not require it at runtime.  @xref{Q1.2.5, What are
+Cygwin and MinGW, and do I need them to run XEmacs?}, for more
+information.
+
+Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
+port.  This was actually the first version of XEmacs that ran under MS
+Windows, and although the code is still in XEmacs, it's essentially
+orphaned and it's unlikely it will compile without a lot of work.  If
+you want an MS Windows versin of XEmacs that supports X, use the Cygwin
+version. (The X support there is actively maintained, so that Windows
+developers can test the X support in XEmacs.)
+
+@node Q2.3.2, Q2.3.3, Q2.3.1, Installation
+@unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs?
+
+You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
+some beta testers currently trying to compile with VC.NET, aka version
+7.0, but we can't yet report complete success.) For the Cygwin and
+MinGW versions, you need the Cygwin environment, which comes with GCC,
+the compiler used for those versions.  @xref{Q1.2.5, What are Cygwin
+and MinGW, and do I need them to run XEmacs?}, for more information on
+Cygwin and MinGW.
+
+@node Q2.3.3, Q2.3.4, Q2.3.2, Installation
+@unnumberedsubsec Q2.3.3: How do I compile the native port?
 
-@node Q3.3.3, Q3.3.4, Q3.3.2, Customization
-@unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
+Please read the file @file{nt/README} in the XEmacs distribution, which
+contains the full description.
 
-Add the following line to your @file{.emacs} file to display the
-time:
+@node Q2.3.4, Q2.3.5, Q2.3.3, Installation
+@unnumberedsubsec Q2.3.4: What do I need for Cygwin?
 
-@lisp
-(display-time)
-@end lisp
+You can find the Cygwin tools and compiler at:
 
-See @code{Customize} from the @code{Options} menu for customization.
+@uref{http://www.cygwin.com/}
 
-@node Q3.3.4, Q3.3.5, Q3.3.3, Customization
-@unnumberedsubsec Q3.3.4: How do I turn off current chapter from AUC TeX modeline?
+Click on the @samp{Install or update now!} link, which will download a
+file @file{setup.exe}, which you can use to download everything
+else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
+probably the best.) You should go ahead and install everything --
+you'll get various ancillary libraries that XEmacs needs or likes,
+e.g. XPM, PNG, JPEG, TIFF, etc.  You can also get X Windows here, if you
+want to compile under X.
 
-With AUC TeX, fast typing is hard because the current chapter, section
-etc. are given in the modeline.  How can I turn this off?
+If you want to compile without X, you will need the @file{xpm-nox}
+library, which must be specifically selected in the Cygwin netinstaller;
+it is not selected by default.  The package has had various names.
+Currently it is called @file{cygXpm-noX4.dll}.
 
-It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
-Add this code to your @file{.emacs} to turn it off:
+@node Q2.3.5, Q2.3.6, Q2.3.4, Installation
+@unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
 
-@lisp
-(setq fume-display-in-modeline-p nil)
-@end lisp
+Similar as on Unix; use the usual `configure' and `make' process.
+Some problems to watch out for:
 
-Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
-mode:
+@itemize @bullet
+@item
+make sure HOME is set. This controls where you
+@file{init.el} file comes from;
 
-@lisp
-(add-hook 'TeX-mode-hook
-	  '(lambda () (setq fume-display-in-modeline-p nil)))
-@end lisp
+@item
+@samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
 
-@email{dhughes@@origin-at.co.uk, David Hughes} writes:
+@item
+picking up some other grep or other UNIX-like tools can kill configure;
 
-@quotation
-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 @samp{Rescan Buffer} option in the
-function-menu.
+@item
+static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
+number;
 
-@lisp
-(setq-default fume-auto-rescan-buffer-p nil)
-@end lisp
-@end quotation
+@item
+(Unconfirmed) The Cygwin version doesn't understand
+@file{//machine/path} type paths so you will need to manually mount a
+directory of this form under a unix style directory for a build to work
+on the directory;
 
-@node Q3.3.5, Q3.4.1, Q3.3.4, Customization
-@unnumberedsubsec Q3.3.5: How can one change the modeline color based on the mode used?
+@item
+If you're building @strong{WITHOUT} X11, don't forget to change symlinks
+@file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
+the non-X versions of these libraries.  By default they point to the X
+versions.  So:
 
-You can use something like the following:
+@example
+/usr/lib/libXpm.a     -> /usr/lib/libXpm-noX.a
+/usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
+@end example
 
-@lisp
-(add-hook 'lisp-mode-hook
-          (lambda ()
-            (set-face-background 'modeline "red" (current-buffer))))
-@end lisp
+(This advice may now be obsolete because of the availability of the
+cygXpm-noX4.dll package from Cygwin.  Send confirmation to
+@email{faq@@xemacs.org}.)
 
-Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
-colors change from the default set in your @file{.emacs}.  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.
+@item
+Other problems are listed in the @file{PROBLEMS} file, in the top-level
+directory of the XEmacs sources.
 
-Notes:
+@end itemize
+
+
+@node Q2.3.6, Q2.3.7, Q2.3.5, Installation
+@unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+
+Similar to the method for Unix.  Things to remember:
 
 @itemize @bullet
+@item
+Specify the target host on the command line for @file{./configure}, e.g.
+@samp{./configure i586-pc-mingw32}.
 
 @item
-The hook is the mode name plus @code{-hook}.  eg. c-mode-hook,
-c++-mode-hook, emacs-lisp-mode-hook (used for your @file{.emacs} or a
-@file{xx.el} file), lisp-interaction-mode-hook (the @samp{*scratch*}
-buffer), text-mode-hook, etc.
+Be sure that your build directory is mounted such that it has the
+same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
+path (@file{c:\build\xemacs}).
 
 @item
-Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
-otherwise you will erase anything that anybody has already put on the
-hook.
+Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
+@file{compface}, etc.
 
 @item
-You can also do @code{(set-face-font 'modeline @var{font})},
-eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
-(current-buffer))} if you wish the modeline font to vary based on the
-current mode.
+Specify the target location of the extra libs on the command line
+to @file{configure}, e.g.for 21.4 or earlier
+@samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for
+21.5 or later 
+@samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}.
 @end itemize
 
-This works in 19.15 as well, but there are additional modeline faces,
-@code{modeline-buffer-id}, @code{modeline-mousable}, and
-@code{modeline-mousable-minor-mode}, which you may want to customize.
+@node Q2.3.7, Q2.3.8, Q2.3.6, Installation
+@unnumberedsubsec Q2.3.7: How do I compile with X support?
 
-@node Q3.4.1, Q3.4.2, Q3.3.5, Customization
-@unnumberedsec 3.4: Multiple Device Support
-@unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
+To compile under Cygwin, all you need to do is install XFree86, which
+is available as part of the standard Cygwin installation.
+@uref{http://www.cygwin.com/}.  Once installed, @file{configure}
+should automatically find the X libraries and compile with X support.
 
-The support for this was revamped for 19.14.  Use the command
-@kbd{M-x make-frame-on-display}.  This command is also on the File menu
-in the menubar.
+As noted above, the non-Cygwin X support is basically orphaned, and
+probably won't work.  But if it want to try, it's described in
+@file{nt/README} in some detail.  Basically, you need to get X11
+libraries from @uref{http://ftp.x.org}, and compile them.  If the
+precompiled versions are available somewhere, we don't know of it.
 
-XEmacs 19.14 and later also have the command @code{make-frame-on-tty}
-which will establish a connection to any tty-like device.  Opening the
-TTY devices should be left to @code{gnuclient}, though.
+@node Q2.3.8, Q2.4.1, Q2.3.7, Installation
+@unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
 
-@node Q3.4.2, Q3.5.1, Q3.4.1, Customization
-@unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem?  How?
+The Cygwin binary distributed with the netinstaller uses an external DLL
+to handle XPM images (such as toolbar buttons).  You may get an error like
 
-If you're not running at least XEmacs 19.14, you can't.  Otherwise check
-out the @code{gnuattach} program supplied with XEmacs.  Starting with
-XEmacs 20.3, @code{gnuattach} and @code{gnudoit} functionality is
-provided by @code{gnuclient}.
+@example
+This application has failed to start because cygXpm-noX4.dll was not found.
+Re-installing the application may fix this problem.
+@end example
 
-Also @xref{Q5.0.12}.
+Andy Piper <andy@@xemacs.org> sez:
 
-@node Q3.5.1, Q3.5.2, Q3.4.2, Customization
-@unnumberedsec 3.5: The Keyboard
-@unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
+@example
+cygXpm-noX4 is part of the cygwin distribution under libraries or
+graphics, but is not installed by default. You need to run the
+cygwin setup again and select this package.
+@end example
 
-As an example, say you want the @kbd{paste} key on a Sun keyboard to
-insert the current Primary X selection at point. You can accomplish this
-with:
+Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
+distribution.
 
-@lisp
-(define-key global-map [f18] 'x-insert-selection)
-@end lisp
+@unnumberedsec 2.4: General Troubleshooting
 
-However, this only works if there is a current X selection (the
-selection will be highlighted).  The functionality I like is for the
-@kbd{paste} key to insert the current X selection if there is one,
-otherwise insert the contents of the clipboard.  To do this you need to
-pass arguments to @code{x-insert-selection}.  This is done by wrapping
-the call in a 'lambda form:
+@node Q2.4.1, Q2.4.2, Q2.3.8, Installation
+@unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
 
-@lisp
-(global-set-key [f18]
-  (lambda () (interactive) (x-insert-selection t nil)))
-@end lisp
+The file @file{PROBLEMS} contains information on many common problems that
+occur in building, installing and running XEmacs.
 
-This binds the f18 key to a @dfn{generic} functional object.  The
-interactive spec is required because only interactive functions can be
-bound to keys.
+Reports of bugs in XEmacs should be sent to
+@email{xemacs-beta@@xemacs.org}.  You can also post to the newsgroup
+comp.emacs.xemacs (or equivalentlt, send to the mailing list
+@email{xemacs@@xemacs.org}), but it is less likely that the developers
+will see it in a timely fashion.  @xref{Bugs,,, xemacs, the XEmacs
+User's Manual}, for more information on how to report bugs.
+@xref{Q1.4.2}, for more information on mailing lists relating to
+XEmacs.
 
-For the FAQ example you could use:
+There are three ways to read the Bugs section.
 
-@lisp
-(global-set-key [(control ?.)]
-  (lambda () (interactive) (scroll-up 1)))
-(global-set-key [(control ?		;)]
-			  (lambda () (interactive) (scroll-up -1)))
-@end lisp
+@enumerate
+@item
+In a printed copy of the XEmacs manual.
 
-This is fine if you only need a few functions within the lambda body.
-If you're doing more it's cleaner to define a separate function as in
-question 3.5.3 (@pxref{Q3.5.3}).
+@item
+With Info.  First, start XEmacs.  From the menu, select
+@samp{Help->Info (Online Docs)->Info Contents} to enter Info, then
+click on @samp{XEmacs}, then on @samp{Bugs}.  Or, use the keyboard: do
+@kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs
+manual, then @kbd{m Bugs RET} to get to the section on bugs.  Or use
+standalone Info in a like manner.  (Standalone Info is part of the
+Texinfo distribution, not part of the XEmacs distribution.)
 
-@node Q3.5.2, Q3.5.3, Q3.5.1, Customization
-@unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
+@item
+By hand.  Do
+@example
+cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"
+@end example
+@end enumerate
 
-Add the following line to your @file{.emacs} file:
+@node Q2.4.2, Q2.4.3, Q2.4.1, Installation
+@unnumberedsubsec Q2.4.2: Help!  XEmacs just crashed on me!
 
-@lisp
-(setq next-line-add-newlines nil)
-@end lisp
+First of all, don't panic.  Whenever XEmacs crashes, it tries extremely
+hard to auto-save all of your files before dying.  (The main time that
+this will not happen is if the machine physically lost power or if you
+killed the XEmacs process using @code{kill -9}).  The next time you try
+to edit those files, you will be informed that a more recent auto-save
+file exists.  You can use @kbd{M-x recover-file} to retrieve the
+auto-saved version of the file.
 
-This has been the default setting in XEmacs for some time.
+You can use the command @kbd{M-x recover-session} after a crash to pick
+up where you left off.
 
-@node Q3.5.3, Q3.5.4, Q3.5.2, Customization
-@unnumberedsubsec Q3.5.3: How do I bind C-. and C-; to scroll one line up and down?
+Now, XEmacs is not perfect, and there may occasionally be times, or
+particular sequences of actions, that cause it to crash.  If you can
+come up with a reproducible way of doing this (or even if you have a
+pretty good memory of exactly what you were doing at the time), the
+maintainers would be very interested in knowing about it.  The best
+way to report a bug is using @kbd{M-x report-emacs-bug} (or by
+selecting @samp{Send Bug Report...} from the Help menu).  If that
+won't work (e.g. you can't get XEmacs working at all), send ordinary
+mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
+the output from the crash, especially including the Lisp backtrace, as
+well as the XEmacs configuration from @kbd{M-x describe-installation}
+(or equivalently, the file @file{Installation} in the top of the build
+tree).  Note that the developers do @emph{not} usually follow
+@samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
+general questions about XEmacs than bug reports.
+
+If at all possible, include a C stack backtrace of the core dump that
+was produced.  This shows where exactly things went wrong, and makes
+it much easier to diagnose problems.  To do this under Unix and Mac OS
+X, you need to locate the core file (it's called @file{core}, and is
+usually sitting in the directory that you started XEmacs from, or your
+home directory if that other directory was not writable).  Then, go to
+that directory and execute a command like:
 
-Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
-@email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
+@example
+gdb `which xemacs` core
+@end example
 
-@lisp
-(defun scroll-up-one-line ()
-  (interactive)
-  (scroll-up 1))
+and then issue the command @samp{where} to get the stack backtrace.  You
+might have to use @code{dbx} or some similar debugger in place of
+@code{gdb}.  If you don't have any such debugger available, complain to
+your system administrator.
 
-(defun scroll-down-one-line ()
-  (interactive)
-  (scroll-down 1))
+It's possible that a core file didn't get produced or the stack trace
+from gdb is garbage, in which case you're out of luck unless you can
+reproduce the bug.  A nonexistent core file can happen in some
+circumstances on some operating systems, depending on what exactly
+triggered the crash.  It's also possible, however, that your limits
+are set to turn them off.  You may be able to reenable them using a
+command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
+out how your limits are set, use the command @samp{limit}.) However, if
+you didn't explicitly set your limits this way, go complain to your
+system administrator and tell him not to disable core files by
+default.
+
+A garbaged stack trace can happen for various reasons.  Some versions
+of gdb are broken on certain operating systems and aren't able to read
+the core file.  It's also possible that the stack got overwritten
+during the crash.  A very simple reason, however, is that your version
+of XEmacs was compiled without debugging information or had the
+debugging information stripped.  A compilation with optimization can
+also result in partly or completely garbaged stack trace.  In such
+cases, you will need to recompile XEmacs with debugging information
+and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem
+with a debugger}.  Note also that core files currently don't work at
+all under Cygwin, and the only way to get a backtrace is to run XEmacs
+from gdb.
+
+If you cannot get a backtrace from the core dump, but can reproduce
+the problem, try running XEmacs under gdb.  The goal is to get clean C
+and Lisp backtraces and submit a bug report including full
+configuration information as described above, as this will greatly
+assist in the process of tracking down the bug.  However, even partial
+information is better than none.  The process of getting backtraces
+from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs
+problem with a debugger}.
+
+If you're under Microsoft Windows, you're out of luck unless you happen
+to have a debugging aid installed on your system, for example Visual
+C++.  In this case, the crash will result in a message giving you the
+option to enter a debugger (for example, by pressing @samp{Cancel}).  Do
+this and locate the stack-trace window. (If your XEmacs was built
+without debugging information, the stack trace may not be very useful.)
 
-(global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
-(global-set-key [(control ?		;)] 'scroll-down-one-line) ; C-;
-@end lisp
+When making a problem report make sure that:
 
-The key point is that you can only bind simple functions to keys; you
-can not bind a key to a function that you're also passing arguments to.
-(@pxref{Q3.5.1} for a better answer).
+@enumerate
+@item
+Report @strong{all} of the information output by XEmacs during the
+crash.
 
-@node Q3.5.4, Q3.5.5, Q3.5.3, Customization
-@unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
+@item
+You mention what O/S and Hardware you are running XEmacs on.
 
-I cannot manage to globally bind my @kbd{Delete} key to something other
-than the default.  How does one do this?
+@item
+What version of XEmacs you are running.
 
-@lisp
-(defun foo ()
-  (interactive)
-  (message "You hit DELETE"))
+@item
+What build options you are using.
 
-(global-set-key 'delete 'foo)
-@end lisp
+@item
+If the problem is related to graphics and you are running Unix or Mac
+OS X, we will also need to know what version of the X Window System
+you are running, and what window manager you are using.
 
-However, some modes explicitly bind @kbd{Delete}, so you would need to
-add a hook that does @code{local-set-key} for them.  If what you want to
-do is make the Backspace and Delete keys work more PC/Motif-like, then
-take a look at the @file{delbs.el} package.
+@item
+If the problem happened on a TTY, please include the terminal type.
 
-New in XEmacs 19.14 is a variable called @code{key-translation-map}
-which makes it easier to bind @kbd{Delete}.  @file{delbs.el} is a
-good example of how to do this correctly.
+@item
+Try very hard to get both C and Lisp backtraces, as described above.
+@end enumerate
 
-Also @xref{Q3.5.10}.
+Much of the information above is automatically generated by @kbd{M-x
+report-emacs-bug}.  Even more, and often useful, information can be
+generated by redirecting the output of @code{make} and @code{make check}
+to a file (@file{beta.err} is the default used by @code{build-report}),
+and executing @kbd{M-x build-report}.
 
-@node Q3.5.5, Q3.5.6, Q3.5.4, Customization
-@unnumberedsubsec Q3.5.5: Scrolling one line at a time.
 
-Can the cursor keys scroll the screen a line at a time, rather than the
-default half page jump?  I tend it to find it disorienting.
+@node Q2.4.3, Q2.4.4, Q2.4.2, Installation
+@unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
 
-Try this:
+There have been a variety of reports of crashes due to compilers with
+buggy optimizers.  If you are compiling with optimization, consider
+turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
+debugger}) and recompiling.
 
-@lisp
-(defun scroll-one-line-up (&optional arg)
-  "Scroll the selected window up (forward in the text) one line (or N lines)."
-  (interactive "p")
-  (scroll-up (or arg 1)))
-
-(defun scroll-one-line-down (&optional arg)
-  "Scroll the selected window down (backward in the text) one line (or N)."
-  (interactive "p")
-  (scroll-down (or arg 1)))
-
-(global-set-key [up]   'scroll-one-line-up)
-(global-set-key [down] 'scroll-one-line-down)
-@end lisp
+Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
+the top-level source directory) to read what it says about your
+platform.
 
-The following will also work but will affect more than just the cursor
-keys (i.e. @kbd{C-n} and @kbd{C-p}):
+If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or
+21.5 or later using @samp{--enable-union-type} (or in either case used
+the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows),
+try recompiling again without it.  The union type has been known to
+trigger compiler errors in a number of cases.
 
-@lisp
-(setq scroll-step 1)
-@end lisp
+@node Q2.4.4, Q2.4.5, Q2.4.3, Installation
+@unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
 
-Starting with XEmacs-20.3 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Windows->Scroll Step...} or type
-@kbd{M-x customize @key{RET} windows @key{RET}}.
+If XEmacs does crash on you, one of the most productive things you can
+do to help get the bug fixed is to poke around a bit with the debugger.
+Here are some hints:
 
-@node Q3.5.6, Q3.5.7, Q3.5.5, Customization
-@unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
+@itemize @bullet
+@item
+First of all, if the crash is at all reproducible, consider very
+strongly recompiling your XEmacs with debugging symbols and with no
+optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
+that's an "oh" followed by a zero), and with the configure options
+@samp{--debug=yes} and @samp{--error-checking=all}
+(@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on
+XEmacs 21.5 or later).  This will make your XEmacs run somewhat slower,
+but you are a lot more likely to catch the problem earlier (closer to
+its source).  It makes it a lot easier to determine what's going on with
+a debugger.  The way to control the compiler flags is with the
+configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5).  If
+you have a recent version of 21.5, you should use
+@samp{--without-optimization} in preference to directly setting
+@samp{--cflags}.
 
-The following works in GNU Emacs 19:
+@item
+If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
+process), or it's inconvenient to run XEmacs again because XEmacs is
+already running or is running in batch mode as part of a bunch of
+scripts, you may be able to attach to the existing process with your
+debugger.  Under Unix and Mac OS X, the typical way to do this is to
+first use some variant of the @samp{ps} command to figure out the
+process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
+a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
+or @samp{ps -aW | grep xemacs} under Cygwin.  Then run
 
-@lisp
-(global-set-key [help] 'help-command);; Help
-@end lisp
+@example
+gdb /path/to/xemacs/xemacs ####
+@end example
 
-The following works in XEmacs 19.15 with the addition of shift:
+Where @code{####} is the process id of your XEmacs. (If you're not
+sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
+will stop and you can type @samp{where} in gdb to get a stack trace as
+usual.  To get things moving again, you can just type @samp{quit} in
+gdb.  It'll tell you the program is running and ask if you want to
+quit anyways.  Say @samp{y} and it'll quit and have your emacs
+continue from where it was at.
 
-@lisp
-(global-set-key [(shift help)] 'help-command);; Help
-@end lisp
+If you're running another debugger, a similar method may work, or you
+may have to run the debugger first and then use the @code{attach}
+command or something similar.
 
-But it doesn't work alone.  This is in the file @file{PROBLEMS} which
-should have come with your XEmacs installation: @emph{Emacs ignores the
-@kbd{help} key when running OLWM}.
+Under Microsoft Windows, use the menu item @samp{Build->Start
+Debug->Attach to Process...} and select the XEmacs process from the list
+given.
 
-OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
-client using
-@iftex
-@*
-@end iftex
-@code{XSendEvent}.  Allowing Emacs to react to synthetic
-events is a security hole, so this is turned off by default.  You can
-enable it by setting the variable @code{x-allow-sendevents} to t.  You
-can also cause fix this by telling OLWM to not grab the help key, with
-the null binding @code{OpenWindows.KeyboardCommand.Help:}.
+@item
+If you're able to run XEmacs under a debugger and reproduce the crash,
+here are some things you can do:
 
-@node Q3.5.7, Q3.5.8, Q3.5.6, Customization
-@unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
-@c Changed
-One way is to use the package @code{x-compose}.  Then you can use
-sequences like @kbd{Compose " a} to get ä, etc.
+@item
+If XEmacs is hitting an assertion failure, put a breakpoint on
+@code{assert_failed()}.
 
-Another way is to use the @code{iso-insert} package, provided in XEmacs
-19.15 and later. Then you can use sequences like @kbd{C-x 8 " a} to get
-ä, etc.
+@item
+If XEmacs is hitting some weird Lisp error that's causing it to crash
+(e.g. during startup), put a breakpoint on @code{signal_1()}---this is
+declared static in @file{eval.c}.
 
-@email{glynn@@sensei.co.uk, Glynn Clements} writes:
+@item
+If XEmacs is outputting lots of X errors, put a breakpoint on
+@code{x_error_handler()}; that will tell you which call is causing
+them.  Note that the result may not be very useful by default because
+X Windows normally operates asynchronously: A bunch of commands are
+buffered up and then sent to the server all at once.  This greatly
+improves performance over a network but means that an error may not be
+reported until the server receives the commands, which can be long
+after XEmacs made the erroneous calls.  For best results, you need to
+make the X server synchronous before getting the backtrace.  This can
+be done by starting XEmacs with the @samp{-sync} option or executing
+the Lisp code @code{(x-debug-mode t)}.
 
-@quotation
-It depends upon your X server.
+@item
+Internally, you will probably see lots of variables that hold objects of
+type @code{Lisp_Object}.  These are references to Lisp objects.
+Printing them out with the debugger probably won't be too
+useful---you'll likely just see a number.  To decode them, do this:
 
-Generally, the simplest way is to define a key as Multi_key with
-xmodmap, e.g.
-@c hey, show some respect, willya -- there's xkeycaps, isn't there? --
-@c chr ;)
 @example
-	xmodmap -e 'keycode 0xff20 = Multi_key'
+call debug_print (OBJECT)
 @end example
 
-You will need to pick an appropriate keycode. Use xev to find out the
-keycodes for each key.
-
-[NB: On a `Windows' keyboard, recent versions of XFree86 automatically
-define the right `Windows' key as Multi_key'.]
+where @var{OBJECT} is whatever you want to decode (it can be a variable,
+a function call, etc.).  This uses the Lisp printing routines to out a
+readable representation on the TTY from which the xemacs process was
+invoked.
 
-Once you have Multi_key defined, you can use e.g.
-@example
-	Multi a '	=> á
-	Multi e "	=> ë
-	Multi c ,	=> ç
-@end example
+Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
+of @code{debug_print}.  You can also try @code{dpa} if you can't see
+the output from @code{debug_print} (this will return a string containing
+the output), or use @code{debug_p3} if @code{debug_print} itself triggers
+a crash (this is a less comprehensive but super-safe way to print out
+a Lisp object).
 
-etc.
+@item
+If you want to get a Lisp backtrace showing the Lisp call
+stack, do this:
 
-Also, recent versions of XFree86 define various AltGr-<key>
-combinations as dead keys, i.e.
 @example
-	AltGr [		=> dead_diaeresis
-	AltGr ]		=> dead_tilde
-	AltGr ;		=> dead_acute
+call debug_backtrace ()
 @end example
-etc.
-
-Running @samp{xmodmap -pk} will list all of the defined keysyms.
-@end quotation
 
-@node Q3.5.8, Q3.5.9, Q3.5.7, Customization
-@unnumberedsubsec Q3.5.8: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
+Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
+of @code{debug_backtrace}.
 
-Why does @code{(define-key global-map [ delete-forward ] 'delete-char)}
-complain of not being able to bind an unknown key?
-
-Try this instead:
+@item
+Using @code{debug_print} and @code{debug_backtrace} has two
+disadvantages - they can only be used with a running (including hung
+or zombie) xemacs process, and they do not display the internal C
+structure of a Lisp Object.  Even if all you've got is a core dump,
+all is not lost.
 
-@lisp
-(define-key global-map [delete_forward] 'delete-char)
-@end lisp
+If you're using GDB, there are some macros in the file
+@file{src/.gdbinit} in the XEmacs source distribution that should make
+it easier for you to decode Lisp objects.  This file is automatically
+read by gdb if gdb is run in the directory where xemacs was built, and
+contains these useful macros to inspect the state of xemacs:
 
-and it will work.
+@table @code
+@item pobj
+Usage: pobj lisp_object @*
+Print the internal C representation of a lisp object.
+
+@item xtype
+Usage: xtype lisp_object @*
+Print the Lisp type of a lisp object.
+
+@item lbt
+Usage: lbt @*
+Print the current Lisp stack trace.
+Requires a running xemacs process.  (It works by calling the db
+routine described above.)
+
+@item ldp
+Usage: ldp lisp_object @*
+Print a Lisp Object value using the Lisp printer.
+Requires a running xemacs process.  (It works by calling the dp
+routine described above.)
+
+@item run-temacs
+Usage: run-temacs @*
+Run temacs interactively, like xemacs.
+Use this with debugging tools (like purify) that cannot deal with dumping,
+or when temacs builds successfully, but xemacs does not.
+
+@item dump-temacs
+Usage: dump-temacs @*
+Run the dumping part of the build procedure.
+Use when debugging temacs, not xemacs!
+Use this when temacs builds successfully, but xemacs does not.
+
+@item check-xemacs
+Usage: check-xemacs @*
+Run the test suite.  Equivalent to 'make check'.
+
+@item check-temacs
+Usage: check-temacs @*
+Run the test suite on temacs.  Equivalent to 'make check-temacs'.
+Use this with debugging tools (like purify) that cannot deal with dumping,
+or when temacs builds successfully, but xemacs does not.
+@end table
 
-What you are seeing above is a bug due to code that is trying to check
-for GNU Emacs syntax like:
+If you are using Sun's @file{dbx} debugger, there is an equivalent file
+@file{src/.dbxrc}, which defines the same commands for dbx.
 
-(define-key global-map [C-M-a] 'delete-char)
+@item
+If you're using a debugger to get a C stack backtrace and you're seeing
+stack traces with some of the innermost frames mangled, it may be due to
+dynamic linking. (This happens especially under Linux.) Consider
+reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5
+or later).  Also, sometimes (again under Linux), stack backtraces of
+core dumps will have the frame where the fatal signal occurred mangled;
+if you can obtain a stack trace while running the XEmacs process under a
+debugger, the stack trace should be clean.
 
-which otherwise would cause no errors but would not result in the
-expected behavior.
+@email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
+version 1.8 if dynamic linking and debugging is a problem on Linux.
 
-This bug has been fixed in 19.14.
+@item
+If you're using a debugger to get a C stack backtrace and you're
+getting a completely mangled and bogus stack trace, it's probably due to
+one of the following:
 
-@node Q3.5.9, Q3.5.10, Q3.5.8, Customization
-@unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
+@enumerate a
+@item
+Your executable has been stripped.  Bad news.  Tell your sysadmin not to
+do this---it doesn't accomplish anything except to save a bit of disk
+space, and makes debugging much much harder.
 
-With XEmacs-20.2 use the @code{delbs} package:
+@item
+Your stack is getting trashed.  Debugging this is hard; you have to do a
+binary-search type of narrowing down where the crash occurs, until you
+figure out exactly which line is causing the problem.  Of course, this
+only works if the bug is highly reproducible.  Also, in many cases if
+you run XEmacs from the debugger, the debugger can protect the stack
+somewhat.  However, if the stack is being smashed, it is typically the
+case that there is a wild pointer somewhere in the program, often quite
+far from where the crash occurs.
 
-@lisp
-(require 'delbs)
-@end lisp
+@item
+If your stack trace has exactly one frame in it, with address 0x0, this
+could simply mean that XEmacs attempted to execute code at that address,
+e.g. through jumping to a null function pointer.  Unfortunately, under
+those circumstances, GDB under Linux doesn't know how to get a stack
+trace. (Yes, this is the fourth Linux-related problem I've mentioned.  I
+have no idea why GDB under Linux is so bogus.  Complain to the GDB
+authors, or to comp.os.linux.development.system.) Again, you'll have to
+use the narrowing-down process described above.
 
-This will give you the functions @code{delbs-enable-delete-forward} to
-set things up, and @code{delbs-disable-delete-forward} to revert to
-``normal'' behavior.  Note that @code{delbackspace} package is obsolete.
+@item
+You will get a Lisp backtrace output when XEmacs crashes, so you'll have
+something useful.
 
-Starting with XEmacs-20.3 better solution is to set variable
-@code{delete-key-deletes-forward} to t.  You can also change this with
-Customize. Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Basics->Delete Key Deletes Forward} or
-type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
+@end enumerate
 
-Also @xref{Q3.5.4}.
+@item
+If you compile with the newer gcc variants gcc-2.8 or egcs, you will
+also need gdb 4.17 or above.  Earlier releases of gdb can't handle the
+debug information generated by the newer compilers.
 
-@node Q3.5.10, Q3.5.11, Q3.5.9, Customization
-@unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
+@item
+In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
+@file{src/gdbinit}.  This had the disadvantage of not being sourced
+automatically by gdb, so you had to set that up yourself.
 
-Yes, with @code{(setq modifier-keys-are-sticky t)}.  This will give the
-effect of being able to press and release Shift and have the next
-character typed come out in upper case.  This will affect all the other
-modifier keys like Control and Meta as well.
+@item
+If you are running Microsoft Windows, the the file @file{nt/README} for
+further information about debugging XEmacs.
 
-@email{ben@@xemacs.org, Ben Wing} writes:
+@end itemize
 
-@quotation
-One thing about the sticky modifiers is that if you move the mouse out
-of the frame and back in, it cancels all currently ``stuck'' modifiers.
-@end quotation
+@node Q2.4.5, Q2.4.6, Q2.4.4, Installation
+@unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
 
-@node Q3.5.11, Q3.6.1, Q3.5.10, Customization
-@unnumberedsubsec Q3.5.11: How do I map the arrow keys?
-@c New
-Say you want to map @kbd{C-@key{right}} to forward-word:
+When I try to use some particular option of some particular package, I
+get a cryptic error message in the minibuffer.
+
+If the message went by too quickly, use @samp{Help->Recent Messages}
+from the menubar (or type @kbd{C-h l}) to see recent messages.
+
+If you can't figure out what's going on, select
+@samp{Options->Troubleshooting->Debug on Error} from the menubar (or
+type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
+the error happen again.  This will put in the debugger (you can get
+out of this and continue what you were doing before by typing @kbd{c})
+and give you a backtrace that may be enlightening.  If not, try
+reading through this FAQ; if that fails, you could try posting to
+@samp{comp.emacs.xemacs} (making sure to include the backtrace) and
+someone may be able to help.  If you can identify which XEmacs Lisp
+source file the error is coming from you can get a more detailed stack
+backtrace by doing the following:
 
-@email{sds@@usa.net, Sam Steingold} writes:
+@enumerate
+@item
+Visit the .el file in an XEmacs buffer.
 
-@quotation
-@lisp
-; both XEmacs and Emacs
-(define-key global-map [(control right)] 'forward-word)
-@end lisp
-or
-@lisp
-; Emacs only
-(define-key global-map [C-right] 'forward-word)
-@end lisp
-or
-@lisp
-; ver > 20, both
-(define-key global-map (kbd "C-<right>") 'forward-word)
-@end lisp
-@end quotation
+@item
+Issue the command @kbd{M-x eval-current-buffer}.
 
+@item
+Reproduce the error.
+@end enumerate
 
+For more information on debugging Lisp code, @xref{Debugging,,,
+lispref, XEmacs Lisp Reference Manual}.
+
+@node Q2.4.6, Q2.4.7, Q2.4.5, Installation
+@unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something.
+
+XEmacs might just be slow; some operations take a long time.  XEmacs
+may also be waiting on a response from the network, for example when
+you are trying to send mail.
+
+You can usually interrupt XEmacs by typing @kbd{C-g}.  If not (for
+example, Lisp code explicitly disabled this by setting
+@code{inhibit-quit}), you can use the "critical quit" mechanism by
+typing @kbd{Control-Shift-G}.  This should also pop you into the
+debugger and give you a backtrace, which can tell you where the
+problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a
+debugger}). (Note that setting @code{debug-on-quit} or selecting
+@samp{Options->Troubleshooting->Debug on Quit} will also cause regular
+@kbd{C-g} to enter the debugger and give you a backtrace.)
+
+If you can't interrupt XEmacs this way, or for some reason XEmacs is
+not talking to the keyboard, you can try sending the @samp{SIGINT}
+signal using the @samp{kill} command.
+
+If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
+you can't interrupt it at all, you could try attaching to the process
+and getting a C stack backtrace.  @xref{Q2.4.4, How to debug an XEmacs
+problem with a debugger}.
+
+@node Q2.4.7, Q2.4.8, Q2.4.6, Installation
+@unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode.
+
+Typically this happens when you are trying to compile some Elisp code.
+If you are doing this as part of XEmacs or the XEmacs packages, you
+should automatically get a backtrace, which can help you determine the
+source of the problem.  In other cases, you can get equivalent results
+by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
+stack-trace-on-error t load-always-display-messages t
+load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
+t)} (this needs to be all on one line; to set an environment variable,
+use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
+etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
+@samp{tcsh}).  @samp{XEMACSDEBUG} specifies Lisp code that will be
+executed at startup time.
+
+If the backtrace is not sufficiently useful in helping you diagnose
+the problem, you should consider using a debugger such as GDB.
+@xref{Q2.4.4, How to debug an XEmacs problem with a debugger}.  You
+probably want to set a breakpoint on @code{signal_1}.  Since such
+errors often occur during compiling, which is often triggered by a
+complex command run from a make suite, it may be easier to attach to
+the process once it's running.
+
+Under Microsoft Windows (and perhaps other operating systems), there is
+another useful trick you can do if you have configured with debugging
+support (configure option @samp{--debug} (@samp{--with-debug} in 21.5)
+or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}).  Set the
+environment variable @samp{XEMACSDEBUG} (as described above) to
+@samp{(setq debug-on-error t)}.  Then, when an error occurs
+noninteractively, instead of trying to invoke the Lisp debugger (which
+obviously won't work), XEmacs will break out to a C debugger using
+@code{(force-debugging-signal t)}.  @emph{NOTE}: This runs
+@code{abort()}!!! (As well as and after executing INT 3 under MS
+Windows, which should invoke a debugger if it's active.) This is
+guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
+die anyway, and if no debugger is present, this will usefully dump
+core.)
+
+@node Q2.4.8, Q2.4.9, Q2.4.7, Installation
+@unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem.
+
+XEmacs has various facilities for debugging event handling.
+
+First, try setting the variable @code{debug-emacs-events} to non-zero.
+This will output various information showing which events are being
+received and how they are being translated.  This may show you, for
+example, that a key command is getting intercepted using
+@code{key-translation-map}; this problem can otherwise be very tricky
+to debug.
+
+Under X, you can see exactly which events are being received from the
+window system by setting @code{x-debug-events} to non-zero. (The value
+@samp{1} gives you regular output, and @samp{2} gives you verbose
+output, including all parameters.)
+
+A similar facility exists under MS Windows: Set
+@code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
+you regular output.  The value @samp{2} gives you verbose output,
+including all parameters.  The value @samp{3} gives you
+super-gorily-detailed output.)
+
+@node Q2.4.9, Q2.4.10, Q2.4.8, Installation
+@unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me.  Is it broken?
 
-@node Q3.6.1, Q3.6.2, Q3.5.11, Customization
-@unnumberedsec 3.6: The Cursor
-@unnumberedsubsec Q3.6.1: Is there a way to make the bar cursor thicker?
+@kbd{C-g} does work for most people in most circumstances.  If it
+doesn't, there are two possible explanations:
 
-I'd like to have the bar cursor a little thicker, as I tend to "lose" it
-often.
+@enumerate
+@item
+XEmacs is hung in a way that prevents @kbd{C-g} from working.  This
+can happen when code is wrapped with a binding of @code{inhibit-quit}
+to @code{t}; you should still be able interrupt XEmacs using "critical
+quit".  On the other hand, XEmacs may be seriously wedged. (If you're
+lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.) 
+@xref{Q2.4.6, XEmacs hangs when I try to do something.}.
 
-For a 1 pixel bar cursor, use:
+@item
+@kbd{C-g} is indeed broken on your system.  To test, try executing
+@code{(while t)} from the @samp{*scratch*} buffer.  If @kbd{C-g}
+doesn't interrupt, then it's broken.  This used to happen with systems
+where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
+However, there may not be very many such systems nowadays.
+@end enumerate
 
-@lisp
-(setq bar-cursor t)
-@end lisp
+@node Q2.4.10, Q2.4.11, Q2.4.9, Installation
+@unnumberedsubsec Q2.4.10: How do I debug process-related problems?
+
+Under MS Windows, you can set the variable
+@code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
+information on exactly what is getting passed to a process.  This can
+be useful in determining problems with quoting. (Under Unix, a process
+receives each argument separately, but under MS Windows a single
+command line is received, and arguments with spaces or other special
+characters in them must be quoted.  Unfortunately this means that each
+process, potentially at least, has its own quoting conventions, and
+the code to process quoting conventions in @file{cmd.exe}, the Visual
+C++ startup code and the like is baroque and poorly documented.
+XEmacs uses the variable
+@code{mswindows-construct-process-command-line-alist} to construct a
+command line from a list of arguments based on the command to be run,
+but it is (and cannot be) a perfect solution.)
+
+@node Q2.4.11, Q2.4.12, Q2.4.10, Installation
+@unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors.
+
+If this is happening, we would very much like to know what's causing
+them.  To find this out, see @ref{Q2.4.4, How to debug an XEmacs
+problem with a debugger}.  Try to get both a C and Lisp backtrace, and
+send them along with the full error output to
+@email{xemacs-beta@@xemacs.org}.
+
+@node Q2.4.12, Q2.5.1, Q2.4.11, Installation
+@unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more!
+
+You have been used to doing `foo', but now when you invoke it (or
+click the toolbar button or select the menu item), nothing (or an
+error) happens.  The simplest explanation is that you are missing a
+package that is essential to you.  You can either track it down and
+install it (there is a list of packages and brief descriptions of
+their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
+(@pxref{Q2.1.2, How do I figure out which packages to install?}).
+
+@c #### should xref to XEmacs manual here
+
+@unnumberedsec 2.5: Startup-Related Problems
+
+@node Q2.5.1, Q2.5.2, Q2.4.12, Installation
+@unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
 
-For a 2 pixel bar cursor, use:
+Help!  I can not get XEmacs to display on my Envizex X-terminal!
 
-@lisp
-(setq bar-cursor 'anything-else)
-@end lisp
+Try setting the @code{DISPLAY} variable using the numeric IP address of
+the host you are running XEmacs from.
 
-Starting with XEmacs-20.3 you can also change these with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
-@kbd{M-x customize @key{RET} display @key{RET}}.
+@node Q2.5.2, Q2.5.3, Q2.5.1, Installation
+@unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
 
-You can use a color to make it stand out better:
+First of all, if XEmacs can't find the packages, check to make sure
+that you put the packages in the right place, or that you told XEmacs
+where to look for the packages when you compiled it.  @xref{Q2.1.1}.
+
+If something is still going wrong, or you get a startup warning about
+not being able to deduce some paths, you can get detailed information
+on the path-searching process at startup by setting the environment
+variable @samp{EMACSDEBUGPATHS} to a non-null value.  One thing to
+look for if you're having package problems is the value of
+@samp{configure-package-path}.  This corresponds to what was compiled
+into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
+parameter (@pxref{Q2.1.1}).  If this has the value of @samp{nil},
+this means that no value was compiled into XEmacs using these parameters.
+
+@node Q2.5.3, Q2.5.4, Q2.5.2, Installation
+@unnumberedsubsec Q2.5.3: XEmacs won't start without network.
+
+If XEmacs starts when you're on the network, but fails when you're not
+on the network, you may be missing a "localhost" entry in your
+@file{/etc/hosts} file.  The file should contain an entry like:
 
 @example
-Emacs*cursorColor:	Red
+127.0.0.1        localhost
 @end example
 
-@node Q3.6.2, Q3.6.3, Q3.6.1, Customization
-@unnumberedsubsec Q3.6.2: Is there a way to get back the block cursor?
+Add that line, and XEmacs will be happy.
 
-@lisp
-(setq bar-cursor nil)
-@end lisp
+@node Q2.5.4, Q2.5.5, Q2.5.3, Installation
+@unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
 
-Starting with XEmacs-20.3 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
-@kbd{M-x customize @key{RET} display @key{RET}}.
+How can I avoid the startup warnings about deducing proper fonts?
+
+This is highly dependent on your installation, but try with the
+following font as your base font for XEmacs and see what it does:
+
+@format
+-adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
+@end format
+
+More precisely, do the following in your resource file:
 
-@node Q3.6.3, Q3.7.1, Q3.6.2, Customization
-@unnumberedsubsec Q3.6.3: Can I make the cursor blink?
+@format
+Emacs.default.attributeFont: \
+-adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
+@end format
 
-If you are running a version of XEmacs older than 19.14, no.  Otherwise
-you can do the following:
+If you just don't want to see the @samp{*Warnings*} buffer at startup
+time, you can set this:
 
 @lisp
-(blink-cursor-mode)
+(setq display-warning-minimum-level 'error)
 @end lisp
 
-This function toggles between a steady cursor and a blinking cursor.
-You may also set this mode from the menu bar by selecting @samp{Options
-=> Frame Appearance => Blinking Cursor}.  Remember to save options.
+The buffer still exists; it just isn't in your face.
 
-@node Q3.7.1, Q3.7.2, Q3.6.3, Customization
-@unnumberedsec 3.7: The Mouse and Highlighting
-@unnumberedsubsec Q3.7.1: How can I turn off Mouse pasting?
+@node Q2.5.5, Q2.5.6, Q2.5.4, Installation
+@unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
 
-I keep hitting the middle mouse button by accident and getting stuff
-pasted into my buffer so how can I turn this off?
+The following information comes from the @file{PROBLEMS} file that comes
+with XEmacs.
 
-Here is an alternative binding, whereby the middle mouse button selects
-(but does not cut) the expression under the mouse. Clicking middle on a
-left or right paren will select to the matching one.  Note that you can
-use @code{define-key} or @code{global-set-key}.
+If you're having troubles with HP/UX it is because HP/UX defines the
+modifiers wrong in X.  Here is a shell script to fix the problem; be
+sure that it is run after VUE configures the X server.
 
-@lisp
-(defun mouse-set-point-and-select (event)
-  "Sets the point at the mouse location, then marks following form"
-  (interactive "@@e")
-  (mouse-set-point event)
-  (mark-sexp 1))
-(define-key global-map [button2] 'mouse-set-point-and-select)
-@end lisp
+@example
+#! /bin/sh
+xmodmap 2> /dev/null - << EOF
+keysym Alt_L = Meta_L
+keysym Alt_R = Meta_R
+EOF
 
-@node Q3.7.2, Q3.7.3, Q3.7.1, Customization
-@unnumberedsubsec Q3.7.2: How do I set control/meta/etc modifiers on mouse buttons?
+xmodmap - << EOF
+clear mod1
+keysym Mode_switch = NoSymbol
+add mod1 = Meta_L
+keysym Meta_R = Mode_switch
+add mod2 = Mode_switch
+EOF
+@end example
 
-Use, for instance, @code{[(meta button1)]}. For example, here is a common
-setting for Common Lisp programmers who use the bundled @code{ilisp}
-package, whereby meta-button1 on a function name will find the file where
-the function name was defined, and put you at that location in the source
-file.
+@node Q2.5.6,  , Q2.5.5, Installation
+@unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+
+Yes.
+
+The console was there because @file{temacs} (and in turn, @file{xemacs})
+was a console application, and Windows typically creates a new
+console for a console process unless the creating process requests that
+one isn't created.  This used to be fixed with @file{runemacs}, a small
+Windows application that existed merely to start @file{xemacs}, stating
+that it didn't want a console.
+
+XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
+application.  The explanation of what that means is included for
+educational value.
+
+When building an application to be run in a Win32 environment, you must
+state which sub-system it is to run in.  Valid subsystems include
+"console" and "gui".  The subsystem you use affects the run time
+libraries linked into your application, the start up function that is
+run before control is handed over to your application, the entry point
+to your program, and how Windows normally invokes your program. (Console
+programs automatically get a console created for them at startup if
+their stdin/stdout don't point anywhere useful, which is the case when
+run from the GUI.  This is a stupid design, of course -- instead, the
+console should get created only when the first I/O actually occurs!
+GUI programs have an equally stupid design: When called from
+@file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
+point nowhere useful, even though the command shell has its own
+stdin/stdout.  It's as if someone who had learned a bit about stdio but
+had no actual knowledge of interprocess communication designed the
+scheme; unfortunately, the whole process-communication aspect of the
+Win32 API is equally badly designed.) For example, the entry point for a
+console app is "main" (which is what you'd expect for a C/C++ program),
+but the entry point for a "gui" app is "WinMain".  This confuses and
+annoys a lot of programmers who've grown up on Unix systems, where the
+kernel doesn't really care whether your application is a gui program or
+not.
+
+For reasons not altogether clear, and are lost in the mists of time and
+tradition, XEmacs on Win32 started out as a console application, and
+therefore a console was automatically created for it. (It may have been
+made a console application partly because a console is needed in some
+circumstances, especially under Win95, to interrupt, terminate, or send
+signals to a child process, and because of the bogosity mentioned above
+with GUI programs and the standard command shell.  Currently, XEmacs
+just creates and immediately hides a console when necessary, and
+works around the "no useful stdio" problem by creating its own console
+window as necessary to display messages in.)
+
+@node Editing, Display, Installation, Top
+@unnumbered 3 Editing Functions
 
-[Inside a function that gets called by the lisp-mode-hook and
-ilisp-mode-hook]
+This is part 3 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to the editing-related capabilities of XEmacs (the
+keyboard, mouse, buffers, text selections, etc.) and how to customize
+them.
 
-@lisp
-(local-set-key [(meta button1)] 'edit-definitions-lisp)
-@end lisp
+@menu
+3.0: The Keyboard
+* Q3.0.1::    How can I customize the keyboard?
+* Q3.0.2::    How can I bind complex functions (or macros) to keys?
+* Q3.0.3::    How do I bind C-. and C-; to scroll one line up and down?
+* Q3.0.4::    Globally binding @kbd{Delete}?
+* Q3.0.5::    How to map @kbd{Help} key alone on Sun type4 keyboard?
+* Q3.0.6::    How can you type in special characters in XEmacs?
+* Q3.0.7::    Can I turn on @dfn{sticky} modifier keys?
+* Q3.0.8::    How do I map the arrow keys?
+* Q3.0.9::    HP Alt key as Meta.
+* Q3.0.10::   Why does edt emulation not work?
+* Q3.0.11::   How can I emulate VI and use it as my default mode?
+
+3.1: The Mouse
+* Q3.1.1::    How can I turn off Mouse pasting?
+* Q3.1.2::    How do I set control/meta/etc modifiers on mouse buttons?
+* Q3.1.3::    Clicking the left button does not do anything in buffer list.
+* Q3.1.4::    How can I get a list of buffers when I hit mouse button 3?
+* Q3.1.5::    How can I set XEmacs up so that it pastes where the text cursor is?
+
+3.2: Buffers, Text Editing
+* Q3.2.1::    Can I have the end of the buffer delimited in some way?
+* Q3.2.2::    How do I insert today's date into a buffer?
+* Q3.2.3::    How do I get a single minibuffer frame?
+* Q3.2.4::    How can I enable auto-indent and/or Filladapt?
+* Q3.2.5::    How can I get XEmacs to come up in text/auto-fill mode by default?
+
+3.3: Text Selections
+* Q3.3.1::    How do I select a rectangular region?
+* Q3.3.2::    How can I turn off or change highlighted selections?
+* Q3.3.3::    How do I cause typing on an active region to remove it?
+* Q3.3.4::    Can I turn off the highlight during isearch?
+* Q3.3.5::    Why is killing so slow?
+* Q3.3.6::    Why does @kbd{M-w} take so long?
+
+3.4: Editing Source Code
+* Q3.4.1::    I do not like cc-mode.  How do I use the old c-mode?
+* Q3.4.2::    How do you make XEmacs indent CL if-clauses correctly?
+@end menu
 
-@node Q3.7.3, Q3.7.4, Q3.7.2, Customization
-@unnumberedsubsec Q3.7.3: Clicking the left button does not do anything in buffer list.
+@unnumberedsec 3.0: The Keyboard
 
-I do @kbd{C-x C-b} to get a list of buffers and the entries get
-highlighted when I move the mouse over them but clicking the left mouse
-does not do anything.
+@node Q3.0.1, Q3.0.2, Editing, Editing
+@unnumberedsubsec Q3.0.1: How can I customize the keyboard?
 
-Use the middle mouse button.
+#### Write me.
 
-@node Q3.7.4, Q3.7.5, Q3.7.3, Customization
-@unnumberedsubsec Q3.7.4: How can I get a list of buffers when I hit mouse button 3?
+@node Q3.0.2, Q3.0.3, Q3.0.1, Editing
+@unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
 
-The following code will replace the default popup on button3:
+As an example, say you want the @kbd{paste} key on a Sun keyboard to
+insert the current Primary X selection at point. You can accomplish this
+with:
 
 @lisp
-(global-set-key [button3] 'popup-buffer-menu)
+(define-key global-map [f18] 'x-insert-selection)
 @end lisp
 
-@node Q3.7.5, Q3.7.6, Q3.7.4, Customization
-@unnumberedsubsec Q3.7.5: Why does cut-and-paste not work between XEmacs and a cmdtool?
-
-We don't know.  It's a bug.  There does seem to be a work-around,
-however.  Try running xclipboard first.  It appears to fix the problem
-even if you exit it.  (This should be mostly fixed in 19.13, but we
-haven't yet verified that).
-
-@node Q3.7.6, Q3.7.7, Q3.7.5, Customization
-@unnumberedsubsec Q3.7.6: How I can set XEmacs up so that it pastes where the text cursor is?
+However, this only works if there is a current X selection (the
+selection will be highlighted).  The functionality I like is for the
+@kbd{paste} key to insert the current X selection if there is one,
+otherwise insert the contents of the clipboard.  To do this you need to
+pass arguments to @code{x-insert-selection}.  This is done by wrapping
+the call in a 'lambda form:
 
-By default XEmacs pastes X selections where the mouse pointer is.  How
-do I disable this?
+@lisp
+(global-set-key [f18]
+  (lambda () (interactive) (x-insert-selection t nil)))
+@end lisp
 
-Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
-@key{RET}}.
+This binds the f18 key to a @dfn{generic} functional object.  The
+interactive spec is required because only interactive functions can be
+bound to keys.
 
-To get XEmacs to paste at the text cursor, add this your @file{.emacs}:
+For the FAQ example you could use:
 
 @lisp
-(setq mouse-yank-at-point t)
+(global-set-key [(control ?.)]
+  (lambda () (interactive) (scroll-up 1)))
+(global-set-key [(control ?;)]
+  (lambda () (interactive) (scroll-up -1)))
 @end lisp
 
-Starting with XEmacs-20.2 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Mouse->Yank At Point...} or type
-@kbd{M-x customize @key{RET} mouse @key{RET}}.
+This is fine if you only need a few functions within the lambda body.
+If you're doing more it's cleaner to define a separate function.
+@xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
+down?}.
 
-@node Q3.7.7, Q3.7.8, Q3.7.6, Customization
-@unnumberedsubsec Q3.7.7: How do I select a rectangular region?
+@node Q3.0.3, Q3.0.4, Q3.0.2, Editing
+@unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
 
-Just select the region normally, then use the rectangle commands (e.g.
-@code{kill-rectangle} on it.  The region does not highlight as a
-rectangle, but the commands work just fine.
+Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
+@email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
 
-To actually sweep out rectangular regions with the mouse you can use
-@code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
-Then use rectangle commands.
+@lisp
+(defun scroll-up-one-line ()
+  (interactive)
+  (scroll-up 1))
 
-You can also do the following to change default behavior to sweep out
-rectangular regions:
+(defun scroll-down-one-line ()
+  (interactive)
+  (scroll-down 1))
 
-@lisp
-(setq mouse-track-rectangle-p t)
+(global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
+(global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
 @end lisp
 
-Starting with XEmacs-20.2 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Mouse->Track Rectangle...} or type
-@kbd{M-x customize @key{RET} mouse @key{RET}}.
+The key point is that you can only bind simple functions to keys; you
+can not bind a key to a function that you're also passing arguments
+to.  (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
+keys?} for a better answer).
 
+@node Q3.0.4, Q3.0.5, Q3.0.3, Editing
+@unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
 
-@example
- mouse-track-do-rectangle: (event)
-   -- an interactive compiled Lisp function.
- Like `mouse-track' but selects rectangles instead of regions.
-@end example
+I cannot manage to globally bind my @kbd{Delete} key to something other
+than the default.  How does one do this?
 
-@node Q3.7.8, Q3.8.1, Q3.7.7, Customization
-@unnumberedsubsec Q3.7.8: Why does @kbd{M-w} take so long?
+Answer: The problem is that many modes explicitly bind @kbd{Delete}.  To
+get around this, try the following:
 
-It actually doesn't.  It leaves the region visible for a second so that
-you can see what area is being yanked.  If you start working, though, it
-will immediately complete its operation.  In other words, it will only
-delay for a second if you let it.
+@lisp
+(defun foo ()
+  (interactive)
+  (message "You hit DELETE"))
+
+(define-key key-translation-map 'delete 'redirected-delete)
+(global-set-key 'redirected-delete 'foo)
+@end lisp
 
-@node Q3.8.1, Q3.8.2, Q3.7.8, Customization
-@unnumberedsec 3.8: The Menubar and Toolbar
-@unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
+@node Q3.0.5, Q3.0.6, Q3.0.4, Editing
+@unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
 
-If you are running XEmacs 19.13 and earlier, add this command to your
-@file{.emacs}.
+The following works in GNU Emacs 19:
 
 @lisp
-(set-menubar nil)
+(global-set-key [help] 'help-command);; Help
 @end lisp
 
-Starting with XEmacs 19.14 the preferred method is:
+The following works in XEmacs with the addition of shift:
 
 @lisp
-(set-specifier menubar-visible-p nil)
+(global-set-key [(shift help)] 'help-command);; Help
 @end lisp
 
-@node Q3.8.2, Q3.8.3, Q3.8.1, Customization
-@unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
+But it doesn't work alone.  This is in the file @file{PROBLEMS} which
+should have come with your XEmacs installation: @emph{Emacs ignores the
+@kbd{help} key when running OLWM}.
 
-For an extensive menubar, add this line to your @file{.emacs}:
+OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
+client using
+@iftex
+@*
+@end iftex
+@code{XSendEvent}.  Allowing Emacs to react to synthetic
+events is a security hole, so this is turned off by default.  You can
+enable it by setting the variable @code{x-allow-sendevents} to t.  You
+can also cause fix this by telling OLWM to not grab the help key, with
+the null binding @code{OpenWindows.KeyboardCommand.Help:}.
 
-@lisp
-(load "big-menubar")
-@end lisp
+@node Q3.0.6, Q3.0.7, Q3.0.5, Editing
+@unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
+One way is to use the package @code{x-compose}.  Then you can use
+sequences like @kbd{Compose " a} to get ä, etc.
 
-If you'd like to write your own, this file provides as good a set of
-examples as any to start from.  The file is located in
-@file{lisp/packages/big-menubar.el} in the XEmacs installation
-directory.
+Another way is to use the @code{iso-insert} package. Then you can use
+sequences like @kbd{C-x 8 " a} to get ä, etc.
 
-@node Q3.8.3, Q3.8.4, Q3.8.2, Customization
-@unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
+@email{glynn@@sensei.co.uk, Glynn Clements} writes:
 
-Add the following to your @file{.emacs} (suit to fit):
+@quotation
+It depends upon your X server.
 
-@lisp
-(setq buffers-menu-max-size 20)
-@end lisp
-
-For no limit, use an argument of @samp{nil}.
-
-Starting with XEmacs-20.3 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
-type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
-
-@node Q3.8.4, Q3.8.5, Q3.8.3, Customization
-@unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
+Generally, the simplest way is to define a key as Multi_key with
+xmodmap, e.g.
+@c hey, show some respect, willya -- there's xkeycaps, isn't there? --
+@c chr ;)
+@example
+        xmodmap -e 'keycode 0xff20 = Multi_key'
+@end example
 
-I am trying to use a resource like @code{Emacs*menubar*font} to set the
-font of the menubar but it's not working.
+You will need to pick an appropriate keycode. Use xev to find out the
+keycodes for each key.
 
-If you are using the real Motif menubar, this resource is not
-recognized; you have to say:
+[NB: On a `Windows' keyboard, recent versions of XFree86 automatically
+define the right `Windows' key as Multi_key'.]
 
+Once you have Multi_key defined, you can use e.g.
 @example
-Emacs*menubar*fontList: FONT
+        Multi a '       => á
+        Multi e "       => ë
+        Multi c ,       => ç
 @end example
 
-If you are using the Lucid menubar, the former resource will be
-recognized only if the latter resource is unset.  This means that the
-resource
+etc.
 
+Also, recent versions of XFree86 define various AltGr-<key>
+combinations as dead keys, i.e.
 @example
-*fontList: FONT
+        AltGr [         => dead_diaeresis
+        AltGr ]         => dead_tilde
+        AltGr ;         => dead_acute
 @end example
+etc.
 
-will override
+Running @samp{xmodmap -pk} will list all of the defined keysyms.
+@end quotation
 
-@example
-Emacs*menubar*font: FONT
-@end example
+For the related problem of @emph{displaying} non-ASCII characters in a
+non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
 
-even though the latter is more specific.
+@node Q3.0.7, Q3.0.8, Q3.0.6, Editing
+@unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
+
+Yes, with @code{(setq modifier-keys-are-sticky t)}.  This will give the
+effect of being able to press and release Shift and have the next
+character typed come out in upper case.  This will affect all the other
+modifier keys like Control and Meta as well.
 
-@node Q3.8.5, Q3.9.1, Q3.8.4, Customization
-@unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
+@email{ben@@xemacs.org, Ben Wing} writes:
 
-Try something like:
+@quotation
+One thing about the sticky modifiers is that if you move the mouse out
+of the frame and back in, it cancels all currently ``stuck'' modifiers.
+@end quotation
+
+@node Q3.0.8, Q3.0.9, Q3.0.7, Editing
+@unnumberedsubsec Q3.0.8: How do I map the arrow keys?
+@c New
+Say you want to map @kbd{C-@key{right}} to forward-word:
+
+@email{sds@@usa.net, Sam Steingold} writes:
 
+@quotation
 @lisp
-(defun my-toggle-toolbar ()
-  (interactive)
-  (set-specifier default-toolbar-visible-p
-                 (not (specifier-instance default-toolbar-visible-p))))
-(global-set-key "\C-xT" 'my-toggle-toolbar)
+; both XEmacs and Emacs
+(define-key global-map [(control right)] 'forward-word)
 @end lisp
+or
+@lisp
+; Emacs only
+(define-key global-map [C-right] 'forward-word)
+@end lisp
+or
+@lisp
+; ver > 20, both
+(define-key global-map (kbd "C-<right>") 'forward-word)
+@end lisp
+@end quotation
 
-There are redisplay bugs in 19.14 that may make the preceding result in
-a messed-up display, especially for frames with multiple windows.  You
-may need to resize the frame before XEmacs completely realizes the
-toolbar is really gone.
-
-Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
-code.
+@node Q3.0.9, Q3.0.10, Q3.0.8, Editing
+@unnumberedsubsec Q3.0.9: HP Alt key as Meta.
 
-@node Q3.9.1, Q3.9.2, Q3.8.5, Customization
-@unnumberedsec 3.9: Scrollbars
-@unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
+How can I make XEmacs recognize the Alt key of my HP workstation as a
+Meta key?
 
-To disable them for all frames, add the following line to
-your @file{.Xdefaults}:
+Put the following line into a file and load it with xmodmap(1) before
+starting XEmacs:
 
 @example
-Emacs.scrollBarWidth:  0
+remove Mod1 = Mode_switch
 @end example
 
-Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
-Remember to save options.
+@node Q3.0.10, Q3.0.11, Q3.0.9, Editing
+@unnumberedsubsec Q3.0.10: Why does edt emulation not work?
 
-To turn the scrollbar off on a per-frame basis, use the following
-function:
+We don't know, but you can use tpu-edt emulation instead, which works
+fine and is a little fancier than the standard edt emulation.  To do
+this, add the following line to your @file{init.el}:
 
 @lisp
-(set-specifier scrollbar-width 0 (selected-frame))
+(tpu-edt)
 @end lisp
 
-You can actually turn the scrollbars on at any level you want by
-substituting for (selected-frame) in the above command.  For example, to
-turn the scrollbars off only in a single buffer:
+If you don't want it to replace @kbd{C-h} with an edt-style help menu
+add this as well:
 
 @lisp
-(set-specifier scrollbar-width 0 (current-buffer))
+(global-set-key [(control h)] 'help-for-help)
 @end lisp
 
-In XEmacs versions prior to 19.14, you had to use the hairier construct:
+@node Q3.0.11, Q3.1.1, Q3.0.10, Editing
+@unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
+
+Our recommended VI emulator is viper. To make viper-mode the default,
+add this to your @file{init.el}:
 
 @lisp
-(set-specifier scrollbar-width (cons (selected-frame) 0))
+(viper-mode)
 @end lisp
 
-@node Q3.9.2, Q3.9.3, Q3.9.1, Customization
-@unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
-
-Here's a recap of how to use resources to change your scrollbar colors:
+@email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
 
-@example
-! Motif scrollbars
+@quotation
+This should be added as close to the top of @file{init.el} as you can get
+it, otherwise some minor modes may not get viper-ized.
+@end quotation
 
-Emacs*XmScrollBar.Background: skyblue
-Emacs*XmScrollBar.troughColor: lightgray
+@unnumberedsec 3.1: The Mouse
 
-! Athena scrollbars
+@node Q3.1.1, Q3.1.2, Q3.0.11, Editing
+@unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
 
-Emacs*Scrollbar.Foreground: skyblue
-Emacs*Scrollbar.Background: lightgray
-@end example
+I keep hitting the middle mouse button by accident and getting stuff
+pasted into my buffer so how can I turn this off?
 
-Note the capitalization of @code{Scrollbar} for the Athena widget.
+Here is an alternative binding, whereby the middle mouse button selects
+(but does not cut) the expression under the mouse. Clicking middle on a
+left or right paren will select to the matching one.  Note that you can
+use @code{define-key} or @code{global-set-key}.
 
-@node Q3.9.3, Q3.9.4, Q3.9.2, Customization
-@unnumberedsubsec Q3.9.3: Moving the scrollbar can move the point; can I disable this?
+@lisp
+(defun mouse-set-point-and-select (event)
+  "Sets the point at the mouse location, then marks following form"
+  (interactive "@@e")
+  (mouse-set-point event)
+  (mark-sexp 1))
+(define-key global-map [button2] 'mouse-set-point-and-select)
+@end lisp
 
-When I move the scrollbar in an XEmacs window, it moves the point as
-well, which should not be the default behavior.  Is this a bug or a
-feature?  Can I disable it?
+@node Q3.1.2, Q3.1.3, Q3.1.1, Editing
+@unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
 
-The current behavior is a feature, not a bug.  Point remains at the same
-buffer position as long as that position does not scroll off the screen.
-In that event, point will end up in either the upper-left or lower-left
-hand corner.
+Use, for instance, @code{[(meta button1)]}. For example, here is a common
+setting for Common Lisp programmers who use the bundled @code{ilisp}
+package, whereby meta-button1 on a function name will find the file where
+the function name was defined, and put you at that location in the source
+file.
 
-This cannot be changed.
+[Inside a function that gets called by the lisp-mode-hook and
+ilisp-mode-hook]
 
-@node Q3.9.4, Q3.10.1, Q3.9.3, Customization
-@unnumberedsubsec Q3.9.4: How can I get automatic horizontal scrolling?
+@lisp
+(local-set-key [(meta button1)] 'edit-definitions-lisp)
+@end lisp
 
-By the same token, how can I turn it off in specific modes?
+@node Q3.1.3, Q3.1.4, Q3.1.2, Editing
+@unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
 
-To do this, add to your @file{.emacs} file:
+I do @kbd{C-x C-b} to get a list of buffers and the entries get
+highlighted when I move the mouse over them but clicking the left mouse
+does not do anything.
 
-@lisp
-(require 'auto-show)
-@end lisp
+Use the middle mouse button.
 
-Then do @code{(setq truncate-lines t)} in the mode-hooks for any modes
-in which you want lines truncated.
+@node Q3.1.4, Q3.1.5, Q3.1.3, Editing
+@unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
 
-More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
-will never appear.  Otherwise, they will appear only if the value of
-@code{scrollbar-height} for that buffer/window/etc. is non-zero.  If you
-do
+The following code will replace the default popup on button3:
 
 @lisp
-(set-specifier scrollbar-height 0)
+(global-set-key [button3] 'popup-buffer-menu)
 @end lisp
 
-then horizontal scrollbars will not appear in truncated buffers unless
-the package specifically asked for them.
+@node Q3.1.5, Q3.2.1, Q3.1.4, Editing
+@unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
 
-Automatic horizontal scrolling is now standard, starting with 19.14.
+By default XEmacs pastes X selections where the mouse pointer is.  How
+do I disable this?
 
-@node Q3.10.1, Q3.10.2, Q3.9.4, Customization
-@unnumberedsec 3.10: Text Selections
-@unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
+Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
+@key{RET}}.
 
-The @code{zmacs} mode allows for what some might call gratuitous
-highlighting for selected regions (either by setting mark or by using
-the mouse).  This is the default behavior.  To turn off, add the
-following line to your @file{.emacs} file:
+To get XEmacs to paste at the text cursor, add this your @file{init.el}:
 
 @lisp
-(setq zmacs-regions nil)
+(setq mouse-yank-at-point t)
 @end lisp
 
-Starting with XEmacs-20.2 you can also change this with Customize. Select
-from the @code{Options} menu @code{Customize->Emacs->Editing->Basics->Zmacs
-Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
-
-To change the face for selection, look at @code{Options->Customize} on
-the menubar.
+You can also change this with Customize.  Select from the
+@code{Options} menu @code{Advanced
+(Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
+customize @key{RET} mouse @key{RET}}.
 
-@node Q3.10.2, Q3.10.3, Q3.10.1, Customization
-@unnumberedsubsec Q3.10.2: How do I get that typing on an active region removes it?
+@unnumberedsec 3.2: Buffers, Text Editing
 
-I want to change things so that if I select some text and start typing,
-the typed text replaces the selected text, similar to Motif.
+@node Q3.2.1, Q3.2.2, Q3.1.5, Editing
+@unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
 
-You want to use something called @dfn{pending delete}.  Pending delete
-is what happens when you select a region (with the mouse or keyboard)
-and you press a key to replace the selected region by the key you typed.
-Usually backspace kills the selected region.
+Say, with: @samp{[END]}?
 
-To get this behavior, add the following line to your @file{.emacs}:
+Try this:
 
 @lisp
-(turn-on-pending-delete)
+(let ((ext (make-extent (point-min) (point-max))))
+  (set-extent-property ext 'start-closed t)
+  (set-extent-property ext 'end-closed t)
+  (set-extent-property ext 'detachable nil)
+  (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
 @end lisp
 
-Note that this will work with both Backspace and Delete.
-
-@node Q3.10.3, Q3.10.4, Q3.10.2, Customization
-@unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
+Since this is XEmacs, you can specify an icon to be shown on
+window-system devices.  To do so, change the @code{make-glyph} call to
+something like this:
 
-I do not like my text highlighted while I am doing isearch as I am not
-able to see what's underneath.  How do I turn it off?
+@lisp
+(make-glyph '([xpm :file "~/something.xpm"]
+              [string :data "[END]"]))
+@end lisp
 
-Put the following in your @file{.emacs}:
+You can inline the @sc{xpm} definition yourself by specifying
+@code{:data} instead of @code{:file}.  Here is such a full-featured
+version that works on both X and TTY devices:
 
 @lisp
-(setq isearch-highlight nil)
+(let ((ext (make-extent (point-min) (point-max))))
+  (set-extent-property ext 'start-closed t)
+  (set-extent-property ext 'end-closed t)
+  (set-extent-property ext 'detachable nil)
+  (set-extent-end-glyph ext (make-glyph '([xpm :data "\
+/* XPM */
+static char* eye = @{
+\"20 11 7 2\",
+\"__ c None\"
+\"_` c #7f7f7f\",
+\"_a c #fefefe\",
+\"_b c #7f0000\",
+\"_c c #fefe00\",
+\"_d c #fe0000\",
+\"_e c #bfbfbf\",
+\"___________`_`_`___b_b_b_b_________`____\",
+\"_________`_`_`___b_c_c_c_b_b____________\",
+\"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
+\"___`_`_e_a___b_b_d___b___b___b___b______\",
+\"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
+\"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
+\"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
+\"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
+\"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
+\"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
+\"___`_____`_`_`_`___b_b_b_b_b_b__________\",
+@} ;"]
+                                          [string :data "[END]"]))))
 @end lisp
 
-Starting with XEmacs-20.2 you can also change this with Customize. Type
-@kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
-
-Note also that isearch-highlight affects query-replace and ispell.
-Instead of disabling isearch-highlight you may find that a better
-solution consists of customizing the @code{isearch} face.
+Note that you might want to make this a function, and put it to a hook.
+We leave that as an exercise for the reader.
 
-@node Q3.10.4, Q3.10.5, Q3.10.3, Customization
-@unnumberedsubsec Q3.10.4: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
+@node Q3.2.2, Q3.2.3, Q3.2.1, Editing
+@unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
 
-Put this in your @code{.emacs}:
+Like this:
 
 @lisp
-(setq zmacs-regions nil)
+(insert (current-time-string))
 @end lisp
 
-@strong{Warning: This command turns off all region highlighting.}
+@node Q3.2.3, Q3.2.4, Q3.2.2, Editing
+@unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
+
+@email{acs@@acm.org, Vin Shelton} writes:
 
-Also @xref{Q3.10.1}.
+@lisp
+(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)
+@end lisp
 
-@node Q3.10.5,  , Q3.10.4, Customization
-@unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
+@strong{Please note:} 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.
 
-This has been fixed by default starting with XEmacs-20.3.
+@node Q3.2.4, Q3.2.5, Q3.2.3, Editing
+@unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
 
-With older versions you can turn this feature (if it indeed is a feature)
-off like this:
+Put the following line in your @file{init.el}:
 
 @lisp
-(defadvice scroll-up (around scroll-up freeze)
-  (interactive "_P")
-  (let ((zmacs-region-stays t))
-    (if (interactive-p)
-	(condition-case nil
-	    ad-do-it
-	  (end-of-buffer (goto-char (point-max))))
-      ad-do-it)))
-
-(defadvice scroll-down (around scroll-down freeze)
-  (interactive "_P")
-  (let ((zmacs-region-stays t))
-    (if (interactive-p)
-	(condition-case nil
-	    ad-do-it
-	  (beginning-of-buffer (goto-char (point-min))))
-      ad-do-it)))
+(setq indent-line-function 'indent-relative-maybe)
 @end lisp
 
-Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
-answer.
+If you want to get fancy, try the @code{filladapt} package available
+standard with XEmacs.  Put this into your @file{init.el}:
 
-@node Subsystems, Miscellaneous, Customization, Top
-@unnumbered 4 Major Subsystems
+@lisp
+(require 'filladapt)
+(setq-default filladapt-mode t)
+(add-hook 'c-mode-hook 'turn-off-filladapt-mode)
+@end lisp
 
-This is part 4 of the XEmacs Frequently Asked Questions list.  This
-section is devoted to major XEmacs subsystems.
-
-@menu
-Reading Mail with VM:
-* Q4.0.1::      How do I set up VM to retrieve remote mail using POP?
-* Q4.0.2::      How do I get VM to filter mail for me?
-* Q4.0.3::      How can I get VM to automatically check for new mail?
-* Q4.0.4::      [This question intentionally left blank]
-* Q4.0.5::      How do I get my outgoing mail archived?
-* Q4.0.6::      I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
-* Q4.0.7::      Is there a mailing list or FAQ for VM?
-* Q4.0.8::      Remote mail reading with VM.
-* Q4.0.9::      rmail or VM gets an error incorporating new mail.
-* Q4.0.10::     How do I make VM stay in a single frame?
-* Q4.0.11::     How do I make VM or mh-e display graphical smilies?
-* Q4.0.12::     Customization of VM not covered in the manual or here.
-
-Web browsing with W3:
-* Q4.1.1::      What is W3?
-* Q4.1.2::      How do I run W3 from behind a firewall?
-* Q4.1.3::      Is it true that W3 supports style sheets and tables?
-
-Reading Netnews and Mail with Gnus:
-* Q4.2.1::      GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,argh!
-* Q4.2.2::      [This question intentionally left blank]
-* Q4.2.3::      How do I make Gnus stay within a single frame?
-* Q4.2.4::      How do I customize the From: line?
-
-Other Mail & News:
-* Q4.3.1::      How can I read and/or compose MIME messages?
-* Q4.3.2::      What is TM and where do I get it?
-* Q4.3.3::      Why isn't this @code{movemail} program working?
-* Q4.3.4::      Movemail is also distributed by Netscape?  Can that cause problems?
-* Q4.3.5::      Where do I find pstogif (required by tm)?
-
-Sparcworks, EOS, and WorkShop:
-* Q4.4.1::      What is SPARCworks, EOS, and WorkShop
-* Q4.4.2::      How do I start the Sun Workshop support in XEmacs 21?
-
-Energize:
-* Q4.5.1::      What is/was Energize?
-
-Infodock:
-* Q4.6.1::      What is Infodock?
-
-Other Unbundled Packages:
-* Q4.7.1::      What is AUC TeX?  Where do you get it?
-* Q4.7.2::      Are there any Emacs Lisp Spreadsheets?
-* Q4.7.3::      Byte compiling AUC TeX on XEmacs 19.14
-* Q4.7.4::      Problems installing AUC TeX
-* Q4.7.5::      Is there a reason for an Emacs package not to be included in XEmacs?
-* Q4.7.6::      Is there a MatLab mode?
-@end menu
-
-@node Q4.0.1, Q4.0.2, Subsystems, Subsystems
-@unnumberedsec 4.0: Reading Mail with VM
-@unnumberedsubsec Q4.0.1: How do I set up VM to retrieve mail from a remote site using POP?
-
-Use @code{vm-spool-files}, like this for example:
+This will enable Filladapt for all modes except C mode, where it doesn't
+work well.  To turn Filladapt on only in particular major modes, remove
+the @code{(setq-default ...)} line and use
+@code{turn-on-filladapt-mode}, like this:
 
 @lisp
-(setq vm-spool-files '("/var/spool/mail/wing"
-                       "netcom23.netcom.com:110:pass:wing:MYPASS"))
+(add-hook 'text-mode-hook 'turn-on-filladapt-mode)
 @end lisp
 
-Of course substitute your actual password for MYPASS.
+You can customize filling and adaptive filling with Customize.
+Select from the @code{Options} menu
+@code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
+or type @kbd{M-x customize @key{RET} fill @key{RET}}.
 
-@node Q4.0.2, Q4.0.3, Q4.0.1, Subsystems
-@unnumberedsubsec Q4.0.2: How do I get VM to filter mail for me?
+Note that well-behaving text-lookalike modes will run
+@code{text-mode-hook} by default (e.g. that's what Message does).  For
+the nasty ones, you'll have to provide the @code{add-hook}s yourself.
 
-One possibility is to use procmail to split your mail before it gets to
-VM.  I prefer this personally, since there are many strange and
-wonderful things one can do with procmail.  Procmail may be found at
-@uref{ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/}.
+Please note that the @code{fa-extras} package is no longer useful.
 
-Also see the Mail Filtering FAQ at:
-@iftex
-@*
-@end iftex
-@uref{ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq}.
-@c Link above,
-@c <URL:http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html>
-@c was dead.
+@node Q3.2.5, Q3.3.1, Q3.2.4, Editing
+@unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
 
-@node Q4.0.3, Q4.0.4, Q4.0.2, Subsystems
-@unnumberedsubsec Q4.0.3: How can I get VM to automatically check for new mail?
+Try the following lisp in your @file{init.el}:
 
-@email{turner@@lanl.gov, John Turner} writes:
+@lisp
+(setq default-major-mode 'text-mode)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+@end lisp
 
-@quotation
-Use the following:
+@strong{WARNING}: note that changing the value of
+@code{default-major-mode} from @code{fundamental-mode} can break a large
+amount of built-in code that expects newly created buffers to be in
+@code{fundamental-mode}.  (Changing from @code{fundamental-mode} to
+@code{text-mode} might not wreak too much havoc, but changing to
+something more exotic like a lisp-mode would break many Emacs packages).
+
+Note that Emacs by default starts up in buffer @code{*scratch*} in
+@code{initial-major-mode}, which defaults to
+@code{lisp-interaction-mode}. Thus adding the following form to your
+Emacs init file will cause the initial @code{*scratch*} buffer to be put
+into auto-fill'ed @code{text-mode}:
 
 @lisp
-(setq vm-auto-get-new-mail 60)
+(setq initial-major-mode
+      (lambda ()
+        (text-mode)
+        (turn-on-auto-fill)))
 @end lisp
-@end quotation
 
-@node Q4.0.4, Q4.0.5, Q4.0.3, Subsystems
-@unnumberedsubsec Q4.0.4: [This question intentionally left blank]
+Note that after your init file is loaded, if
+@code{inhibit-startup-message} is @code{nil} (the default) and the
+startup buffer is @code{*scratch*} then the startup message will be
+inserted into @code{*scratch*}; it will be removed after a timeout by
+erasing the entire @code{*scratch*} buffer.  Keep in mind this default
+usage of @code{*scratch*} if you desire any prior manipulation of
+@code{*scratch*} from within your Emacs init file. In particular,
+anything you insert into @code{*scratch*} from your init file will be
+later erased. Also, if you change the mode of the @code{*scratch*}
+buffer, be sure that this will not interfere with possible later
+insertion of the startup message (e.g. if you put @code{*scratch*} into
+a nonstandard mode that has automatic font lock rules, then the startup
+message might get fontified in a strange foreign manner, e.g. as code in
+some programming language).
+
+@unnumberedsec 3.3: Text Selections
+
+@node Q3.3.1, Q3.3.2, Q3.2.5, Editing
+@unnumberedsubsec Q3.3.1: How do I select a rectangular region?
 
-Obsolete question, left blank to avoid renumbering.
+Just select the region normally, then use the rectangle commands (e.g.
+@code{kill-rectangle} on it.  The region does not highlight as a
+rectangle, but the commands work just fine.
+
+To actually sweep out rectangular regions with the mouse you can use
+@code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
+Then use rectangle commands.
 
-@node Q4.0.5, Q4.0.6, Q4.0.4, Subsystems
-@unnumberedsubsec Q4.0.5: How do I get my outgoing mail archived?
+You can also do the following to change default behavior to sweep out
+rectangular regions:
 
 @lisp
-(setq mail-archive-file-name "~/outbox")
+(setq mouse-track-rectangle-p t)
 @end lisp
 
-@node Q4.0.6, Q4.0.7, Q4.0.5, Subsystems
-@unnumberedsubsec Q4.0.6: I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
+You can also change this with Customize.
+Select from the @code{Options} menu
+@code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
+@kbd{M-x customize @key{RET} mouse @key{RET}}.
+
 
-Set @code{vm-reply-ignored-addresses} to a list, like
+@example
+ mouse-track-do-rectangle: (event)
+   -- an interactive compiled Lisp function.
+ Like `mouse-track' but selects rectangles instead of regions.
+@end example
+
+@node Q3.3.2, Q3.3.3, Q3.3.1, Editing
+@unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
+
+The @code{zmacs} mode allows for what some might call gratuitous
+highlighting for selected regions (either by setting mark or by using
+the mouse).  This is the default behavior.  To turn off, add the
+following line to your @file{init.el} file:
 
 @lisp
-(setq vm-reply-ignored-addresses
-      '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
-	"wing@@netcom.com" "wing@@xemacs.org"))
+(setq zmacs-regions nil)
 @end lisp
 
-Note that each string is a regular expression.
+You can also change this with Customize.  Select from the
+@code{Options} menu
+@code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
+or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
 
-@node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
-@unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
+To change the face for selection, look at @code{Options->Advanced (Customize)}
+on the menubar.
 
-A FAQ for VM exists at @uref{http://www.cyberpass.net/~gorkab/vmfaq.htm}.
+@node Q3.3.3, Q3.3.4, Q3.3.2, Editing
+@unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
 
-VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
+I want to change things so that if I select some text and start typing,
+the typed text replaces the selected text, similar to Motif.
 
-@node Q4.0.8, Q4.0.9, Q4.0.7,  Subsystems
-@unnumberedsubsec Q4.0.8: Remote mail reading with VM.
+You want to use something called @dfn{pending delete}.  Pending delete
+is what happens when you select a region (with the mouse or keyboard)
+and you press a key to replace the selected region by the key you typed.
+Usually backspace kills the selected region.
 
-My mailbox lives at the office on a big honkin server.  My regular INBOX
-lives on my honkin desktop machine.  I now can PPP to the office from
-home which is far from honking...  I'd like to be able to read mail at
-home without storing it here and I'd like to use xemacs and VM at
-home...  Is there a recommended setup?
+To get this behavior, ensure that you have the @file{pc} package
+installed, and add the following lines to your
+@file{init.el}:
 
-@email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
+@lisp
+(cond
+ ((fboundp 'turn-on-pending-delete)
+  (turn-on-pending-delete))
+ ((fboundp 'pending-delete-on)
+  (pending-delete-on t)))
+@end lisp
 
-@quotation
-There are several ways to do this.
+Note that this will work with both Backspace and Delete.  This code is a
+tad more complicated than it has to be for XEmacs in order to make it
+more portable.
 
-@enumerate
-@item
-Set your display to your home machine and run dxpc or one of the other X
-compressors.
+@node Q3.3.4, Q3.3.5, Q3.3.3, Editing
+@unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
 
-@item
-NFS mount your desktop machine on your home machine and modify your pop
-command on your home machine to rsh to your desktop machine and actually
-do the pop get's.
+I do not like my text highlighted while I am doing isearch as I am not
+able to see what's underneath.  How do I turn it off?
 
-@item
-Run a POP server on your desktop machine as well and do a sort of two
-tiered POP get.
-@end enumerate
-@end quotation
+Put the following in your @file{init.el}:
+
+@lisp
+(setq isearch-highlight nil)
+@end lisp
 
-        @email{wmperry@@monolith.spry.com, William Perry} adds:
+You can also change this with Customize. Type
+@kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
 
-@quotation
-Or you could run a pop script periodically on your desktop machine, and
-just use ange-ftp or NFS to get to your mailbox.  I used to do this all
-the time back at IU.
-@end quotation
+Note also that isearch-highlight affects query-replace and ispell.
+Instead of disabling isearch-highlight you may find that a better
+solution consists of customizing the @code{isearch} face.
 
-@node Q4.0.9, Q4.0.10, Q4.0.8, Subsystems
-@unnumberedsubsec Q4.0.9: rmail or VM gets an error incorporating new mail.
+@node Q3.3.5, Q3.3.6, Q3.3.4, Editing
+@unnumberedsubsec Q3.3.5: Why is killing so slow?
 
-Quoting the XEmacs PROBLEMS file:
+This actually is an X Windows question, although you'll notice it with
+keyboard operations as well as while using the GUI.  Basically, there
+are four ways to communicate interprogram via the X server:
 
-@quotation
-rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
-program called @code{movemail}.  This program interlocks with
-@code{/bin/mail} using the protocol defined by @code{/bin/mail}.
+@table @strong
+@item Primary selection
+a transient selection that gets replaced every time a new selection is made
 
-There are two different protocols in general use.  One of them uses the
-@code{flock} system call.  The other involves creating a lock file;
-@code{movemail} must be able to write in @file{/usr/spool/mail} in order
-to do this.  You control which one is used by defining, or not defining,
-the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
-it includes.
+@item Secondary selection
+for "exchanging" with the primary selection
 
-@strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
-SYSTEM, YOU CAN LOSE MAIL!}
+@item Cut buffers
+a clipboard internal to the X server (deprecated)
 
-If your system uses the lock file protocol, and fascist restrictions
-prevent ordinary users from writing the lock files in
-@file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
-suitable group such as @samp{mail}.  You can use these commands (as
-root):
+@item Clipboard selection
+a selection with a notification protocol that allows a separate app to
+manage the clipboard
+@end table
 
-@example
-chgrp mail movemail
-chmod 2755 movemail
-@end example
+The cut buffers are deprecated because managing them is even more
+inefficient than the clipboard notification protocol.  The primary
+selection works fine for many users and applications, but is not very
+robust under intensive or sophisticated use.
+
+In Motif and MS Windows, a clipboard has become the primary means for
+managing cut and paste.  These means that "modern" applications tend to
+be oriented toward a true clipboard, rather than the primary selection.
+(On Windows, there is nothing equivalent to the primary selection.)
+It's not that XEmacs doesn't support the simple primary selection
+method, it's that more and more other applications don't.
+
+So the slowdown occurs because XEmacs now engages in the clipboard
+notification protocol on @emph{every} kill.  This is especially slow on
+Motif.
+
+With most people running most clients and server on the same host, and
+many of the rest working over very fast communication, you may expect
+that the situation is not going to improve.
+
+There are a number of workarounds.  The most effective is to use a
+special command to do selection ownership only when you intend to paste
+to another application.  Useful commands are @code{kill-primary-selection}
+and @code{copy-primary-selection}.  These work only on text selected
+with the mouse (probably; experiment), and are bound by default to the
+@kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
+@code{copy-primary-selection} is also bound to @kbd{C-Insert}.  You can
+yank the clipboard contents with @code{yank-primary-selection}, bound to
+the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
+
+If you are communicating by cut and paste with applications that use the
+primary selection, then you can customize
+@code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
+version 20 behavior.  How can you tell if a program will support this?
+Motifly-correct programs require the clipboard; you lose.  For others,
+only by trying it.  You also need to customize the complementary
+@code{interprogram-paste-function} to @code{nil}.  (Otherwise
+XEmacs-to-XEmacs pastes will not work correctly.)
+
+You may get some relief on Motif by setting
+@code{x-selection-strict-motif-ownership} to nil, but this means you will
+only intermittently be able to paste XEmacs kills to Motif applications.
+
+Thanks to Jeff Mincy and Glynn Clements for corrections.
+
+@node Q3.3.6, Q3.4.1, Q3.3.5, Editing
+@unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
 
-If your system uses the lock file protocol, and fascist restrictions
-prevent ordinary users from writing the lock files in
-@file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
-suitable group such as @code{mail}.  To do this, use the following
-commands (as root) after doing the make install.
+It actually doesn't.  It leaves the region visible for a second so that
+you can see what area is being yanked.  If you start working, though, it
+will immediately complete its operation.  In other words, it will only
+delay for a second if you let it.
 
-@example
-chgrp mail movemail
-chmod 2755 movemail
-@end example
+@unnumberedsec 3.4: Editing Source Code
 
-Installation normally copies movemail from the build directory to an
-installation directory which is usually under @file{/usr/local/lib}.
-The installed copy of @code{movemail} is usually in the directory
-@file{/usr/local/lib/emacs/VERSION/TARGET}.  You must change the group
-and mode of the installed copy; changing the group and mode of the build
-directory copy is ineffective.
-@end quotation
+@node Q3.4.1, Q3.4.2, Q3.3.6, Editing
+@unnumberedsubsec Q3.4.1: I do not like cc-mode.  How do I use the old c-mode?
 
-@node Q4.0.10, Q4.0.11, Q4.0.9, Subsystems
-@unnumberedsubsec Q4.0.10: How do I make VM stay in a single frame?
+Well, first off, consider if you really want to do this.  cc-mode is
+much more powerful than the old c-mode.  If you're having trouble
+getting your old offsets to work, try using @code{c-set-offset} instead.
+You might also consider using the package @code{cc-compat}.
 
-John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
+But, if you still insist, add the following lines to your @file{init.el}:
 
-@quotation
 @lisp
-					; Don't use multiple frames
-(setq vm-frame-per-composition nil)
-(setq vm-frame-per-folder nil)
-(setq vm-frame-per-edit nil)
-(setq vm-frame-per-summary nil)
+(fmakunbound 'c-mode)
+(makunbound 'c-mode-map)
+(fmakunbound 'c++-mode)
+(makunbound 'c++-mode-map)
+(makunbound 'c-style-alist)
+(load-library "old-c-mode")
+(load-library "old-c++-mode")
 @end lisp
-@end quotation
 
-@node Q4.0.11, Q4.0.12, Q4.0.10, Subsystems
-@unnumberedsubsec Q4.0.11: How do I make VM or mh-e display graphical smilies?
-@c Changed June
-For mh-e use the following:
+This must be done before any other reference is made to either c-mode or
+c++-mode.
 
-@lisp
-(add-hook 'mh-show-mode-hook '(lambda ()
-				(smiley-region (point-min)
-                                               (point-max))))
-@end lisp
+@node Q3.4.2,  , Q3.4.1, Editing
+@unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
 
-@email{bill@@carpenter.ORG, WJCarpenter} writes:
-For VM use the following:
-@lisp
-       (autoload 'smiley-region "smiley" nil t)
-       (add-hook 'vm-select-message-hook
-                 '(lambda ()
-                    (smiley-region (point-min)
-                                   (point-max))))
-@end lisp
+I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
+same amount instead of indenting the 3rd clause differently from the
+first two.
+
+The package @code{cl-indent} that comes with XEmacs sets up this kind
+of indentation by default.  @code{cl-indent} also knows about many
+other CL-specific forms.  To use @code{cl-indent}, one can do this:
 
-For tm use the following:
 @lisp
-(autoload 'smiley-buffer "smiley" nil t)
-(add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
+(setq lisp-indent-function 'common-lisp-indent-function)
 @end lisp
 
-@node Q4.0.12, Q4.1.1, Q4.0.11, Subsystems
-@unnumberedsubsec Q4.0.12: Customization of VM not covered in the manual, or here.
-
-@email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
+One can also customize @file{cl-indent.el} so it mimics the default
+@code{if} indentation @code{then} indented more than the @code{else}.
+Here's how:
 
-@quotation
-The meta-answer is to look into the file @file{vm-vars.el}, in the vm
-directory of the lisp library.
+@lisp
+(put 'if 'common-lisp-indent-function '(nil nil &body))
+@end lisp
 
-@file{vm-vars.el} contains, initializes and carefully describes, with
-examples of usage, the plethora of user options that @emph{fully}
-control VM's behavior.
+@node Display, External Subsystems, Editing, Top
+@unnumbered 4 Display Functions
 
-Enter vm-vars, @code{forward-search} for toolbar, find the variables
-that control the toolbar placement, appearance, existence, copy to your
-@file{.emacs} or @file{.vm} and modify according to the detailed
-instructions.
+This is part 4 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to the display-related capabilities of XEmacs
+(fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
+to customize them.
 
-The above also applies to all the various features of VM: search for
-some keywords, maybe the first you conjure isn't appropriate, find the
-appropriate variables, copy and experiment.
-@end quotation
+@menu
+4.0: Textual Fonts and Colors
+* Q4.0.1::    How do I specify a font?
+* Q4.0.2::    How do I set the text, menu and modeline fonts?
+* Q4.0.3::    How can I set color options from @file{init.el}?
+* Q4.0.4::    How can I set the colors when highlighting a region?
+* Q4.0.5::    How can I limit color map usage?
+* Q4.0.6::    My tty supports color, but XEmacs doesn't use them.
+* Q4.0.7::    Can I have pixmap backgrounds in XEmacs?
+* Q4.0.8::    How do I display non-ASCII characters?
+* Q4.0.9::    Font selections in don't get saved after @code{Save Options}.
+
+4.1: Syntax Highlighting (Font Lock)
+* Q4.1.1::    How can I do source code highlighting using font-lock?
+* Q4.1.2::    How do I get @samp{More} Syntax Highlighting on by default?
+
+4.2: The Modeline
+* Q4.2.1::    How can I make the modeline go away?
+* Q4.2.2::    How do you have XEmacs display the line number in the modeline?
+* Q4.2.3::    How do I get XEmacs to put the time of day on the modeline?
+* Q4.2.4::    How can I change the modeline color based on the mode used?
+
+4.3: The Cursor
+* Q4.3.1::    Is there a way to make the bar cursor thicker?
+* Q4.3.2::    Is there a way to get back the block cursor?
+* Q4.3.3::    Can I make the cursor blink?
+
+4.4: The Menubar
+* Q4.4.1::    How do I get rid of the menubar?
+* Q4.4.2::    How can I customize the menubar?
+* Q4.4.3::    How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
+* Q4.4.4::    How do I control how many buffers are listed in the menu @code{Buffers List}?
+* Q4.4.5::    Resources like @code{Emacs*menubar*font} are not working?
+
+4.5: The Toolbar
+* Q4.5.1::    How do I get rid of the toolbar?
+* Q4.5.2::    How can I customize the toolbar?
+* Q4.5.3::    How can I bind a key to a function to toggle the toolbar?
+* Q4.5.4::    @samp{Can't instantiate image error...} in toolbar
+
+4.6: Scrollbars and Scrolling
+* Q4.6.1::    How can I disable the scrollbar?
+* Q4.6.2::    How can I change the scrollbar width?
+* Q4.6.3::    How can I use resources to change scrollbar colors?
+* Q4.6.4::    Moving the scrollbar can move the point; can I disable this?
+* Q4.6.5::    Scrolling one line at a time.
+* Q4.6.6::    How can I turn off automatic horizontal scrolling in specific modes?
+* Q4.6.7::    I find auto-show-mode disconcerting.  How do I turn it off?
+
+4.7: The Gutter Tabs, The Progress Bar, Widgets
+* Q4.7.1::    How can I disable the gutter tabs?
+* Q4.7.2::    How can I disable the progress bar?
+* Q4.7.3::    There are bugs in the gutter or widgets.
+* Q4.7.4::    How can I customize the gutter or gutter tabs?
+@end menu
 
-@node Q4.1.1, Q4.1.2, Q4.0.12, Subsystems
-@unnumberedsec 4.1: Web browsing with W3
-@unnumberedsubsec Q4.1.1: What is W3?
+@unnumberedsec 4.0: Textual Fonts and Colors
 
-W3 is an advanced graphical browser written in Emacs lisp that runs on
-XEmacs.  It has full support for cascaded style sheets, and more...
+@node Q4.0.1, Q4.0.2, Display, Display
+@unnumberedsubsec Q4.0.1: How do I specify a font?
 
-It has a home web page at
-@uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
+#### Update me.
 
-@node Q4.1.2, Q4.1.3, Q4.1.1, Subsystems
-@unnumberedsubsec Q4.1.2: How do I run W3 from behind a firewall?
+In 21.4 and above, you can use the @samp{Options} menu to change the font.
+You can also do it in your init file, e.g. like this (for MS Windows):
 
-There is a long, well-written, detailed section in the W3 manual that
-describes how to do this.  Look in the section entitled "Firewalls".
+@display
+    (set-face-font 'default "Lucida Console:Regular:10")
+    (set-face-font 'modeline "MS Sans Serif:Regular:10")
+@end display
 
-@node Q4.1.3, Q4.2.1, Q4.1.2, Subsystems
-@unnumberedsubsec Q4.1.3: Is it true that W3 supports style sheets and tables?
+@node Q4.0.2, Q4.0.3, Q4.0.1, Display
+@unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
 
-Yes, and much more.  W3, as distributed with the latest XEmacs is a
-full-featured web browser.
+#### Update me.
 
-@node Q4.2.1, Q4.2.2, Q4.1.3, Subsystems
-@unnumberedsec 4.2: Reading Netnews and Mail with Gnus
-@unnumberedsubsec Q4.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
+Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
+setting face values.
 
-The Gnus numbering issues are not meant for mere mortals to know them.
-If you feel you @emph{must} enter the muddy waters of Gnus, visit the
-excellent FAQ, maintained by Justin Sheehy, at:
+In @file{.Xresources}:
 
 @example
-@uref{http://www.ccs.neu.edu/software/contrib/gnus/}
+Emacs.default.attributeFont:  -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
+Emacs*menubar*font:           fixed
+Emacs.modeline.attributeFont: fixed
 @end example
 
-See also Gnus home page
-@example
-@uref{http://www.gnus.org/}
-@end example
+This is confusing because @samp{default} and @samp{modeline} are face
+names, and can be found listed with all faces in the current mode by
+using @kbd{M-x set-face-font (enter) ?}.  They use the face-specific
+resource @samp{attributeFont}.
 
-@node Q4.2.2, Q4.2.3, Q4.2.1, Subsystems
-@unnumberedsubsec Q4.2.2: This question intentionally left blank.
+On the other hand, @samp{menubar} is a normal X thing that uses the
+resource @samp{font}.  With Motif it @emph{may be} necessary to use
+@samp{fontList} @emph{instead of} @samp{font}.  In @emph{non-Motif}
+configurations with Mule it @emph{is} necessary to use @samp{fontSet}
+instead of @samp{font}.  (Sorry, there just is no simple recipe here.)
 
-Obsolete question, left blank to avoid renumbering.
+@node Q4.0.3, Q4.0.4, Q4.0.2, Display
+@unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
 
-@node Q4.2.3, Q4.2.4, Q4.2.2, Subsystems
-@unnumberedsubsec Q4.2.3: How do I make Gnus stay within a single frame?
+How can I set the most commonly used color options from my
+@file{init.el} instead of from my @file{.Xresources}?
 
-The toolbar code to start Gnus opens the new frame---and it's a feature
-rather than a bug.  If you don't like it, but would still like to click
-on the seemly icon, use the following code:
+Like this:
 
 @lisp
-(defun toolbar-news ()
-  (gnus))
-@end lisp
-
-It will redefine the callback function of the icon to just call
-@code{gnus}, without all the fancy frame stuff.
+(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
+@end lisp
 
-@node Q4.2.4, Q4.3.1, Q4.2.3, Subsystems
-@unnumberedsubsec Q4.2.4: How do I customize the From: line?
+@node Q4.0.4, Q4.0.5, Q4.0.3, Display
+@unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
+
+How can I set the background/foreground colors when highlighting a
+region?
+
+You can change the face @code{zmacs-region} either in your
+@file{.Xresources}:
 
-How do I change the @code{From:} line?  I have set gnus-user-from-line
-to
-@example
-Gail Gurman <gail.gurman@@sybase.com>
-@end example
-@noindent , but XEmacs Gnus doesn't use
-it. Instead it uses
 @example
-Gail Mara Gurman @email{gailg@@deall}
+Emacs.zmacs-region.attributeForeground: firebrick
+Emacs.zmacs-region.attributeBackground: lightseagreen
 @end example
-@noindent and then complains
-that it's incorrect. Also, as you perhaps can see, my Message-ID is
-screwy. How can I change that?
 
-@email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
+or in your @file{init.el}:
 
-@quotation
-Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
-@code{mail-host-address} to @samp{sybase.com}.
-@end quotation
+@lisp
+(set-face-background 'zmacs-region "red")
+(set-face-foreground 'zmacs-region "yellow")
+@end lisp
 
-@node Q4.3.1, Q4.3.2, Q4.2.4, Subsystems
-@unnumberedsec 4.3: Other Mail & News
-@unnumberedsubsec Q4.3.1: How can I read and/or compose MIME messages?
-@c Changed June
+@node Q4.0.5, Q4.0.6, Q4.0.4, Display
+@unnumberedsubsec Q4.0.5: How can I limit color map usage?
 
-VM supports MIME natively.
+I'm using Netscape (or another color grabber like XEmacs);
+is there any way to limit the number of available colors in the color map?
 
-You probably want to use the Tools for MIME (tm).  @xref{Q4.3.2}, for
-details.
+Answer: No, but you can start Netscape before XEmacs, and it will use
+the closest available color if the colormap is full.  You can also limit
+the number of colors Netscape uses, using the flags -mono, -ncols <#> or
+-install (for mono, limiting to <#> colors, or for using a private color
+map).
 
-@email{trey@@cs.berkeley.edu, Trey Jackson} has an Emacs & MIME web page at
-@iftex
-@*
-@end iftex
-@uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}.
+If you have the money, another solution would be to use a truecolor or
+direct color video.
 
+@node Q4.0.6, Q4.0.7, Q4.0.5, Display
+@unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
 
-Another possibility is RMIME.  You may find RMIME at
-@iftex
-@*
-@end iftex
-@uref{http://www.cinti.net/~rmoody/rmime/index.html}.
+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:
 
+@lisp
+(if (eq 'tty (device-type))
+    (set-device-class nil 'color))
+@end lisp
 
-@node Q4.3.2, Q4.3.3, Q4.3.1, Subsystems
-@unnumberedsubsec Q4.3.2: What is TM and where do I get it?
+@node Q4.0.7, Q4.0.8, Q4.0.6, Display
+@unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
+@c New
+@email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
 
-TM stands for @dfn{Tools for MIME} and not Tiny MIME.  TM integrates
-with all major XEmacs packages like Gnus (all flavors), VM, MH-E, and
-mailcrypt.  It provides totally transparent and trouble-free MIME
-support.  When appropriate a message will be decoded in place in an
-XEmacs buffer.
+@quotation
+There are several ways to do it.  For example, you could specify a
+default pixmap image to use in your @file{~/.Xresources}, e.g.,
 
-TM now comes as a package with XEmacs 19.16 and XEmacs 20.2.
 
-TM was written by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} and
-@email{shuhei-k@@jaist.ac.jp, KOBAYASHI
-Shuhei}.
+@example
+  Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
+@end example
 
-It is based on the work of @email{umerin@@mse.kyutech.ac.jp, UMEDA
-Masanobu}, the original writer of GNUS.
 
-The following information is from the @file{README}:
+and then reload ~/.Xresources and restart XEmacs.  Alternatively,
+since each face can have its own pixmap background, a better way
+would be to set a face's pixmap within your XEmacs init file, e.g.,
 
-@dfn{tm} is a MIME package for GNU Emacs.
-tm has following functions:
+@lisp
+  (set-face-background-pixmap 'default "/path/to/image.xpm")
+  (set-face-background-pixmap 'bold    "/path/to/another_image.xpm")
+@end lisp
 
-@itemize @bullet
-@item MIME style multilingual header.
-@item MIME message viewer (mime/viewer-mode).
-@item MIME message composer (mime/editor-mode).
-@item MIME extenders for mh-e, GNUS, RMAIL and VM.
-@end itemize
+and so on.  You can also do this interactively via @kbd{M-x edit-faces}.
 
-tm is available from following anonymous ftp sites:
-@itemize @bullet
-@comment @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
-@comment @item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
-@comment @c The host above is unknown.
-@comment @item @uref{ftp://ftp.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
-@comment @item @uref{ftp://ftp.miranova.com/pub/gnus/jaist.ac.jp/} (US).
-@item @uref{ftp://ftp.unicamp.br/pub/mail/mime/tm/} (Brasil).
-@item @uref{ftp://ftp.th-darmstadt.de/pub/editors/GNU-Emacs/lisp/mime/} (Germany).
-@item @uref{ftp://ftp.tnt.uni-hannover.de/pub/editors/xemacs/contrib/} (Germany).
-@end itemize
+@end quotation
 
-Don't let the installation procedure & instructions stop you from trying
-this package out---it's much simpler than it looks, and once installed,
-trivial to use.
+@node Q4.0.8, Q4.0.9, Q4.0.7, Display
+@unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
+@c New
 
-@node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
-@unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
+If you're using a Mule-enabled XEmacs, then display is automatic.  If
+you're not seeing the characters you expect, either (1) you don't have
+appropriate fonts available or (2) XEmacs did not correctly detect the
+coding system (@pxref{Recognize Coding, , , xemacs}).  In case (1),
+install fonts as is customary for your platform.  In case (2), you
+need to tell XEmacs explicitly what coding systems you're using.
+@ref{Specify Coding, , , xemacs}.
 
-Ben Wing @email{ben@@xemacs.org} writes:
+If your XEmacs is not Mule-enabled, and for some reason getting a
+Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
+You can arrange it by brute force.  In @file{event-Xt.c} (suppress the
+urge to look in this file---play Doom instead, because you'll survive
+longer), it is written:
 
 @quotation
-It wasn't chown'ed/chmod'd correctly.
+In a non-Mule world, a user can still have a multi-lingual editor, by
+doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
+their Latin-2 buffers, etc.
 @end quotation
 
-@node Q4.3.4, Q4.3.5, Q4.3.3, Subsystems
-@unnumberedsubsec Q4.3.4: Movemail is also distributed by Netscape?  Can that cause problems?
+For the related problem of @emph{inputting} non-ASCII characters in a
+non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
+in XEmacs?}.
 
-@email{steve@@xemacs.org, Steve Baur} writes:
+@node Q4.0.9, Q4.1.1, Q4.0.8, Display
+@unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
+
+@email{mannj@@ll.mit.edu, John Mann} writes:
 
 @quotation
-Yes.  Always use the movemail installed with your XEmacs.  Failure to do
-so can result in lost mail.
+You have to go to @samp{Options->Menubars} and unselect
+@samp{Frame-Local Font Menu}.  If this option is selected, font changes
+are only applied to the @emph{current} frame and do @emph{not} get saved
+when you save options.
 @end quotation
 
-Please refer to @email{jwz@@jwz.org, Jamie Zawinski's} notes at
-@iftex
-@*
-@end iftex
-@uref{http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/movemail.html}.
-In particular, this document will show you how to make Netscape use the
-version of movemail configured for your system by the person who built
-XEmacs.
+Also, set the following in your @file{init.el}:
 
-@node Q4.3.5, Q4.4.1, Q4.3.4, Subsystems
-@unnumberedsubsec Q4.3.5: Where do I find pstogif (required by tm)?
+@lisp
+(setq options-save-faces t)
+@end lisp
 
-pstogif is part of the latex2html package.
+@unnumberedsec 4.1: Syntax Highlighting (Font Lock)
 
-@email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
+@node Q4.1.1, Q4.1.2, Q4.0.9, Display
+@unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
 
-latex2html is best found at the CTAN hosts and their mirrors
-in
-@iftex
-@*
-@end iftex
-@file{tex-archive/support/latex2html}.
+For most modes, font-lock is already set up and just needs to be turned
+on.  This can be done by adding the line:
 
-CTAN hosts are:
+@lisp
+(require 'font-lock)
+@end lisp
 
-@itemize @bullet
-@item @uref{ftp://ftp.tex.ac.uk/tex-archive/support/latex2html/}.
-@item @uref{ftp://ftp.dante.de/tex-archive/support/latex2html/}.
-@end itemize
+to your @file{init.el}. (You can turn it on for the
+current buffer and session only by @kbd{M-x font-lock-mode}.) See the
+file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
+versions prior to 21.4) for more information.
 
-There is a good mirror at ftp.cdrom.com;
-@iftex
-@*
-@end iftex
-@uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
+@c the old way:
+@c     (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
+@c     (add-hook 'dired-mode-hook      'turn-on-font-lock)
 
-@node Q4.4.1, Q4.4.2, Q4.3.5, Subsystems
-@unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
-@unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
+See also @code{Syntax Highlighting} from the @code{Options} menu.
+Remember to save options.
 
-@email{turner@@lanl.gov, John Turner} writes:
+@node Q4.1.2, Q4.2.1, Q4.1.1, Display
+@unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
 
-@quotation
-SPARCworks is SunSoft's development environment, comprising compilers
-(C, C++, FORTRAN 77, Fortran 90, Ada, and Pascal), a debugger, and other
-tools such as TeamWare (for configuration management), MakeTool, etc.
-@end quotation
+Use the following code in your @file{init.el}:
 
-See @uref{http://www.sun.com/software/Developer-products/}
-for more info.
+@lisp
+(setq-default font-lock-maximum-decoration t)
+@end lisp
 
-EOS stands for "Era on SPARCworks", but I don't know what Era stands
-for.
+See also @code{Syntax Highlighting} from the @code{Options} menu.
+Remember to save options.
 
-EOS is the integration of XEmacs with the SPARCworks debugger.  It
-allows one to use an XEmacs frame to view code (complete with
-fontification, etc.), set breakpoints, print variables, etc., while
-using the SPARCworks debugger.  It works very well and I use it all the
-time.
+@unnumberedsec 4.2: The Modeline
 
-@email{cthomp@@xemacs.org, Chuck Thompson} writes:
+@node Q4.2.1, Q4.2.2, Q4.1.2, Display
+@unnumberedsubsec Q4.2.1: How can I make the modeline go away?
 
-@quotation
-Era stood for "Emacs Rewritten Again".  It was what we were calling the
-modified version of Lucid Emacs for Sun when I was dragged, er, allowed
-to work on this wonderful editor.
-@end quotation
+@lisp
+(set-specifier has-modeline-p nil)
+@end lisp
 
-@email{martin@@xemacs.org, Martin Buchholz} writes:
+@node Q4.2.2, Q4.2.3, Q4.2.1, Display
+@unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
 
-@quotation
-EOS is being replaced with a new graphical development environment
-called Sun WorkShop, which is currently (07/96) in Alpha Test.  For more
-details, check out
-@iftex
-@*
-@end iftex
-@uref{http://www.sun.com/software/Products/Developer-products}.
-@end quotation
+Add the following line to your @file{init.el} file to
+display the line number:
 
-@node Q4.4.2, Q4.5.1, Q4.4.1, Subsystems
-@unnumberedsubsec Q4.4.2: How do I start the Sun Workshop support in XEmacs 21?
+@lisp
+(line-number-mode 1)
+@end lisp
 
-Add the switch ---with-workshop to the configure command when building
-XEmacs and put the following in one of your startup files
-(e.g. site-start.el or .emacs):
+Use the following to display the column number:
 
 @lisp
-(when (featurep 'tooltalk)
-  (load "tooltalk-macros")
-  (load "tooltalk-util")
-  (load "tooltalk-init"))
-(when (featurep 'sparcworks)
-  (load "sunpro-init")
-  (load "ring")
-  (load "comint")
-  (load "annotations")
-  (sunpro-startup))
+(column-number-mode 1)
 @end lisp
 
-If you are not using the latest Workshop (5.0) you have to apply the
-following patch:
+Or select from the @code{Options} menu
+@iftex
+@*
+@end iftex
+@code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
+and/or
+@iftex
+@*
+@end iftex
+@code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
 
-@format
---- /opt/SUNWspro/lib/eserve.el.ORIG    Fri May 14 15:23:26 1999
-+++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
-@@@@ -42,7 +42,7 @@@@
- (defvar running-xemacs nil "t if we're running XEmacs")
- (defvar running-emacs  nil "t if we're running GNU Emacs 19")
- 
--(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
-+(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
-     (setq running-xemacs t)
-     (setq running-emacs  t))
-@end format 
+Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
 
+@node Q4.2.3, Q4.2.4, Q4.2.2, Display
+@unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
 
+Add the following line to your @file{init.el} file to
+display the time:
 
-@node Q4.5.1, Q4.6.1, Q4.4.2, Subsystems
-@unnumberedsec 4.5: Energize
-@unnumberedsubsec Q4.5.1: What is/was Energize?
+@lisp
+(display-time)
+@end lisp
 
-@email{gray@@meteor.harlequin.com, David N Gray} writes:
-@quotation
-The files in @file{lisp/energize} are to enable Emacs to interface with
-the "Energize Programming System", a C and C++ development environment,
-which was a product of Lucid, Inc.  Tragically, Lucid went out of
-business in 1994, so although Energize is still a great system, if you
-don't already have it, there isn't any way to get it now.  (Unless you
-happen to be in Japan; INS Engineering may still be selling it there.
-Tartan bought the rights to sell it in the rest of the world, but never
-did so.)
-@end quotation
+See @code{Customize} from the @code{Options} menu for customization.
 
-@node Q4.6.1, Q4.7.1, Q4.5.1, Subsystems
-@unnumberedsec 4.6: Infodock
-@unnumberedsubsec Q4.6.1: What is Infodock?
+@node Q4.2.4, Q4.3.1, Q4.2.3, Display
+@unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
 
-InfoDock is an integrated productivity toolset, mainly aimed at
-technical people.  It is developed and supported by InfoDock
-Associates, a firm that offers custom support and development
-for InfoDock, XEmacs and GNU Emacs.  ( @uref{http://www.infodock.com},
-@email{info@@infodock.com}, +1 408 243 3300).
+You can use something like the following:
 
-InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
-the power of Emacs, but with an easier to use and more comprehensive
-menu-based user interface.  The bottom portion of this text describes
-how it differs from XEmacs and GNU Emacs from the Free Software
-Foundation.
+@lisp
+(add-hook 'lisp-mode-hook
+          (lambda ()
+            (set-face-background 'modeline "red" (current-buffer))))
+@end lisp
 
-InfoDock is aimed at people who want a free, turn-key productivity
-environment.  Although InfoDock is customizable, it is not intended for
-people who like basic versions of Emacs which need to be customized
-extensively for local use; standard Emacs distributions are better for
-such uses.  InfoDock is for those people who want a complete,
-pre-customized environment in one package, which they need not touch
-more than once or twice a year to update to new revisions.
+Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
+colors change from the default set in your @file{init.el}.
+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.
 
-InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
-and Intel Linux systems.  It is intended for use on a color display,
-although most features will work on monochrome monitors.  Simply unpack
-InfoDock according to the instructions in the ID-INSTALL file and you
-are ready to run.
+Notes:
 
-The InfoDock Manual is concise, yet sufficient as a user guide for users
-who have never used an Emacs-type editor before.  For users who are
-already familiar with Emacs, it supplements the information in the GNU
-Emacs Manual.
+@itemize @bullet
 
-InfoDock menus are much more extensive and more mature than standard
-Emacs menus.  Each menu offers a @samp{Manual} item which displays
-documentation associated with the menu's functions.
+@item The hook is the mode name plus @code{-hook}.  eg. c-mode-hook,
+c++-mode-hook, emacs-lisp-mode-hook (used for your
+@file{init.el} or a @file{xx.el} file),
+lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
+text-mode-hook, etc.
 
-@noindent
-Four types of menubars are provided:
-@enumerate
-@item
-An extensive menubar providing access to global InfoDock commands.
 @item
-Mode-specific menubars tailored to the current major mode.
-@item
-A simple menubar for basic editing to help novices get started with InfoDock.
+Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
+otherwise you will erase anything that anybody has already put on the
+hook.
+
 @item
-The standard XEmacs menubar.
-@end enumerate
+You can also do @code{(set-face-font 'modeline @var{font})},
+eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
+(current-buffer))} if you wish the modeline font to vary based on the
+current mode.
+@end itemize
 
-Most modes also include mode-specific popup menus.  Additionally, region and
-rectangle popup menus are included.
+There are additional modeline faces, @code{modeline-buffer-id},
+@code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
+you may want to customize.
 
-@samp{Hyperbole}, the everyday information manager, is a core part of
-InfoDock.  This provides context-sensitive mouse keys, a rolodex-type
-contact manager, programmable hypertext buttons, and an autonumbered
-outliner with embedded hyperlink anchors.
+@unnumberedsec 4.3: The Cursor
 
-The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
-standard part of InfoDock.
+@node Q4.3.1, Q4.3.2, Q4.2.4, Display
+@unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
 
-InfoDock saves a more extensive set of user options than other Emacs
-versions.
+I'd like to have the bar cursor a little thicker, as I tend to "lose" it
+often.
 
-InfoDock inserts a useful file header in many file types, showing the
-author, summary, and last modification time of each file.  A summary
-program can then be used to summarize all of the files in a directory,
-for easy MANIFEST file creation.
+For a 1 pixel bar cursor, use:
 
-Your working set of buffers is automatically saved and restored (if you
-answer yes to a prompt) between InfoDock sessions.
+@lisp
+(setq bar-cursor t)
+@end lisp
 
-Refined color choices for code highlighting are provided for both dark and
-light background display frames.
+For a 2 pixel bar cursor, use:
 
-The @kbd{C-z} key prefix performs frame-based commands which parallel the
-@kbd{C-x} key prefix for window-based commands.
+@lisp
+(setq bar-cursor 'anything-else)
+@end lisp
 
-The Smart Menu system is included for producing command menus on dumb
-terminals.
+You can also change these with Customize.
+Select from the @code{Options} menu
+@code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
+@kbd{M-x customize @key{RET} display @key{RET}}.
 
-Lisp libraries are better categorized according to function.
+You can use a color to make it stand out better:
 
-Extensions and improvements to many areas of Emacs are included, such as:
-paragraph filling, mail reading with Rmail, shell handling, outlining, code
-highlighting and browsing, and man page browsing.
+@example
+Emacs*cursorColor:      Red
+@end example
 
-InfoDock questions, answers and discussion should go to the mail list
-@iftex
-@*
-@end iftex
-@email{infodock@@infodock.com}.  Use
-@email{infodock-request@@infodock.com} to be added or removed from the
-list.  Always include your InfoDock version number when sending help
-requests.
+@node Q4.3.2, Q4.3.3, Q4.3.1, Display
+@unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
 
-InfoDock is available across the Internet via anonymous FTP.  To get
-it, first move to a directory into which you want the InfoDock archive
-files placed.  We will call this <DIST-DIR>.
+@lisp
+(setq bar-cursor nil)
+@end lisp
 
-@example
-   cd <DIST-DIR>
-@end example
+You can also change this with Customize.
+Select from the @code{Options} menu
+@code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
+@kbd{M-x customize @key{RET} display @key{RET}}.
 
-Ftp to ftp.xemacs.org  (Internet Host ID = 128.174.252.16):
+@node Q4.3.3, Q4.4.1, Q4.3.2, Display
+@unnumberedsubsec Q4.3.3: Can I make the cursor blink?
 
-@example
-   prompt> ftp ftp.xemacs.org
-@end example
+Yes, like this:
 
-Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
+@lisp
+(blink-cursor-mode)
+@end lisp
 
-@example
-   Name (ftp.xemacs.org): anonymous
-   331 Guest login ok, send your complete e-mail address as password.
-   Password: -<your-user-id>@@<your-domain>
-   230 Guest login ok, access restrictions apply.
-@end example
+This function toggles between a steady cursor and a blinking cursor.
+You may also set this mode from the menu bar by selecting
+@samp{Options->Display->Blinking Cursor}.  Remember to save options.
 
-Move to the location of the InfoDock archives:
+@unnumberedsec 4.4: The Menubar
 
-@example
-   ftp> cd pub/infodock
-@end example
+@node Q4.4.1, Q4.4.2, Q4.3.3, Display
+@unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
+
+@lisp
+(set-specifier menubar-visible-p nil)
+@end lisp
+
+@node Q4.4.2, Q4.4.3, Q4.4.1, Display
+@unnumberedsubsec Q4.4.2: How can I customize the menubar?
+
+For an extensive menubar, add this line to your @file{init.el}:
+
+@lisp
+(load "big-menubar")
+@end lisp
+
+If you'd like to write your own, this file provides as good a set of
+examples as any to start from.  The file is located in edit-utils
+package. 
 
-Set your transfer mode to binary:
+@node Q4.4.3, Q4.4.4, Q4.4.2, Display
+@unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
+
+#### Write me.
+
+@node Q4.4.4, Q4.4.5, Q4.4.3, Display
+@unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
+
+Add the following to your @file{init.el} (suit to fit):
+
+@lisp
+(setq buffers-menu-max-size 20)
+@end lisp
+
+For no limit, use an argument of @samp{nil}.
+
+You can also change this with Customize.  Select from the
+@code{Options} menu
+@code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
+or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
+
+@node Q4.4.5, Q4.5.1, Q4.4.4, Display
+@unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
+
+I am trying to use a resource like @code{Emacs*menubar*font} to set the
+font of the menubar but it's not working.
+
+In Motif, the use of @samp{font} resources is obsoleted in order to
+support internationalization.  If you are using the real Motif menubar,
+this resource is not recognized at all; you have to say:
 
 @example
-   ftp> bin
-   200 Type set to I.
+Emacs*menubar*fontList: FONT
 @end example
 
-Turn off prompting:
+If you are using the Lucid menubar, for backward compatibility with
+existing user configurations, the @samp{font} resource is recognized.
+Since this is not supported by Motif itself, the code is a kludge and
+the @samp{font} resource will be recognized only if the @samp{fontList}
+resource resource is unset.  This means that the resource
 
 @example
-   ftp> prompt
-   Interactive mode off.
+*fontList: FONT
 @end example
 
-Retrieve the InfoDock archives that you want, either by using a
-@samp{get <file>} for each file you want or by using the following to
-get a complete distribution, including all binaries:
+will override
 
 @example
-   ftp> mget ID-INSTALL
-   ftp> mget id-*
+Emacs*menubar*font: FONT
 @end example
 
-Close the FTP connection:
+even though the latter is more specific.
+
+In non-Motif configurations using @samp{--with-mule} and
+@samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
+resource @emph{instead of} the @code{font} resource.  The backward
+compatibility kludge was never implemented for non-Motif builds.
+Example:
 
 @example
-   ftp> quit
-   221 Goodbye.
+*fontSet: FONT
 @end example
 
-Read the @file{ID-INSTALL} file which you just retrieved for
-step-by-step installation instructions.
+@unnumberedsec 4.5: The Toolbar
 
-@node Q4.7.1, Q4.7.2, Q4.6.1, Subsystems
-@unnumberedsec 4.7: Other Unbundled Packages
-@unnumberedsubsec Q4.7.1: What is AUC TeX?  Where do you get it?
+@node Q4.5.1, Q4.5.2, Q4.4.5, Display
+@unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
 
-AUC TeX is a package written by @email{abraham@@dina.kvl.dk, Per Abrahamsen}.
-Starting with XEmacs 19.16, AUC TeX is bundled with XEmacs.  The
-following information is from the @file{README} and website.
+#### Write me.
 
-AUC TeX is an extensible package that supports writing and formatting
-TeX files for most variants of GNU Emacs. Many different macro packages
-are supported, including AMS TeX, LaTeX, and TeXinfo.
+@node Q4.5.2, Q4.5.3, Q4.5.1, Display
+@unnumberedsubsec Q4.5.2: How can I customize the toolbar?
 
-The most recent version is always available by ftp at
-@iftex
-@*
-@end iftex
-@uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}.
+#### Write me.
 
-In case you don't have access to anonymous ftp, you can get it by an
-email request to @email{ftpmail@@decwrl.dec.com}.
+@node Q4.5.3, Q4.5.4, Q4.5.2, Display
+@unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
 
-WWW users may want to check out the AUC TeX page at
-@iftex
-@*
-@end iftex
-@uref{http://sunsite.auc.dk/auctex/}.
+Try something like:
+
+@lisp
+(defun my-toggle-toolbar ()
+  (interactive)
+  (set-specifier default-toolbar-visible-p
+                 (not (specifier-instance default-toolbar-visible-p))))
+(global-set-key "\C-xT" 'my-toggle-toolbar)
+@end lisp
 
-@node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
-@unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
+@ignore
+@c Probably not relevant any more
+There are redisplay bugs in 19.14 that may make the preceding result in
+a messed-up display, especially for frames with multiple windows.  You
+may need to resize the frame before XEmacs completely realizes the
+toolbar is really gone.
+@end ignore
 
-Yes.  Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
-@iftex
-@*
-@end iftex
-@uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
+Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
+code.
 
-@node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
-@unnumberedsubsec Q4.7.3: Byte compiling AUC TeX on XEmacs 19.14.
+@node Q4.5.4, Q4.6.1, Q4.5.3, Display
+@unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
 
-@email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} writes:
+@email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
 
-@quotation
-When byte compiling auctex-9.4g, you must use the command:
+I just installed the XEmacs (20.4-2) RPMS that I downloaded from
+@uref{http://www.xemacs.org/}.  Everything works fine, except that when
+I place my mouse over the toolbar, it beeps and gives me this message:
 
 @example
-xemacs -batch -l lpath.el
+ Can't instantiate image (probably cached):
+ [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
+ (16 16 <strange control characters> ...
 @end example
-@end quotation
 
-@node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
-@unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
+@email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
+@quotation
+This is problem specific to some Chips and Technologies video
+chips, when running XFree86.  Putting
 
-@email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
+@code{Option "sw_cursor"}
 
-@quotation
-AUC TeX works fine on both stock Emacs and XEmacs has been doing so for
-a very very long time. This is mostly due to the work of
-@email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
-package.  Which leads to what is probably the problem...
+in @file{XF86Config} gets rid of the problem.
 @end quotation
 
-Most problems with AUC TeX are one of two things:
+@unnumberedsec 4.6: Scrollbars and Scrolling
 
-@itemize @bullet
-@item
-The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
-match.
+@node Q4.6.1, Q4.6.2, Q4.5.4, Display
+@unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
 
-Fix: make sure you configure AUC TeX properly @strong{before} installing.
+To disable them for all frames, add the following line to
+your @file{.Xresources}:
 
-@item
-You have an old version of easymenu.el in your path.
+@example
+Emacs.scrollBarWidth:  0
+@end example
 
-Fix: use @code{locate-library} and remove old versions to make sure it
-@strong{only} finds the one that came with XEmacs.
-@end itemize
+Or select @samp{Options->Display->Scrollbars}.
+Remember to save options.
 
+To turn the scrollbar off on a per-frame basis, use the following
+function:
 
-@node Q4.7.5, Q4.7.6, Q4.7.4, Subsystems
-@unnumberedsubsec Q4.7.5: Is there a reason for an Emacs package not to be included in XEmacs?
+@lisp
+(set-specifier scrollbar-width 0 (selected-frame))
+@end lisp
 
-The reason for an Emacs package not to be included in XEmacs is
-usually one or more of the following:
+You can actually turn the scrollbars on at any level you want by
+substituting for (selected-frame) in the above command.  For example, to
+turn the scrollbars off only in a single buffer:
 
-@enumerate
-@item
-The package has not been ported to XEmacs.  This will typically happen
-when it uses GNU-Emacs-specific features, which make it fail under
-XEmacs.
+@lisp
+(set-specifier scrollbar-width 0 (current-buffer))
+@end lisp
 
-Porting a package to XEmacs can range from a trivial amount of change to
-a partial or full rewrite.  Fortunately, the authors of modern packages
-usually choose to support both Emacsen themselves.
+@node Q4.6.2, Q4.6.3, Q4.6.1, Display
+@unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
 
-@item
-The package has been decided not to be appropriate for XEmacs.  It may
-have an equivalent or better replacement within XEmacs, in which case
-the developers may choose not to burden themselves with supporting an
-additional package.
+#### Write me.
 
-Each package bundled with XEmacs means more work for the maintainers,
-whether they want it or not.  If you are ready to take over the
-maintenance responsibilities for the package you port, be sure to say
-so -- we will more likely include it.
+@node Q4.6.3, Q4.6.4, Q4.6.2, Display
+@unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
 
-@item
-The package simply hasn't been noted by the XEmacs development.  If
-that's the case, the messages like yours are very useful for attracting
-our attention.
+Here's a recap of how to use resources to change your scrollbar colors:
 
-@item
-The package was noted by the developers, but they simply haven't yet
-gotten around to including/porting it.  Wait for the next release or,
-even better, offer your help.  It will be gladly accepted and
-appreciated.
-@end enumerate
+@example
+! Motif scrollbars
 
-@node Q4.7.6,  , Q4.7.5, Subsystems
-@unnumberedsubsec Q4.7.5: Is there a MatLab mode?
-@c New
-Is there any way I can get syntax highlighting for MatLab .m files?
-Can I "teach" emacs what words are MatLab commands, comments, etc. ?
+Emacs*XmScrollBar.Background: skyblue
+Emacs*XmScrollBar.troughColor: lightgray
 
-@email{elsner@@mathematik.tu-chemnitz.de, Ulrich Elsner} writes:
-@quotation
-One way to do this (and much more) is by using the
-@iftex
-@*
-@end iftex
-@comment @uref{ftp://ftp.mathworks.com/pub/contrib/v5/tools/matlab.el, matlab mode}.
-matlab mode.  (If someone knows where this can be found, please contact
-the @email{faq@@xemacs.org,XEmacs FAQ maintainer}.
+! Athena scrollbars
 
-Instructions on how to install this mode are included in this file.
-@end quotation
+Emacs*Scrollbar.Foreground: skyblue
+Emacs*Scrollbar.Background: lightgray
+@end example
 
+Note the capitalization of @code{Scrollbar} for the Athena widget.
 
-@node Miscellaneous, MS Windows, Subsystems, Top
-@unnumbered 5 The Miscellaneous Stuff
+@node Q4.6.4, Q4.6.5, Q4.6.3, Display
+@unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
 
-This is part 5 of the XEmacs Frequently Asked Questions list.  This
-section is devoted to anything that doesn't fit neatly into the other
-sections.
+When I move the scrollbar in an XEmacs window, it moves the point as
+well, which should not be the default behavior.  Is this a bug or a
+feature?  Can I disable it?
 
-@menu
-Major & Minor Modes:
-* Q5.0.1::      How can I do source code highlighting using font-lock?
-* Q5.0.2::      I do not like cc-mode.  How do I use the old c-mode?
-* Q5.0.3::      How do I get @samp{More} Syntax Highlighting on by default?
-* Q5.0.4::      How can I enable auto-indent?
-* Q5.0.5::      How can I get XEmacs to come up in text/auto-fill mode by default?
-* Q5.0.6::      How do I start up a second shell buffer?
-* Q5.0.7::      Telnet from shell filters too much.
-* Q5.0.8::      Why does edt emulation not work?
-* Q5.0.9::      How can I emulate VI and use it as my default mode?
-* Q5.0.10::     [This question intentionally left blank]
-* Q5.0.11::     Filladapt doesn't work in 19.15?
-* Q5.0.12::     How do I disable gnuserv from opening a new frame?
-* Q5.0.13::     How do I start gnuserv so that each subsequent XEmacs is a client?
-* Q5.0.14::     Strange things are happening in Shell Mode.
-* Q5.0.15::     Where do I get the latest CC Mode?
-* Q5.0.16::     I find auto-show-mode disconcerting.  How do I turn it off?
-* Q5.0.17::     How can I get two instances of info?
-* Q5.0.18::     I upgraded to XEmacs 19.14 and gnuserv stopped working
-* Q5.0.19::     Is there something better than LaTeX mode?
-* Q5.0.20::     Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
-
-Emacs Lisp Programming Techniques:
-* Q5.1.1::      The difference in key sequences between XEmacs and GNU Emacs?
-* Q5.1.2::      Can I generate "fake" keyboard events?
-* Q5.1.3::      Could you explain @code{read-kbd-macro} in more detail?
-* Q5.1.4::      What is the performance hit of @code{let}?
-* Q5.1.5::      What is the recommended use of @code{setq}?
-* Q5.1.6::      What is the typical misuse of @code{setq}?
-* Q5.1.7::      I like the the @code{do} form of cl, does it slow things down?
-* Q5.1.8::      I like recursion, does it slow things down?
-* Q5.1.9::      How do I put a glyph as annotation in a buffer?
-* Q5.1.10::     @code{map-extents} won't traverse all of my extents!
-* Q5.1.11::     My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
-
-Sound:
-* Q5.2.1::      How do I turn off the sound?
-* Q5.2.2::      How do I get funky sounds instead of a boring beep?
-* Q5.2.3::      What's NAS, how do I get it?
-* Q5.2.4::      Sunsite sounds don't play.
-
-Miscellaneous:
-* Q5.3.1::      How do you make XEmacs indent CL if-clauses correctly?
-* Q5.3.2::      Fontifying hangs when editing a postscript file.
-* Q5.3.3::      How can I print WYSIWYG a font-locked buffer?
-* Q5.3.4::      Getting @kbd{M-x lpr} to work with postscript printer.
-* Q5.3.5::      How do I specify the paths that XEmacs uses for finding files?
-* Q5.3.6::      [This question intentionally left blank]
-* Q5.3.7::      Can I have the end of the buffer delimited in some way?
-* Q5.3.8::      How do I insert today's date into a buffer?
-* Q5.3.9::      Are only certain syntactic character classes available for abbrevs?
-* Q5.3.10::     How can I get those oh-so-neat X-Face lines?
-* Q5.3.11::     How do I add new Info directories?
-* Q5.3.12::     What do I need to change to make printing work?
-@end menu
+The current behavior is a feature, not a bug.  Point remains at the same
+buffer position as long as that position does not scroll off the screen.
+In that event, point will end up in either the upper-left or lower-left
+hand corner.
+
+This cannot be changed.
 
-@node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
-@unnumberedsec 5.0: Major & Minor Modes
-@unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
+@node Q4.6.5, Q4.6.6, Q4.6.4, Display
+@unnumberedsubsec Q4.6.5: Scrolling one line at a time.
 
-For most modes, font-lock is already set up and just needs to be turned
-on.  This can be done by @kbd{M-x font-lock-mode}, or by having XEmacs
-automatically start it by adding lines like:
+Can the cursor keys scroll the screen a line at a time, rather than the
+default half page jump?  I tend it to find it disorienting.
+
+Use the following:
 
 @lisp
-(add-hook 'emacs-lisp-mode-hook	'turn-on-font-lock)
-(add-hook 'dired-mode-hook	'turn-on-font-lock)
+(setq scroll-step 1)
 @end lisp
 
-to your @file{.emacs}.  See the file @file{etc/sample.emacs} for more
-examples.
-
-See also @code{Syntax Highlighting} from the @code{Options} menu.
-Remember to save options.
+You can also change this with Customize.  Select from the
+@code{Options} menu
+@code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
+or type @kbd{M-x customize @key{RET} windows @key{RET}}.
 
-@node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
-@unnumberedsubsec Q5.0.2: I do not like cc-mode.  How do I use the old c-mode?
+@node Q4.6.6, Q4.6.7, Q4.6.5, Display
+@unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
 
-Well, first off, consider if you really want to do this.  cc-mode is
-much more powerful than the old c-mode.  If you're having trouble
-getting your old offsets to work, try using @code{c-set-offset} instead.
-You might also consider using the package @code{cc-compat}.
+Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
+in which you want lines truncated.
 
-But, if you still insist, add the following lines to your @file{.emacs}:
+More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
+will never appear.  Otherwise, they will appear only if the value of
+@code{scrollbar-height} for that buffer/window/etc. is non-zero.  If you
+do
 
 @lisp
-(fmakunbound 'c-mode)
-(makunbound 'c-mode-map)
-(fmakunbound 'c++-mode)
-(makunbound 'c++-mode-map)
-(makunbound 'c-style-alist)
-(load-library "old-c-mode")
-(load-library "old-c++-mode")
+(set-specifier scrollbar-height 0)
 @end lisp
 
-This must be done before any other reference is made to either c-mode or
-c++-mode.
+then horizontal scrollbars will not appear in truncated buffers unless
+the package specifically asked for them.
 
-@node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
-@unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
+@node Q4.6.7, Q4.7.1, Q4.6.6, Display
+@unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting.  How do I turn it off?
 
-Use the following code in your @file{.emacs}:
+@code{auto-show-mode} controls whether or not a horizontal scrollbar
+magically appears when a line is too long to be displayed.  This is
+enabled by default.  To turn it off, put the following in your
+@file{init.el}:
 
 @lisp
-(setq-default font-lock-maximum-decoration t)
+(setq auto-show-mode nil)
+(setq-default auto-show-mode nil)
 @end lisp
 
-In versions of XEmacs prior to 19.14, you had to use a kludgy solution
-like this:
-
-@lisp
-(setq c-font-lock-keywords c-font-lock-keywords-2
-      c++-font-lock-keywords c++-font-lock-keywords-2
-      lisp-font-lock-keywords lisp-font-lock-keywords-2)
-@end lisp
+@unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
 
-It will work for C, C++ and Lisp.
+@node Q4.7.1, Q4.7.2, Q4.6.7, Display
+@unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
 
-See also @code{Syntax Highlighting} from the @code{Options} menu.
-Remember to save options.
+#### Write me.
 
-@node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
-@unnumberedsubsec Q5.0.4: How can I enable auto-indent?
+@node Q4.7.2, Q4.7.3, Q4.7.1, Display
+@unnumberedsubsec Q4.7.2: How can I disable the progress bar?
 
-Put the following line in your @file{.emacs}:
+#### Write me.
 
-@lisp
-(setq indent-line-function 'indent-relative-maybe)
-@end lisp
+@node Q4.7.3, Q4.7.4, Q4.7.2, Display
+@unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
 
-If you want to get fancy, try the @code{filladapt} package available
-standard with XEmacs.  Put this into your @file{.emacs}:
+#### Write me.
 
-@lisp
-(require 'filladapt)
-(add-hook 'text-mode-hook    'turn-on-filladapt-mode)
-;;; and others ...
-@end lisp
+@node Q4.7.4,  , Q4.7.3, Display
+@unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
 
-You can customize filling and adaptive filling with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->->Editing->Fill->Fill...}
-or type @kbd{M-x customize @key{RET} fill @key{RET}}.
+#### Write me.
 
-Note that well-behaving text-lookalike modes will run
-@code{text-mode-hook} by default (e.g. that's what Message does).  For
-the nasty ones, you'll have to provide the @code{add-hook}s yourself.
+@node External Subsystems, Internet, Display, Top
+@unnumbered 5 Interfacing with the Operating System and External Devices
 
-Please note that the @code{fa-extras} package is no longer useful.
+This is part 5 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to the various ways that XEmacs interfaces with the
+operating system, with other processes and with external devices such
+as speakers and the printer.
 
-@node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
-@unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
+@menu
+5.0: X Window System and Resources
+* Q5.0.1::    Where is a list of X resources?
+* Q5.0.2::    How can I detect a color display?
+* Q5.0.3::    How can I get the icon to just say @samp{XEmacs}?
+* Q5.0.4::    How can I have the window title area display the full path?
+* Q5.0.5::    @samp{xemacs -name junk} doesn't work?
+* Q5.0.6::    @samp{-iconic} doesn't work.
+
+5.1: Microsoft Windows
+* Q5.1.1::    Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
+* Q5.1.2::    How do I get Windows Explorer to associate a file type with XEmacs?
+
+5.2: Printing
+* Q5.2.1::    What do I need to change to make printing work?
+* Q5.2.2::    How can I print WYSIWYG a font-locked buffer?
+* Q5.2.3::    Getting @kbd{M-x lpr} to work with postscript printer.
+* Q5.2.4::    Can you print under MS Windows?
+
+5.3: Sound
+* Q5.3.1::    How do I turn off the sound?
+* Q5.3.2::    How do I get funky sounds instead of a boring beep?
+* Q5.3.3::    What are NAS and ESD (EsounD)?
+* Q5.3.4::    Sunsite sounds don't play.
+
+5.4: Running an Interior Shell, Invoking Subprocesses
+* Q5.4.1::    What is an interior shell?
+* Q5.4.2::    How do I start up a second shell buffer?
+* Q5.4.3::    Telnet from shell filters too much
+* Q5.4.4::    Strange things are happening in Shell Mode.
+* Q5.4.5::    XEmacs complains "No such file or directory, diff"
+* Q5.4.6::    Cygwin error "fork_copy: linked dll/bss pass 0 failed"
+
+5.5: Multiple Device Support
+* Q5.5.1::    How do I open a frame on another screen of my multi-headed display?
+* Q5.5.2::    Can I really connect to a running XEmacs after calling up over a modem?  How?
+* Q5.5.3::    How do I disable gnuserv from opening a new frame?
+* Q5.5.4::    How do I start gnuserv so that each subsequent XEmacs is a client?
+* Q5.5.5::    Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
+@end menu
 
-Try the following lisp in your @file{.emacs}:
+@unnumberedsec 5.0: X Window System and Resources
 
-@lisp
-(setq default-major-mode 'text-mode)
-(setq text-mode-hook 'turn-on-auto-fill)
-@end lisp
+@node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
+@unnumberedsubsec Q5.0.1: Where is a list of X resources?
 
-@strong{WARNING}: note that changing the value of
-@code{default-major-mode} from @code{fundamental-mode} can break a large
-amount of built-in code that expects newly created buffers to be in
-@code{fundamental-mode}.  (Changing from @code{fundamental-mode} to
-@code{text-mode} might not wreak too much havoc, but changing to
-something more exotic like a lisp-mode would break many Emacs packages).
-
-Note that Emacs by default starts up in buffer @code{*scratch*} in
-@code{initial-major-mode}, which defaults to
-@code{lisp-interaction-mode}. Thus adding the following form to your
-Emacs init file will cause the initial @code{*scratch*} buffer to be put
-into auto-fill'ed @code{text-mode}:
-
-@lisp
-(setq initial-major-mode
-      (lambda ()
-        (text-mode)
-        (turn-on-auto-fill)))
-@end lisp
+Search through the @file{NEWS} file for @samp{X Resources}.  A fairly
+comprehensive list is given after it.
 
-Note that after your init file is loaded, if
-@code{inhibit-startup-message} is @code{nil} (the default) and the
-startup buffer is @code{*scratch*} then the startup message will be
-inserted into @code{*scratch*}; it will be removed after a timeout by
-erasing the entire @code{*scratch*} buffer.  Keep in mind this default
-usage of @code{*scratch*} if you desire any prior manipulation of
-@code{*scratch*} from within your Emacs init file. In particular,
-anything you insert into @code{*scratch*} from your init file will be
-later erased. Also, if you change the mode of the @code{*scratch*}
-buffer, be sure that this will not interfere with possible later
-insertion of the startup message (e.g. if you put @code{*scratch*} into
-a nonstandard mode that has automatic font lock rules, then the startup
-message might get fontified in a strange foreign manner, e.g. as code in
-some programming language).
+In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
+supplied, listing the defaults.  The file @file{etc/sample.Xresources}
+gives a different set of defaults that you might consider for
+installation in your @file{~/.Xresources} file.  It is nearly the same
+as @file{etc/Emacs.ad}, but a few entries are altered.  Be careful about
+installing the contents of this file into your @file{.Xresources} (or
+legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
 
-@node Q5.0.6, Q5.0.7, Q5.0.5, Miscellaneous
-@unnumberedsubsec Q5.0.6: How do I start up a second shell buffer?
+@node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
+@unnumberedsubsec Q5.0.2: How can I detect a color display?
 
-In the @code{*shell*} buffer:
+You can test the return value of the function @code{(device-class)}, as
+in:
 
 @lisp
-M-x rename-buffer @key{RET} *shell-1* @key{RET}
-M-x shell RET
+(when (eq (device-class) 'color)
+  (set-face-foreground  'font-lock-comment-face "Grey")
+  (set-face-foreground  'font-lock-string-face  "Red")
+  ....
+  )
 @end lisp
 
-This will then start a second shell.  The key is that no buffer named
-@samp{*shell*} can exist.  It might be preferable to use @kbd{M-x
-rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
-rename-buffer}.
+@node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
+@unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
 
-Alternately, you can set the variable @code{shell-multiple-shells}.
-If the value of this variable is non-nil, each time shell mode is invoked, 
-a new shell is made
+I'd like the icon to just say @samp{XEmacs}, and not include the name of
+the current file in it.
 
-@node Q5.0.7, Q5.0.8, Q5.0.6, Miscellaneous
-@unnumberedsubsec Q5.0.7: Telnet from shell filters too much
+Add the following line to your @file{init.el}:
 
-I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
-and use a telnet session within it.  Everything works fine except that
-now all @samp{^M}'s are filtered out by Emacs.  Fixes?
+@lisp
+(setq frame-icon-title-format "XEmacs")
+@end lisp
 
-Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
-than doing rsh or telnet within the local shell buffer.  Starting with
-XEmacs-20.3 you can also use @kbd{M-x ssh} to open secure remote session
-if you have @code{ssh} installed.
+@node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
+@unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
 
-@node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
-@unnumberedsubsec Q5.0.8: Why does edt emulation not work?
+I'd like to have the window title area display the full directory/name
+of the current buffer file and not just the name.
 
-We don't know, but you can use tpu-edt emulation instead, which works
-fine and is a little fancier than the standard edt emulation.  To do
-this, add the following line to your @file{.emacs}:
+Add the following line to your @file{init.el}:
 
 @lisp
-(tpu-edt)
+(setq frame-title-format "%S: %f")
 @end lisp
 
-If you don't want it to replace @kbd{C-h} with an edt-style help menu
-add this as well:
+A more sophisticated title might be:
 
 @lisp
-(global-set-key [(control h)] 'help-for-help)
+(setq frame-title-format
+      '("%S: " (buffer-file-name "%f"
+                                 (dired-directory dired-directory "%b"))))
 @end lisp
 
-@node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
-@unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
+That is, use the file name, or the dired-directory, or the buffer name.
 
-Our recommended VI emulator is viper. To make viper-mode the default,
-add this to your @file{.emacs}:
+@node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
+@unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
 
-@lisp
-(viper-mode)
-@end lisp
+When I run @samp{xterm -name junk}, I get an xterm whose class name
+according to xprop, is @samp{junk}.  This is the way it's supposed to
+work, I think.  When I run @samp{xemacs -name junk} the class name is
+not set to @samp{junk}.  It's still @samp{emacs}.  What does
+@samp{xemacs -name} 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?
 
-@email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
+@samp{xemacs -name} sets the application name for the program (that is,
+the thing which normally comes from @samp{argv[0]}).  Using @samp{-name}
+is the same as making a copy of the executable with that new name.  The
+@code{WM_CLASS} property on each frame is set to the frame-name, and the
+application-class.  So, if you did @samp{xemacs -name FOO} and then
+created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
+@code{( "BAR", "Emacs")}.  However, the resource hierarchy for this
+widget would be:
 
-@quotation
-This should be added as close to the top of @file{.emacs} as you can get
-it, otherwise some minor modes may not get viper-ized.
-@end quotation
+@example
+Name:    FOO   .shell             .container   .BAR
+Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+@end example
+
+instead of the default
 
-@node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
-@unnumberedsubsec Q5.0.10: [This question intentionally left blank]
+@example
+Name:    xemacs.shell             .container   .emacs
+Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+@end example
 
-Obsolete question, left blank to avoid renumbering
 
-@node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
-@unnumberedsubsec Q5.0.11: Filladapt doesn't work in 19.15
+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}.  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} to @samp{xemacs}, or whatever
+the executable happened to be named), so we'd rather avoid it.
 
-Filladapt 2.x is included in 19.15.  In it filladapt is now a minor
-mode and minor modes are traditionally off by default.  The following
-added to your @file{.emacs} will turn it on for all buffers:
+To make a frame with a particular name use:
 
 @lisp
-(setq-default filladapt-mode t)
+(make-frame '((name . "the-name")))
 @end lisp
 
-Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
-major modes, like this:
+@node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
+@unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
 
-@lisp
-(add-hook 'text-mode-hook 'turn-on-filladapt-mode)
-@end lisp
+When I start up XEmacs using @samp{-iconic} it doesn't work right.
+Using @samp{-unmapped} on the command line, and setting the
+@code{initiallyUnmapped} X Resource don't seem to help much either...
 
-@node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
-@unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
+@email{ben@@xemacs.org, Ben Wing} writes:
 
-If you set the @code{gnuserv-frame} variable to the frame that should be
-used to display buffers that are pulled up, a new frame will not be
-created. For example, you could put
+@quotation
+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...
+@end quotation
 
-@lisp
-(setq gnuserv-frame (selected-frame))
-@end lisp
+@unnumberedsec 5.1: Microsoft Windows
 
-early on in your @file{.emacs}, to ensure that the first frame created
-is the one used for your gnuserv buffers.
+@node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
+@unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
 
-Starting in 19.15, there is an option to set the gnuserv target to
-the current frame.  See
-@code{Options->"Other Window" Location->Make current frame gnuserv target}
+In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
+symbols to @samp{w32-*}.  Does XEmacs do the same?
 
-Starting with XEmacs-20.3 you can also change this with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
-@kbd{M-x customize @key{RET} gnuserv @key{RET}}.
+We consider such a move counter-productive, thus we do not use the
+@samp{w32} prefix. (His rather questionable justification was that he
+did not consider Windows to be a "winning" platform.) However, the name
+@samp{Win32} is not particularly descriptive outside the Windows world,
+and using just @samp{windows-} would be too generic.  So we chose a
+compromise, the prefix @samp{mswindows-} for Windows-related variables
+and functions.
 
+Thus all the XEmacs variables and functions directly related to either
+the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
+couple of debugging variables, prefixed @samp{debug-mswindows-}).  From
+an architectural perspective, however, we believe that this is mostly a
+non-issue because there should be a very small number of
+window-systems-specific variables anyway.  Whenever possible, we try to
+provide generic interfaces that apply to all window systems.
 
-@node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
-@unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
+@c not true:
+@c The user variables
+@c that share functionality with existing NT Emacs variables are be named
+@c with our convention, but we provide the GNU Emacs names as
+@c compatibility aliases.
 
-Put the following in your @file{.emacs} file to start the server:
+@node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
+@unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
 
-@lisp
-(gnuserv-start)
-@end lisp
+@unnumberedsubsubsec Associating a new file type with XEmacs.
 
-Start your first XEmacs as usual.  After that, you can do:
+In Explorer select @samp{View->Options->File Types}, press @samp{[New
+Type...]} and fill in the dialog box, e.g.:
 
 @example
-gnuclient randomfilename
+        Description of type:    Emacs Lisp source
+        Associated extension:   el
+        Content Type (MIME):    text/plain
 @end example
 
-from the command line to get your existing XEmacs process to open a new
-frame and visit randomfilename in that window. When you're done editing
-randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
-frame.
+then press @samp{[New...]} and fill in the @samp{Action} dialog box as
+follows:
 
-See also man page of gnuclient.
+@example
+        Action:
+        Open
 
-@node Q5.0.14, Q5.0.15, Q5.0.13, Miscellaneous
-@unnumberedsubsec Q5.0.14: Strange things are happening in Shell Mode.
+        Application used to perform action:
+        D:\Full\path\for\xemacs.exe "%1"
 
-Sometimes (i.e. it's not repeatable, and I can't work out why it
-happens) when I'm typing into shell mode, I hit return and only a
-portion of the command is given to the shell, and a blank prompt is
-returned.  If I hit return again, the rest of the previous command is
-given to the shell.
+        [x] Use DDE
 
-@email{martin@@xemacs.org, Martin Buchholz} writes:
+        DDE Message:
+        open("%1")
 
-@quotation
-There is a known problem with interaction between @code{csh} and the
-@code{filec} option and XEmacs.  You should add the following to your
-@file{.cshrc}:
+        Application:
+        <leave blank>
 
-@example
-if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
+        DDE Application Not Running:
+        <leave blank>
+
+        Topic:
+        <leave blank>
 @end example
-@end quotation
 
-@node Q5.0.15, Q5.0.16, Q5.0.14, Miscellaneous
-@unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
+@unnumberedsubsubsec Associating an existing file type with XEmacs.
 
-@email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
+In Explorer select @samp{View->Options->File Types}.  Click on the file
+type in the list and press @samp{[Edit...]}.  If the file type already
+has an @samp{Open} action, double click on it and fill in the
+@samp{Action} dialog box as described above; otherwise create a new
+action.
 
-@quotation
-This can be had from @uref{http://www.python.org/emacs/}.
-@end quotation
+If the file type has more than one action listed, you probably want to
+make the @samp{Open} action that you just edited the default by clicking on
+it and pressing @samp{Set Default}.
 
-@node Q5.0.16, Q5.0.17, Q5.0.15, Miscellaneous
-@unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting.  How do I turn it off?
+Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
+using @samp{Control Panel->Folder Options->File Types}.
 
-@code{auto-show-mode} controls whether or not a horizontal scrollbar
-magically appears when a line is too long to be displayed.  This is
-enabled by default.  To turn it off, put the following in your
-@file{.emacs}:
+@unnumberedsec 5.2: Printing
+
+@node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
+@unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
+
+For regular printing there are two variables that can be customized.
+
+@table @code
+@item lpr-command
+This should be set to a command that takes standard input and sends
+it to a printer.  Something like:
 
 @lisp
-(setq auto-show-mode nil)
-(setq-default auto-show-mode nil)
+(setq lpr-command "lp")
 @end lisp
 
-@node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
-@unnumberedsubsec Q5.0.17: How can I get two instances of info?
+@item lpr-switches
+This should be set to a list that contains whatever the print command
+requires to do its job.  Something like:
 
-You can't.  The @code{info} package does not provide for multiple info buffers.
+@lisp
+(setq lpr-switches '("-depson"))
+@end lisp
+@end table
 
-@node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
-@unnumberedsubsec Q5.0.18: I upgraded to XEmacs 19.14 and gnuserv stopped working.
+For postscript printing there are three analogous variables to
+customize.
 
-@email{daku@@nortel.ca, Mark Daku} writes:
+@table @code
+@item ps-lpr-command
+This should be set to a command that takes postscript on standard input
+and directs it to a postscript printer.
 
-@quotation
-It turns out I was using an older version of gnuserv.  The installation
-didn't put the binary into the public bin directory.  It put it in
-@iftex
-@*
-@end iftex
-@file{lib/xemacs-19.14/hppa1.1-hp-hpux9.05/gnuserv}.  Shouldn't it have
-been put in @file{bin/hppa1.1-hp-hpux9.0}?
-@end quotation
+@item ps-lpr-switches
+This should be set to a list of switches required for
+@code{ps-lpr-command} to do its job.
 
-@node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
-@unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
+@item ps-print-color-p
+This boolean variable should be set @code{t} if printing will be done in
+color, otherwise it should be set to @code{nil}.
+@end table
 
-@email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
+NOTE: It is an undocumented limitation in XEmacs that postscript
+printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
+window system environment.  It cannot be used outside of X11.
 
-@quotation
-The standard TeX modes leave much to be desired, and are somewhat
-leniently maintained.  Serious TeX users use AUC TeX (@pxref{Q4.7.1}).
-@end quotation
+@node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
+@unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
 
-@node Q5.0.20, Q5.1.1, Q5.0.19, Miscellaneous
-@unnumberedsubsec Q5.0.20: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
+Font-lock looks nice.  How can I print (WYSIWYG) the highlighted
+document?
 
-@email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
-@quotation
-Here is one of the solutions, we have this in a script called
-@file{etc/editclient.sh}.
-@example
- #!/bin/sh
- if gnuclient -batch -eval t >/dev/null 2>&1
- then
-   exec gnuclient $@{1+"$@@"@}
- else
-   xemacs -unmapped -f gnuserv-start &
-   until gnuclient -batch -eval t >/dev/null 2>&1
-   do
-      sleep 1
-   done
-   exec gnuclient $@{1+"$@@"@}
- fi
-@end example
+The package @code{ps-print}, which is now included with XEmacs, provides
+the ability to do this.  The source code contains complete instructions
+on its use, in
+@file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
+being the default location of an installed ps-print package.
 
-Note that there is a known problem when running XEmacs and 'gnuclient
--nw' on the same TTY.
-@end quotation
+@node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
+@unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
 
-@node Q5.1.1, Q5.1.2, Q5.0.20, Miscellaneous
-@unnumberedsec 5.1: Emacs Lisp Programming Techniques
-@unnumberedsubsec Q5.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
+My printer is a Postscript printer and @code{lpr} only works for
+Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
+lpr-buffer} to work?
 
-@email{clerik@@naggum.no, Erik Naggum} writes;
+Put something like this in your @file{init.el}:
 
-@quotation
-Emacs has a legacy of keyboards that produced characters with modifier
-bits, and therefore map a variety of input systems into this scheme even
-today.  XEmacs is instead optimized for X events.  This causes an
-incompatibility in the way key sequences are specified, but both Emacs
-and XEmacs will accept a key sequence as a vector of lists of modifiers
-that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
-@code{[(meta control a)]} in both Emacsen.  XEmacs has an abbreviated
-form for a single key, just (meta control a).  Emacs has an abbreviated
-form for the Control and the Meta modifiers to string-characters (the
-ASCII characters), as in @samp{\M-\C-a}.  XEmacs users need to be aware
-that the abbreviated form works only for one-character key sequences,
-while Emacs users need to be aware that the string-character is rather
+@lisp
+(setq lpr-command "a2ps")
+(setq lpr-switches '("-p" "-1"))
+@end lisp
+
+If you don't use a2ps to convert ASCII to postscript (why not, it's
+free?), replace with the command you do use.  Note also that some
+versions of a2ps require a @samp{-Pprinter} to ensure spooling.
+
+@node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
+@unnumberedsubsec Q5.2.4: Can you print under MS Windows?
+
+As of 21.4, printing works on Windows, using simply
+@samp{File->Print BUFFER...}, and can be configured with
+@samp{File->Page Setup...}.
+
+Prior to 21.4, there is no built-in support, but there are some clever
+hacks out there.  If you know how, please let us know and we'll put it
+here.
+
+@unnumberedsec 5.3: Sound
+
+@node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
+@unnumberedsubsec Q5.3.1: How do I turn off the sound?
+
+Add the following line to your @file{init.el}:
+
+@lisp
+(setq bell-volume 0)
+(setq sound-alist nil)
+@end lisp
+
+That will make your XEmacs totally silent---even the default ding sound
+(TTY beep on TTY-s) will be gone.
+
+You can also change these with Customize.  Select from the
+@code{Options} menu @code{Advanced
+(Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
+customize @key{RET} sound @key{RET}}.
+
+
+@node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
+@unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
+
+Make sure your XEmacs was compiled with sound support, and then put this
+in your @file{init.el}:
+
+@lisp
+(load-default-sounds)
+@end lisp
+
+@node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
+@unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
+
+@dfn{Network Audio System} (NAS) is a client-server sound library for X.
+
+@uref{http://radscan.com/nas.html}.
+
+To build XEmacs with it, use the @file{configure} flag
+@samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later).
+
+@dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
+
+@uref{http://www.tux.org/~ricdude/EsounD.html}.
+
+To build XEmacs with it, use the @file{configure} flag
+@samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later).
+
+You can specify support for both with a flag like
+@samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or
+later).
+
+@node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
+@unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
+
+I'm having some trouble with sounds I've downloaded from sunsite.  They
+play when I run them through @code{showaudio} or cat them directly to
+@file{/dev/audio}, but XEmacs refuses to play them.
+
+@email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
+
+@quotation
+[Many of] These files have an (erroneous) 24byte header that tells about
+the format that they have been recorded in. If you cat them to
+@file{/dev/audio}, the header will be ignored and the default behavior
+for /dev/audio will be used. This happens to be 8kHz uLaw. It is
+probably possible to fix the header by piping through @code{sox} and
+passing explicit parameters for specifying the sampling format; you then
+need to perform a 'null' conversion from SunAudio to SunAudio.
+@end quotation
+
+@unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
+
+@node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
+@unnumberedsubsec Q5.4.1: What is an interior shell?
+
+#### Write me.
+
+@node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
+@unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
+
+In the @code{*shell*} buffer:
+
+@lisp
+M-x rename-buffer @key{RET} *shell-1* @key{RET}
+M-x shell RET
+@end lisp
+
+This will then start a second shell.  The key is that no buffer named
+@samp{*shell*} can exist.  It might be preferable to use @kbd{M-x
+rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
+rename-buffer}.
+
+Alternately, you can set the variable @code{shell-multiple-shells}.
+If the value of this variable is non-nil, each time shell mode is invoked,
+a new shell is made
+
+@node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
+@unnumberedsubsec Q5.4.3: Telnet from shell filters too much
+
+I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
+and use a telnet session within it.  Everything works fine except that
+now all @samp{^M}'s are filtered out by Emacs.  Fixes?
+
+Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
+than doing rsh or telnet within the local shell buffer.  You can also
+use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
+installed.
+
+@node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
+@unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
+
+Sometimes (i.e. it's not repeatable, and I can't work out why it
+happens) when I'm typing into shell mode, I hit return and only a
+portion of the command is given to the shell, and a blank prompt is
+returned.  If I hit return again, the rest of the previous command is
+given to the shell.
+
+@email{martin@@xemacs.org, Martin Buchholz} writes:
+
+@quotation
+There is a known problem with interaction between @code{csh} and the
+@code{filec} option and XEmacs.  You should add the following to your
+@file{.cshrc}:
+
+@example
+if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
+@end example
+@end quotation
+
+@node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems
+@unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
+
+or "ispell" or other commands that seem related to whatever you just
+tried to do (M-x ediff or M-$, for example).
+
+There are a large number of common (in the sense that "everyone has
+these, they really do") Unix utilities that are not provided with
+XEmacs.  The GNU Project's implementations are available for Windows in
+the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
+provides a complete Unix emulation environment (and thus makes ports of
+Unix utilities nearly trivial).  Another implementation is that from
+MinGW (@uref{http://www.mingw.org/msys.shtml}).  If you know of others,
+please let us know!
+
+@node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems
+@unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
+
+If you are getting an error like
+
+@example
+17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed,
+0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487
+bash: fork: resource temporarily unavailable
+@end example
+
+when trying to run bash using @kbd{M-x shell}, then you need to rebase
+your Cygwin DLL's.  This is a known problem with Cygwin.  To fix:
+
+@enumerate
+@item
+Download the @file{rebase} utility from Cygwin setup (it's under
+@samp{System}).
+@item
+Kill @strong{all} of your Cygwin processes, including all of your
+shells and all background processes.  Use @code{ps -a} to list all the
+processes you need to kill.
+@item
+From a DOS prompt, run @file{ash} (@strong{not} @file{bash},
+@file{tcsh} or @file{zsh}).  Do not try to be clever and @code{exec
+/bin/ash} from your last shell; it won't work.
+@item
+Type @code{/bin/rebaseall -v}.
+@end enumerate
+
+The problem should now be fixed -- at least, until you install another
+Cygwin package with DLL's, in which case you may have to repeat the
+procedure.
+
+@unnumberedsec 5.5: Multiple Device Support
+
+@node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems
+@unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
+
+Use the command @kbd{M-x make-frame-on-display}.  This command is also
+on the File menu in the menubar.
+
+The command @code{make-frame-on-tty} also exists, which will establish a
+connection to any tty-like device.  Opening the TTY devices should be
+left to @code{gnuclient}, though.
+
+@node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
+@unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem?  How?
+
+Yes.  Use @code{gnuclient -nw}.
+
+Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
+
+@node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
+@unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
+
+If you set the @code{gnuserv-frame} variable to the frame that should be
+used to display buffers that are pulled up, a new frame will not be
+created. For example, you could put
+
+@lisp
+(setq gnuserv-frame (selected-frame))
+@end lisp
+
+early on in your @file{init.el}, to ensure that the first frame created
+is the one used for your gnuserv buffers.
+
+There is an option to set the gnuserv target to the current frame.  See
+@code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
+
+You can also change this with Customize.  Select from the
+@code{Options} menu @code{Advanced
+(Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...}  or type
+@kbd{M-x customize @key{RET} gnuserv @key{RET}}.
+
+
+@node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
+@unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
+
+Put the following in your @file{init.el} file to start the server:
+
+@lisp
+(gnuserv-start)
+@end lisp
+
+Start your first XEmacs as usual.  After that, you can do:
+
+@example
+gnuclient randomfilename
+@end example
+
+from the command line to get your existing XEmacs process to open a new
+frame and visit randomfilename in that window. When you're done editing
+randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
+frame.
+
+See also man page of gnuclient.
+
+@node Q5.5.5,  , Q5.5.4, External Subsystems
+@unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
+
+@email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
+@quotation
+Here is one of the solutions, we have this in a script called
+@file{etc/editclient.sh}.
+@example
+ #!/bin/sh
+ if gnuclient -batch -eval t >/dev/null 2>&1
+ then
+   exec gnuclient $@{1+"$@@"@}
+ else
+   xemacs -unmapped -f gnuserv-start &
+   until gnuclient -batch -eval t >/dev/null 2>&1
+   do
+      sleep 1
+   done
+   exec gnuclient $@{1+"$@@"@}
+ fi
+@end example
+
+Note that there is a known problem when running XEmacs and 'gnuclient
+-nw' on the same TTY.
+@end quotation
+
+@node Internet, Advanced, External Subsystems, Top
+@unnumbered 6 Connecting to the Internet
+
+This is part 6 of the XEmacs Frequently Asked Questions list.  This
+section is devoted connecting to the Internet.
+
+@menu
+6.0: General Mail and News
+* Q6.0.1::    What are the various packages for reading mail?
+* Q6.0.2::    How can I send mail?
+* Q6.0.3::    How do I get my outgoing mail archived?
+* Q6.0.4::    How can I read and/or compose MIME messages?
+* Q6.0.5::    How do I customize the From line?
+* Q6.0.6::    How do I get my MUA to filter mail for me?
+* Q6.0.7::    Remote mail reading with an MUA.
+* Q6.0.8::    An MUA gets an error incorporating new mail.
+* Q6.0.9::    Why isn't @file{movemail} working?
+* Q6.0.10::   How do I make my MUA display graphical smilies?
+* Q6.0.11::   How can I get those oh-so-neat X-Face lines?
+
+6.1: Reading Mail with VM
+* Q6.1.1::    How do I set up VM to retrieve mail from a remote site using POP?
+* Q6.1.2::    How can I get VM to automatically check for new mail?
+* Q6.1.3::    I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
+* Q6.1.4::    Is there a mailing list or FAQ for VM?
+* Q6.1.5::    How do I make VM stay in a single frame?
+* Q6.1.6::    Customization of VM not covered in the manual, or here.
+
+6.2: Reading Netnews and Mail with Gnus
+* Q6.2.1::    GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
+* Q6.2.2::    How do I make Gnus stay within a single frame?
+
+6.3: FTP Access
+* Q6.3.1::    Can I edit files on other hosts?
+* Q6.3.2::    What is EFS?
+
+6.4: Web Browsing with W3
+* Q6.4.1::    What is W3?
+* Q6.4.2::    How do I run W3 from behind a firewall?
+* Q6.4.3::    Is it true that W3 supports style sheets and tables?
+@end menu
+
+@unnumberedsec 6.0: General Mail and News
+
+@node Q6.0.1, Q6.0.2, Internet, Internet
+@unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
+
+#### Write me.
+
+@node Q6.0.2, Q6.0.3, Q6.0.1, Internet
+@unnumberedsubsec Q6.0.2: How can I send mail?
+
+Under Unix and Mac OS X, the @samp{sendmail} package is normally used
+for this.
+#### Write me.
+
+Under Windows, you need to use @samp{smtpmail}, which communicates
+directly with the mail server, as there is no @file{sendmail} program
+running.  To get it working, use code like the following in your
+@file{init.el} file:
+
+@lisp
+  ;; Get mail working under Windows.
+  (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
+  (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
+  ;; the following ensures that mail problems can be debugged: it logs a trace
+  ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
+  (setq smtpmail-debug-info t)
+  ;; Substitute your info here.
+  ;(setq user-mail-address "ben@@xemacs.org")
+  ;(setq user-full-name "Ben Wing")
+  ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
+  ;; The following two aren't completely necessary but may help.
+  ;(setq smtpmail-local-domain "666.com")
+  ;(setq smtpmail-sendto-domain "666.com")
+  ;; If your SMTP server requires a username/password to authenticate, as
+  ;; many do nowadays, set them like this:
+  ;(setq smtpmail-auth-credentials  ; or use ~/.authinfo
+  ;	'(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
+
+  ;; Other possibilities for getting smtpmail to work:
+  ;;
+  ;;  If for some reason you need to authenticate using the STARTTLS protocol
+  ;;   (don't look into this unless you know what it is), use
+  ;;  (setq smtpmail-starttls-credentials
+  ;;      '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
+  ;;  Requires external program
+  ;;    ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
+  ;;  See http://www.ietf.org/rfc/rfc2246.txt,
+  ;;      http://www.ietf.org/rfc/rfc2487.txt
+@end lisp
+
+The lines you need to care about are those that set
+@code{user-mail-address}, @code{user-full-name},
+@code{smtpmail-default-smtp-server}, and
+@code{smtpmail-auth-credentials}.  You need to set these with,
+respectively, your email address, your full name, the SMTP server you
+use for outgoing mail, and the username and password you need to log
+in to your SMTP server. (If for some reason your SMTP server doesn't
+require logging in to send mail, don't uncomment this last line.)
+
+The other settings may be useful in specific cases, but you should know what
+you're doing before enabling them.
+
+@node Q6.0.3, Q6.0.4, Q6.0.2, Internet
+@unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
+
+@lisp
+(setq mail-archive-file-name "~/outbox")
+@end lisp
+
+@node Q6.0.4, Q6.0.5, Q6.0.3, Internet
+@unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
+
+VM, MH-E and GNUS support MIME natively.  Other MUAs may or may not
+have MIME support; refer to their documentation and other resources,
+such as web pages and mailing lists.  Packages like SEMI/WEMI may be
+useful in connection with MUAs like mew and Wanderlust.
+
+@node Q6.0.5, Q6.0.6, Q6.0.4, Internet
+@unnumberedsubsec Q6.0.5: How do I customize the From line?
+
+How do I change the @samp{From:} line?  I have set gnus-user-from-line
+to
+@example
+Gail Gurman <gail.gurman@@sybase.com>
+@end example
+@noindent , but XEmacs Gnus doesn't use
+it. [This should apply to all MUA's. --ed] Instead it uses
+@example
+Gail Mara Gurman @email{gailg@@deall}
+@end example
+@noindent and then complains
+that it's incorrect. Also, as you perhaps can see, my Message-ID is
+screwy. How can I change that?
+
+@email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
+
+@quotation
+Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
+@code{mail-host-address} to @samp{sybase.com}.
+@end quotation
+
+@node Q6.0.6, Q6.0.7, Q6.0.5, Internet
+@unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
+
+One possibility is to use procmail to split your mail before it gets to
+the MUA.  I prefer this personally, since there are many strange and
+wonderful things one can do with procmail.  Procmail may be found at
+@uref{http://www.procmail.org/}.
+
+Also see the Mail Filtering FAQ at:
+@iftex
+@*
+@end iftex
+@uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
+
+@node Q6.0.7, Q6.0.8, Q6.0.6, Internet
+@unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
+
+My mailbox lives at the office on a big honkin server.  My regular INBOX
+lives on my honkin desktop machine.  I now can PPP to the office from
+home which is far from honking...  I'd like to be able to read mail at
+home without storing it here and I'd like to use xemacs and the MUA at
+home...  Is there a recommended setup?
+
+@email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
+
+@quotation
+There are several ways to do this.
+
+@enumerate
+@item
+Set your display to your home machine and run dxpc or one of the other X
+compressors.
+
+@item
+NFS mount your desktop machine on your home machine and modify your pop
+command on your home machine to rsh to your desktop machine and actually
+do the pop get's.
+
+@item
+Run a POP server on your desktop machine as well and do a sort of two
+tiered POP get.
+@end enumerate
+@end quotation
+
+@email{wmperry@@monolith.spry.com, William Perry} adds:
+
+@quotation
+Or you could run a pop script periodically on your desktop machine, and
+just use ange-ftp or NFS to get to your mailbox.  I used to do this all
+the time back at IU.
+@end quotation
+
+@node Q6.0.8, Q6.0.9, Q6.0.7, Internet
+@unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
+
+rmail and VM, and probably other MUA's as well, get new mail from
+your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
+or something similar) using a program called @code{movemail}.
+This program interlocks with @code{/bin/mail} using the protocol
+defined by @code{/bin/mail}.
+
+There are various different protocols in general use, which you need to
+specify using the @samp{--mail-locking} option
+(@samp{--with-mail-locking} in 21.5 or later) to @file{configure}:
+
+@table @samp
+@item lockf
+POSIX file locking with @code{lockf()}
+@item flock
+BSD file locking with @code{flock()}
+@item dot
+To manipulate mail file @file{foo}, first create file @file{foo.lock}
+@item locking
+Use @code{locking()}, Microsoft's renamed @code{flock()}
+@item mmdf
+Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
+Memo Distribution Facility
+@item pop
+Retrieve mail using POP (the Post Office Protocol).  This is the
+default for Cygwin/MinGW.
+@end table
+
+@strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
+SYSTEM, YOU CAN LOSE MAIL!}
+
+Usually the value is correctly determined automatically:
+@file{configure} tries to detect the method in use, and defaults exist
+on systems for which this doesn't work.
+
+However, if you run into problems incorporating new mail, it may be
+because an incorrect method is being used.
+
+If your system uses the lock file protocol, and permissions are set
+so that ordinary users cannot write lock files in the mail spool
+directory, you may need to make @file{movemail} setgid to a
+suitable group such as @samp{mail}.  You can use these commands (as
+root):
+
+@example
+chgrp mail movemail
+chmod 2755 movemail
+@end example
+
+If you are using the @samp{pop} locking method, @file{movemail} must
+be setuid root.
+
+Installation normally copies movemail from the build directory to an
+installation directory which is usually under @file{/usr/local/lib}.
+The installed copy of @file{movemail} is usually in the directory
+@file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
+@file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}).  You must change
+the group and mode of the installed copy; changing the group and mode
+of the build directory copy is ineffective.
+
+@node Q6.0.9, Q6.0.10, Q6.0.8, Internet
+@unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
+
+@xref{Q6.0.8}.
+
+Note also that older versions of Mozilla came with a @file{movemail}
+program that is @strong{not} compatible with XEmacs.  Do not use it.
+Always use the @file{movemail} installed with your XEmacs.  Failure to
+do so can result in lost mail.
+
+@node Q6.0.10, Q6.0.11, Q6.0.9, Internet
+@unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
+For mh-e use the following:
+
+@lisp
+(add-hook 'mh-show-mode-hook '(lambda ()
+                                (smiley-region (point-min)
+                                               (point-max))))
+@end lisp
+
+@email{bill@@carpenter.ORG, WJCarpenter} writes:
+For VM use the following:
+@lisp
+       (autoload 'smiley-region "smiley" nil t)
+       (add-hook 'vm-select-message-hook
+                 '(lambda ()
+                    (smiley-region (point-min)
+                                   (point-max))))
+@end lisp
+
+For tm use the following:
+@lisp
+(autoload 'smiley-buffer "smiley" nil t)
+(add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
+@end lisp
+
+@node Q6.0.11, Q6.1.1, Q6.0.10, Internet
+@unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
+
+Firstly there is an ftp site which describes X-faces and has the
+associated tools mentioned below, at
+@uref{http://ftp.cs.indiana.edu/pub/faces/}.
+
+Then the steps are
+
+@enumerate
+@item
+Create 48x48x1 bitmap with your favorite tool
+
+@item
+Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
+and then compile the face.
+
+@item
+@example
+cat file.xbm | xbm2ikon |compface > file.face
+@end example
+
+@item
+Then be sure to quote things that are necessary for emacs strings:
+
+@example
+cat ./file.face | sed 's/\\/\\\\/g'
+@iftex
+\ @*
+@end iftex
+| sed 's/\"/\\\"/g' > ./file.face.quoted
+@end example
+
+@item
+Then set up emacs to include the file as a mail header - there were a
+couple of suggestions here---either something like:
+
+@lisp
+(setq  mail-default-headers
+       "X-Face:  @email{Ugly looking text string here}")
+@end lisp
+
+Or, alternatively, as:
+
+@lisp
+(defun mail-insert-x-face ()
+  (save-excursion
+    (goto-char (point-min))
+    (search-forward mail-header-separator)
+    (beginning-of-line)
+    (insert "X-Face:")
+    (insert-file-contents "~/.face")))
+
+(add-hook 'mail-setup-hook 'mail-insert-x-face)
+@end lisp
+@end enumerate
+
+However, 2 things might be wrong:
+
+Some versions of pbmtoicon produces some header lines that is not
+expected by the version of compface that I grabbed. So I found I had to
+include a @code{tail +3} in the pipeline like this:
+
+@example
+cat file.xbm | xbm2ikon | tail +3 |compface > file.face
+@end example
+
+Some people have also found that if one uses the @code{(insert-file)}
+method, one should NOT quote the face string using the sed script .
+
+It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
+xbm2face (included in the compface distribution at XEmacs.org) to do the
+conversion.
+
+Contributors for this item:
+
+Paul Emsley,
+Ricardo Marek,
+Amir J. Katz,
+Glen McCort,
+Heinz Uphoff,
+Peter Arius,
+Paul Harrison, and
+Vegard Vesterheim
+
+@unnumberedsec 6.1: Reading Mail with VM
+
+@node Q6.1.1, Q6.1.2, Q6.0.11, Internet
+@unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
+
+Use @code{vm-spool-files}, like this for example:
+
+@lisp
+(setq vm-spool-files '("/var/spool/mail/wing"
+                       "netcom23.netcom.com:110:pass:wing:MYPASS"))
+@end lisp
+
+Of course substitute your actual password for MYPASS.
+
+@node Q6.1.2, Q6.1.3, Q6.1.1, Internet
+@unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
+
+@email{turner@@lanl.gov, John Turner} writes:
+
+@quotation
+Use the following:
+
+@lisp
+(setq vm-auto-get-new-mail 60)
+@end lisp
+@end quotation
+
+@node Q6.1.3, Q6.1.4, Q6.1.2, Internet
+@unnumberedsubsec Q6.1.3: I have various addresses at which I receive mail.  How can I tell VM to ignore them when doing a "reply-all"?
+
+Set @code{vm-reply-ignored-addresses} to a list, like
+
+@lisp
+(setq vm-reply-ignored-addresses
+      '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
+        "wing@@netcom.com" "wing@@xemacs.org"))
+@end lisp
+
+Note that each string is a regular expression.
+
+@node Q6.1.4, Q6.1.5, Q6.1.3, Internet
+@unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
+
+A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
+
+VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
+
+@node Q6.1.5, Q6.1.6, Q6.1.4, Internet
+@unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
+
+John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
+
+@quotation
+@lisp
+                                        ; Don't use multiple frames
+(setq vm-frame-per-composition nil)
+(setq vm-frame-per-folder nil)
+(setq vm-frame-per-edit nil)
+(setq vm-frame-per-summary nil)
+@end lisp
+@end quotation
+
+@node Q6.1.6, Q6.2.1, Q6.1.5, Internet
+@unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
+
+@email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
+
+@quotation
+The meta-answer is to look into the file @file{vm-vars.el}, in the vm
+directory of the lisp library.
+
+@file{vm-vars.el} contains, initializes and carefully describes, with
+examples of usage, the plethora of user options that @emph{fully}
+control VM's behavior.
+
+Enter vm-vars, @code{forward-search} for toolbar, find the variables
+that control the toolbar placement, appearance, existence, copy to your
+@file{init.el} or @file{.vm} and modify according to the
+detailed instructions.
+
+The above also applies to all the various features of VM: search for
+some keywords, maybe the first you conjure isn't appropriate, find the
+appropriate variables, copy and experiment.
+@end quotation
+
+@unnumberedsec 6.2: Reading Netnews and Mail with Gnus
+
+@node Q6.2.1, Q6.2.2, Q6.1.6, Internet
+@unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
+
+The Gnus numbering issues are not meant for mere mortals to know them.
+If you feel you @emph{must} enter the muddy waters of Gnus, visit the
+excellent FAQ, maintained by Justin Sheehy, at:
+
+@example
+@uref{http://my.gnus.org/FAQ/}
+@end example
+
+See also Gnus home page
+@example
+@uref{http://www.gnus.org/}
+@end example
+
+@node Q6.2.2, Q6.3.1, Q6.2.1, Internet
+@unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
+
+The toolbar code to start Gnus opens the new frame---and it's a feature
+rather than a bug.  If you don't like it, but would still like to click
+on the seemly icon, use the following code:
+
+@lisp
+(defun toolbar-news ()
+  (gnus))
+@end lisp
+
+It will redefine the callback function of the icon to just call
+@code{gnus}, without all the fancy frame stuff.
+
+@unnumberedsec 6.3: FTP Access
+
+@node Q6.3.1, Q6.3.2, Q6.2.2, Internet
+@unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
+
+Yes.  Of course XEmacs can use any network file system (such as NFS or
+Windows file sharing) you have available, and includes some
+optimizations and safety features appropriate to those environments.
+
+It is also possible to transparently edit files via FTP, ssh, or rsh.  That
+is, XEmacs makes a local copy using the transport in the background, and
+automatically refreshes the remote original from that copy when you save
+it.  XEmacs also is capable of doing file system manipulations like
+creating and removing directories and files.  The FTP interface is
+provided by the standard @samp{efs} package @ref{Top, EFS, , efs}.  The
+ssh/rsh interface is provided by the optional @samp{tramp} package
+@ref{Top, TRAMP, , tramp}.
+
+@node Q6.3.2, Q6.4.1, Q6.3.1, Internet
+@unnumberedsubsec Q6.3.2: What is EFS?
+
+#### Write me.
+
+@unnumberedsec 6.4: Web Browsing with W3
+
+@node Q6.4.1, Q6.4.2, Q6.3.2, Internet
+@unnumberedsubsec Q6.4.1: What is W3?
+
+W3 is an advanced graphical browser written in Emacs lisp that runs on
+XEmacs.  It has full support for cascaded style sheets, and more...
+
+It has a home web page at
+@uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
+
+@node Q6.4.2, Q6.4.3, Q6.4.1, Internet
+@unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
+
+There is a long, well-written, detailed section in the W3 manual that
+describes how to do this.  Look in the section entitled "Firewalls".
+
+@node Q6.4.3,  , Q6.4.2, Internet
+@unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
+
+Yes, and much more.  W3, as distributed with the latest XEmacs is a
+full-featured web browser.
+
+@node Advanced, Other Packages, Internet, Top
+@unnumbered 7 Advanced Customization Using XEmacs Lisp
+
+This is part 7 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to advanced customization using XEmacs Lisp.
+
+@menu
+7.0: Emacs Lisp and @file{init.el}
+* Q7.0.1::    What version of Emacs am I running?
+* Q7.0.2::    How can I evaluate Emacs-Lisp expressions?
+* Q7.0.3::    @code{(setq tab-width 6)} behaves oddly.
+* Q7.0.4::    How can I add directories to the @code{load-path}?
+* Q7.0.5::    How to check if a lisp function is defined?
+* Q7.0.6::    Can I force the output of @code{(face-list)} to a buffer?
+
+7.1: Emacs Lisp Programming Techniques
+* Q7.1.1::    What is the difference in key sequences between XEmacs and GNU Emacs?
+* Q7.1.2::    Can I generate "fake" keyboard events?
+* Q7.1.3::    Could you explain @code{read-kbd-macro} in more detail?
+* Q7.1.4::    What is the performance hit of @code{let}?
+* Q7.1.5::    What is the recommended use of @code{setq}?
+* Q7.1.6::    What is the typical misuse of @code{setq}?
+* Q7.1.7::    I like the @code{do} form of cl, does it slow things down?
+* Q7.1.8::    I like recursion, does it slow things down?
+* Q7.1.9::    How do I put a glyph as annotation in a buffer?
+* Q7.1.10::   @code{map-extents} won't traverse all of my extents!
+* Q7.1.11::   My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
+
+7.2: Mathematics
+* Q7.2.1::    What are bignums, ratios, and bigfloats in Lisp?
+* Q7.2.2::    XEmacs segfaults when I use very big numbers!
+* Q7.2.3::    Bignums are really slow!
+* Q7.2.4::    Equal bignums don't compare as equal!  What gives?
+@end menu
+
+@unnumberedsec 7.0: Emacs Lisp and @file{init.el}
+
+@node Q7.0.1, Q7.0.2, Advanced, Advanced
+@unnumberedsubsec Q7.0.1: What version of Emacs am I running?
+
+How can @file{init.el} determine which of the family of
+Emacsen I am using?
+
+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 @file{etc/sample.init.el} (@file{etc/sample.emacs} in
+XEmacs versions prior to 21.4).  There are other nifty things in there
+as well!
+
+For all new code, all you really need to do is:
+
+@lisp
+(defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
+@end lisp
+
+@node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
+@unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
+
+I know I can evaluate Elisp expressions from @code{*scratch*} buffer
+with @kbd{C-j} after the expression.  How do I do it from another
+buffer?
+
+Press @kbd{M-:} (the default binding of @code{eval-expression}), and
+enter the expression to the minibuffer.
+
+@node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
+@unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly.
+
+If you put @code{(setq tab-width 6)} in your
+@file{init.el} file it does not work!  Is there a reason
+for this?  If you do it at the EVAL prompt it works fine!! How strange.
+
+Use @code{setq-default} instead, since @code{tab-width} is
+all-buffer-local.
+
+@node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
+@unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}?
+
+Here are two ways to do that, one that puts your directories at the
+front of the load-path, the other at the end:
+
+@lisp
+;;; 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")))
+@end lisp
+
+@email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
+
+@quotation
+To add directories using Unix shell metacharacters use
+@file{expand-file-name} like this:
+
+@lisp
+(push (expand-file-name "~keithh/.emacsdir") load-path)
+@end lisp
+@end quotation
+
+@node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
+@unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
+
+Use the following elisp:
+
+@lisp
+(fboundp 'foo)
+@end lisp
+
+It's almost always a mistake to test @code{emacs-version} or any similar
+variables.
+
+Instead, use feature-tests, such as @code{featurep}, @code{boundp},
+@code{fboundp}, or even simple behavioral tests, eg.:
+
+@lisp
+(defvar foo-old-losing-code-p
+  (condition-case nil (progn (losing-code t) nil)
+    (wrong-number-of-arguments t)))
+@end lisp
+
+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.
+
+@node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
+@unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer?
+
+It would be good having it in a buffer, as the output of
+@code{(face-list)} is too wide to fit to a minibuffer.
+
+Evaluate the expression in the @samp{*scratch*} buffer with point after
+the rightmost paren and typing @kbd{C-j}.
+
+If the minibuffer smallness is the only problem you encounter, you can
+simply press @kbd{C-h l} to get the former minibuffer contents in a
+buffer.
+
+@unnumberedsec 7.1: Emacs Lisp Programming Techniques
+
+@node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
+@unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
+
+@email{clerik@@naggum.no, Erik Naggum} writes;
+
+@quotation
+Emacs has a legacy of keyboards that produced characters with modifier
+bits, and therefore map a variety of input systems into this scheme even
+today.  XEmacs is instead optimized for X events.  This causes an
+incompatibility in the way key sequences are specified, but both Emacs
+and XEmacs will accept a key sequence as a vector of lists of modifiers
+that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
+@code{[(meta control a)]} in both Emacsen.  XEmacs has an abbreviated
+form for a single key, just (meta control a).  Emacs has an abbreviated
+form for the Control and the Meta modifiers to string-characters (the
+ASCII characters), as in @samp{\M-\C-a}.  XEmacs users need to be aware
+that the abbreviated form works only for one-character key sequences,
+while Emacs users need to be aware that the string-character is rather
 limited.  Specifically, the string-character can accommodate only 256
 different values, 128 of which have the Meta modifier and 128 of which
 have not.  In each of these blocks, only 32 characters have the Control
@@ -5414,8 +7430,8 @@ Another (even safer) way to be sure of the key-sequences is to use the
 <up>}, and converts it to the internal key representation of the Emacs
 you use.  The function is available both on XEmacs and GNU Emacs.
 
-@node Q5.1.2, Q5.1.3, Q5.1.1, Miscellaneous
-@unnumberedsubsec Q5.1.2: Can I generate "fake" keyboard events?
+@node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
+@unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
 
 I wonder if there is an interactive function that can generate
 @dfn{fake} keyboard events.  This way, I could simply map them inside
@@ -5435,8 +7451,8 @@ This seems to work:
   (lambda () (interactive) (cg--generate-char-event 4)))
 @end lisp
 
-@node Q5.1.3, Q5.1.4, Q5.1.2, Miscellaneous
-@unnumberedsubsec Q5.1.3: Could you explain @code{read-kbd-macro} in more detail?
+@node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
+@unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail?
 
 The @code{read-kbd-macro} function returns the internal Emacs
 representation of a human-readable string (which is its argument).
@@ -5526,8 +7542,8 @@ seven keys but @code{<right>} is a single function key.  When in doubt,
 use whitespace.
 @end quotation
 
-@node Q5.1.4, Q5.1.5, Q5.1.3, Miscellaneous
-@unnumberedsubsec Q5.1.4: What is the performance hit of @code{let}?
+@node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
+@unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}?
 
 In most cases, not noticeable.  Besides, there's no avoiding
 @code{let}---you have to bind your local variables, after all.  Some
@@ -5536,8 +7552,8 @@ function.  I think because of clarity and maintenance (and possible
 future implementation), @code{let}-s should be used (nested) in a way to
 provide the clearest code.
 
-@node Q5.1.5, Q5.1.6, Q5.1.4, Miscellaneous
-@unnumberedsubsec Q5.1.5: What is the recommended use of @code{setq}?
+@node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
+@unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}?
 
 @itemize @bullet
 @item Global variables
@@ -5553,7 +7569,7 @@ user-variable temporarily, use @code{let}:
 
 @lisp
 (let ((case-fold-search nil))
-  ...					; code with searches that must be case-sensitive
+  ...                                   ; code with searches that must be case-sensitive
   ...)
 @end lisp
 
@@ -5599,8 +7615,8 @@ returns the value of @code{inbox}, which can be reused, for instance:
 @end lisp
 @end itemize
 
-@node Q5.1.6, Q5.1.7, Q5.1.5, Miscellaneous
-@unnumberedsubsec Q5.1.6: What is the typical misuse of @code{setq} ?
+@node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
+@unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}?
 
 A typical misuse is probably @code{setq}ing a variable that was meant to
 be local.  Such a variable will remain bound forever, never to be
@@ -5618,7 +7634,7 @@ unbound.  The correct thing is to do it like this:
 
 @lisp
 (defun my-function (whatever)
-  (let (a)				; default initialization is to nil
+  (let (a)                              ; default initialization is to nil
     ... build a large list ...
     ... and exit, unbinding `a' in the process  ...)
 @end lisp
@@ -5631,18 +7647,18 @@ Note that even global variables should not be @code{setq}ed without
 The reason for the warning is the following:
 
 @lisp
-(defun flurgoze nil)			; ok, global internal variable
+(defun flurgoze nil)                    ; ok, global internal variable
 ...
 
-(setq flurghoze t)			; ops!  a typo, but semantically correct.
-					; however, the byte-compiler warns.
+(setq flurghoze t)                      ; ops!  a typo, but semantically correct.
+                                        ; however, the byte-compiler warns.
 
 While compiling toplevel forms:
 ** assignment to free variable flurghoze
 @end lisp
 
-@node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
-@unnumberedsubsec Q5.1.7: I like the the @code{do} form of cl, does it slow things down?
+@node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
+@unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down?
 
 It shouldn't.  Here is what Dave Gillespie has to say about cl.el
 performance:
@@ -5683,10 +7699,10 @@ You can find out how a macro expands by using the @code{cl-prettyexpand}
 function.
 @end quotation
 
-@node Q5.1.8, Q5.1.9, Q5.1.7, Miscellaneous
-@unnumberedsubsec Q5.1.8: I like recursion, does it slow things down?
+@node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
+@unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
 
-Yes.  Emacs byte-compiler cannot do much to optimize recursion.  But
+Yes.  The Emacs byte-compiler cannot do much to optimize recursion.  But
 think well whether this is a real concern in Emacs.  Much of the Emacs
 slowness comes from internal mechanisms such as redisplay, or from the
 fact that it is an interpreter.
@@ -5694,8 +7710,8 @@ fact that it is an interpreter.
 Please try not to make your code much uglier to gain a very small speed
 gain.  It's not usually worth it.
 
-@node Q5.1.9, Q5.1.10, Q5.1.8, Miscellaneous
-@unnumberedsubsec Q5.1.9: How do I put a glyph as annotation in a buffer?
+@node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
+@unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
 
 Here is a solution that will insert the glyph annotation at the
 beginning of buffer:
@@ -5715,14 +7731,14 @@ Instead of @samp{FILE}, use the image file name
 @iftex
 @*
 @end iftex
-@file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
+@file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
 
 You can turn this to a function (that optionally prompts you for a file
 name), and inserts the glyph at @code{(point)} instead of
 @code{(point-min)}.
 
-@node Q5.1.10, Q5.1.11, Q5.1.9, Miscellaneous
-@unnumberedsubsec Q5.1.10: @code{map-extents} won't traverse all of my extents!
+@node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
+@unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents!
 
 I tried to use @code{map-extents} to do an operation on all the extents
 in a region.  However, it seems to quit after processing a random number
@@ -5752,834 +7768,802 @@ is:
                nil))
 @end lisp
 
-@node Q5.1.11, Q5.2.1, Q5.1.10, Miscellaneous
-@unnumberedsubsec Q5.1.11: My elisp program is horribly slow.  Is there
-an easy way to find out where it spends time?
+@node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
+@unnumberedsubsec Q7.1.11: My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
 @c New
 
-z@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
-@quotation
-Under XEmacs 20.4 and later  you can use @kbd{M-x profile-key-sequence}, press a key
-(say @key{RET} in the Gnus Group buffer), and get the results using
-@kbd{M-x profile-results}.  It should give you an idea of where the time
-is being spent.
-@end quotation
-
-@node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
-@unnumberedsubsec Q5.2.1: How do I turn off the sound?
-
-Add the following line to your @file{.emacs}:
-
-@lisp
-(setq bell-volume 0)
-(setq sound-alist nil)
-@end lisp
-
-That will make your XEmacs totally silent -- even the default ding sound
-(TTY beep on TTY-s) will be gone.
-
-Starting with XEmacs-20.2 you can also change these with Customize.
-Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Sound->Sound...} or type
-@kbd{M-x customize @key{RET} sound @key{RET}}.
-
-
-@node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
-@unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
-
-Make sure your XEmacs was compiled with sound support, and then put this
-in your @file{.emacs}:
-
-@lisp
-(load-default-sounds)
-@end lisp
-
-The sound support in XEmacs 19.14 was greatly improved over previous
-versions.
-
-@node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
-@unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
-
-@xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
-
-@node Q5.2.4, Q5.3.1, Q5.2.3, Miscellaneous
-@unnumberedsubsec Q5.2.4: Sunsite sounds don't play.
-
-I'm having some trouble with sounds I've downloaded from sunsite.  They
-play when I run them through @code{showaudio} or cat them directly to
-@file{/dev/audio}, but XEmacs refuses to play them.
-
-@email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
-
-@quotation
-[Many of] These files have an (erroneous) 24byte header that tells about
-the format that they have been recorded in. If you cat them to
-@file{/dev/audio}, the header will be ignored and the default behavior
-for /dev/audio will be used. This happens to be 8kHz uLaw. It is
-probably possible to fix the header by piping through @code{sox} and
-passing explicit parameters for specifying the sampling format; you then
-need to perform a 'null' conversion from SunAudio to SunAudio.
-@end quotation
-
-@node Q5.3.1, Q5.3.2, Q5.2.4, Miscellaneous
-@unnumberedsec 5.3: Miscellaneous
-@unnumberedsubsec Q5.3.1: How do you make XEmacs indent CL if-clauses correctly?
-
-I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
-same amount instead of indenting the 3rd clause differently from the
-first two.
-
-One way is to add, to @file{.emacs}:
-
-@lisp
-(put 'if 'lisp-indent-function nil)
-@end lisp
-
-However, note that the package @code{cl-indent} that comes with
-XEmacs sets up this kind of indentation by default.  @code{cl-indent}
-also knows about many other CL-specific forms.  To use @code{cl-indent},
-one can do this:
-
-@lisp
-(load "cl-indent")
-(setq lisp-indent-function (function common-lisp-indent-function))
-@end lisp
-
-One can also customize @file{cl-indent.el} so it mimics the default
-@code{if} indentation @code{then} indented more than the @code{else}.
-Here's how:
-
-@lisp
-(put 'if 'common-lisp-indent-function '(nil nil &body))
-@end lisp
-
-Also, a new version (1.2) of @file{cl-indent.el} was posted to
-comp.emacs.xemacs on 12/9/94.  This version includes more documentation
-than previous versions.  This may prove useful if you need to customize
-any indent-functions.
-
-@node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
-@unnumberedsubsec Q5.3.2: Fontifying hang when editing a postscript file.
-
-When I try to edit a postscript file it gets stuck saying:
-@samp{fontifying 'filename' (regexps....)} and it just sits there.  If I
-press @kbd{C-c} in the window where XEmacs was started, it suddenly
-becomes alive again.
-
-This was caused by a bug in the Postscript font-lock regular
-expressions.  It was fixed in 19.13.  For earlier versions of XEmacs,
-have a look at your @file{.emacs} file.  You will probably have a line
-like:
-
-@lisp
-(add-hook 'postscript-mode-hook	'turn-on-font-lock)
-@end lisp
-
-Take it out, restart XEmacs, and it won't try to fontify your postscript
-files anymore.
-
-@node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
-@unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
-
-Font-lock looks nice.  How can I print (WYSIWYG) the highlighted
-document?
-
-The package @code{ps-print}, which is now included with XEmacs, provides
-the ability to do this.  The source code contains complete instructions
-on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
-
-@node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
-@unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
-
-My printer is a Postscript printer and @code{lpr} only works for
-Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
-lpr-buffer} to work?
-
-Put something like this in your @file{.emacs}:
-
-@lisp
-(setq lpr-command "a2ps")
-(setq lpr-switches '("-p" "-1"))
-@end lisp
-
-If you don't use a2ps to convert ASCII to postscript (why not, it's
-free?), replace with the command you do use.  Note also that some
-versions of a2ps require a @samp{-Pprinter} to ensure spooling.
-
-@node Q5.3.5, Q5.3.6, Q5.3.4, Miscellaneous
-@unnumberedsubsec Q5.3.5: How do I specify the paths that XEmacs uses for finding files?
-
-You can specify what paths to use by using a number of different flags
-when running configure.  See the section MAKE VARIABLES in the top-level
-file INSTALL in the XEmacs distribution for a listing of those flags.
-
-Most of the time, however, the simplest fix is: @strong{do not} specify
-paths as you might for GNU Emacs.  XEmacs can generally determine the
-necessary paths dynamically at run time.  The only path that generally
-needs to be specified is the root directory to install into.  That can
-be specified by passing the @code{--prefix} flag to configure.  For a
-description of the XEmacs install tree, please consult the @file{NEWS}
-file.
-
-@node Q5.3.6, Q5.3.7, Q5.3.5, Miscellaneous
-@unnumberedsubsec Q5.3.6: [This question intentionally left blank]
-
-Obsolete question, left blank to avoid renumbering.
+@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
+@quotation
+Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
+press a key (say @key{RET} in the Gnus Group buffer), and get the
+results using @kbd{M-x profile-results}.  It should give you an idea of
+where the time is being spent.
+@end quotation
 
-@node Q5.3.7, Q5.3.8, Q5.3.6, Miscellaneous
-@unnumberedsubsec Q5.3.7: Can I have the end of the buffer delimited in some way?
+@unnumberedsec 7.2: Mathematics
+
+@node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
+@unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
+
+Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
+later can use the capabilities of multiple-precision libraries that may
+be available for your platform.  The GNU Multiple Precision (GMP) and
+BSD Multiple Precision (MP) libraries are partially supported.  GMP
+gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
+(arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
+precision floating point numbers).  GNU MP is better-supported by XEmacs
+at the time of writing (2004-04-06).  BSD MP support does not include
+ratios or bigfloats, and it throws errors that aren't understood.
+
+In most cases, bignum support should be transparent to users and Lisp
+programmers.  A bignum-enabled XEmacs will automatically convert from
+fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
+from floats to bigfloats.  (Bigfloats must be explicitly coerced to
+other types, even if they are exactly representable by less precise
+types.)  The Lisp reader and printer have been enhanced to handle
+bignums, as have the mathematical functions.  Rationals (fixnums,
+bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
+@samp{%x}, and @samp{%u} format conversions.  The read syntax for ratios
+is @samp{3/5}.
+
+User-visible changes in behavior include (in probable order of annoyance)
+
+@itemize
+@item
+Arithmetic can cause a segfault, depending on your MP library
+@ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
 
-Say, with: @samp{[END]}?
+@item
+Terminology is not Common-Lisp-conforming.  For example, ``integer'' for
+Emacs Lisp means what Common Lisp calls ``fixnum''.  This issue is being
+investigated, but the use of ``integer'' for fixnum is pervasive and may
+cause backward-compatibility and GNU-Emacs-compatibility problems.
 
-Try this:
+@item
+Many operations that used to cause a range error now succeed, with
+intermediate results and return values coerced to bignums as needed.
 
-@lisp
-(let ((ext (make-extent (point-min) (point-max))))
-  (set-extent-property ext 'start-closed t)
-  (set-extent-property ext 'end-closed t)
-  (set-extent-property ext 'detachable nil)
-  (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
-@end lisp
+@item
+An atom with ratio read syntax now returns a number, not a symbol.
 
-Since this is XEmacs, you can specify an icon to be shown on
-window-system devices.  To do so, change the @code{make-glyph} call to
-something like this:
+@item
+The @samp{%u} format conversion will now give an error if its argument
+is negative.  (Without MP, it prints a number which Lisp can't read.)
+@end itemize
 
-@lisp
-(make-glyph '([xpm :file "~/something.xpm"]
-              [string :data "[END]"]))
-@end lisp
+@emph{Surgeon General's Warning}: The automatic conversions cannot be
+disabled at runtime.  New functions have been added which produce
+ratios, so there should be few surprises with type conflicts, but they
+can't be ruled out.  ``Arbitrary'' precision means precisely what it
+says.  If you work with extremely large numbers, your machine may
+arbitrarily decide to hand you an unpleasant surprise rather than a
+bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
 
-You can inline the @sc{xpm} definition yourself by specifying
-@code{:data} instead of @code{:file}.  Here is such a full-featured
-version that works on both X and TTY devices:
+To configure with GNU MP, add @samp{--use-number-lib=gmp}
+(@samp{--enable-bignum=gmp} in 21.5 or later) to your invocation of
+@file{configure}.  For BSD MP, use @samp{--use-number-lib=mp}
+(@samp{--enable-bignum=mp} for 21.5).
 
-@lisp
-(let ((ext (make-extent (point-min) (point-max))))
-  (set-extent-property ext 'start-closed t)
-  (set-extent-property ext 'end-closed t)
-  (set-extent-property ext 'detachable nil)
-  (set-extent-end-glyph ext (make-glyph '([xpm :data "\
-/* XPM */
-static char* eye = @{
-\"20 11 7 2\",
-\"__ c None\"
-\"_` c #7f7f7f\",
-\"_a c #fefefe\",
-\"_b c #7f0000\",
-\"_c c #fefe00\",
-\"_d c #fe0000\",
-\"_e c #bfbfbf\",
-\"___________`_`_`___b_b_b_b_________`____\",
-\"_________`_`_`___b_c_c_c_b_b____________\",
-\"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
-\"___`_`_e_a___b_b_d___b___b___b___b______\",
-\"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
-\"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
-\"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
-\"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
-\"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
-\"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
-\"___`_____`_`_`_`___b_b_b_b_b_b__________\",
-@} ;"]
-                                          [string :data "[END]"]))))
-@end lisp
+If you would like to help with bignum support, especially on BSD MP,
+please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
+XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
+@file{number-mp.h}.  Jerry has promised to write internals documentation
+eventually, but if your skills run more to analysis and documentation
+than to writing new code, feel free to fill in the gap!
 
-Note that you might want to make this a function, and put it to a hook.
-We leave that as an exercise for the reader.
 
-@node Q5.3.8, Q5.3.9, Q5.3.7, Miscellaneous
-@unnumberedsubsec Q5.3.8: How do I insert today's date into a buffer?
+@node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
+@unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
 
-Like this:
+GMP by default allocates temporaries on the stack.  If you run out of
+stack space, you're dead; there is no way that we know of to reliably
+detect this condition, because @samp{alloca} is typically implemented to
+be @emph{fast} rather than robust.  If you just need a little more
+oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
+bash(1)).  If you want robustness at the cost of speed, configure GMP
+with @samp{--disable-alloca} and rebuild the GMP library.
 
-@lisp
-(insert (current-time-string))
-@end lisp
+We do not know whether BSD MP uses @samp{alloca} or not.  Please send
+any information you have as a bug report (@kbd{M-x report-xemacs-bug
+@key{RET}}), which will give us platform information.  (We do know that
+BSD MP implementations vary across vendors, but how much, we do not know
+yet.)
 
-@node Q5.3.9, Q5.3.10, Q5.3.8, Miscellaneous
-@unnumberedsubsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
 
-@email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
+@node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
+@unnumberedsubsec Q7.2.3: Bignums are really slow!
 
-@quotation
-Yes, abbrevs only expands word-syntax strings. While XEmacs does not
-prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
-abbrevs that contain special characters, it will refuse to expand
-them. So you need to ensure, that the abbreviation contains letters and
-digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
-valid abbrevs, but @samp{&d}, and @samp{x d} are not.
-
-If this sounds confusing to you, (re-)read the online documentation for
-abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
-read this question/answer again.
-@end quotation
+Many Linux distributions compile all their packages for the i386, and
+this is costly.  An optimized version can give you two or three orders
+of magnitude better performance for a Pentium III or IV.  (Yes, really.
+See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
 
-Starting with XEmacs 20.3 this restriction has been lifted.
 
-@node Q5.3.10, Q5.3.11, Q5.3.9, Miscellaneous
-@unnumberedsubsec Q5.3.10: How can I get those oh-so-neat X-Face lines?
+@node Q7.2.4,  , Q7.2.3, Advanced
+@unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal!  What gives?
 
-Firstly there is an ftp site which describes X-faces and has the
-associated tools mentioned below, at
-@uref{ftp://ftp.cs.indiana.edu:/pub/faces/}.
+Ah, Grasshopper, I see you are using @code{(eq x y)}.  The Bodhisattva
+CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
+Meditate on the deeper truths of @samp{eql}, in which numbers of the same
+type which have equal values compare equal, and @samp{=}, which does any
+necessary type coercions before comparing for equality.
 
-Then the steps are
+Yeah, yeah, it has always worked for integer types, because fixnums and
+characters have an immediate representation.  Sorry about that;
+arbitrary precision obviously requires consing new objects because the
+objects are ``large'' and of variable size, and the definition of
+@samp{eq} does not permit different objects to compare as equal.
 
-@enumerate
-@item
-Create 48x48x1 bitmap with your favorite tool
+@node Other Packages, Current Events, Advanced, Top
+@unnumbered 8 Other External Packages
 
-@item
-Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
-and then compile the face.
+This is part 8 of the XEmacs Frequently Asked Questions list.  This
+section is devoted to miscellaneous external packages not covered
+elsewhere in XEmacs.
 
-@item
-@example
-cat file.xbm | xbm2ikon |compface > file.face
-@end example
+@menu
+8.0: TeX
+* Q8.0.1::    Is there something better than LaTeX mode?
+* Q8.0.2::    What is AUCTeX?  Where do you get it?
+* Q8.0.3::    Problems installing AUCTeX.
+* Q8.0.4::    How do I turn off current chapter from AUCTeX modeline?
+
+8.1: Other Unbundled Packages
+* Q8.1.1::    Is there a reason for an Emacs package not to be included in XEmacs?
+* Q8.1.2::    Are there any Emacs Lisp Spreadsheets?
+* Q8.1.3::    Is there a MatLab mode?
+
+8.2: Environments Built Around XEmacs
+* Q8.2.1::    What are SPARCworks, EOS, and WorkShop?
+* Q8.2.2::    How do I start the Sun Workshop support in XEmacs 21?
+* Q8.2.3::    What is/was Energize?
+* Q8.2.4::    What is Infodock?
+@end menu
 
-@item
-Then be sure to quote things that are necessary for emacs strings:
+@unnumberedsec 8.0: TeX
 
-@example
-cat ./file.face | sed 's/\\/\\\\/g'
-@iftex
-\ @*
-@end iftex
-| sed 's/\"/\\\"/g' > ./file.face.quoted
-@end example
+@node Q8.0.1, Q8.0.2, Other Packages, Other Packages
+@unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
 
-@item
-Then set up emacs to include the file as a mail header - there were a
-couple of suggestions here---either something like:
+@email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
 
-@lisp
-(setq  mail-default-headers
-       "X-Face:  @email{Ugly looking text string here}")
-@end lisp
+@quotation
+The standard TeX modes leave much to be desired, and are somewhat
+leniently maintained.  Serious TeX users use AUCTeX (@pxref{Q8.0.2,
+What is AUCTeX?  Where do you get it?}).
+@end quotation
 
-Or, alternatively, as:
+@node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
+@unnumberedsubsec Q8.0.2: What is AUCTeX?  Where do you get it?
+
+AUCTeX is a complex and sophisticated editing package dedicated to TeX
+and related text formatting languages, including LaTeX and Texinfo.
+It provides support for running TeX on a file or part of a file,
+include files, and of course shortcuts for entering common TeX macros,
+LaTeX environments, etc, and for fontlock.
+
+AUCTeX is a standard package provided by XEmacs.  You can get it as
+usual through the @kbd{M-x list-packages} interface.  It is also
+included in the (non-Mule) SUMO package.  The AUCTeX XEmacs package is
+maintained by Uwe Brauer <GET MAIL ADDRESS>.
+
+AUCTeX is extremely complicated, and its developers primarily 
+use GNU Emacs.  Not all features of the bleeding edge version 
+of AUCTeX are immediately ported to XEmacs; if you need 
+these, you may be better off getting the most recent versions 
+from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
+ 
+@node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
+@unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
 
-@lisp
-(defun mail-insert-x-face ()
-  (save-excursion
-    (goto-char (point-min))
-    (search-forward mail-header-separator)
-    (beginning-of-line)
-    (insert "X-Face:")
-    (insert-file-contents "~/.face")))
+@email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
 
-(add-hook 'mail-setup-hook 'mail-insert-x-face)
-@end lisp
-@end enumerate
+@quotation
+AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
+a very very long time. This is mostly due to the work of
+@email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
+package.  Which leads to what is probably the problem...
+@end quotation
 
-However, 2 things might be wrong:
+Most problems with AUCTeX are one of two things:
 
-Some versions of pbmtoicon produces some header lines that is not
-expected by the version of compface that I grabbed. So I found I had to
-include a @code{tail +3} in the pipeline like this:
+@itemize @bullet
+@item
+The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
+match.
 
-@example
-cat file.xbm | xbm2ikon | tail +3 |compface > file.face
-@end example
+Fix: make sure you configure AUCTeX properly @strong{before} installing.
 
-Some people have also found that if one uses the @code{(insert-file)}
-method, one should NOT quote the face string using the sed script .
+@item
+You have an old version of easymenu.el in your path.
 
-It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
-(included in the compface distribution at XEmacs.org) to do the
-conversion.
-@comment For convenience xbm2xface is available for anonymous FTP at
-@comment @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
+Fix: use @code{locate-library} and remove old versions to make sure it
+@strong{only} finds the one that came with XEmacs.
+@end itemize
 
-Contributors for this item:
+@node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
+@unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
 
-Paul Emsley,
-Ricardo Marek,
-Amir J. Katz,
-Glen McCort,
-Heinz Uphoff,
-Peter Arius,
-Paul Harrison, and
-Vegard Vesterheim
+With AUCTeX, fast typing is hard because the current chapter, section
+etc. are given in the modeline.  How can I turn this off?
 
-@node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
-@unnumberedsubsec Q5.3.11: How do I add new Info directories?
+It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
+
+@c Add this code to your @file{init.el} to turn it off:
+@c
+@c @lisp
+@c (setq fume-display-in-modeline-p nil)
+@c @end lisp
+@c
+@c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
+@c mode:
+@c
+@c @lisp
+@c (add-hook 'TeX-mode-hook
+@c           '(lambda () (setq fume-display-in-modeline-p nil)))
+@c @end lisp
+@c
+@email{dhughes@@origin-at.co.uk, David Hughes} writes:
 
-You use something like:
+@quotation
+Try this; 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 @samp{Rescan
+Buffer} option in the function-menu.
 
 @lisp
-(setq Info-directory-list (cons
-			   (expand-file-name "~/info")
-			   Info-default-directory-list))
+(setq-default fume-auto-rescan-buffer-p nil)
 @end lisp
+@end quotation
 
-@email{davidm@@prism.kla.com, David Masterson} writes:
+@unnumberedsec 8.1: Other Unbundled Packages
 
-@quotation
-Emacs Info and XEmacs Info do many things differently.  If you're trying to
-support a number of versions of Emacs, here are some notes to remember:
+@node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
+@unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
+
+The reason for an Emacs package not to be included in XEmacs is
+usually one or more of the following:
 
 @enumerate
 @item
-Emacs Info scans @code{Info-directory-list} from right-to-left while
-XEmacs Info reads it from left-to-right, so append to the @emph{correct}
-end of the list.
+The package has not been ported to XEmacs.  This will typically happen
+when it uses GNU-Emacs-specific features, which make it fail under
+XEmacs.
+
+Porting a package to XEmacs can range from a trivial amount of change to
+a partial or full rewrite.  Fortunately, the authors of modern packages
+usually choose to support both Emacsen themselves.
 
 @item
-Use @code{Info-default-directory-list} to initialize
-@code{Info-directory-list} @emph{if} it is available at startup, but not
-all Emacsen define it.
+The package has been decided not to be appropriate for XEmacs.  It may
+have an equivalent or better replacement within XEmacs, in which case
+the developers may choose not to burden themselves with supporting an
+additional package.
+
+Each package bundled with XEmacs means more work for the maintainers,
+whether they want it or not.  If you are ready to take over the
+maintenance responsibilities for the package you port, be sure to say
+so---we will more likely include it.
 
 @item
-Emacs Info looks for a standard @file{dir} file in each of the
-directories scanned from #1 and magically concatenates them together.
+The package simply hasn't been noted by the XEmacs development.  If
+that's the case, the messages like yours are very useful for attracting
+our attention.
 
 @item
-XEmacs Info looks for a @file{localdir} file (which consists of just the
-menu entries from a @file{dir} file) in each of the directories scanned
-from #1 (except the first), does a simple concatenation of them, and
-magically attaches the resulting list to the end of the menu in the
-@file{dir} file in the first directory.
+The package was noted by the developers, but they simply haven't yet
+gotten around to including/porting it.  Wait for the next release or,
+even better, offer your help.  It will be gladly accepted and
+appreciated.
 @end enumerate
 
-Another alternative is to convert the documentation to HTML with
-texi2html and read it from a web browser like Lynx or W3.
-@end quotation
-
-@node Q5.3.12,  , Q5.3.11, Miscellaneous
-@unnumberedsubsec Q5.3.12: What do I need to change to make printing work?
-
-For regular printing there are two variables that can be customized.
+@node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
+@unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
 
-@table @code
-@item lpr-command
-This should be set to a command that takes standard input and sends
-it to a printer.  Something like:
+Yes.  Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
+@iftex
+@*
+@end iftex
+@uref{http://acs.ist.psu.edu/dismal/dismal.html}.
 
-@lisp
-(setq lpr-command "lp")
-@end lisp
+@node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
+@unnumberedsubsec Q8.1.3: Is there a MatLab mode?
 
-@item lpr-switches
-This should be set to a list that contains whatever the print command
-requires to do its job.  Something like:
+Yes, a matlab mode and other items are available at the
+@uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
 
-@lisp
-(setq lpr-switches '("-depson"))
-@end lisp
-@end table
+@unnumberedsec 8.2: Environments Built Around XEmacs
 
-For postscript printing there are three analogous variables to
-customize.
+@node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
+@unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
 
-@table @code
-@item ps-lpr-command
-This should be set to a command that takes postscript on standard input
-and directs it to a postscript printer.
+SPARCworks was a development environment from Sun (circa 1993-1996)
+and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
+Pascal), a debugger, and other tools such as TeamWare (for
+configuration management), MakeTool, etc.
 
-@item ps-lpr-switches
-This should be set to a list of switches required for
-@code{ps-lpr-command} to do its job.
+EOS is the integration of XEmacs with the SPARCworks debugger.  It
+allows one to use an XEmacs frame to view code (complete with
+fontification, etc.), set breakpoints, print variables, etc., while
+using the SPARCworks debugger.
 
-@item ps-print-color-p
-This boolean variable should be set @code{t} if printing will be done in
-color, otherwise it should be set to @code{nil}.
-@end table
+EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
+Again" and was the name used by Sun for its modified version of Lucid
+Emacs (later XEmacs) in the early-mid 90's.  This is documented in
+more detail in the history section of the XEmacs About page.
 
-NOTE: It is an undocumented limitation in XEmacs that postscript
-printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
-window system environment.  It cannot be used outside of X11.
+EOS was replaced around 1996 with a newer graphical development
+environment called Sun WorkShop.  The current status of this is
+unknown.
 
-@node MS Windows, Current Events, Miscellaneous, Top
-@unnumbered 6 XEmacs on MS Windows
+@node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
+@unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
 
-This is part 6 of the XEmacs Frequently Asked Questions list, written by
-Hrvoje Niksic and others.  This section is devoted to the MS Windows
-port of XEmacs.
+Add the switch ---with-workshop to the configure command when building
+XEmacs and put the following in one of your startup files
+(e.g. site-start.el or .emacs):
 
-@menu
+@lisp
+(when (featurep 'tooltalk)
+  (load "tooltalk-macros")
+  (load "tooltalk-util")
+  (load "tooltalk-init"))
+(when (featurep 'sparcworks)
+  (load "sunpro-init")
+  (load "ring")
+  (load "comint")
+  (load "annotations")
+  (sunpro-startup))
+@end lisp
 
-General Info
-* Q6.0.1::	What is the status of the XEmacs port to Windows?
-* Q6.0.2::	What flavors of MS Windows are supported?  
-* Q6.0.3::      Where are the XEmacs on MS Windows binaries?
-* Q6.0.4::	Does XEmacs on MS Windows require an X server to run?
-
-Building XEmacs on MS Windows
-* Q6.1.1::	I decided to run with X.  Where do I get an X server?
-* Q6.1.2::	What compiler do I need to compile XEmacs?
-* Q6.1.3::	How do I compile for the native port?
-* Q6.1.4::	How do I compile for the X port?
-* Q6.1.5::	How do I compile for Cygnus' Cygwin?
-* Q6.1.6::	What do I need for Cygwin?
-
-Customization and User Interface
-* Q6.2.1::	How will the port cope with differences in the Windows user interface?
-* Q6.2.2::	How do I change fonts in XEmacs on MS Windows?
-* Q6.2.3::	Where do I put my @file{.emacs} file?
-
-Miscellaneous
-* Q6.3.1::	Will XEmacs rename all the win32-* symbols to w32-*?
-* Q6.3.2::	What are the differences between the various MS Windows emacsen?
-* Q6.3.3::	What is the porting team doing at the moment?
+If you are not using the latest Workshop (5.0) you have to apply the
+following patch:
 
-@end menu
+@format
+--- /opt/SUNWspro/lib/eserve.el.ORIG    Fri May 14 15:23:26 1999
++++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
+@@@@ -42,7 +42,7 @@@@
+ (defvar running-xemacs nil "t if we're running XEmacs")
+ (defvar running-emacs  nil "t if we're running GNU Emacs 19")
 
-@node Q6.0.1, Q6.0.2, MS Windows, MS Windows
-@unnumberedsec 6.0: General Info
-@unnumberedsubsec Q6.0.1: What is the status of the XEmacs port to Windows?
+-(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
++(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
+     (setq running-xemacs t)
+     (setq running-emacs  t))
+@end format
 
-Is XEmacs really getting ported to MS Windows?  What is the status of the port?
+@node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
+@unnumberedsubsec Q8.2.3: What is/was Energize?
 
-Yes, a group of volunteers actively works on making XEmacs code base
-cleanly compile and run on MS Windows operating systems.  The mailing
-list at @email{xemacs-nt@@xemacs.org} is dedicated to that effort (please use
-the -request address to subscribe).
+The "Energize Programming System" was a C and C++ development environment
+sold by Lucid, Inc.  It was the reason why Lucid Emacs, now XEmacs, was
+created in the first place.  Unfortunately, Lucid went out of business in
+1994.  The rights to sell it in Japan were purchased by INS
+Engineering (which briefly employed Stig Hackvan aka Jonathan
+Stigelman to work on Japanese support for XEmacs, in late 1994 and
+early 1995) and Tartan bought the rights to sell it in the rest of the
+world.  However, INS is not selling Energize at this point and may or
+may not have ever done so; Tartan certainly never did.
 
-At this time, XEmacs on MS Windows is usable, but lacks some of the
-features of XEmacs on UNIX and UNIX-like systems.  Notably,
-internationalization does not work.
+@node Q8.2.4,  , Q8.2.3, Other Packages
+@unnumberedsubsec Q8.2.4: What is Infodock?
 
-@node Q6.0.2, Q6.0.3, Q6.0.1, MS Windows
-@unnumberedsubsec Q6.0.2: What flavors of MS Windows are supported?  The list name implies NT only.
+@uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
+integrated productivity toolset, mainly aimed at technical people,
+hosted at SourceForge.
 
-The list name is misleading, as XEmacs will support both Windows 95,
-Windows 98 and Windows NT.  The MS Windows-specific code is based on
-Microsoft Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
+InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
+the power of Emacs, but with an easier to use and more comprehensive
+menu-based user interface.  The bottom portion of this text describes
+how it differs from XEmacs and GNU Emacs from the Free Software
+Foundation.
 
+InfoDock is aimed at people who want a free, turn-key productivity
+environment.  Although InfoDock is customizable, it is not intended for
+people who like basic versions of Emacs which need to be customized
+extensively for local use; standard Emacs distributions are better for
+such uses.  InfoDock is for those people who want a complete,
+pre-customized environment in one package, which they need not touch
+more than once or twice a year to update to new revisions.
 
-@node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
-@unnumberedsubsec Q6.0.3: Are binary kits available?
+InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
+and Intel Linux systems.  It is intended for use on a color display,
+although most features will work on monochrome monitors.  Simply unpack
+InfoDock according to the instructions in the ID-INSTALL file and you
+are ready to run.
 
-Binary kits are available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binary-kits/win32/} for the
-"plain" MS Windows version.
+The InfoDock Manual is concise, yet sufficient as a user guide for users
+who have never used an Emacs-type editor before.  For users who are
+already familiar with Emacs, it supplements the information in the GNU
+Emacs Manual.
 
-@node Q6.0.4, Q6.1.1, Q6.0.3, MS Windows
-@unnumberedsubsec Q6.0.4: Does XEmacs on MS Windows require an X server to run?
+InfoDock menus are much more extensive and more mature than standard
+Emacs menus.  Each menu offers a @samp{Manual} item which displays
+documentation associated with the menu's functions.
 
-Short answer: No.
+@noindent
+Four types of menubars are provided:
+@enumerate
+@item
+An extensive menubar providing access to global InfoDock commands.
+@item
+Mode-specific menubars tailored to the current major mode.
+@item
+A simple menubar for basic editing to help novices get started with InfoDock.
+@item
+The standard XEmacs menubar.
+@end enumerate
 
-Long answer: XEmacs can be built in several ways in the MS Windows
-environment, some of them requiring an X server and some not.
+Most modes also include mode-specific popup menus.  Additionally, region and
+rectangle popup menus are included.
 
-One is what we call the "X" port -- it requires X libraries to build
-and an X server to run.  Internally it uses the Xt event loop and
-makes use of X toolkits.  Its look is quite un-Windowsy, but it works
-reliably and supports all of the graphical features of Unix XEmacs.
+@samp{Hyperbole}, the everyday information manager, is a core part of
+InfoDock.  This provides context-sensitive mouse keys, a rolodex-type
+contact manager, programmable hypertext buttons, and an autonumbered
+outliner with embedded hyperlink anchors.
 
-The other is what we call the "native" port.  It uses the Win32 API
-and does not require X libraries to build, nor does it require an X to
-run.  In fact, it has no connection with X whatsoever.  At this time,
-the native port obsoletes the X port, providing almost all of its
-features, including support for menus, scrollbars, toolbars, embedded
-images and background pixmaps, frame pointers, etc.  Most of the
-future work will be based on the native port.
+The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
+standard part of InfoDock.
 
-There is also a third special case, the Cygwin port.  It takes
-advantage of Cygnus emulation library under Win32, which enables it to
-reuse much of the Unix XEmacs code base, such as processes and network
-support, or internal select() mechanisms.
+InfoDock saves a more extensive set of user options than other Emacs
+versions.
 
-Cygwin port supports all display types -- TTY, X & MS gui, and can be
-built with support for all three.  If you build with ms gui support
-then the Cygwin version uses the majority of the msw code, which is
-mostly related to display.  If you want to build with X support you
-need X libraries.  If you want to build with tty support you need
-ncurses.  MS gui requires no additional libraries.
+InfoDock inserts a useful file header in many file types, showing the
+author, summary, and last modification time of each file.  A summary
+program can then be used to summarize all of the files in a directory,
+for easy MANIFEST file creation.
 
-Some of the advantages of the Cygwin version are that it:
+Your working set of buffers is automatically saved and restored (if you
+answer yes to a prompt) between InfoDock sessions.
 
-@itemize @bullet
+Refined color choices for code highlighting are provided for both dark and
+light background display frames.
 
-@item integrates well with Cygwin environment for existing Cygwin users;
-@item uses configure so building with different features is very easy;
-@item has process support in X & tty.
+The @kbd{C-z} key prefix performs frame-based commands which parallel the
+@kbd{C-x} key prefix for window-based commands.
 
-@end itemize
+The Smart Menu system is included for producing command menus on dumb
+terminals.
 
-The disadvantage is that it requires several Unix utilities and the
-whole Cygwin environment, whereas the native port requires only a
-suitable MS Windows compiler.  Also, it follows the Unix filesystem and
-process model very closely (some will undoubtedly view this as an
-advantage).
+Lisp libraries are better categorized according to function.
 
-@node Q6.1.1, Q6.1.2, Q6.0.4, MS Windows
-@unnumberedsec 6.1: Building XEmacs on MS Windows
-@unnumberedsubsec Q6.1.1: I decided to run with X.  Where do I get an X server?
+Extensions and improvements to many areas of Emacs are included, such as:
+paragraph filling, mail reading with Rmail, shell handling, outlining, code
+highlighting and browsing, and man page browsing.
 
-Pointers to X servers can be found at
+InfoDock questions, answers and discussion should go to the mail list
 @iftex
 @*
 @end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}; 
+@email{infodock@@infodock.com}.  Use
+@email{infodock-request@@infodock.com} to be added or removed from the
+list.  Always include your InfoDock version number when sending help
+requests.
 
-look for "Where to get an X server".  Also note that, although the above
-page talks about Cygnus gnu-win32 (Cygwin), the information on X servers
-is Cygwin-independent.  You don't have to be running/using Cygwin to use
-these X servers, and you don't have to compile XEmacs under Cygwin to
-use XEmacs with these X servers.  An "X port" XEmacs compiled under
-Visual C++ will work with these X servers (as will XEmacs running on a
-Unix box, redirected to the server running on your PC).
+@node Current Events, Legacy Versions, Other Packages, Top
+@unnumbered 9 What the Future Holds
 
+This is part 9 of the XEmacs Frequently Asked Questions list.  This
+section will change frequently, and (in theory) should contain any
+interesting items that have transpired recently. (But in practice it's
+not getting updated like this.)
 
-@node Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
-@unnumberedsubsec Q6.1.2: What compiler do I need to compile XEmacs?
+This section also contains descriptions of the new features in all the
+recent releases of XEmacs.  For the most part, the information below is
+a synopsis of the more complete information that can be found in the
+file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
+You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
+menu.
 
-You need Visual C++ 4.2 or 5.0, with the exception of the Cygwin port,
-which uses Gcc.
+Information on older versions of XEmacs can be find in @file{ONEWS} in
+the same directory, or @file{OONEWS} for really old versions.
 
+@menu
+9.0: Changes
+* Q9.0.1::    What new features will be in XEmacs soon?
+* Q9.0.2::    What's new in XEmacs 21.4?
+* Q9.0.3::    What's new in XEmacs 21.1?
+* Q9.0.4::    What's new in XEmacs 20.4?
+* Q9.0.5::    What's new in XEmacs 20.3?
+* Q9.0.6::    What's new in XEmacs 20.2?
+@end menu
 
-@node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
-@unnumberedsubsec Q6.1.3: How do I compile for the native port?
+@unnumberedsec 9.0: Changes
 
-Please read the file @file{nt/README} in the XEmacs distribution, which
-contains the full description.
+@node Q9.0.1, Q9.0.2, Current Events, Current Events
+@unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
 
+#### Write me.
 
-@node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
-@unnumberedsubsec Q6.1.4: How do I compile for the X port?
+@node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
+@unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
 
-Again, it is described in @file{nt/README} in some detail.  Basically, you
-need to get X11 libraries from ftp.x.org, and compile them.  If the
-precompiled versions are available somewhere, I don't know of it.
+21.4 was the "stable" version of the 21.2 series, which was considered
+"experimental" throughout its life; thus there were no "official"
+releases at all.  In essence, XEmacs is now following the "alternating"
+scheme of Linux, where at any point there are at least two different
+development branches, one "stable" and one "experimental".  Periodic
+releases happen in both branches, but those in the experimental branch
+are not tested as well, and there's no guarantee they will work at all.
+The experiemental branch is open to any and all code that's acceptable
+to the developers; the stable branch, however, is in general limited
+only to bug fixes, and all contributions are carefully reviewed to make
+sure they will increase and not decrease stability.
 
+21.3 never existed at all; it was decided to follow the Linux scheme
+exactly, where odd-numbered series are experimental and even-numbered
+ones stable.
 
-@node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
-@unnumberedsubsec Q6.1.5: How do I compile for Cygnus' Cygwin?
+The following lists summarizes the essential changes made in this
+version.  For a fuller list, see the @file{NEWS} in the @file{etc}
+directory of the XEmacs distribution, or use @kbd{C-h n} or the
+@samp{Help} menu to view this file inside of XEmacs.
 
-Similar as on Unix; use the usual `configure' and `make' process.
-Some problems to watch out for:
+@unnumberedsubsubsec User-visible changes in XEmacs 21.4
 
 @itemize @bullet
-@item
-make sure HOME is set. This controls where you @file{.emacs} file comes
-from;
 
 @item
-CYGWIN32 needs to be set to tty for process support
-work. e.g. CYGWIN32=tty;
-
+The delete key now deletes forward by default.
 @item
-picking up some other grep or other unix like tools can kill configure;
-
+Shifted motion keys now select text by default.
 @item
-static heap too small, adjust src/sheap-adjust.h to a more positive
-number;
-
+You can now build XEmacs with support for GTK+ widget set.
 @item
-The Cygwin version doesn't understand @file{//machine/path} type paths so you
-will need to manually mount a directory of this form under a unix style
-directory for a build to work on the directory.
-
+~/.xemacs/init.el is now the preferred location for the init
+file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
+file will move to ~/.xemacs/custom.el.)
+@item
+Much-improved sample init.el, showing how to use many useful features.
+@item
+XEmacs support for menu accelerators has been much improved.
+@item
+Default menubar improvements. (Default menubar has many new commands and
+better organization.  The font-menu is now available under MS Windows.)
+@item
+Dialog box improvements, including a real file dialog box. (XEmacs now
+has a proper file dialog box under MS Windows (and GTK)!  The old
+clunky file dialog box is improved.  Keyboard traversal now works
+correctly in MS Windows dialog boxes.  There is a Search dialog box
+available from @samp{Edit->Find...})
+@item
+New buffer tabs.
+@item
+There is a new MS Windows installer, netinstall, ported from Cygwin.
+@item
+The subprocess quote-handling mechanism under Windows is much improved.
+@item
+Printing support now available under MS Windows.
+@item
+Selection improvements. (Kill and yank now interact with the clipboard under Windows.  MS Windows support for selection is now much more robust.  Motif selection support is now more correct (but slower).)
+@item
+Mail spool locking now works correctly.
+@item
+International support changes. (The default coding-priority-list is now
+safer.  International keysyms are now supported under X.  MS Windows
+1251 code page now supported.  Czech, Thai, Cyrillic-KOI8, Vietnamese,
+Ethiopic now supported.  Proper support for words in Latin 3 and Latin
+4.)
+@item
+Help buffers contain hyperlinks, and other changes.
+@item
+The modeline's text is now scrollable.
+@item
+The mouse wheel under MS Windows now functions correctly.
+@item
+Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches.  Interactive searches always respect uppercase characters.)
+@item
+Rectangle functions rewritten to avoid inserting extra spaces.
+@item
+New command `kill-entire-line' that always kills the entire line.
+@item
+Default values correctly stored in minibuffer histories.
+@item
+You can now create "indirect buffers", like in GNU Emacs.
+@item
+Pixel-based scrolling has been implemented.
+@item
+Operation progress can be displayed using graphical widgets.
+@item
+User names following a tilde can now be completed at file name prompts.
+@item
+XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
+@item
+X-Face support is now available under MS Windows.
+@item
+The PostgreSQL Relational Database Management System is now supported.
+@item
+Indentation no longer indents comments that begin at column zero.
+@item
+Face and variable settings can have comments in Customize.
+@item
+New locations for early package hierarchies.
+@item
+The `auto-save' library has been greatly improved.
+@item
+New variable `mswindows-alt-by-itself-activates-menu'.
+@item
+Other init-file-related changes. (Init file in your home directory may be called `.emacs.el'.  New command-line switches -user-init-file and -user-init-directory.)
+@item
+Etags changes.  See @file{NEWS} for full details.
 @end itemize
 
-@node Q6.1.6, Q6.2.1, Q6.1.5, MS Windows
-@unnumberedsubsec Q6.1.6: What do I need for Cygwin?
-
-You can find the Cygwin tools and compiler at:
-
-@uref{http://sourceware.cygnus.com/cygwin/}
-
-You will need version b19 or later.
-
-You will also need the X libraries.  There are libraries at
-@iftex
-@*
-@end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}, but
-these are not b19 compatible.  You can get b19 X11R6.3 binaries, as
-well as pre-built ncurses and graphic libraries, from:
-
-@uref{ftp://ftp.parallax.co.uk/pub/andyp/}.
-
-
-@node Q6.2.1, Q6.2.2, Q6.1.6, MS Windows
-@unnumberedsec 6.2: Customization and User Interface
-@unnumberedsubsec Q6.2.1: How will the port cope with differences in the Windows user interface?
-
-XEmacs (and Emacs in general) UI is pretty 
-different from what is expected of a typical MS Windows program.  How will
-the MS Windows port cope with it?
-
-Fortunately, Emacs is also one of the most configurable editor beasts
-in the world.  The MS Windows "look and feel" (mark via shift-arrow,
-self-inserting deletes region, etc.) can be easily configured via
-various packages distributed with XEmacs.  The `pending-delete'
-package is an example of such a utility.
-
-In future versions, some of these packages might be turned on by
-default in the MS Windows environment.
-
-
-@node Q6.2.2, Q6.2.3, Q6.2.1, MS Windows
-@unnumberedsubsec Q6.2.2: How do I change fonts in XEmacs on MS Windows?
-
-You can change font manually, but not from the menubar, yet. For
-example:
-
-@display
-    (set-face-font 'default "Lucida Console:Regular:10")
-    (set-face-font 'modeline "MS Sans Serif:Regular:10")
-@end display
-
-
-@node Q6.2.3, Q6.3.1, Q6.2.2, MS Windows
-@unnumberedsubsec Q6.2.3: Where do I put my @file{.emacs} file?
-
-If the HOME environment variable is set, @file{.emacs} will be looked for
-there.  Else the directory defaults to `c:\'.
-
-@node Q6.3.1, Q6.3.2, Q6.2.3, MS Windows
-@unnumberedsec 6.3: Miscellaneous
-@unnumberedsubsec Q6.3.1: Will XEmacs rename all the win32-* symbols to w32-*?
+@unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
 
-In his flavor of Emacs 20, Richard Stallman has renamed all the win32-*
-symbols to w32-*.  Will XEmacs do the same?
+Not yet written.
 
-We consider such a move counter-productive, thus we will not use the
-`w32' prefix.  However, we do recognize that Win32 name is little more
-than a marketing buzzword (will it be Win64 in the next release?), so
-we decided not to use it.  Using `windows-' would be wrong because the
-term is too generic, which is why we settled on a compromise
-`mswindows' term.
+@c APA: Texi2html produces invalid HTML from an empty list of bullets!
+@c Please uncomment following list when it does contain bullets.
+@c @itemize @bullet
+@c @end itemize
 
-Thus all the XEmacs variables and functions directly related to Win32
-are prefixed `mswindows-'.  The user-variables shared with NT Emacs
-will be provided as compatibility aliases.
+@node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
+@unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
 
-Architectural note: We believe that there should be a very small
-number of window-systems-specific variables, and will try to provide
-generic interfaces whenever possible.
+21.1 was the "stable" version of "experimental" 21.0 series.
+@xref{Q9.0.2, What's new in XEmacs 21.4?}.
 
+The following lists summarizes the essential changes made in this
+version.  For a fuller list, see the @file{NEWS} in the @file{etc}
+directory of the XEmacs distribution, or use @kbd{C-h n} or the
+@samp{Help} menu to view this file inside of XEmacs.
 
-@node Q6.3.2, Q6.3.3, Q6.3.1, MS Windows
-@unnumberedsubsec Q6.3.2: What are the differences between the various MS Windows emacsen?
-
-XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
-Could you briefly explain the differences between them?
-
-Here is a recount of various Emacs versions running on MS Windows:
+@unnumberedsubsubsec User-visible changes in XEmacs 21.1
 
 @itemize @bullet
 
-@item 
-Win-Emacs
-
-@itemize @minus
-
 @item
-Win-Emacs is a port of Lucid Emacs 19.6 to MS Windows using X
-compatibility libraries.  Win-Emacs has been written by Ben Wing.  The
-MS Windows code has not made it back to Lucid Emacs, which left Win-Emacs
-pretty much dead for our purposes.  Win-Emacs used to be available at
-Pearlsoft, but not anymore, since Pearlsoft went out of business.
-@end itemize
+XEmacs is now supported under Microsoft Windows 95/98 and Windows
+NT/2000/XP operating systems.  To discuss Windows-specific issues,
+subscribe to the mailing list at
+@email{xemacs-winnt-request@@xemacs.org}.
 
 @item
-GNU Emacs for DOS
-
-@itemize @minus  
+XEmacs has been unbundled into constituent installable packages.
 
 @item
-GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
-port of Gcc).  Such an Emacs is heavily underfeatured, because it does
-not supports long file names, lacks proper subprocesses support, and
-is far too big compared to typical DOS editors.
-@end itemize
+@strong{Other notable changes}: The @samp{Options} menu has been ported to
+Custom; XEmacs now is able to choose X visuals and use private
+colormaps; You can drag the vertical divider of "horizontally"
+(side-by-side) split windows.
 
 @item
-GNU Emacs compiled with Win32
+@strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
+integers and 32-bit pointers (previously, it was 28-bit integers and
+pointers); XEmacs can be built with LDAP support; @file{dir} files can be
+removed in the Info subsystem, and will be regenerated on-the-fly.
 
-@itemize @minus  
+@item
+@strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
 
 @item
-Starting with version 19.30, it has been possible to compile GNU Emacs
-under MS Windows using the DJGPP compiler and X libraries.  The result
-is is very similar to GNU Emacs compiled under MS DOS, only it
-supports longer file names, etc.  This "port" is similar to the "X"
-flavor of XEmacs on MS Windows.
-@end itemize
+@strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
+@file{gnuclient}.  See @file{NEWS} for full details.
 
 @item
-NT Emacs
+@strong{New commands, variables and functions}:
+@code{center-to-window-line} (like @code{recenter} but doesn't force a
+redisplay); variable @code{user-full-name} (customize what your full
+name looks like in mail); @kbd{M-x customize-changed-options} (customize
+options whose default values changes because you upgraded your XEmacs);
+@kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
+new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
+doesn't delete the char searched for); commands to store, retrieve and
+increment numbers in registers, useful for macros.
 
-@itemize @minus  
+@item
+@strong{Changes to commands, variables, and functions}: @kbd{M-x
+query-replace} and friends operate only on the region when it's active;
+@code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
+searches exact tag matches before inexact ones; function
+@code{user-full-name} with no arguments returns the var
+@code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
+the result in the current buffer.
 
 @item
-NT Emacs is a version of GNU Emacs modified to compile and run under
-MS MS Windows 95 and NT using the native Win32 API.  As such, it is close
-in spirit to the XEmacs "native" port.
+@strong{Other changes}: Under X, new application class @samp{XEmacs};
+byte-compilation of user-specs now works.
 
 @item
-NT Emacs has been written by Geoff Voelker, and more information can be
-found at 
-@iftex
-@*
-@end iftex
-@uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
+@strong{XEmacs/Mule (internationalization) changes}: Mule support now
+works on TTY's; Egg/SJ3 input method now officially supported (Quail and
+Egg/Skk already available through LEIM since 20.3); localized Japanese
+menubars if XEmacs is built with the right support.
 
 @end itemize
 
+@unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
+
+@itemize @bullet
+
 @item
-XEmacs
+@strong{Specifier changes}: The window locale now has a higher
+precedence than the buffer locale when instantiating; new macro
+@code{let-specifier}; new specifiers
+@code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
+@code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
+@code{vertical-divider-always-visible-p},
+@code{vertical-divider-shadow-thickness},
+@code{vertical-divider-line-width}, @code{vertical-divider-spacing};
+specifiers and symbols whose value is a specifier allowed as modeline
+specifications.
 
-@itemize @minus  
+@item
+@strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
+prevents any attempt to permanently change the selected frame; new
+function @code{focus-frame} sets the window system focus a frame; new
+special forms @code{save-selected-frame} and @code{with-selected-frame}.
 
 @item
-Beginning with XEmacs 19.12, XEmacs' architecture has been redesigned
-in such a way to allow clean support of multiple window systems.  At
-this time the TTY support was added, making X and TTY the first two
-"window systems" XEmacs supported.  The 19.12 design is the basis for
-the current native MS Windows code.
+@strong{Window function changes}: @code{select-window} now has optional
+argument @var{NORECORD} to inhibit recording a buffer change;
+@code{vertical-motion} now correctly handles optional @var{WINDOW}
+argument and has new optional argument @var{PIXELS}, to have the
+returned values be in pixels; new function
+@code{vertical-motion-pixels}; new functions
+@code{window-text-area-pixel-@{width,height,edges@}}; new functions
+@code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
+function @code{window-displayed-text-pixel-height}.
 
 @item
-Some time during 1997, David Hobley (soon joined by Marc Paquette)
-imported some of the NT-specific portions of GNU Emacs, making XEmacs
-with X support compile under Windows NT, and creating the "X" port.
+@strong{Other function changes}: Arithmetic comparison functions
+@code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
+arguments; hashtables now have a consistent read/print syntax; keyword
+symbols cannot be set to a value other than themselves; @code{concat} no
+longer accepts integer arguments; new function @code{string}, like
+@code{list}, @code{vector}, etc.; new function @code{temp-directory}
+(OS-independent way to get a temp directory); @code{load-average} has
+optional argument @var{USE-FLOATS}; @code{make-event} implemented
+completely; new function @code{function-interactive} (returns a
+function's interactive spec); new functions @code{lmessage},
+@code{lwarn} (printf-like versions of @code{display-wessage},
+@code{display-warning}); new keyword @code{:version} to
+@code{defcustom}.
 
 @item
-Several months later, Jonathan Harris sent out initial patches to use
-the Win32 API, thus creating the native port.  Since then, various
-people have contributed, including Kirill M. Katsnelson (contributed
-support for menubars, subprocesses and network, as well as loads of
-other code), Andy Piper (ported XEmacs to Cygwin environment,
-contributed Windows unexec, Windows-specific glyphs and toolbars code,
-and more), Jeff Sparkes (contributed scrollbars support) and many
-others.
+@strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
+available, it will be used (better performance on libc6 Linux systems);
+tracking line-numbers in modeline is now efficient; profiling records a
+call-count of all called functions, retrievable through
+@code{profile-call-count-results}.
 
-@end itemize
+@item
+@strong{Startup and path searching}: code to assemble paths at startup
+rewritten for new package system; new function @code{split-path} (splits
+by @code{path-separator}); @code{Info-default-directory-list} obsolete,
+use @code{Info-directory-list} instead; site-lisp is deprecated and no
+longer on the load-path by default.
 
 @end itemize
 
+@node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
+@unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
 
-@node Q6.3.3, , Q6.3.2, MS Windows
-@unnumberedsubsec Q6.3.3: What is the porting team doing at the moment?
-
-The porting team is continuing work on the MS Windows-specific code.
+XEmacs 20.4 is a bugfix release with no user-visible changes.
+@c Filled in from NEWS file of 20.5-b33
 
+@node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
+@unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
 
-@node Current Events,  , MS Windows, Top
-@unnumbered 7 What the Future Holds
+XEmacs 20.3 was released in November 1997. It contains many bugfixes,
+and a number of new features, including Autoconf 2 based configuration,
+additional support for Mule (Multi-language extensions to Emacs), many
+more customizations, multiple frames on TTY-s, support for multiple info
+directories, an enhanced gnuclient, improvements to regexp matching,
+increased MIME support, and many, many synches with GNU Emacs 20.
 
-This is part 7 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.
+The XEmacs/Mule support has been only seriously tested in a Japanese
+locale, and no doubt many problems still remain.  The support for
+ISO-Latin-1 and Japanese is fairly strong.  MULE support comes at a
+price---about a 30% slowdown from 19.16.  We're making progress on
+improving performance and XEmacs 20.3 compiled without Mule (which is
+the default) is definitely faster than XEmacs 19.16.
 
-@menu
-* Q7.0.1::      What is new in 20.2?
-* Q7.0.2::      What is new in 20.3?
-* Q7.0.3::      What is new in 20.4?
-* Q7.0.4::      Procedural changes in XEmacs development.
-@end menu
+XEmacs 20.3 is the first non-beta v20 release, and will be the
+basis for all further development.
 
-@node Q7.0.1, Q7.0.2, Current Events, Current Events
-@unnumberedsec 7.0: Changes
-@unnumberedsubsec Q7.0.1: What is new in 20.2?
+@node Q9.0.6,  , Q9.0.5, Current Events
+@unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
 
 The biggest changes in 20.2 include integration of EFS (the next
 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
@@ -6591,65 +8575,83 @@ customize}.
 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
 considered unstable.
 
-@node Q7.0.2, Q7.0.3, Q7.0.1, Current Events
-@unnumberedsubsec Q7.0.2: What is new in 20.3?
+For older news, see the file @file{ONEWS} in the @file{etc} directory of
+the XEmacs distribution.
 
-XEmacs 20.3 was released in November 1997. It contains many bugfixes,
-and a number of new features, including Autoconf 2 based configuration,
-additional support for Mule (Multi-language extensions to Emacs), many
-more customizations, multiple frames on TTY-s, support for multiple info
-directories, an enhanced gnuclient, improvements to regexp matching,
-increased MIME support, and many, many synches with GNU Emacs 20.
+@node Legacy Versions,  , Current Events, Top
+@unnumbered 10 New information about old XEmacsen
 
-The XEmacs/Mule support has been only seriously tested in a Japanese
-locale, and no doubt many problems still remain.  The support for
-ISO-Latin-1 and Japanese is fairly strong.  MULE support comes at a
-price -- about a 30% slowdown from 19.16.  We're making progress on
-improving performance and XEmacs 20.3 compiled without Mule (which is
-the default) is definitely faster than XEmacs 19.16.
+This is part 10 of the XEmacs Frequently Asked Questions list.  It will
+occasionally be updated to reflect new information about versions which
+are no longer being revised by the XEmacs Project.  The primary purpose
+is advice on compatibility of older XEmacsen with new packages and
+updated versions of packages, but bug fixes (which will not be applied
+to released XEmacsen, but users can apply themselves) are also accepted.
 
-XEmacs 20.3 is the first non-beta v20 release, and will be the
-basis for all further development.
+@menu
+10.0: XEmacs 21.1
+* Q10.0.1::   Gnus 5.10 won't display smileys in XEmacs 21.1.
+* Q10.0.2::   XEmacs won't start on Windows in XEmacs 21.1.
+@end menu
 
-@node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
-@unnumberedsubsec Q7.0.3: What's new in XEmacs 20.4?
+@unnumberedsec 10.0: XEmacs 21.1
 
-XEmacs 20.4 is a bugfix release with no user-visible changes.
-@c Filled in from NEWS file of 20.5-b33
+@node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions
+@unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
 
+@email{eeide@@cs.utah.edu, Eric Eide} wrote:
 
-@node Q7.0.4,  , Q7.0.3, Current Events
-@unnumberedsubsec Q7.0.4: Procedural changes in XEmacs development.
+@quotation
+Previously I wrote:
 
-@enumerate
-@item
-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
-@email{xemacs-beta-request@@xemacs.org} with @samp{subscribe} as the
-BODY of the message to join the list.  Please note this is a developers
-mailing list for people who have an active interest in the development
-process.
+    Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
+    Eric> any smileys :-(.
 
-The discussion of NT XEmacs development is taking place on a separate
-mailing list.  Send mail to
-@iftex
-@*
-@end iftex
-@email{xemacs-nt-request@@xemacs.org} to
-subscribe.
+After a bit of sleuthing, I discovered the essence of the problem.
+For me, the form:
 
-@item
-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.
+@lisp
+    	(with-temp-buffer
+    	  (insert-file-contents "foo.xpm")
+    	  (buffer-string))
+@end lisp
 
-XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
-the collected bugfixes.
+returns the empty string.  This is because something somewhere
+replaces the XPM data with a glyph --- I haven't figured out where
+this occurs.
+@end quotation
 
-@item
-As of December 1996, @email{steve@@xemacs.org, Steve Baur} has become
-the lead maintainer of XEmacs.
-@end enumerate
+@email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
+
+@quotation
+Do this:
+
+@lisp
+    (setq format-alist nil)
+@end lisp
+
+The image-mode stuff is gone from format-alist in the 21.4
+branch, praise be.
+@end quotation
+
+@node Q10.0.2,  , Q10.0.1, Legacy Versions
+@unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1.
+
+XEmacs relies on a process called "dumping" to generate a working
+executable. Under MS-Windows this process effectively fixes the memory
+addresses of information in the executable. When XEmacs starts up it tries
+to reserve these memory addresses so that the dumping process can be
+reversed -- putting the information back at the correct addresses.
+Unfortunately some .DLLs (for instance the soundblaster driver) occupy
+memory addresses that can conflict with those needed by the dumped XEmacs
+executable. In this instance XEmacs will fail to start without any
+explanation. Note that this is extremely machine specific.
+
+21.1.10 includes a fix for this that makes more intelligent guesses
+about which memory addresses will be free, and this should cure the
+problem for most people.  21.4 implements "portable dumping", which
+eliminates the problem altogether.  We recommend you use the 21.4
+binaries, but you can use the 21.1 binaries if you are very paranoid
+about stability.  @xref{Q1.1.2, Are binaries available?}.
 
 @bye