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

comparison man/xemacs-faq.texi @ 442:abe6d1db359e r21-2-36

Import from CVS: tag r21-2-36

author	cvs
date	Mon, 13 Aug 2007 11:35:02 +0200
parents	8de8e3f6228a
children	576fb035e263

comparison

equal deleted inserted replaced

-:72a7cfa4a488
+:abe6d1db359e
-\input texinfo.tex      @c -*-texinfo-*-
+\input texinfo.tex      @c -*- mode: texinfo; coding: iso-2022-8 -*-
 @c %**start of header
 @setfilename ../info/xemacs-faq.info
 @settitle Frequently asked questions about XEmacs
 @setchapternewpage off
 @c %**end of header
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2000/01/27 17:11:28 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2000/09/19 07:50:41 $
 @sp 1
 @author Tony Rossini <rossini@@biostat.washington.edu>
 @author Ben Wing <ben@@xemacs.org>
 @author Chuck Thompson <cthomp@@xemacs.org>
 @author Steve Baur <steve@@xemacs.org>
 @top XEmacs FAQ
 @unnumbered Introduction
 This is the guide to the XEmacs Frequently Asked Questions list---a
 compendium of questions and answers pertaining to one of the finest
-programs ever written.  It is much more than just a Text Editor.
+programs ever written.  XEmacs is much more than just a Text Editor.
-This FAQ is freely redistributable.  I take no liability for the
+This FAQ is freely redistributable.  This FAQ is distributed in the hope
-correctness and safety of any procedures or advice given here.  This
+that it will be useful, but WITHOUT ANY WARRANTY; without even the
-FAQ is distributed in the hope that it will be useful, but WITHOUT ANY
+implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE.
 If you have a Web browser, the official hypertext version is at
 @iftex
 @*
 @end iftex
