xemacs-beta: man/xemacs-faq.texi comparison

comparison man/xemacs-faq.texi @ 2559:0e04aba50e0b

[xemacs-hg @ 2005-02-04 02:51:20 by ben] More FAQ updates; incorporate top-level files xemacs-faq.texi: Flesh out intro section on packages and section on installing packages. Incorporate README, README.packages, BUGS, etc/PACKAGES. Various other changes.

author	ben
date	Fri, 04 Feb 2005 02:51:21 +0000
parents	b7b90f750a78
children	640e02d61e7f

comparison

equal deleted inserted replaced

-:4e9b54b828ac
+:0e04aba50e0b
 @setchapternewpage off
 @c %**end of header
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/01/31 20:08:48 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/02/04 02:51:21 $
 @sp 1
 @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>
 wonder, does texinfo-master-menu generate the detailmenu from the
 individual menus or vice-versa or neither?)
 Then,
-1. Use the Lisp line below to get the spacing correct for the Q#.#.#
+6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
-menu entries.
-(set (make-local-variable 'texinfo-column-for-description) 14)
-2. 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. Copy the whole detailmenu beforehand.
+1. Use the Lisp line below to get the spacing correct for the Q#.#.#
-2. Run C-u C-C C-u m to fix up the nodes.
+menu entries.
-3. Run `fix-main-menu' and `fix-omitted-menu-lines'.
-4. Check the new detailmenu carefully to see if anything is screwed up
+(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.
-5. If so, paste back the appropriate sections and fix up the corresponding
+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)
-(search-forward "@menu")
+(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)
 (indent-to-column 26)))))
 (defun fix-omitted-menu-lines ()
 (interactive)
 (save-excursion
-(loop for x from 1 to 7 do
+(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)))
-	(search-backward "@menu")
+	(re-search-backward "^@menu")
 	(forward-line 1)
-	(unless (looking-at "[0-9].0:")
+	(unless (looking-at "[0-9]+.0:")
 	  (insert line)
 	  (insert "\n"))
 	(goto-char (point-min))
-	(search-forward "@menu")
+	(re-search-forward "^@menu")
 	(search-forward (format "Q%d.0.1:" x))
 	(forward-line -1)
-	(unless (looking-at "[0-9].0:")
+	(unless (looking-at "[0-9]+.0:")
-	  (insert line)
+	  (insert "\n")
-	  (insert "\n"))))))
+	  (insert line))))))
 *****************************************
 *****            Other work         *****
 *****************************************
 * 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.2::    Where are the mailing lists archived?
+* Q1.4.3::    Where are the mailing lists archived?
-* Q1.4.3::    How can I get two instances of info?
+* Q1.4.4::    How can I get two instances of info?
-* Q1.4.4::    How do I add new Info directories?
+* 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::    Which external packages are there?
+* 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.8::    Does XEmacs support Unicode?
 * Q1.8.9::    How does XEmacs display Unicode?
 2 Installation and Troubleshooting
