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

comparison man/xemacs-faq.texi @ 412:697ef44129c6 r21-2-14

Import from CVS: tag r21-2-14

author	cvs
date	Mon, 13 Aug 2007 11:20:41 +0200
parents	de805c49cfc1
children	11054d720c21

comparison

equal deleted inserted replaced

-:12e008d41344
+:697ef44129c6
-\input texinfo.tex      @c -*- mode: texinfo; coding: iso-2022-8 -*-
+\input texinfo.tex      @c -*-texinfo-*-
 @c %**start of header
 @setfilename ../info/xemacs-faq.info
 @settitle Frequently asked questions about XEmacs
 @setchapternewpage off
 @c %**end of header
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2000/07/08 09:14:11 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 1999/05/13 12:26:40 $
 @sp 1
-@author Tony Rossini <rossini@@biostat.washington.edu>
+@author Tony Rossini <arossini@@stat.sc.edu>
-@author Ben Wing <ben@@xemacs.org>
+@author Ben Wing <wing@@666.com>
 @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@@xemacs.org>
 @page
 @end titlepage
 @ifinfo
 @dircategory XEmacs Editor
 @direntry
-* FAQ: (xemacs-faq).            XEmacs FAQ.
+* FAQ: (xemacs-faq).		XEmacs FAQ.
 @end direntry
 @end ifinfo
 @node Top, Introduction, (dir), (dir)
 @top XEmacs FAQ
 * 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.
 @detailmenu
 --- The Detailed Node Listing ---
 * 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.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.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::     [This question intentionally left blank]
+* 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::     [This question intentionally left blank]
+* 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.
-* Q2.1.24::     XEmacs won't start without network. (NEW)
 Customization and Options
 * Q3.0.1::      What version of Emacs am I running?
 * Q3.0.2::      How do I evaluate Elisp expressions?
 * 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::      [This question intentionally left blank]
+* Q3.1.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
-* Q3.1.4::      [This question intentionally left blank]
+* 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.
 * 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::      [This question intentionally left blank]
+* 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.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::     How do I turn on filladapt for all buffers?
+* 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::     [This question intentionally left blank]
+* 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.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
+What the Future Holds
-General Info:
+* Q6.0.1::      What is new in 20.2?
-* Q6.0.1::      What is the status of the XEmacs port to Windows?
+* Q6.0.2::      What is new in 20.3?
-* Q6.0.2::      What flavors of MS Windows are supported?
+* Q6.0.3::      What is new in 20.4?
-* Q6.0.3::      Are binary kits available?
+* Q6.0.4::      Procedural changes in XEmacs development.
-* 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?
-Troubleshooting:
-* Q6.4.1::      XEmacs won't start on Windows. (NEW)
-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.
 @end detailmenu
 @end menu
 @node Introduction, Installation, Top, Top
 @unnumbered 1 Introduction, Policy, Credits
 be complete.  Instead it is aimed at the person who is either
 considering XEmacs for their own use, or has just obtained it and is
 wondering what to do next.  It is also useful as a reference to
 available resources.