-@uref{http://www.xemacs.org/faq/xemacs-faq.html}.
+@uref{http://www.xemacs.org/faq/xemacs-faq.html}
-This version is somewhat nicer than the unofficial hypertext versions
-that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
-archives.
 @ifset CANONICAL
 @html
 This document is available in several different formats:
 @itemize @bullet
 * Q1.0.2::      What is the current version of XEmacs?
 * Q1.0.3::      Where can I find it?
 * Q1.0.4::      Why Another Version of Emacs?
 * Q1.0.5::      Why Haven't XEmacs and GNU Emacs Merged?
 * Q1.0.6::      Where can I get help?
-* Q1.0.7::      Where is the mailing list archived?
+* Q1.0.7::      Where are the mailing lists archived?
 * Q1.0.8::      How do you pronounce XEmacs?
 * Q1.0.9::      What does XEmacs look like?
 * Q1.0.10::     Is there a port of XEmacs to Microsoft ('95 or NT)?
 * Q1.0.11::     Is there a port of XEmacs to the Macintosh?
 * Q1.0.12::     Is there a port of XEmacs to NextStep?
 * Q1.2.1::      Who wrote XEmacs?
 * Q1.2.2::      Who contributed to this version of the FAQ?
 * Q1.2.3::      Who contributed to the FAQ in the past?
 Internationalization:
-* Q1.3.1::      What is the status of XEmacs v20?
+* Q1.3.1::      What is the status of internationalization support aka MULE (including Asian language support?
-* Q1.3.2::      What is the status of Asian-language support, aka @var{mule}?
+* Q1.3.2::      How can I help with internationalization?
 * Q1.3.3::      How do I type non-ASCII characters?
 * Q1.3.4::      Can XEmacs messages come out in a different language?
-* Q1.3.5::      Please explain the various input methods in MULE/XEmacs 20.0
+* Q1.3.5::      Please explain the various input methods in MULE/XEmacs
-* Q1.3.6::      How do I portably code for MULE/XEmacs 20.0?
+* Q1.3.6::      How do I portably code for MULE/XEmacs?
 * Q1.3.7::      How about Cyrillic Modes?
 Getting Started:
 * Q1.4.1::      What is a @file{.emacs} and is there a sample one?
 * Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
 * Q5.1.2::      Can I generate "fake" keyboard events?
 * Q5.1.3::      Could you explain @code{read-kbd-macro} in more detail?
 * Q5.1.4::      What is the performance hit of @code{let}?
 * Q5.1.5::      What is the recommended use of @code{setq}?
 * Q5.1.6::      What is the typical misuse of @code{setq} ?
-* Q5.1.7::      I like the the @code{do} form of cl, does it slow things down?
+* Q5.1.7::      I like the @code{do} form of cl, does it slow things down?
 * Q5.1.8::      I like recursion, does it slow things down?
 * Q5.1.9::      How do I put a glyph as annotation in a buffer?
 * Q5.1.10::     @code{map-extents} won't traverse all of my extents!
 * Q5.1.11::     My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
 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?
 * Q1.0.2::      What is the current version of XEmacs?
 * Q1.0.3::      Where can I find it?
 * Q1.0.4::      Why Another Version of Emacs?
 * Q1.0.5::      Why Haven't XEmacs and GNU Emacs Merged?
 * Q1.0.6::      Where can I get help?
-* Q1.0.7::      Where is the mailing list archived?
+* Q1.0.7::      Where are the mailing lists archived?
 * Q1.0.8::      How do you pronounce XEmacs?
 * Q1.0.9::      What does XEmacs look like?
 * Q1.0.10::     Is there a port of XEmacs to Microsoft ('95 or NT)?
 * Q1.0.11::     Is there a port of XEmacs to the Macintosh?
 * Q1.0.12::     Is there a port of XEmacs to NextStep?
 * Q1.2.1::      Who wrote XEmacs?
 * Q1.2.2::      Who contributed to this version of the FAQ?
 * Q1.2.3::      Who contributed to the FAQ in the past?
 Internationalization:
-* Q1.3.1::      What is the status of XEmacs v20?
+* Q1.3.1::      What is the status of internationalization support aka MULE (including Asian language support?
-* Q1.3.2::      What is the status of Asian-language support, aka @var{mule}?
+* Q1.3.2::      How can I help with internationalization?
 * Q1.3.3::      How do I type non-ASCII characters?
 * Q1.3.4::      Can XEmacs messages come out in a different language?
-* Q1.3.5::      Please explain the various input methods in MULE/XEmacs 20.0
+* Q1.3.5::      Please explain the various input methods in MULE/XEmacs
-* Q1.3.6::      How do I portably code for MULE/XEmacs 20.0?
+* Q1.3.6::      How do I portably code for MULE/XEmacs?
 * Q1.3.7::      How about Cyrillic Modes?
 Getting Started:
 * Q1.4.1::      What is a @file{.emacs} and is there a sample one?
 * Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
 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 versions 21.1.* are releases made from the current stable
+sources.  XEmacs versions 21.2.* are releases made from the development
-XEmacs 20.4 is a minor upgrade from 20.3, containing many bugfixes. It
+sources.  Check at @uref{http://www.xemacs.org} for the current minor
-was released in February 1998.
+version.
 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
 list.  To cancel a subscription, you @strong{must} use the
 xemacs-request address.  Send a message with a subject of
 @samp{unsubscribe} to be removed.
 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
-@unnumberedsubsec Q1.0.7: Where is the mailing list archived?
+@unnumberedsubsec Q1.0.7: Where are the mailing lists archived?
 The archives can be found at @uref{http://www.xemacs.org/Lists/Archive}
 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
 @c
 @c For the MacOS, there is a port of
 @c @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 @uref{pjarvis@@ispchannel.com,Pitts Jarvis}.  It's available
+8.5.1 by @email{pjarvis@@ispchannel.com, Pitts Jarvis}.  It's available
-at @uref{http://my.ispchannel.com/~pjarvis/xemacs.html,
+at @uref{http://my.ispchannel.com/~pjarvis/xemacs.html}.
-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
 Pre-printed manuals are not available.  If you are familiar with
 TeX, you can generate your own manual from the XEmacs sources.
 HTML and Postscript versions of XEmacs manuals may be available from the
-XEmacs web site in the future.
+XEmacs web site in the future.  Send requests to @email{faq@@xemacs.org}.
 @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?
 maintainers}.
 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
 If you think you have a better way of answering a question, or think a
 question should be included, we'd like to hear about it.  Questions and
-answers included into the FAQ will be edited for spelling and grammar,
+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
+either from versions of the FAQ dated before May 1996 or are from
-of the four people listed at the top of this document.  Answers quoted
+previous FAQ maintainers.  Answers quoted from Usenet news articles will
-from Usenet news articles will always be attributed, regardless of the
+always be attributed, regardless of the author.
-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
 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
 @end itemize
 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
 @unnumberedsec 1.3: Internationalization
-@unnumberedsubsec Q1.3.1: What is the status of XEmacs v20?
+@unnumberedsubsec Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
-XEmacs v20 is the version of XEmacs that includes MULE (Asian-language)
+Both the stable and development versions of XEmacs include
-support.  XEmacs 20.0 was released in February 1997, followed by XEmacs
+internationalization support (aka MULE).  MULE currently works on UNIX
-20.2 in May, XEmacs 20.3 in November and XEmacs 20.4 in February 1998.  When compiled without MULE
+and Linux systems; work for supporting MULE on Windows operating systems
-support, 20.4 is approximately as stable as 19.16, and probably faster
+is in progress.  Binaries compiled without MULE support run faster than
-(due to additional optimization work.)
+MULE capable XEmacsen.
-As of XEmacs 20.3, version 20 is @emph{the} supported version of
-XEmacs.  This means that 19.16 will optionally receive stability fixes
-(if any), but that all the real development work will be done on the v20
-tree.
-The incompatible changes in XEmacs 20 include the additional byte-codes,
-new primitive data types (@code{character}, @code{char-table}, and
-@code{range-table}).  This means that the character-integer equivalence
-inherent to all the previous Emacs and XEmacs releases no longer
-applies.
-However, to avoid breaking old code, many functions that should normally
-accept characters work with integers, and vice versa.  For more
-information, see the Lisp reference manual.  Here is a relevant excerpt,
-for your convenience.
-@quotation
-In XEmacs version 19, and in all versions of FSF GNU Emacs, a
-@dfn{character} in XEmacs Lisp is nothing more than an integer.
-This is yet another holdover from XEmacs Lisp's derivation from
-vintage-1980 Lisps; modern versions of Lisp consider this equivalence
-a bad idea, and have separate character types.  In XEmacs version 20,
-the modern convention is followed, and characters are their own
-primitive types. (This change was necessary in order for @sc{mule},
-i.e. Asian-language, support to be correctly implemented.)
-Even in XEmacs version 20, remnants of the equivalence between
-characters and integers still exist; this is termed the @dfn{char-int
-confoundance disease}.  In particular, many functions such as @code{eq},
-@code{equal}, and @code{memq} have equivalent functions (@code{old-eq},
-@code{old-equal}, @code{old-memq}, etc.) that pretend like characters
-are integers are the same.  Byte code compiled under any version 19
-Emacs will have all such functions mapped to their @code{old-} equivalents
-when the byte code is read into XEmacs 20.  This is to preserve
-compatibility---Emacs 19 converts all constant characters to the equivalent
-integer during byte-compilation, and thus there is no other way to preserve
-byte-code compatibility even if the code has specifically been written
-with the distinction between characters and integers in mind.
-Every character has an equivalent integer, called the @dfn{character
-code}.  For example, the character @kbd{A} is represented as the
-@w{integer 65}, following the standard @sc{ascii} representation of
-characters.  If XEmacs was not compiled with @sc{mule} support, the
-range of this integer will always be 0 to 255---eight bits, or one
-byte. (Integers outside this range are accepted but silently truncated;
-however, you should most decidedly @emph{not} rely on this, because it
-will not work under XEmacs with @sc{mule} support.)  When @sc{mule}
-support is present, the range of character codes is much
-larger. (Currently, 19 bits are used.)
-FSF GNU Emacs uses kludgy character codes above 255 to represent
-keyboard input of @sc{ascii} characters in combination with certain
-modifiers.  XEmacs does not use this (a more general mechanism is
-used that does not distinguish between @sc{ascii} keys and other
-keys), so you will never find character codes above 255 in a
-non-@sc{mule} XEmacs.
-Individual characters are not often used in programs.  It is far more
-common to work with @emph{strings}, which are sequences composed of
-characters.
-@end quotation
 @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?
+@unnumberedsubsec Q1.3.2: How can I help with internationalization?
-MULE support is now available for UNIX versions of XEmacs.
 If you would like to help, you may want to join the
 @email{xemacs-mule@@xemacs.org} mailing list.  Especially needed are
 people who speak/write languages other than English, who are willing to
 use XEmacs/MULE regularly, and have some experience with Elisp.
 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
 @unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
 The message-catalog support has mostly been written but doesn't
 currently work.  The first release of XEmacs 20 will @emph{not} support
-it.  However, menubar localization @emph{does} work, even in 19.14.  To
+it.  However, menubar localization @emph{does} work.  To
 enable it, add to your @file{Emacs} file entries like this:
 @example
 Emacs*XlwMenu.resourceLabels:                   True
 Emacs*XlwMenu.file.labelString:                 Fichier
-Emacs*XlwMenu.openInOtherWindow.labelString:    In anderem Fenster offnen
+Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster oeffnen
 @end example
 The name of the resource is derived from the non-localized entry by
 removing punctuation and capitalizing as above.
 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
-@unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
+@unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs
 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
 @quotation
 Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
 plan is stopped.  Perhaps after Mule merged GNU Emacs will be released,
 it will be continued.
 @end quotation
 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
-@unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs 20?
+@unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs?
 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
 @quotation
 MULE and XEmacs are quite different. So the application
 @end menu
 @node Q2.0.1, Q2.0.2, Installation, Installation
 @unnumberedsec 2.0: Installation
 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
-The @file{INSTALL} file says that up to 108 MB of space is needed
-temporarily during installation!  How can I just try it out?
+How can I just try XEmacs without installing it?
 XEmacs will run in place without requiring installation and copying of
 the Lisp directories, and without having to specify a special build-time
 flag.  It's the copying of the Lisp directories that requires so much
 space.  XEmacs is largely written in Lisp.
 This will let you run XEmacs without massive copying.
 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
 @unnumberedsubsec Q2.0.2: XEmacs is too big
-Although this entry has been written for XEmacs 19.13, most of it still
+The space required by the installation directories can be
-stands true.
-@email{steve@@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
+the packages you'll never want to use.  Remove the TexInfo manuals.
-obsolete mailcrypts and Gnus 4 in 19.13).  Remove the TexInfo manuals.
 Remove the Info (and use just hardcopy versions of the manual).  Remove
 most of the stuff in etc.  Remove or gzip all the source code.  Gzip or
 remove the C source code.  Configure it so that copies are not made of
-the support lisp.  I'm not advocating any of these things, just pointing
+the support lisp.
-out ways to reduce the disk requirements if desired.
-Now examine the space used by directory:
-@format
-0       /usr/local/bin/xemacs
-2048    /usr/local/bin/xemacs-19.13
-1546    /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
-1158    /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
-@end format
-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
-122     /usr/local/lib/xemacs-19.13/etc/sounds
-18      /usr/local/lib/xemacs-19.13/etc/sparcworks
-159     /usr/local/lib/xemacs-19.13/etc/vm
-6       /usr/local/lib/xemacs-19.13/etc/e
-21      /usr/local/lib/xemacs-19.13/etc/eos
-172     /usr/local/lib/xemacs-19.13/etc/toolbar
-61      /usr/local/lib/xemacs-19.13/etc/ns
-43      /usr/local/lib/xemacs-19.13/etc/gnus
-@end format
-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
-175     /usr/local/lib/xemacs-19.13/lisp/bytecomp
-340     /usr/local/lib/xemacs-19.13/lisp/calendar
-342     /usr/local/lib/xemacs-19.13/lisp/comint
-517     /usr/local/lib/xemacs-19.13/lisp/dired
-42      /usr/local/lib/xemacs-19.13/lisp/electric
-212     /usr/local/lib/xemacs-19.13/lisp/emulators
-238     /usr/local/lib/xemacs-19.13/lisp/energize
-289     /usr/local/lib/xemacs-19.13/lisp/gnus
-457     /usr/local/lib/xemacs-19.13/lisp/ilisp
-1439    /usr/local/lib/xemacs-19.13/lisp/modes
-2276    /usr/local/lib/xemacs-19.13/lisp/packages
-1040    /usr/local/lib/xemacs-19.13/lisp/prim
-176     /usr/local/lib/xemacs-19.13/lisp/pcl-cvs
-154     /usr/local/lib/xemacs-19.13/lisp/rmail
-3       /usr/local/lib/xemacs-19.13/lisp/epoch
-45      /usr/local/lib/xemacs-19.13/lisp/term
-860     /usr/local/lib/xemacs-19.13/lisp/utils
-851     /usr/local/lib/xemacs-19.13/lisp/vm
-13      /usr/local/lib/xemacs-19.13/lisp/vms
-157     /usr/local/lib/xemacs-19.13/lisp/x11
-19      /usr/local/lib/xemacs-19.13/lisp/tooltalk
-14      /usr/local/lib/xemacs-19.13/lisp/sunpro
-291     /usr/local/lib/xemacs-19.13/lisp/games
-198     /usr/local/lib/xemacs-19.13/lisp/edebug
-619     /usr/local/lib/xemacs-19.13/lisp/w3
-229     /usr/local/lib/xemacs-19.13/lisp/eos
-55      /usr/local/lib/xemacs-19.13/lisp/iso
-59      /usr/local/lib/xemacs-19.13/lisp/mailcrypt
-187     /usr/local/lib/xemacs-19.13/lisp/eterm
-356     /usr/local/lib/xemacs-19.13/lisp/ediff
-408     /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
-1262    /usr/local/lib/xemacs-19.13/lisp/hyperbole
-247     /usr/local/lib/xemacs-19.13/lisp/hm--html-menus
-161     /usr/local/lib/xemacs-19.13/lisp/mh-e
-299     /usr/local/lib/xemacs-19.13/lisp/viper
-53      /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
-4       /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib
-3       /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib
-3       /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib
-11      /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
-53      /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
-466     /usr/local/lib/xemacs-19.13/lisp/oobr
-14142   /usr/local/lib/xemacs-19.13/lisp
-@end format
 These are all Emacs Lisp source code and bytecompiled object code.  You
 may safely gzip everything named *.el here.  You may remove any package
 you don't use.  @emph{Nothing bad will happen if you delete a package
 that you do not use}.  You must be sure you do not use it though, so be
 conservative at first.
-Possible candidates for deletion include w3 (newer versions exist, or
+Possible candidates for deletion include w3, games, hyperbole, mh-e,
-you may just use Lynx or Netscape for web browsing), games, hyperbole,
+hm-html-menus, vm, viper, oobr, gnus, etc.  Ask yourself, @emph{Do I
-mh-e, hm--html-menus (better packages exist), vm, viper, oobr, gnus (new
+ever want to use this package?}  If the answer is no, then it is a
-versions exist), etc.  Ask yourself, @emph{Do I ever want to use this
+candidate for removal.
-package?}  If the answer is no, then it is a candidate for removal.
 First, gzip all the .el files.  Then go about package by package and
 start gzipping the .elc files.  Then run XEmacs and do whatever it is
 you normally do.  If nothing bad happens, then delete the directory.  Be
 conservative about deleting directories, and it would be handy to have a
-backup tape around in case you get too zealous.
+backup around in case you get too zealous.
 @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
+Online texinfo sources in the @file{info} can either be compressed them
-1972    /usr/local/lib/xemacs-19.13/info
+or remove them.  In either case, @kbd{C-h i} (info mode) will no longer
-@end example
+work.
-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
-@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
-@email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} provides this procedure:
-@quotation
-Substitute @file{/usr/local/lib/} with the path where the xemacs tree is
-rooted, then use this script:
-@example
-#!/bin/sh
-r=/usr/local/lib/xemacs-19.13/lisp
-cd $r ; rm -f cmpr ; touch cmpr
-du -s .
-for d in * ; do
-if test -d $d ; then
-cd $d
-for f in *.el ; do
-#     compress (remove) only (ONLY) the sources that have a
-#     corresponding compiled file --- do not (DO NOT)
-#     touch other sources
-if test -f $@{f@}c ; then gzip -v9 $f >> $r/cmpr ; fi
-done
-cd ..
-fi
-done
-du -s .
-@end example
-A step beyond would be substituting @samp{rm -f} for @samp{gzip -v9},
-but you have to be desperate for removing the sources (remember that
-emacs can access compressed files transparently).
-Also, a good megabyte could easily be trimmed from the $r/../etc
-directory, e.g., the termcap files, some O+NEWS, others that I don't
-remember as well.
-@end quotation
-@quotation
-XEmacs 21.0 will unbundle the lisp hierarchy and allow the installer
-to choose exactly how much support code gets installed.
-@end quotation
 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
 @unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
 What is the best way to compile XEmacs with the netaudio system, since I
 @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
+@strong{not} an X Window System-only version of Emacs.  XEmacs has
-19.14 XEmacs has full color support on a color-capable character
+full color support on a color-capable character terminal.
-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?
 There have been a variety of reports of crashes due to compilers with
 @end example
 @end quotation
 @node Q2.1.24,  , Q2.1.23, Installation
 @unnumberedsubsec Q2.1.24:  XEmacs won't start without network. (NEW)
-Q2.1.23:  Movemail on Linux does not work for XEmacs 19.15 and later.
 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:
 and so on.  You can also do this interactively via @kbd{M-x edit-faces}.
 @end quotation
+@node Q3.3.1, Q3.3.2, Q3.2.6, Customization
 @unnumberedsec 3.3: The Modeline
-@node Q3.3.1, Q3.3.2, Q3.2.6, Customization
 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
 @lisp
 (set-specifier has-modeline-p nil)
 @end lisp
 * Q5.1.2::      Can I generate "fake" keyboard events?
 * Q5.1.3::      Could you explain @code{read-kbd-macro} in more detail?
 * Q5.1.4::      What is the performance hit of @code{let}?
 * Q5.1.5::      What is the recommended use of @code{setq}?
 * Q5.1.6::      What is the typical misuse of @code{setq}?
-* Q5.1.7::      I like the the @code{do} form of cl, does it slow things down?
+* Q5.1.7::      I like the @code{do} form of cl, does it slow things down?
 * Q5.1.8::      I like recursion, does it slow things down?
 * Q5.1.9::      How do I put a glyph as annotation in a buffer?
 * Q5.1.10::     @code{map-extents} won't traverse all of my extents!
 * Q5.1.11::     My elisp program is horribly slow.  Is there an easy way to find out where it spends time?
 While compiling toplevel forms:
 ** assignment to free variable flurghoze
 @end lisp
 @node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
-@unnumberedsubsec Q5.1.7: I like the the @code{do} form of cl, does it slow things down?
+@unnumberedsubsec Q5.1.7: I like the @code{do} form of cl, does it slow things down?
 It shouldn't.  Here is what Dave Gillespie has to say about cl.el
 performance:
 @quotation
 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?
 @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 or 5.0, with the exception of the Cygwin port,
+You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the Cygwin
-which uses Gcc.
+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?
 @item
 make sure HOME is set. This controls where you @file{.emacs} file comes
 from;
 @item
-CYGWIN32 needs to be set to tty for process support
+CYGWIN needs to be set to tty for process support work. e.g. CYGWIN=tty;
-work. e.g. CYGWIN32=tty;
+(use CYGWIN32=tty under b19 and older.)
 @item
 picking up some other grep or other unix like tools can kill configure;
 @item
 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.
-You will also need the X libraries.  There are libraries at
+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.  You can get b19 X11R6.3 binaries, as
+these are not b19 compatible, and may in fact be native-compiled.
-well as pre-built ncurses and graphic libraries, from:
-@uref{ftp://ftp.parallax.co.uk/pub/andyp/}.
 @node Q6.2.1, Q6.2.2, Q6.1.6, MS Windows
 @unnumberedsec 6.2: Customization and User Interface
 @unnumberedsubsec Q6.2.1: How will the port cope with differences in the Windows user interface?
 @end itemize
 @end itemize
-@node Q6.3.3, , Q6.3.2, MS Windows
+@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

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 442:abe6d1db359e r21-2-36