-2.0: Installation (General), Packages
+2.0: Installation (General)
-* Q2.0.1::    How do I install the packages?
+* Q2.0.1::    How do I build and install XEmacs?
-* Q2.0.2::    I don't need no steenkin' packages.  Do I?
+* Q2.0.2::    Where do I find external libraries?
-* Q2.0.3::    Where do I find external libraries?
+* Q2.0.3::    How do I specify the paths that XEmacs uses for finding files?
-* Q2.0.4::    How do I specify the paths that XEmacs uses for finding files?
+* Q2.0.4::    Running XEmacs without installing
-* Q2.0.5::    Running XEmacs without installing
+* Q2.0.5::    XEmacs is too big
-* Q2.0.6::    XEmacs is too big
-* Q2.0.7::    EFS fails with "500 AUTH not understood" (NEW)
+2.1: Package Installation
+* Q2.1.1::    How do I install the packages?
-2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
+* Q2.1.2::    Can I install the packages individually?
-* Q2.1.1::    Libraries in non-standard locations
+* Q2.1.3::    Can I install the packages automatically?
-* Q2.1.2::    Why can't I strip XEmacs?
+* Q2.1.4::    Can I upgrade or remove packages?
+* Q2.1.5::    Which packages to install?
-2.2: Windows Installation (Windows, Cygwin, MinGW)
+* Q2.1.6::    Can you describe the package location process in more detail?
-* Q2.2.1::    What exactly are all the different ways to build XEmacs under Windows?
+* Q2.1.7::    EFS fails with "500 AUTH not understood"
-* Q2.2.2::    What compiler/libraries do I need to compile XEmacs?
-* Q2.2.3::    How do I compile the native port?
+2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
-* Q2.2.4::    What do I need for Cygwin?
+* Q2.2.1::    Libraries in non-standard locations
-* Q2.2.5::    How do I compile under Cygwin?
+* Q2.2.2::    Why can't I strip XEmacs?
-* Q2.2.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q2.2.7::    How do I compile with X support?
+2.3: Windows Installation (Windows, Cygwin, MinGW)
-* Q2.2.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
+* 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?
-2.3: General Troubleshooting
+* Q2.3.3::    How do I compile the native port?
-* Q2.3.1::    Help!  XEmacs just crashed on me!
+* Q2.3.4::    What do I need for Cygwin?
-* Q2.3.2::    XEmacs crashes and I compiled it myself.
+* Q2.3.5::    How do I compile under Cygwin?
-* Q2.3.3::    How to debug an XEmacs problem with a debugger
+* Q2.3.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q2.3.4::    I get a cryptic error message when trying to do something.
+* Q2.3.7::    How do I compile with X support?
-* Q2.3.5::    XEmacs hangs when I try to do something.
+* Q2.3.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
-* Q2.3.6::    I get an error message when XEmacs is running in batch mode.
-* Q2.3.7::    The keyboard or mouse is not working properly, or I have some other event-related problem.
+2.4: General Troubleshooting
-* Q2.3.8::    @kbd{C-g} doesn't work for me.  Is it broken?
+* Q2.4.1::    How do I deal with bugs or with problems building, installing, or running?
-* Q2.3.9::    How do I debug process-related problems?
+* Q2.4.2::    Help!  XEmacs just crashed on me!
-* Q2.3.10::   XEmacs is outputting lots of X errors.
+* Q2.4.3::    XEmacs crashes and I compiled it myself.
-* Q2.3.11::   After upgrading, XEmacs won't do `foo' any more!
+* 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.
-2.4: Startup-Related Problems
+* Q2.4.6::    XEmacs hangs when I try to do something.
-* Q2.4.1::    XEmacs cannot connect to my X Terminal!
+* Q2.4.7::    I get an error message when XEmacs is running in batch mode.
-* Q2.4.2::    XEmacs won't start on Windows.
+* Q2.4.8::    The keyboard or mouse is not working properly, or I have some other event-related problem.
-* Q2.4.3::    XEmacs won't start without network.
+* Q2.4.9::    @kbd{C-g} doesn't work for me.  Is it broken?
-* Q2.4.4::    Startup warnings about deducing proper fonts?
+* Q2.4.10::   How do I debug process-related problems?
-* Q2.4.5::    Warnings from incorrect key modifiers.
+* Q2.4.11::   XEmacs is outputting lots of X errors.
-* Q2.4.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+* 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?
 * 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.1.1::    What are bignums, ratios, and bigfloats in Lisp?
+* Q7.2.1::    What are bignums, ratios, and bigfloats in Lisp?
-* Q7.1.2::    XEmacs segfaults when I use very big numbers!
+* Q7.2.2::    XEmacs segfaults when I use very big numbers!
-* Q7.1.3::    Bignums are really slow!
+* Q7.2.3::    Bignums are really slow!
-* Q7.1.4::    Equal bignums don't compare as equal!  What gives?
+* 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?
 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
 @node Introduction, Installation, Top, Top
 @unnumbered 1 Introduction, Policy, Credits
 * 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.2.13::
 * 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.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::    How can I get two instances of info?
+* Q1.4.3::    Where are the mailing lists archived?
-* Q1.4.4::    How do I add new Info directories?
+* 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.4.5::
 * 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::    Which external packages are there?
+* 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?
 full color support on a color-capable character terminal.
 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
+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.
 For problems with particular machines and versions of Unix, see the
 @file{PROBLEMS} file.
 Much effort has gone into making XEmacs work on as many different
 machines, configurations, and compilers as possible.
 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.2.7}.  TTY and Win32 GUI
+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 &
 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}.
 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
-@unnumberedsubsec Q1.2.9: Is there a port of XEmacs to the Macintosh?
+@unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
-Yes.
+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
-XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
+particularly interested in patches for these platforms, as they would
-will not feel very much like a Mac application as it has no Mac-specific
+introduce huge amounts of code clutter due to the woefully
-code in it.
+underfeatured nature of these systems. (See GNU Emacs for a port to
+MS-DOS.)
-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}.
 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
-@unnumberedsubsec Q1.2.10: Is there a port of XEmacs to MS-DOS?
+@unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
-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.
-@node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
-@unnumberedsubsec Q1.2.11: Is there a port of XEmacs to OS/2?
 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
 working on it.
-@node Q1.2.12, Q1.2.13, Q1.2.11, Introduction
+@node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
-@unnumberedsubsec Q1.2.12: Is there a port of XEmacs to NextStep?
+@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.
-@node Q1.2.13, Q1.3.1, Q1.2.12, Introduction
+@node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
-@unnumberedsubsec Q1.2.13: Is there a port of XEmacs to VMS?
+@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.13, Introduction
+@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
 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