-The previous maintainer of the FAQ was @email{rossini@@biostat.washington.edu,
+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
+@email{ben@@666.com, 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 version was converted to hypertext format, and edited by
-@email{steve@@xemacs.org, Steven L. Baur}.  It was converted back to
+@email{steve@@altair.xemacs.org, Steven L. Baur}.  It was converted back to
-texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}.  The FAQ was then
+texinfo by @email{hniksic@@srce.hr, Hrvoje Niksic}.
-maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
-on to ChristianNyb@o{}.
+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.
 If you notice any errors or items which should be added or amended to
-this FAQ please send email to @email{faq@@xemacs.org, Sandra
+this FAQ please send email to @email{faq@@xemacs.org, Christian
-Wambold}.  Include @samp{XEmacs FAQ} on the Subject: line.
+Nyb@o{}}. 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.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?
 @end menu
 @node Q1.0.1, Q1.0.2, Introduction, Introduction
 @unnumberedsec 1.0: Introduction
 @unnumberedsubsec Q1.0.1: What is XEmacs?
 track changes to GNU Emacs while also working to add new features.
 @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 20.4 is a minor upgrade from 20.3, containing many bugfixes. It
 was released in February 1998.
 XEmacs 19.16 was the last release of v19, released in November, 1997,
 which 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:
+The canonical source and binaries is found via anonymous FTP at:
 @example
 @uref{ftp://ftp.xemacs.org/pub/xemacs/}
 @end example
 @unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
 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}
+@uref{http://www.xemacs.org/NEWS.html, NEWS file}
 @end example
 However, here is a list of some of the reasons why we think you might
 consider using it:
 @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
+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
+pressing @kbd{C-h i}, or selecting @code{Emacs Info} from the Help Menu.
-Help Menu.  @kbd{M-x apropos} can be used to look for particular commands.
+Also, @kbd{M-x apropos} will look for commands for you.
-For items not found in the manual, try reading this FAQ
-@comment , examining the regular GNU Emacs FAQ (which can be
+Try reading this FAQ, examining the regular GNU Emacs FAQ (which can be
-@comment found with the Emacs 19 distribution) as well as at
+found with the Emacs 19 distribution) as well as at
-@comment @uref{http://www.eecs.nwu.edu/emacs/faq/}
+@uref{http://www.eecs.nwu.edu/emacs/faq/} and reading the Usenet group
-and reading the Usenet group comp.emacs.xemacs.
+comp.emacs.xemacs.
-If you choose to post to a newsgroup, @strong{please use
+If that does not help, try posting your question to comp.emacs.xemacs.
-comp.emacs.xemacs}.  Please do not post XEmacs related questions to
+Please @strong{do not} post XEmacs related questions to gnu.emacs.help.
-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
+with a subject of @samp{subscribe} to @email{xemacs-request@@xemacs.org}
-body of the message.  Send to the list at @email{xemacs@@xemacs.org}.
+for subscription information and @email{xemacs@@xemacs.org} to send messages
-list.  To cancel a subscription, you @strong{must} use the
+to the list.
-xemacs-request address.  Send a message with a subject of
-@samp{unsubscribe} to be removed.
+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}
+The mailing list was archived in the directory
+@example
+@uref{ftp://ftp.xemacs.org/pub/mlists/}.
+@end example
+However, this archive is out of date.  The current mailing list server
+supports an @code{archive} feature, which may be utilized.
 @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}.
+I pronounce it @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.
 @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}.
+Thanks to efforts of many people, coordinated by
+@email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
-@comment Thanks to efforts of many people, coordinated by
+Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
-@comment @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
+(NT and 95).  The current betas require having an X server to run
-@comment Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
+XEmacs; however, a native NT/95 port is in alpha, thanks to
-@comment (NT and 95).  The current betas require having an X server to run
+@email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
-@comment XEmacs; however, a native NT/95 port is in alpha, thanks to
-@comment @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
+Although some features are still unimplemented, XEmacs 21.0 will support
-@comment
+MS-Windows.
-@comment Although some features are still unimplemented, XEmacs 21.0 will support
-@comment MS-Windows.
+The NT development is now coordinated by a mailing list at
-@comment
+@email{xemacs-nt@@xemacs.org}.
-@comment The NT development is now coordinated by a mailing list at
-@comment @email{xemacs-nt@@xemacs.org}.
+If you are willing to contribute or want to follow the progress, mail to
-@comment
+@iftex
-@comment If you are willing to contribute or want to follow the progress, mail to
+@*
-@comment @iftex
+@end iftex
-@comment @*
+@email{xemacs-nt-request@@xemacs.org} to subscribe.
-@comment @end iftex
-@comment @email{xemacs-nt-request@@xemacs.org} to subscribe.
+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 Furthermore, Altrasoft is seeking corporate and government sponsors to
+full-time, senior-level staff working under a professionally managed
-@comment help fund a fully native port of XEmacs to Windows 95 and NT using
+project structure.  See @uref{http://www.altrasoft.com/, the Altrasoft
-@comment full-time, senior-level staff working under a professionally managed
+web site} for more details
-@comment project structure.  See @uref{http://www.altrasoft.com/, the Altrasoft
+or contact Altrasoft directly at 1-888-ALTSOFT.
-@comment web site} for more details
-@comment or contact Altrasoft directly at 1-888-ALTSOFT.
-@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 The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
-@comment Emacs 19.6.  Available from @uref{http://www.pearlsoft.com/}.
+There's a port of GNU Emacs (not XEmacs) at
-@comment
+@example
-@comment There's a port of GNU Emacs (not XEmacs) at
+@uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
-@comment @example
+@end 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
-@c There has been a port to the MachTen environment of XEmacs 19.13, but no
+There has been a port to the MachTen environment of XEmacs 19.13, but no
-@c patches have been submitted to the maintainers to get this in the
+patches have been submitted to the maintainers to get this in the
-@c mainstream distribution.
+mainstream distribution.
-@c
-@c For the MacOS, there is a port of
+For the MacOS, there is a port of
-@c @uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
+@uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
-Yes, there is a port of XEmacs 19.14, tested on MacOS 7.6.1 and MacOS
-8.5.1 by @email{pjarvis@@ispchannel.com, Pitts Jarvis}.  It's available
-at @uref{http://my.ispchannel.com/~pjarvis/xemacs.html}.
 @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
 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, but Alexander Nikolaev <avn_1251@@mail.ru> is working on it.
+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
+Altrasoft Associates, a firm specializing in Emacs-related support and
-TeX, you can generate your own manual from the XEmacs sources.
+development, will be maintaining the XEmacs user manual.  The firm plans
+to begin publishing printed copies of the manual soon.
-HTML and Postscript versions of XEmacs manuals may be available from the
+@c This used to say `March 1997'!
-XEmacs web site in the future.
+@example
+Web:     @uref{http://www.xemacs.com}
+E-mail:  @email{info@@xemacs.com}
+Tel:     +1 408 243 3300
+@end example
 @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?
 The FAQ is actively maintained and modified regularly.  All links should
-be up to date.  Unfortunately, some of the information is out of date --
+be up to 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
+Changes are displayed on a monthly basis.  @dfn{Months}, for this
-maintainers}.
+purpose are defined as the 5th of the month through the 5th of the
+month.  Preexisting questions that have been changed are marked as such.
+Brand new questions are tagged.
+All submissions are welcome.  E-mail submissions
+to
+@iftex
+@*
+@end iftex
+@email{faq@@xemacs.org, Christian Nyb@o{}}.
 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
+question should be included, I'd like to hear about it.  Questions and
 answers included into the FAQ will be edited for spelling and grammar,
 and will be attributed.  Answers appearing without attribution are
 either from versions of the FAQ dated before May 1996, or are from one
 of the four people listed at the top of this document.  Answers quoted
 from Usenet news articles will always be attributed, regardless of the
 author.
 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
 @unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
-Send an email message to @email{xemacs-beta-request@@xemacs.org} with
+Send an email message to @email{xemacs-beta-request@@xemacs.org} with a
-the line @samp{subscribe} in the body of the message.
+subject line of @samp{subscribe}.
 Be prepared to get your hands dirty, as beta testers are expected to
 identify problems as best they can.
 @node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
 @unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
-Ben Wing @email{ben@@xemacs.org} writes:
+Ben Wing @email{ben@@666.com} writes:
 @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):
 @ifhtml
 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
 @end ifhtml
-@item @email{steve@@xemacs.org, Steve Baur}
+@item @email{steve@@altair.xemacs.org, Steve Baur}
 @ifhtml
 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
 @end ifhtml
-@item @email{hniksic@@xemacs.org, Hrvoje Niksic}
+@item @email{hniksic@@srce.hr, Hrvoje Niksic}
 @ifhtml
 <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
 @end ifhtml
 @end ifhtml
 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{ben@@xemacs.org, Ben Wing}
+@item @email{ben@@666.com, Ben Wing}
 @ifhtml
 <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
 @end ifhtml
 @end itemize
 @itemize @bullet
-@item @email{jwz@@jwz.org, Jamie Zawinski}
+@item @email{jwz@@netscape.com, 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
 version of the FAQ (listed in alphabetical order):
 @itemize @bullet
 @item @email{steve@@xemacs.org, SL Baur}
-@item @email{hniksic@@xemacs.org, Hrvoje Niksic}
+@item @email{hniksic@@srce.hr, Hrvoje Niksic}
 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
 @end itemize
 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}
 @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},
+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
+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
+@w{integer 65}, following the standard @sc{ASCII} representation of
-characters.  If XEmacs was not compiled with @sc{mule} support, the
+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
+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}
+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
+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
+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.
+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
 @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?
-MULE support is now available for UNIX versions of XEmacs.
+The MULE support works OK but still needs a fair amount of work before
+it's really solid.  We could definitely use some help here, esp. people
-If you would like to help, you may want to join the
+who speak Japanese and will use XEmacs/MULE to work with Japanese and
-@email{xemacs-mule@@xemacs.org} mailing list.  Especially needed are
+have some experience with E-Lisp.
-people who speak/write languages other than English, who are willing to
-use XEmacs/MULE regularly, and have some experience with Elisp.
+As the fundings on Mule have stopped, the Mule part of XEmacs is currently
+looking for a full-time maintainer.  If you can provide help here, or
+are willing to fund the work, please mail to @email{xemacs-beta@@xemacs.org}.
 @xref{Q1.1.2}.
 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
 @unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
 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:
 @example
-Emacs*XlwMenu.resourceLabels:                   True
+Emacs*XlwMenu.resourceLabels:			True
-Emacs*XlwMenu.file.labelString:                 Fichier
+Emacs*XlwMenu.file.labelString:	        	Fichier
-Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster oeffnen
+Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster offnen
 @end example
 The name of the resource is derived from the non-localized entry by
 removing punctuation and capitalizing as above.
 @lisp
 (if (featurep 'mule)
 (cond ((boundp 'MULE)
 ;; for original Mule
 )
-((string-match "XEmacs" emacs-version)
+	  ((string-match "XEmacs" emacs-version)
-;; for XEmacs with Mule
+	   ;; for XEmacs with Mule
-)
+	   )
-(t
+	  (t
-;; for next version of Emacs
+	   ;; for next version of Emacs
-))
+	   ))
 ;; for old emacs variants
 )
 @end lisp
 @end quotation
 show you how to handle different versions and flavors of Emacs.
 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
 @unnumberedsubsec Q1.4.3: Any good tutorials around?
-There's the XEmacs tutorial available from the Help Menu under
+There's the XEmacs tutorial available from the Help Menu, or by typing
-@samp{Basics->Tutorials}, or by typing @kbd{C-h t}. To check whether
+@kbd{C-h t}. To check whether it's available in a non-english language,
-it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
+type @kbd{C-u C-h t TAB}, type the first letters of your preferred
-the first letters of your preferred language, then type @key{RET}.
+language, then type @key{RET}.
-@comment There's an Emacs Lisp tutorial at
+There's an Emacs Lisp tutorial at
-@comment
-@comment @example
+@example
-@comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
+@uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
-@comment @end example
+@end example
-@comment
-@comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
+@email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
-@comment page at
+page at
-@comment @iftex
+@iftex
-@comment @*
+@*
-@comment @end iftex
+@end iftex
-@comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
+@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?
 The following function does a little bit of everything useful.  It does
 (global-set-key "\C-cd" 'double-word)
 @end lisp
 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
-@node Q1.4.6, , Q1.4.5, Introduction
+@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?
 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
 @dfn{Macros} enable you to define new control constructs and other
 or parts of them.
 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?
+There's a problem with options of the form:
+@lisp
+(add-spec-list-to-specifier (face-property 'searchm-field 'font)
+'((global (nil))))
+@end lisp
+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.
+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:
+@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 Installation, Customization, Introduction, Top
 @unnumbered 2 Installation and Trouble Shooting
 This is part 2 of the XEmacs Frequently Asked Questions list.  This
 * 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.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::     [This question intentionally left blank]
+* 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::     [This question intentionally left blank]
+* 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.
-* Q2.1.24::     XEmacs won't start without network. (NEW)
 @end menu
 @node Q2.0.1, Q2.0.2, Installation, Installation
 @unnumberedsec 2.0: Installation
 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
 @unnumberedsubsec Q2.0.2: XEmacs is too big
 Although this entry has been written for XEmacs 19.13, most of it still
 stands true.
-@email{steve@@xemacs.org, Steve Baur} writes:
+@email{steve@@altair.xemacs.org, Steve Baur} writes:
 @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
 out ways to reduce the disk requirements if desired.
 Now examine the space used by directory:
 @format
-0       /usr/local/bin/xemacs
+0	/usr/local/bin/xemacs
-2048    /usr/local/bin/xemacs-19.13
+2048	/usr/local/bin/xemacs-19.13
-1546    /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
+1546	/usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
-1158    /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
+1158	/usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
 @end format
 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.
 @format
-207     /usr/local/lib/xemacs-19.13/etc/w3
+207	/usr/local/lib/xemacs-19.13/etc/w3
-122     /usr/local/lib/xemacs-19.13/etc/sounds
+122	/usr/local/lib/xemacs-19.13/etc/sounds
-18      /usr/local/lib/xemacs-19.13/etc/sparcworks
+18	/usr/local/lib/xemacs-19.13/etc/sparcworks
-159     /usr/local/lib/xemacs-19.13/etc/vm
+159	/usr/local/lib/xemacs-19.13/etc/vm
-6       /usr/local/lib/xemacs-19.13/etc/e
+6	/usr/local/lib/xemacs-19.13/etc/e
-21      /usr/local/lib/xemacs-19.13/etc/eos
+21	/usr/local/lib/xemacs-19.13/etc/eos
-172     /usr/local/lib/xemacs-19.13/etc/toolbar
+172	/usr/local/lib/xemacs-19.13/etc/toolbar
-61      /usr/local/lib/xemacs-19.13/etc/ns
+61	/usr/local/lib/xemacs-19.13/etc/ns
-43      /usr/local/lib/xemacs-19.13/etc/gnus
+43	/usr/local/lib/xemacs-19.13/etc/gnus
 @end format
 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.
 @format
-1959    /usr/local/lib/xemacs-19.13/etc
+1959	/usr/local/lib/xemacs-19.13/etc
-175     /usr/local/lib/xemacs-19.13/lisp/bytecomp
+175	/usr/local/lib/xemacs-19.13/lisp/bytecomp
-340     /usr/local/lib/xemacs-19.13/lisp/calendar
+340	/usr/local/lib/xemacs-19.13/lisp/calendar
-342     /usr/local/lib/xemacs-19.13/lisp/comint
+342	/usr/local/lib/xemacs-19.13/lisp/comint
-517     /usr/local/lib/xemacs-19.13/lisp/dired
+517	/usr/local/lib/xemacs-19.13/lisp/dired
-42      /usr/local/lib/xemacs-19.13/lisp/electric
+42	/usr/local/lib/xemacs-19.13/lisp/electric
-212     /usr/local/lib/xemacs-19.13/lisp/emulators
+212	/usr/local/lib/xemacs-19.13/lisp/emulators
-238     /usr/local/lib/xemacs-19.13/lisp/energize
+238	/usr/local/lib/xemacs-19.13/lisp/energize
-289     /usr/local/lib/xemacs-19.13/lisp/gnus
+289	/usr/local/lib/xemacs-19.13/lisp/gnus
-457     /usr/local/lib/xemacs-19.13/lisp/ilisp
+457	/usr/local/lib/xemacs-19.13/lisp/ilisp
-1439    /usr/local/lib/xemacs-19.13/lisp/modes
+1439	/usr/local/lib/xemacs-19.13/lisp/modes
-2276    /usr/local/lib/xemacs-19.13/lisp/packages
+2276	/usr/local/lib/xemacs-19.13/lisp/packages
-1040    /usr/local/lib/xemacs-19.13/lisp/prim
+1040	/usr/local/lib/xemacs-19.13/lisp/prim
-176     /usr/local/lib/xemacs-19.13/lisp/pcl-cvs
+176	/usr/local/lib/xemacs-19.13/lisp/pcl-cvs
-154     /usr/local/lib/xemacs-19.13/lisp/rmail
+154	/usr/local/lib/xemacs-19.13/lisp/rmail
-3       /usr/local/lib/xemacs-19.13/lisp/epoch
+3	/usr/local/lib/xemacs-19.13/lisp/epoch
-45      /usr/local/lib/xemacs-19.13/lisp/term
+45	/usr/local/lib/xemacs-19.13/lisp/term
-860     /usr/local/lib/xemacs-19.13/lisp/utils
+860	/usr/local/lib/xemacs-19.13/lisp/utils
-851     /usr/local/lib/xemacs-19.13/lisp/vm
+851	/usr/local/lib/xemacs-19.13/lisp/vm
-13      /usr/local/lib/xemacs-19.13/lisp/vms
+13	/usr/local/lib/xemacs-19.13/lisp/vms
-157     /usr/local/lib/xemacs-19.13/lisp/x11
+157	/usr/local/lib/xemacs-19.13/lisp/x11
-19      /usr/local/lib/xemacs-19.13/lisp/tooltalk
+19	/usr/local/lib/xemacs-19.13/lisp/tooltalk
-14      /usr/local/lib/xemacs-19.13/lisp/sunpro
+14	/usr/local/lib/xemacs-19.13/lisp/sunpro
-291     /usr/local/lib/xemacs-19.13/lisp/games
+291	/usr/local/lib/xemacs-19.13/lisp/games
-198     /usr/local/lib/xemacs-19.13/lisp/edebug
+198	/usr/local/lib/xemacs-19.13/lisp/edebug
-619     /usr/local/lib/xemacs-19.13/lisp/w3
+619	/usr/local/lib/xemacs-19.13/lisp/w3
-229     /usr/local/lib/xemacs-19.13/lisp/eos
+229	/usr/local/lib/xemacs-19.13/lisp/eos
-55      /usr/local/lib/xemacs-19.13/lisp/iso
+55	/usr/local/lib/xemacs-19.13/lisp/iso
-59      /usr/local/lib/xemacs-19.13/lisp/mailcrypt
+59	/usr/local/lib/xemacs-19.13/lisp/mailcrypt
-187     /usr/local/lib/xemacs-19.13/lisp/eterm
+187	/usr/local/lib/xemacs-19.13/lisp/eterm
-356     /usr/local/lib/xemacs-19.13/lisp/ediff
+356	/usr/local/lib/xemacs-19.13/lisp/ediff
-408     /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
+408	/usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
-1262    /usr/local/lib/xemacs-19.13/lisp/hyperbole
+1262	/usr/local/lib/xemacs-19.13/lisp/hyperbole
-247     /usr/local/lib/xemacs-19.13/lisp/hm--html-menus
+247	/usr/local/lib/xemacs-19.13/lisp/hm--html-menus
-161     /usr/local/lib/xemacs-19.13/lisp/mh-e
+161	/usr/local/lib/xemacs-19.13/lisp/mh-e
-299     /usr/local/lib/xemacs-19.13/lisp/viper
+299	/usr/local/lib/xemacs-19.13/lisp/viper
-53      /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
+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
+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/InfoPanel.nib
-3       /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.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
+11	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
-53      /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
+53	/usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
-466     /usr/local/lib/xemacs-19.13/lisp/oobr
+466	/usr/local/lib/xemacs-19.13/lisp/oobr
-14142   /usr/local/lib/xemacs-19.13/lisp
+14142	/usr/local/lib/xemacs-19.13/lisp
 @end format
 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
 @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.
 @example
-1972    /usr/local/lib/xemacs-19.13/info
+1972	/usr/local/lib/xemacs-19.13/info
 @end example
 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.
 @example
-20778   /usr/local/lib/xemacs-19.13
+20778	/usr/local/lib/xemacs-19.13
 @end example
 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
 @*
 @end iftex
 Terminal type `xterm' undefined (or can't access database?)
 @end example
-@email{ben@@xemacs.org, Ben Wing} writes:
+@email{ben@@666.com, Ben Wing} writes:
 @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
 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
 @unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
 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
+19.14 XEmacs has full color support on a color capable character
 terminal.
 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
 @unnumberedsubsec Q2.0.6: I'm having strange crashes.  What do I do?
 @end iftex
 @samp{h_errno^@@^@@}.  Any version of Emacs will
 suffice.  If you don't understand how to do this, don't do it.
 @item
-Rebuild XEmacs yourself---any working ELF version of libc should be
+Rebuild XEmacs yourself -- any working ELF version of libc should be
 O.K.
 @end enumerate
-@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
+@email{hniksic@@srce.hr, Hrvoje Niksic} writes:
 @quotation
 Why not use a Perl one-liner for No. 2?
 @example
 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
-@node Q2.0.12, Q2.1.1, Q2.0.11, Installation
+@node Q2.0.12, Q2.0.13, Q2.0.11, Installation
 @unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
 @quotation
 @end iftex
 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
 @end enumerate
 @end quotation
-@node Q2.1.1, Q2.1.2, Q2.0.12, Installation
+@node Q2.0.13, Q2.0.14, Q2.0.12, Installation
+@unnumberedsubsec Q2.0.13: Problems linking with Gcc on Solaris
+There are known difficulties linking with Gnu ld on Solaris.  A typical
+error message might look like:
+@example
+unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
+fatal: relocation error:
+symbol not found: main: referenced in ../dynodump/dynodump.so
+@end example
+@email{martin@@xemacs.org, Martin Buchholz} writes:
+@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
+@node Q2.0.14, Q2.1.1, Q2.0.13, Installation
+@unnumberedsubsec Q2.0.14: Make on HP/UX 9 fails after linking temacs
+Problem when building xemacs-19.16 on hpux 9:
+@email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
+@quotation
+make on hpux fails after linking temacs with a message:
+@example
+"make: don't know how to make .y."
+@end example
+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
+@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!
 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
 I think this is due to undefined resources; You need to define color
 backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
 like:
 @example
-*Foreground:    Black   ;everything will be of black on grey95,
+*Foreground:	Black	;everything will be of black on grey95,
-*Background:    Grey95  ;unless otherwise specified.
+*Background:	Grey95	;unless otherwise specified.
-*cursorColor:   Red3    ;red3 cursor with grey95 border.
+*cursorColor:	Red3	;red3 cursor with grey95 border.
-*pointerColor:  Red3    ;red3 pointer with grey95 border.
+*pointerColor:	Red3	;red3 pointer with grey95 border.
 @end example
 @end quotation
 Natalie Kershaw adds:
 @end quotation
 @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?
-@email{ben@@xemacs.org, Ben Wing} writes:
+@email{ben@@666.com, Ben Wing} writes:
 @quotation
 @kbd{C-g} does work for most people in most circumstances.  If it
 doesn't, there are only two explanations:
 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
+@file{src/gdbinit} in the XEmacs source distribution that should make it
-it easier for you to decode Lisp objects.  This file is automatically
+easier for you to decode Lisp objects.  Copy this file to
-read by gdb if gdb is run in the directory where xemacs was built, and
+@file{~/.gdbinit}, or @code{source} it from @file{~/.gdbinit}, and use
-contains these useful macros to inspect the state of xemacs:
+the macros defined therein.  In particular, use the @code{pobj} macro to
+print the internal C representation of a lisp object.  This will work
-@table @code
+with a core file or not-yet-run executable.  The aliases @code{ldp} and
-@item pobj
+@code{lbt} are provided for conveniently calling @code{debug_print} and
-Usage: pobj lisp_object @*
+@code{debug_backtrace}.
-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.
-@item ldp
-Usage: ldp lisp_object @*
-Print a Lisp Object value using the Lisp printer.
-Requires a running xemacs process.
-@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
 If you are using Sun's @file{dbx} debugger, there is an equivalent file
-@file{src/.dbxrc}, which defines the same commands for dbx.
+@file{src/dbxrc} to copy to or source from @file{~/.dbxrc}.
 @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
 @end enumerate
 @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
+also need gdb 4.17.  Earlier releases of gdb can't handle the debug
-debug information generated by the newer compilers.
+information generated by the newer compilers.
 @item
-In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
+The above information on using @file{src/gdbinit} works for XEmacs-21.0
-@file{src/gdbinit}.  This had the disadvantage of not being sourced
+and above.  For older versions of XEmacs, there are different
-automatically by gdb, so you had to set that up yourself.
+@file{gdbinit} files provided in the @file{src} directory.  Use the one
+corresponding to the configure options used when building XEmacs.
 @end itemize
 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
 @unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
-From the problems database (through
+>From the problems database (through
-the former address http://support.mayfield.hp.com/):
+@uref{http://support.mayfield.hp.com/}):
 @example
 Problem Report: 5003302299
 Status:         Open
 A problem with some early versions of Gnus 5.4 caused this error.
 Upgrade your Gnus.
 @end enumerate
 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
-@unnumberedsubsec Q2.1.18: removed
+@unnumberedsubsec Q2.1.18: 19.14 hangs on HP/UX 10.10.
+@email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
+@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
+@email{cognot@@ensg.u-nancy.fr, Richard Cognot} adds:
+@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
+@email{af@@biomath.jussieu.fr, Alain Fauconnet} writes:
+@quotation
+The @emph{real} solution is to @emph{not} link -lcurses in!  I just
+changed -lcurses to -ltermcap in the Makefile and it fixed:
+@enumerate
+@item
+The @samp{poll: interrupted system call} message.
+@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
 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
 When using one of the prebuilt binaries many users have observed that
 @end lisp
 where you load hyperbole and the problem should go away.
 @node Q2.1.21, Q2.1.22, Q2.1.20, Installation
-@unnumberedsubsec Q2.1.21: [This question intentionally left blank]
+@unnumberedsubsec Q2.1.21: Every so often the XEmacs frame freezes
+This problem has been fixed in 19.15, and was due to a not easily
+reproducible race condition.
 @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
 @email{dmoore@@ucsd.edu, David Moore} writes:
 debug-on-quit doesn't work if something's turned on inhibit-quit or in
 some other strange cases.
 @end quotation
-@node Q2.1.23, Q2.1.24, Q2.1.22, Installation
+@node Q2.1.23,  , Q2.1.22, Installation
 @unnumberedsubsec Q2.1.23:  Movemail on Linux does not work for XEmacs 19.15 and later.
 Movemail used to work fine in 19.14 but has stopped working in 19.15
 and 20.x.  I am using Linux.
 @example
 #define MAIL_USE_FLOCK
 @end example
 @end quotation
-@node Q2.1.24,  , Q2.1.23, Installation
-@unnumberedsubsec Q2.1.24:  XEmacs won't start without network. (NEW)
-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
-127.0.0.1        localhost
-@end example
-Add that line, and XEmacs will be happy.
 @node Customization, Subsystems, Installation, Top
 @unnumbered 3 Customization and Options
 This is part 3 of the XEmacs Frequently Asked Questions list.  This
 * 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::      [This question intentionally left blank]
+* Q3.1.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
-* Q3.1.4::      [This question intentionally left blank]
+* 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.
 (setq initial-frame-plist '(minibuffer nil))
 (setq default-frame-plist '(minibuffer nil))
 (setq default-minibuffer-frame
 (make-frame
 '(minibuffer only
-width 86
+		    width 86
-height 1
+		    height 1
-menubar-visible-p nil
+		    menubar-visible-p nil
-default-toolbar-visible-p nil
+		    default-toolbar-visible-p nil
-name "minibuffer"
+		    name "minibuffer"
-top -2
+		    top -2
-left -2
+		    left -2
-has-modeline-p nil)))
+		    has-modeline-p nil)))
 (frame-notice-user-settings)
 @end lisp
 @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
 ....
 )
 @end lisp
 @node Q3.1.3, Q3.1.4, Q3.1.2, Customization
-@unnumberedsubsec Q3.1.3: [This question intentionally left blank]
+@unnumberedsubsec Q3.1.3: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
+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.
+These two functions now take frame arguments:
+@lisp
+(set-frame-width (selected-frame) @var{characters})
+(set-frame-height (selected-frame) @var{lines})
+@end lisp
 @node Q3.1.4, Q3.1.5, Q3.1.3, Customization
-@unnumberedsubsec Q3.1.4: [This question intentionally left blank]
+@unnumberedsubsec Q3.1.4: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
+In XEmacs 19.11 I specified @code{Emacs*EmacsScreen.geometry} in
+my @file{.emacs} but this does not work in XEmacs 19.15.
+We have switched from using the term @dfn{screen} to using the term
+@dfn{frame}.
+The correct entry for your @file{.Xdefaults} is now:
+@example
+Emacs*EmacsFrame.geometry
+@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}?
 I'd like the icon to just say @samp{XEmacs}, and not include the name of
 A more sophisticated title might be:
 @lisp
 (setq frame-title-format
 '("%S: " (buffer-file-name "%f"
-(dired-directory dired-directory "%b"))))
+				 (dired-directory dired-directory "%b"))))
 @end lisp
 That is, use the file name, or the dired-directory, or the buffer name.
 @node Q3.1.7, Q3.1.8, Q3.1.6, Customization
 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...
-@email{ben@@xemacs.org, Ben Wing} writes:
+@email{ben@@666.com, Ben Wing} writes:
 @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...
 @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
+					; 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
+					; buffers
 (set-face-foreground 'highlight    "yellow")
 (set-face-background 'modeline     "blue") ; Line at bottom
-; of buffer
+					; 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
+					; while searching
 (set-face-foreground 'isearch      "red")
 (setq x-pointer-foreground-color   "black") ; Adds to bg color,
-; so keep black
+					; so keep black
 (setq x-pointer-background-color   "blue") ; This is color
-; you really
+					; you really
-; want ptr/crsr
+					; want ptr/crsr
 @end lisp
 @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?
 and so on.  You can also do this interactively via @kbd{M-x edit-faces}.
 @end quotation
+@unnumberedsec 3.3: The Modeline
 @node Q3.3.1, Q3.3.2, Q3.2.6, Customization
-@unnumberedsec 3.3: The Modeline
 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
 @lisp
 (set-specifier has-modeline-p nil)
 @end lisp
 Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
 mode:
 @lisp
 (add-hook 'TeX-mode-hook
-'(lambda () (setq fume-display-in-modeline-p nil)))
+	  '(lambda () (setq fume-display-in-modeline-p nil)))
 @end lisp
 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
 @quotation
 For the FAQ example you could use:
 @lisp
 (global-set-key [(control ?.)]
 (lambda () (interactive) (scroll-up 1)))
-(global-set-key [(control ?;)]
+(global-set-key [(control ?		;)]
-(lambda () (interactive) (scroll-up -1)))
+			  (lambda () (interactive) (scroll-up -1)))
 @end lisp
 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}).
 (defun scroll-down-one-line ()
 (interactive)
 (scroll-down 1))
 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
-(global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
+(global-set-key [(control ?		;)] 'scroll-down-one-line) ; C-;
 @end lisp
 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).
 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'
+	xmodmap -e 'keycode 0xff20 = Multi_key'
 @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'.]
 Once you have Multi_key defined, you can use e.g.
 @example
-Multi a '       => �
+	Multi a '	=> �
-Multi e "       => �
+	Multi e "	=> �
-Multi c ,       => �
+	Multi c ,	=> �
 @end example
 etc.
 Also, recent versions of XFree86 define various AltGr-<key>
 combinations as dead keys, i.e.
 @example
-AltGr [         => dead_diaeresis
+	AltGr [		=> dead_diaeresis
-AltGr ]         => dead_tilde
+	AltGr ]		=> dead_tilde
-AltGr ;         => dead_acute
+	AltGr ;		=> dead_acute
 @end example
 etc.
 Running @samp{xmodmap -pk} will list all of the defined keysyms.
 @end quotation
 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.
-@email{ben@@xemacs.org, Ben Wing} writes:
+@email{ben@@666.com, Ben Wing} writes:
 @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
 @kbd{M-x customize @key{RET} display @key{RET}}.
 You can use a color to make it stand out better:
 @example
-Emacs*cursorColor:      Red
+Emacs*cursorColor:	Red
 @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?
 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.
-To get this behavior, add the following lines to your @file{.emacs}:
+To get this behavior, add the following line to your @file{.emacs}:
 @lisp
-(cond
+(turn-on-pending-delete)
-((fboundp 'turn-on-pending-delete)
+@end lisp
-(turn-on-pending-delete))
-((fboundp 'pending-delete-on)
+Note that this will work with both Backspace and Delete.
-(pending-delete-on t)))
-@end lisp
-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.
 @node Q3.10.3, Q3.10.4, Q3.10.2, Customization
 @unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
 I do not like my text highlighted while I am doing isearch as I am not
 @lisp
 (defadvice scroll-up (around scroll-up freeze)
 (interactive "_P")
 (let ((zmacs-region-stays t))
 (if (interactive-p)
-(condition-case nil
+	(condition-case nil
-ad-do-it
+	    ad-do-it
-(end-of-buffer (goto-char (point-max))))
+	  (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
+	(condition-case nil
-ad-do-it
+	    ad-do-it
-(beginning-of-buffer (goto-char (point-min))))
+	  (beginning-of-buffer (goto-char (point-min))))
 ad-do-it)))
 @end lisp
 Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
 answer.
 * 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::      [This question intentionally left blank]
+* 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
 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"))
+	"wing@@netcom.com" "wing@@666.com"))
 @end lisp
 Note that each string is a regular expression.
 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
 @quotation
 @lisp
-; Don't use multiple frames
+					; 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
 @c Changed June
 For mh-e use the following:
 @lisp
 (add-hook 'mh-show-mode-hook '(lambda ()
-(smiley-region (point-min)
+				(smiley-region (point-min)
 (point-max))))
 @end lisp
 @email{bill@@carpenter.ORG, WJCarpenter} writes:
 For VM use the following:
 @item MIME extenders for mh-e, GNUS, RMAIL and VM.
 @end itemize
 tm is available from following anonymous ftp sites:
 @itemize @bullet
-@comment @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
+@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).
+@item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
-@comment @c The host above is unknown.
+@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.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
+@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
 trivial to use.
 @node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
 @unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
-Ben Wing @email{ben@@xemacs.org} writes:
+Ben Wing @email{ben@@666.com} writes:
 @quotation
 It wasn't chown'ed/chmod'd correctly.
 @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?
-@email{steve@@xemacs.org, Steve Baur} writes:
+@email{steve@@altair.xemacs.org, Steve Baur} writes:
 @quotation
 Yes.  Always use the movemail installed with your XEmacs.  Failure to do
 so can result in lost mail.
 @end quotation
-Please refer to @email{jwz@@jwz.org, Jamie Zawinski's} notes at
+Please refer to @email{jwz@@netscape.com, 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
 @iftex
 @*
 @end iftex
 @uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
-@node Q4.4.1, Q4.4.2, Q4.3.5, Subsystems
+@node Q4.4.1, Q4.5.1, Q4.3.5, Subsystems
 @unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
 @unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
 @email{turner@@lanl.gov, John Turner} writes:
 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}.
+@uref{http://www.sun.com/software/Products/Developer-products/programs.html}.
 @end quotation
-@node Q4.4.2, Q4.5.1, Q4.4.1, Subsystems
+@node Q4.5.1, Q4.6.1, Q4.4.1, Subsystems
-@unnumberedsubsec Q4.4.2: How do I start the Sun Workshop support in XEmacs 21?
-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):
-@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
-If you are not using the latest Workshop (5.0) you have to apply the
-following patch:
-@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
-@node Q4.5.1, Q4.6.1, Q4.4.2, Subsystems
 @unnumberedsec 4.5: Energize
 @unnumberedsubsec Q4.5.1: What is/was Energize?
 @email{gray@@meteor.harlequin.com, David N Gray} writes:
 @quotation
 @*
 @end iftex
 @uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
 @node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
-@unnumberedsubsec Q4.7.3: [This question intentionally left blank]
+@unnumberedsubsec Q4.7.3: Byte compiling AUC TeX on XEmacs 19.14.
+@email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} writes:
+@quotation
+When byte compiling auctex-9.4g, you must use the command:
+@example
+xemacs -batch -l lpath.el
+@end example
+@end quotation
 @node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
 @unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
 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.
+so -- we will more likely include it.
 @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.
 appreciated.
 @end enumerate
 @node Q4.7.6,  , Q4.7.5, Subsystems
 @unnumberedsubsec Q4.7.5: Is there a MatLab mode?
+@c New
-Yes, a matlab mode and other items are available at the
+Is there any way I can get syntax highlighting for MatLab .m files?
-@uref{ftp://ftp.mathworks.com/pub/contrib/emacs_add_ons,
+Can I "teach" emacs what words are MatLab commands, comments, etc. ?
-MathWorks' emacs_add_ons ftp directory}.
+@email{elsner@@mathematik.tu-chemnitz.de, Ulrich Elsner} writes:
-@node Miscellaneous, MS Windows, Subsystems, Top
+@quotation
+One way to do this (and much more) is by using the
+@iftex
+@*
+@end iftex
+@uref{ftp://ftp.mathworks.com/pub/contrib/v5/tools/matlab.el, matlab mode}.
+Instructions on how to install this mode are included in this file.
+@end quotation
+@node Miscellaneous, Current Events, Subsystems, Top
 @unnumbered 5 The Miscellaneous Stuff
 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.
 * 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::     How do I turn on filladapt for all buffers?
+* 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::     [This question intentionally left blank]
+* 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?
 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:
 @lisp
-(add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
+(add-hook 'emacs-lisp-mode-hook	'turn-on-font-lock)
-(add-hook 'dired-mode-hook      'turn-on-font-lock)
+(add-hook 'dired-mode-hook	'turn-on-font-lock)
 @end lisp
 to your @file{.emacs}.  See the file @file{etc/sample.emacs} for more
 examples.
 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.0.7, Q5.0.8, Q5.0.6, Miscellaneous
 @unnumberedsubsec Q5.0.7: 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
 @unnumberedsubsec Q5.0.10: [This question intentionally left blank]
 Obsolete question, left blank to avoid renumbering
 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
-@unnumberedsubsec Q5.0.11: How do I turn on filladapt for all buffers?
+@unnumberedsubsec Q5.0.11: Filladapt doesn't work in 19.15
-Filladapt is a minor mode and minor modes are traditionally off by
+Filladapt 2.x is included in 19.15.  In it filladapt is now a minor
-default.  The following added to your @file{.emacs} will turn it on for
+mode and minor modes are traditionally off by default.  The following
-all buffers:
+added to your @file{.emacs} will turn it on for all buffers:
 @lisp
 (setq-default filladapt-mode t)
 @end lisp
 @unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
 @email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
 @quotation
-This can be had from @uref{http://www.python.org/emacs/}.
+This can be had from @uref{http://www.python.org/ftp/emacs/}.
 @end quotation
 @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?
 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
 You can't.  The @code{info} package does not provide for multiple info buffers.
 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
-@unnumberedsubsec Q5.0.18: [This question intentionally left blank]
+@unnumberedsubsec Q5.0.18: I upgraded to XEmacs 19.14 and gnuserv stopped working.
+@email{daku@@nortel.ca, Mark Daku} writes:
+@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
 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
 @unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
 variable if it was bound previously.  If you wish to change a
 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
 You will notice the user-variables by their docstrings beginning with an
 asterisk (a convention).
 does a bad thing, as @code{a} will keep consuming memory, never to be
 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
 Not only is this prettier syntactically, but it makes it possible for
 Note that even global variables should not be @code{setq}ed without
 @code{defvar}ing them first, because the byte-compiler issues warnings.
 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.
+(setq flurghoze t)			; ops!  a typo, but semantically correct.
-; however, the byte-compiler warns.
+					; however, the byte-compiler warns.
 While compiling toplevel forms:
 ** assignment to free variable flurghoze
 @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?
 @c New
-z@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
+z@email{hniksic@@srce.hr, 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.
 @lisp
 (setq bell-volume 0)
 (setq sound-alist nil)
 @end lisp
-That will make your XEmacs totally silent---even the default ding sound
+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
 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)
+(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.
 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
 (included in the compface distribution at XEmacs.org) to do the
-conversion.
+conversion.  For convenience xbm2xface is available for anonymous FTP at
-@comment For convenience xbm2xface is available for anonymous FTP at
+@uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
-@comment @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
 Contributors for this item:
 Paul Emsley,
 Ricardo Marek,
 You use something like:
 @lisp
 (setq Info-directory-list (cons
-(expand-file-name "~/info")
+			   (expand-file-name "~/info")
-Info-default-directory-list))
+			   Info-default-directory-list))
 @end lisp
 @email{davidm@@prism.kla.com, David Masterson} writes:
 @quotation
 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.
-@node MS Windows, Current Events, Miscellaneous, Top
+@node Current Events,  , Miscellaneous, Top
-@unnumbered 6 XEmacs on MS Windows
+@unnumbered 6 What the Future Holds
-This is part 6 of the XEmacs Frequently Asked Questions list, written by
+This is part 6 of the XEmacs Frequently Asked Questions list.  This
-Hrvoje Niksic and others.  This section is devoted to the MS Windows
-port of XEmacs.
-@menu
-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?
-Troubleshooting:
-* Q6.4.1::      XEmacs won't start on Windows. (NEW)
-@end menu
-@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?
-Is XEmacs really getting ported to MS Windows?  What is the status of the port?
-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).
-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 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.
-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.
-@node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
-@unnumberedsubsec Q6.0.3: Are binary kits available?
-Binary kits are available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binary-kits/win32/} for the
-"plain" MS Windows version.
-@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?
-Short answer: No.
-Long answer: XEmacs can be built in several ways in the MS Windows
-environment, some of them requiring an X server and some not.
-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.
-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.
-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.
-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.
-Some of the advantages of the Cygwin version are that it:
-@itemize @bullet
-@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.
-@end itemize
-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).
-@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?
-Pointers to X servers can be found at
-@iftex
-@*
-@end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/};
-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 Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
-@unnumberedsubsec Q6.1.2: What compiler do I need to compile XEmacs?
-You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the Cygwin
-port, which uses Gcc.  There is also a MINGW32 port of XEmacs (using
-Gcc, but using native libraries rather than the Cygwin libraries).  ####
-More information about this should be provided.
-@node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
-@unnumberedsubsec Q6.1.3: How do I compile for the native port?
-Please read the file @file{nt/README} in the XEmacs distribution, which
-contains the full description.
-@node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
-@unnumberedsubsec Q6.1.4: How do I compile for the X port?
-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.
-@node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
-@unnumberedsubsec Q6.1.5: How do I compile for Cygnus' Cygwin?
-Similar as on Unix; use the usual `configure' and `make' process.
-Some problems to watch out for:
-@itemize @bullet
-@item
-make sure HOME is set. This controls where you @file{.emacs} file comes
-from;
-@item
-CYGWIN needs to be set to tty for process support work. e.g. CYGWIN=tty;
-(use CYGWIN32=tty under b19 and older.)
-@item
-picking up some other grep or other unix like tools can kill configure;
-@item
-static heap too small, adjust src/sheap-adjust.h to a more positive
-number;
-@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.
-@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.
-The latest current version is 1.1.1.
-Other common versions you will see are b20.1.
-Another location, one of the mirror sites of the site just mentioned,
-is usually a last faster:
-@uref{ftp://ftp.freesoftware.com/pub/sourceware/cygwin/}
-You can obtain the latest version (currently 1.1.1) from the
-@samp{latest/} subdirectory of either of the above two just-mentioned
-URL's.
-@strong{WARNING: The version of GCC supplied under @samp{latest/}, as of
-June 6th, 2000, does not appear to work.  It generates loads of spurious
-preprocessor warnings and errors, which makes it impossible to compile
-XEmacs with it.}
-You will also need the X libraries.  You can get them on the XEmacs FTP
-site at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/aux/cygwin/}
-You will find b19 and b20 versions of the X libraries, plus b19 and b20
-versions of stuff that should go into @samp{/usr/local/}, donated by
-Andy Piper.  This includes pre-built versions of various graphics libraries,
-such as PNG, JPEG, TIFF, and XPM. (Remember, GIF support is built-in to
-XEmacs.)
-(X libraries for v1 and beyond of Cygwin can be found on the Cygwin site
-itself -- look in the @samp{xfree/} subdirectory.)
-@emph{NOTE:} There are two versions of the XPM library provided in
-Andy's packets.  Once is for building with X support, and the other for
-building without.  The X version should work if you're building with
-both X and Windows support.  The two files are called @file{libXpm-X.a}
-and @file{libXpm-noX.a} respectively, and you must symlink the
-appropriate one to @file{libXpm.a}. @strong{CAREFUL:} By default, the
-non-X version is symlinked in.  If you then configure XEmacs with X,
-you won't run into problems until you start compiling @file{events.c},
-at which point you'll get strange and decidedly non-obvious errors.
-Please see @uref{http://www.xemacs.freeserve.co.uk/} (Andy Piper's home
-page) for more information.
-BTW There are also libraries at
-@iftex
-@*
-@end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}, but
-these are not b19 compatible, and may in fact be native-compiled.
-@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?
-In 21.2.*, use the font menu.  In 21.1.*, you can change font
-manually. 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-*?
-In his flavor of Emacs 20, Richard Stallman has renamed all the win32-*
-symbols to w32-*.  Will XEmacs do the same?
-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.
-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.
-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.
-@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:
-@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
-@item
-GNU Emacs for DOS
-@itemize @minus
-@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
-@item
-GNU Emacs compiled with Win32
-@itemize @minus
-@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
-@item
-NT Emacs
-@itemize @minus
-@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.
-@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}.
-@end itemize
-@item
-XEmacs
-@itemize @minus
-@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.
-@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.
-@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.
-@end itemize
-@end itemize
-@node Q6.3.3, Q6.4.1, 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.
-@node Q6.4.1, ,Q6.3.3, MS Windows
-@unnumberedsec 6.3: Troubleshooting
-@unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)
-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.  Unfortunately, no binary is yet available for
-this version.  Check back periodically at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/}.
-21.2 implements "portable dumping" which will eliminate the problem
-altogether.  You might have better luck with the 21.2 beta binary,
-available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/beta/binaries/}.
-@node Current Events,  , MS Windows, Top
-@unnumbered 7 What the Future Holds
-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.
 @menu