+is an open list for bug reports about beta versions of XEmacs.  This
-reports about beta versions of XEmacs.  This includes the bug
+includes the bug reports themselves, by both users and developers, as
-reports themselves, by both users and developers, as well as
+well as queries, follow-ups, and discussions further determining their
-queries, follow-ups, and discussions further determining their
+nature and status.  This is the primary channel for this kind of
-nature and status.  This is the primary channel for this kind
+discussion; related code changes will usually not be applied until
-of discussion; related code changes will usually not be
+they have been discussed here.  When such discussions touch on
-applied until they have been discussed here.  When such
+significant changes to the code (in particular, structural changes),
-discussions touch on significant changes to the code (in
+or on changes to API's or external functionality, they should be moved
-particular, structural changes), or on changes to API's or
+to @samp{xemacs-design}.  Requests and proposals for non-bug-related
-external functionality, they should be moved to
+changes do not belong on @samp{xemacs-beta}, and should be sent to
-@samp{xemacs-design}.  Requests and proposals for
+@samp{xemacs-design} instead.
-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.
 the line @samp{subscribe} in the body of the message.
 Be prepared to get your hands dirty, as beta testers are expected to
 identify problems as best they can.
-@node Q1.5.3, Q1.6.1, Q1.5.2, Introduction
+@node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
 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.
 (not that we're necessarily requiring you to write the code, but we can
 always hope :)
 @end quotation
+@node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
+@unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
+First, get yourself set up under CVS so that you can access the CVS
+repositories containing the XEmacs sources and the XEmacs packages.
+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)
+@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.
+@item
+Package source is in @file{<xsrc-top>/package-src}.
+@item
+Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
+@file{<xsrc-top>/mule-packages}.
+@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.
+@item
+Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
+@itemize @bullet
+@item
+@file{<xsrc-top>/working} (the workspace you're actively working on,
+periodically synched up with the latest trunk)
+@item
+@file{<xsrc-top>/stable} (for making changes to the stable version of
+XEmacs, which sits on a branch)
+@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).
+@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.)
+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
+@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
+@item
+@file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
+web site.
+@item
+@file{<xsrc-top>/in-patches} for patches received from email and saved
+to files.
+@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.
+@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.
+@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.
+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.
+The file @file{Makefile.in} is a template used by @file{configure} to create
+@file{Makefile}.
+There are several subdirectories:
+@enumerate
+@item
+@file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
+primitives, the redisplay code, and some basic editing functions).
+@item
+@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
+@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
 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
-@node Q1.6.1, Q1.6.2, Q1.5.3, Introduction
+@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
 that often result.  Mail your questions to
 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
 @unnumberedsec 1.7: External Packages
-@node Q1.7.1, Q1.8.1, Q1.6.6, Introduction
+@node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
-@unnumberedsubsec Q1.7.1: Which external packages are there?
+@unnumberedsubsec Q1.7.1: What is the package system?
+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.
+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.
+@xref{Q2.1.1}, for more info on how to download and install the packages.
+@node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
+@unnumberedsubsec Q1.7.2: Which external packages are there?
 @subheading Normal Packages
 A very broad collection of elisp packages.
 @item skk
 Another Japanese Language Input Method.  Can be used without a
 separate process running as a dictionary server.
 @end table
+@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?
+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_.
+@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?
+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
+	M-x package-get-package-provider RET thingatpt RET
+@end example
+which will return something like: @samp{(fsf-compat "1.08").}
 @unnumberedsec 1.8: Internationalization
-@node Q1.8.1, Q1.8.2, Q1.7.1, Introduction
+@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)?
 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
 This is part 2 of the XEmacs Frequently Asked Questions list.  This
 section is devoted to Installation, Maintenance and Troubleshooting.
 @menu
-2.0: Installation (General), Packages
+2.0: Installation (General)
-* Q2.0.1::    How do I install the packages?
+* Q2.0.1::    How do I build and install XEmacs?
-* Q2.0.2::    I don't need no steenkin' packages.  Do I?
+* Q2.0.2::    Where do I find external libraries?
-* Q2.0.3::    Where do I find external libraries?
+* Q2.0.3::    How do I specify the paths that XEmacs uses for finding files?
-* Q2.0.4::    How do I specify the paths that XEmacs uses for finding files?
+* Q2.0.4::    Running XEmacs without installing
-* Q2.0.5::    Running XEmacs without installing
+* Q2.0.5::    XEmacs is too big
-* Q2.0.6::    XEmacs is too big
-* Q2.0.7::    EFS fails with "500 AUTH not understood" (NEW)
+2.1: Package Installation
+* Q2.1.1::    How do I install the packages?
-2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
+* Q2.1.2::    Can I install the packages individually?
-* Q2.1.1::    Libraries in non-standard locations
+* Q2.1.3::    Can I install the packages automatically?
-* Q2.1.2::    Why can't I strip XEmacs?
+* Q2.1.4::    Can I upgrade or remove packages?
+* Q2.1.5::    Which packages to install?
-2.2: Windows Installation (Windows, Cygwin, MinGW)
+* Q2.1.6::    Can you describe the package location process in more detail?
-* Q2.2.1::    What exactly are all the different ways to build XEmacs under Windows?
+* Q2.1.7::    EFS fails with "500 AUTH not understood"
-* Q2.2.2::    What compiler/libraries do I need to compile XEmacs?
-* Q2.2.3::    How do I compile the native port?
+2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
-* Q2.2.4::    What do I need for Cygwin?
+* Q2.2.1::    Libraries in non-standard locations
-* Q2.2.5::    How do I compile under Cygwin?
+* Q2.2.2::    Why can't I strip XEmacs?
-* Q2.2.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q2.2.7::    How do I compile with X support?
+2.3: Windows Installation (Windows, Cygwin, MinGW)
-* Q2.2.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
+* 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?
-2.3: General Troubleshooting
+* Q2.3.3::    How do I compile the native port?
-* Q2.3.1::    Help!  XEmacs just crashed on me!
+* Q2.3.4::    What do I need for Cygwin?
-* Q2.3.2::    XEmacs crashes and I compiled it myself.
+* Q2.3.5::    How do I compile under Cygwin?
-* Q2.3.3::    How to debug an XEmacs problem with a debugger
+* Q2.3.6::    How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q2.3.4::    I get a cryptic error message when trying to do something.
+* Q2.3.7::    How do I compile with X support?
-* Q2.3.5::    XEmacs hangs when I try to do something.
+* Q2.3.8::    Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
-* Q2.3.6::    I get an error message when XEmacs is running in batch mode.
-* Q2.3.7::    The keyboard or mouse is not working properly, or I have some other event-related problem.
+2.4: General Troubleshooting
-* Q2.3.8::    @kbd{C-g} doesn't work for me.  Is it broken?
+* Q2.4.1::    How do I deal with bugs or with problems building, installing, or running?
-* Q2.3.9::    How do I debug process-related problems?
+* Q2.4.2::    Help!  XEmacs just crashed on me!
-* Q2.3.10::   XEmacs is outputting lots of X errors.
+* Q2.4.3::    XEmacs crashes and I compiled it myself.
-* Q2.3.11::   After upgrading, XEmacs won't do `foo' any more!
+* 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.
-2.4: Startup-Related Problems
+* Q2.4.6::    XEmacs hangs when I try to do something.
-* Q2.4.1::    XEmacs cannot connect to my X Terminal!
+* Q2.4.7::    I get an error message when XEmacs is running in batch mode.
-* Q2.4.2::    XEmacs won't start on Windows.
+* Q2.4.8::    The keyboard or mouse is not working properly, or I have some other event-related problem.
-* Q2.4.3::    XEmacs won't start without network.
+* Q2.4.9::    @kbd{C-g} doesn't work for me.  Is it broken?
-* Q2.4.4::    Startup warnings about deducing proper fonts?
+* Q2.4.10::   How do I debug process-related problems?
-* Q2.4.5::    Warnings from incorrect key modifiers.
+* Q2.4.11::   XEmacs is outputting lots of X errors.
-* Q2.4.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+* 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
-@unnumberedsec 2.0: Installation (General), Packages
+@unnumberedsec 2.0: Installation (General)
 @node Q2.0.1, Q2.0.2, Installation, Installation
-@unnumberedsubsec Q2.0.1: How do I install the packages?
+@unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
-Many people really liked the old way that packages were bundled and do
+See the file @file{etc/NEWS} for information on new features and other
-not want to mess with packages at all.  You can grab all the packages at
+user-visible changes since the last version of XEmacs.
-once like you used to with old XEmacs versions.  Download the file
+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.
+See the file @file{nt/README} for instructions on building XEmacs for
+Microsoft Windows.
+@xref{Q2.1.1}, for the installation of (essential) add on packages.
+@node Q2.0.2, Q2.0.3, Q2.0.1, Installation
+@unnumberedsubsec Q2.0.2: Where do I find external libraries?
+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}.
+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.
+@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?
+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 Q2.0.4, Q2.0.5, Q2.0.3, Installation
+@unnumberedsubsec Q2.0.4: Running XEmacs without installing
+How can I just try XEmacs without installing it?
+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.
+A good method is to make a shell alias for xemacs:
+@example
+alias xemacs=/src/xemacs-21.5/src/xemacs
+@end example
+(You will obviously use whatever directory you downloaded the source
+tree to instead of @file{/src/xemacs-21.5}).
+This will let you run XEmacs without massive copying.
+@node Q2.0.5, Q2.1.1, Q2.0.4, Installation
+@unnumberedsubsec Q2.0.5: XEmacs is too big
+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.
+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.
+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.
+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.
+Another method is to do @code{M-x package-get-delete-package}.
+@unnumberedsec 2.1: Package Installation
+@node Q2.1.1, Q2.1.2, Q2.0.5, Installation
+@unnumberedsubsec Q2.1.1: How do I install the packages?
+There are three ways to install the packages.
+@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 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
 @file{xemacs-sumo.tar.gz}
 For an XEmacs compiled with Mule you also need
 @file{xemacs-mule-sumo.tar.gz}
 These are in the @file{packages} directory on your XEmacs mirror
-archive.  N.B. They are called 'Sumo Tarballs' for good reason. They
+archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
-are currently about 15MB and 2.3MB (gzipped) respectively.
+mirrors.  N.B. They are called 'Sumo Tarballs' for good reason. They
+are currently about 19MB and 4.5MB (gzipped) respectively.
 Install them on Unix and Mac OS X using the shell/Terminal command
 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
 @file{configure}, and defaults to @file{/usr/local}.