-* Q7.0.1::      What is new in 20.2?
+* Q6.0.1::      What is new in 20.2?
-* Q7.0.2::      What is new in 20.3?
+* Q6.0.2::      What is new in 20.3?
-* Q7.0.3::      What is new in 20.4?
+* Q6.0.3::      What is new in 20.4?
-* Q7.0.4::      Procedural changes in XEmacs development.
+* Q6.0.4::      Procedural changes in XEmacs development.
 @end menu
-@node Q7.0.1, Q7.0.2, Current Events, Current Events
+@node Q6.0.1, Q6.0.2, Current Events, Current Events
-@unnumberedsec 7.0: Changes
+@unnumberedsec 6.0: Changes
-@unnumberedsubsec Q7.0.1: What is new in 20.2?
+@unnumberedsubsec Q6.0.1: What is new in 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
 major mode for editing Tex and LaTeX, and a lot of other stuff).  Many
 bugs from 20.0 have been fixed for this release.  20.2 also contains a
 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
+@node Q6.0.2, Q6.0.3, Q6.0.1, Current Events
-@unnumberedsubsec Q7.0.2: What is new in 20.3?
+@unnumberedsubsec Q6.0.2: What is new in 20.3?
 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
 increased MIME support, and many, many synches with GNU Emacs 20.
 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
+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.
 XEmacs 20.3 is the first non-beta v20 release, and will be the
 basis for all further development.
-@node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
+@node Q6.0.3, Q6.0.4, Q6.0.2, Current Events
-@unnumberedsubsec Q7.0.3: What's new in XEmacs 20.4?
+@unnumberedsubsec Q6.0.3: What's new in XEmacs 20.4?
 XEmacs 20.4 is a bugfix release with no user-visible changes.
 @c Filled in from NEWS file of 20.5-b33
-@node Q7.0.4,  , Q7.0.3, Current Events
+@node Q6.0.4,  , Q6.0.3, Current Events
-@unnumberedsubsec Q7.0.4: Procedural changes in XEmacs development.
+@unnumberedsubsec Q6.0.4: Procedural changes in XEmacs development.
 @enumerate
 @item
 Discussion about the development of XEmacs occurs on the xemacs-beta
 mailing list.  Subscriptions to this list will now be fully automated
 XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
 the collected bugfixes.
 @item
-As of December 1996, @email{steve@@xemacs.org, Steve Baur} has become
+As of December 1996, @email{steve@@altair.xemacs.org, Steve Baur} has become
 the lead maintainer of XEmacs.
 @end enumerate
 @bye

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 412:697ef44129c6 r21-2-14