+If you have GNU tar you can use:
+@code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
 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}.
 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.
-See @file{README.packages} in the top-level source directory for more
+However, XEmacs will only notice newly installed packages when it
-detailed installation instructions.
+starts up, so you will have to restart if you are already running
+XEmacs.
+For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
+Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
 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.
-@emph{More detailed info}: If the package path is not explicitly
-specified, XEmacs looks for the package directory
-@file{xemacs-packages} (and @file{mule-packages}, etc.) 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}.
-#### I'm not sure what exactly happens when the package path is
-specifically given, as is the case when the @samp{--package-prefix} or
-@samp{--package-path} options are given to @file{configure}, and
-always under Microsoft Windows.
 @emph{NOTE}: For detailed information about how the package
 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
 Reference Manual}.
-@node Q2.0.2, Q2.0.3, Q2.0.1, Installation
+@node Q2.1.2, Q2.1.3, Q2.1.1, Installation
-@unnumberedsubsec Q2.0.2: I don't need no steenkin' packages.  Do I?
+@unnumberedsubsec Q2.1.2: Can I install the packages individually?
-Strictly speaking, no.  XEmacs will build and install just fine without
+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.
-any packages installed.  However, only the most basic editing functions
-will be available with no packages installed, so installing packages is
+Note: If you are upgrading packages already installed, it's best to
-an essential part of making your installed XEmacs _useful_.
+remove the old package first (@pxref{Q2.1.4}).
-@node Q2.0.3, Q2.0.4, Q2.0.2, Installation
+For example if we are installing the @samp{xemacs-base}
-@unnumberedsubsec Q2.0.3: Where do I find external libraries?
+package (version 1.48):
-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}.
-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.
-@node Q2.0.4, Q2.0.5, Q2.0.3, Installation
-@unnumberedsubsec Q2.0.4: 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 Q2.0.5, Q2.0.6, Q2.0.4, Installation
-@unnumberedsubsec Q2.0.5: Running XEmacs without installing
-How can I just try XEmacs without installing it?
-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.
-A good method is to make a shell alias for xemacs:
 @example
-alias xemacs=/src/xemacs-21.5/src/xemacs
+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
-(You will obviously use whatever directory you downloaded the source
+Or if you have GNU tar, the last step can be:
-tree to instead of @file{/src/xemacs-21.5}).
+@example
-This will let you run XEmacs without massive copying.
+tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
+@end example
-@node Q2.0.6, Q2.0.7, Q2.0.5, Installation
-@unnumberedsubsec Q2.0.6: XEmacs is too big
+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:
-The space required by the installation directories can be
-reduced dramatically if desired.  Gzip all the .el files.  Remove all
+@example
-the packages you'll never want to use.  Remove the TexInfo manuals.
+mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
-Remove the Info (and use just hardcopy versions of the manual).  Remove
+cd $prefix/lib/xemacs/mule-packages RET
-most of the stuff in etc.  Remove or gzip all the source code.  Gzip or
+gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
-remove the C source code.  Configure it so that copies are not made of
+@end example
-the support lisp.
+Or if you have GNU tar, the last step can be:
-These are all Emacs Lisp source code and bytecompiled object code.  You
-may safely gzip everything named *.el here.  You may remove any package
+@example
-you don't use.  @emph{Nothing bad will happen if you delete a package
+tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
-that you do not use}.  You must be sure you do not use it though, so be
+@end example
-conservative at first.
+@node Q2.1.3, Q2.1.4, Q2.1.2, Installation
-Any package with the possible exceptions of xemacs-base, and EFS are
+@unnumberedsubsec Q2.1.3: Can I install the packages automatically?
-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.
+XEmacs comes with some tools to make the periodic updating and
+installing easier. It will notice if new packages or versions are
-First, gzip all the .el files.  Then go about package by package and
+available and will fetch them from the FTP site.
-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
+Unfortunately this requires that a few packages are already in place.
-can remove a package via the PUI interface
+You will have to install them by hand as above or use a SUMO tarball.
-(@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
+This requirement will hopefully go away in the future. The packages
-you wish to delete, and then @kbd{x} to delete them.
+you need are:
-Another method is to do @code{M-x package-get-delete-package}.
+@example
+efs          - To fetch the files from the FTP site or mirrors.
-@node Q2.0.7, Q2.1.1, Q2.0.6, Installation
+xemacs-base  - Needed by efs.
-@unnumberedsubsec Q2.0.7: EFS fails with "500 AUTH not understood" (NEW)
+@end example
+and optionally:
+@example
+mailcrypt    - For PGP verification of the package-index file.
+@end example
+After installing these by hand, fire up XEmacs and follow these
+steps.
+@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
+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
+@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
+XEmacs will now connect to the remote site and download the
+latest package-index file.
+The resulting buffer, "*Packages*" has brief instructions at the
+end of the buffer.
+@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
+@item
+Make sure you have everything you need.
+@itemize @bullet
+@item
+menu: Packages -> Add Required
+@item
+keyb: r
+@end itemize
+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.
+For novices and gurus alike, this step can save your bacon.
+It's easy to forget to install a critical package.
+@item
+Download and install the packages.
+@itemize @bullet
+@item
+menu: Packages -> Install/Remove Selected
+@item
+keyb: x
+@end itemize
+@end enumerate
+@node Q2.1.4, Q2.1.5, Q2.1.3, Installation
+@unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
+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.
+Note that the interactive package tools included with XEmacs already do
+this for you.
+@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.
+If you really want to install only what's absolutely needed, a good
+minimal set of packages for XEmacs-latin1 would be
+@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
+If you are using the XEmacs package tools, don't forget to do:
+@example
+	Packages -> Add Required
+@end example
+To make sure you have everything that the packages you have chosen to
+install need.
+@xref{Q1.7.2}, for a description of the various packages.
+@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?
+On startup XEmacs looks for packages in so-called package hierarchies.
+Normally, there are three system wide hierarchies, like this:
+@example
+$prefix/lib/xemacs/xemacs-packages/
+Normal packages go here.
+$prefix/lib/xemacs/mule-packages/
+Mule packages go here and are only searched by MULE-enabled XEmacsen.
+$prefix/lib/xemacs/site-packages/
+Local and 3rd party packages go here.
+@end example
+This is what you get when you untar the SUMO tarballs under
+@file{$prefix/lib/xemacs}.
+@file{$prefix} is specified using the @samp{--prefix} parameter to
+@file{configure}, and defaults to @file{usr/local}.
+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}.
+You can specify where exactly XEmacs looks for packages by using the
+@samp{--package-prefix} or @samp{--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{--package-path}).
+@xref{Q2.1.1}.
+See @file{configure.usage} for more info about the format of these
+@file{configure} parameters.
+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}.
+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/}.
+@node Q2.1.7, Q2.2.1, Q2.1.6, Installation
+@unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
 Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
 on comp.emacs.xemacs:
 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.
-@unnumberedsec 2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
+@unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
-@node Q2.1.1, Q2.1.2, Q2.0.7, Installation
+@node Q2.2.1, Q2.2.2, Q2.1.7, Installation
-@unnumberedsubsec Q2.1.1: Libraries in non-standard locations
+@unnumberedsubsec Q2.2.1: Libraries in non-standard locations
 If your libraries are in a non-standard location, you can specify the location
 using the following flags to @file{configure}:
 @example
 @example
 --site-libraries='/path/one /path/two /path/etc'
 @end example
-@node Q2.1.2, Q2.2.1, Q2.1.1, Installation
+@node Q2.2.2, Q2.3.1, Q2.2.1, Installation
-@unnumberedsubsec Q2.1.2: Why can't I strip XEmacs?
+@unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
 @quotation
 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
 @end iftex
 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
 @end enumerate
 @end quotation
-@unnumberedsec 2.2: Windows Installation (Windows, Cygwin, MinGW)
+@unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
-@node Q2.2.1, Q2.2.2, Q2.1.2, Installation
+@node Q2.3.1, Q2.3.2, Q2.2.2, Installation
-@unnumberedsubsec Q2.2.1: What exactly are all the different ways to build XEmacs under Windows?
+@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
 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.2.2, Q2.2.3, Q2.2.1, Installation
+@node Q2.3.2, Q2.3.3, Q2.3.1, Installation
-@unnumberedsubsec Q2.2.2: What compiler/libraries do I need to compile XEmacs?
+@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.2.3, Q2.2.4, Q2.2.2, Installation
+@node Q2.3.3, Q2.3.4, Q2.3.2, Installation
-@unnumberedsubsec Q2.2.3: How do I compile the native port?
+@unnumberedsubsec Q2.3.3: How do I compile the native port?
 Please read the file @file{nt/README} in the XEmacs distribution, which
 contains the full description.
-@node Q2.2.4, Q2.2.5, Q2.2.3, Installation
+@node Q2.3.4, Q2.3.5, Q2.3.3, Installation
-@unnumberedsubsec Q2.2.4: What do I need for Cygwin?
+@unnumberedsubsec Q2.3.4: What do I need for Cygwin?
 You can find the Cygwin tools and compiler at:
 @uref{http://www.cygwin.com/}
 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}.
-@node Q2.2.5, Q2.2.6, Q2.2.4, Installation
+@node Q2.3.5, Q2.3.6, Q2.3.4, Installation
-@unnumberedsubsec Q2.2.5: How do I compile under Cygwin?
+@unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
 Similar as on Unix; use the usual `configure' and `make' process.
 Some problems to watch out for:
 @itemize @bullet
 directory of the XEmacs sources.
 @end itemize
-@node Q2.2.6, Q2.2.7, Q2.2.5, Installation
+@node Q2.3.6, Q2.3.7, Q2.3.5, Installation
-@unnumberedsubsec Q2.2.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+@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 location of the extra libs on the command line
 to @file{configure}, e.g.
 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
 @end itemize
-@node Q2.2.7, Q2.2.8, Q2.2.6, Installation
+@node Q2.3.7, Q2.3.8, Q2.3.6, Installation
-@unnumberedsubsec Q2.2.7: How do I compile with X support?
+@unnumberedsubsec Q2.3.7: How do I compile with X support?
 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.
 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.
-@node Q2.2.8, Q2.3.1, Q2.2.7, Installation
+@node Q2.3.8, Q2.4.1, Q2.3.7, Installation
-@unnumberedsubsec Q2.2.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
+@unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
 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
-This application has failed to start because cygXpm-noX4.dll was not found.
+@example
-Re-installing the application may fix this problem.
+This application has failed to start because cygXpm-noX4.dll was not found.
+Re-installing the application may fix this problem.
+@end example
 Andy Piper <andy@@xemacs.org> sez:
-cygXpm-noX4 is part of the cygwin distribution under libraries or
+@example
-graphics, but is not installed by default. You need to run the
+cygXpm-noX4 is part of the cygwin distribution under libraries or
-cygwin setup again and select this package.
+graphics, but is not installed by default. You need to run the
+cygwin setup again and select this package.
+@end example
 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
 distribution.
-@unnumberedsec 2.3: General Troubleshooting
+@unnumberedsec 2.4: General Troubleshooting
-@node Q2.3.1, Q2.3.2, Q2.2.8, Installation
+@node Q2.4.1, Q2.4.2, Q2.3.8, Installation
-@unnumberedsubsec Q2.3.1: Help!  XEmacs just crashed on me!
+@unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
+The file @file{PROBLEMS} contains information on many common problems that
+occur in building, installing and running XEmacs.
+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.
+There are three ways to read the Bugs section.
+@enumerate
+@item
+In a printed copy of the XEmacs manual.
+@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.)
+@item
+By hand.  Do
+@example
+cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"
+@end example
+@end enumerate
+@node Q2.4.2, Q2.4.3, Q2.4.1, Installation
+@unnumberedsubsec Q2.4.2: Help!  XEmacs just crashed on me!
 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
 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.3.3, How to debug an XEmacs problem
+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.3.3, How to debug an XEmacs
+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
 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 Q2.3.2, Q2.3.3, Q2.3.1, Installation
+@node Q2.4.3, Q2.4.4, Q2.4.2, Installation
-@unnumberedsubsec Q2.3.2: XEmacs crashes and I compiled it myself.
+@unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
 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.3.3, How to debug an XEmacs problem with a
+turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
 debugger}) and recompiling.
 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.
 If you compiled XEmacs using @samp{--use-union-type} (or 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.
-@node Q2.3.3, Q2.3.4, Q2.3.2, Installation
+@node Q2.4.4, Q2.4.5, Q2.4.3, Installation
-@unnumberedsubsec Q2.3.3: How to debug an XEmacs problem with a debugger
+@unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
 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:
 If you are running Microsoft Windows, the the file @file{nt/README} for
 further information about debugging XEmacs.
 @end itemize
-@node Q2.3.4, Q2.3.5, Q2.3.3, Installation
+@node Q2.4.5, Q2.4.6, Q2.4.4, Installation
-@unnumberedsubsec Q2.3.4: I get a cryptic error message when trying to do something.
+@unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
 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}
 @end enumerate
 For more information on debugging Lisp code, @xref{Debugging,,,
 lispref, XEmacs Lisp Reference Manual}.
-@node Q2.3.5, Q2.3.6, Q2.3.4, Installation
+@node Q2.4.6, Q2.4.7, Q2.4.5, Installation
-@unnumberedsubsec Q2.3.5: XEmacs hangs when I try to do something.
+@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.3.3, How to debug an XEmacs problem with a
+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.3.3, How to debug an XEmacs
+and getting a C stack backtrace.  @xref{Q2.4.4, How to debug an XEmacs
 problem with a debugger}.
-@node Q2.3.6, Q2.3.7, Q2.3.5, Installation
+@node Q2.4.7, Q2.4.8, Q2.4.6, Installation
-@unnumberedsubsec Q2.3.6: I get an error message when XEmacs is running in batch mode.
+@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
 @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.3.3, How to debug an XEmacs problem with a debugger}.  You
+@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.
 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.3.7, Q2.3.8, Q2.3.6, Installation
+@node Q2.4.8, Q2.4.9, Q2.4.7, Installation
-@unnumberedsubsec Q2.3.7: The keyboard or mouse is not working properly, or I have some other event-related problem.
+@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
 @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.3.8, Q2.3.9, Q2.3.7, Installation
+@node Q2.4.9, Q2.4.10, Q2.4.8, Installation
-@unnumberedsubsec Q2.3.8: @kbd{C-g} doesn't work for me.  Is it broken?
+@unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me.  Is it broken?
 @kbd{C-g} does work for most people in most circumstances.  If it
 doesn't, there are two possible explanations:
 @enumerate
 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.3.5, XEmacs hangs when I try to do something.}.
+@xref{Q2.4.6, XEmacs hangs when I try to do something.}.
 @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
-@node Q2.3.9, Q2.3.10, Q2.3.8, Installation
+@node Q2.4.10, Q2.4.11, Q2.4.9, Installation
-@unnumberedsubsec Q2.3.9: How do I debug process-related problems?
+@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
 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.3.10, Q2.3.11, Q2.3.9, Installation
+@node Q2.4.11, Q2.4.12, Q2.4.10, Installation
-@unnumberedsubsec Q2.3.10: XEmacs is outputting lots of X errors.
+@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.3.3, How to debug an XEmacs
+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.3.11, Q2.4.1, Q2.3.10, Installation
+@node Q2.4.12, Q2.5.1, Q2.4.11, Installation
-@unnumberedsubsec Q2.3.11: After upgrading, XEmacs won't do `foo' any more!
+@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.0.2, How do I figure out which packages to install?}).
+(@pxref{Q2.1.2, How do I figure out which packages to install?}).
 @c #### should xref to XEmacs manual here
-@unnumberedsec 2.4: Startup-Related Problems
+@unnumberedsec 2.5: Startup-Related Problems
-@node Q2.4.1, Q2.4.2, Q2.3.11, Installation
+@node Q2.5.1, Q2.5.2, Q2.4.12, Installation
-@unnumberedsubsec Q2.4.1: XEmacs cannot connect to my X Terminal!
+@unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
 Help!  I can not get XEmacs to display on my Envizex X-terminal!
 Try setting the @code{DISPLAY} variable using the numeric IP address of
 the host you are running XEmacs from.
-@node Q2.4.2, Q2.4.3, Q2.4.1, Installation
+@node Q2.5.2, Q2.5.3, Q2.5.1, Installation
-@unnumberedsubsec Q2.4.2: XEmacs won't start on Windows.
+@unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
-XEmacs relies on a process called "dumping" to generate a working
+First of all, if XEmacs can't find the packages, check to make sure
-executable. Under MS-Windows this process effectively fixes the memory
+that you put the packages in the right place, or that you told XEmacs
-addresses of information in the executable. When XEmacs starts up it tries
+where to look for the packages when you compiled it.  @xref{Q2.1.1}.
-to reserve these memory addresses so that the dumping process can be
-reversed -- putting the information back at the correct addresses.
+If something is still going wrong, or you get a startup warning about
-Unfortunately some .DLLs (for instance the soundblaster driver) occupy
+not being able to deduce some paths, you can get detailed information
-memory addresses that can conflict with those needed by the dumped XEmacs
+on the path-searching process at startup by setting the environment
-executable. In this instance XEmacs will fail to start without any
+variable @samp{EMACSDEBUGPATHS} to a non-null value.  One thing to
-explanation. Note that this is extremely machine specific.
+look for if you're having package problems is the value of
+@samp{configure-package-path}.  This corresponds to what was compiled
-21.1.10 includes a fix for this that makes more intelligent guesses
+into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
-about which memory addresses will be free, and this should cure the
+parameter (@pxref{Q2.1.1}).  If this has the value of @samp{nil},
-problem for most people.  21.4 implements "portable dumping", which
+this means that no value was compiled into XEmacs using these parameters.
-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
+@node Q2.5.3, Q2.5.4, Q2.5.2, Installation
-about stability.  @xref{Q1.1.2, Are binaries available?}.
+@unnumberedsubsec Q2.5.3: XEmacs won't start without network.
-@node Q2.4.3, Q2.4.4, Q2.4.2, Installation
-@unnumberedsubsec Q2.4.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:
 127.0.0.1        localhost
 @end example
 Add that line, and XEmacs will be happy.
-@node Q2.4.4, Q2.4.5, Q2.4.3, Installation
+@node Q2.5.4, Q2.5.5, Q2.5.3, Installation
-@unnumberedsubsec Q2.4.4: Startup warnings about deducing proper fonts?
+@unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
 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:
 (setq display-warning-minimum-level 'error)
 @end lisp
 The buffer still exists; it just isn't in your face.
-@node Q2.4.5, Q2.4.6, Q2.4.4, Installation
+@node Q2.5.5, Q2.5.6, Q2.5.4, Installation
-@unnumberedsubsec Q2.4.5: Warnings from incorrect key modifiers.
+@unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
 The following information comes from the @file{PROBLEMS} file that comes
 with XEmacs.
 If you're having troubles with HP/UX it is because HP/UX defines the
 keysym Meta_R = Mode_switch
 add mod2 = Mode_switch
 EOF
 @end example
-@node Q2.4.6,  , Q2.4.5, Installation
+@node Q2.5.6,  , Q2.5.5, Installation
-@unnumberedsubsec Q2.4.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+@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
 to released XEmacsen, but users can apply themselves) are also accepted.
 @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
 @unnumberedsec 10.0: XEmacs 21.1
-@node Q10.0.1,  , Legacy Versions, Legacy Versions
+@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:
 @quotation
 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

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 2559:0e04aba50e0b