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

comparison man/xemacs-faq.texi @ 462:0784d089fdc9 r21-2-46

Import from CVS: tag r21-2-46

author	cvs
date	Mon, 13 Aug 2007 11:44:37 +0200
parents	d7a9135ec789
children	5aa1854ad537

comparison

equal deleted inserted replaced

-:120ed4009e51
+:0784d089fdc9
 @setchapternewpage off
 @c %**end of header
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/01/18 13:35:02 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/03/08 08:19:10 $
 @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>
 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
 @item
 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
 download the faq} in info format, and install it in @file{<XEmacs
 library directory>/info/}. For example in
-@file{/usr/local/lib/xemacs-20.4/info/}.
+@file{/usr/local/lib/xemacs-21.4/info/}.
 @end itemize
 @end html
 * Q1.3.5::      Please explain the various input methods in MULE/XEmacs
 * 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.1::      What is an @file{init.el} or @file{.emacs} and is there a sample one?
-* Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
+* Q1.4.2::      Can I use the same @file{init.el}/@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?
 * Q3.1.6::      How can I have the window title area display the full path?
 * Q3.1.7::      @samp{xemacs -name junk} doesn't work?
 * Q3.1.8::      @samp{-iconic} doesn't work.
 Textual Fonts & Colors:
-* Q3.2.1::      How can I set color options from @file{.emacs}?
+* Q3.2.1::      How can I set color options from @file{init.el}/@file{.emacs}?
 * Q3.2.2::      How do I set the text, menu and modeline fonts?
 * Q3.2.3::      How can I set the colors when highlighting a region?
 * Q3.2.4::      How can I limit color map usage?
 * Q3.2.5::      My tty supports color, but XEmacs doesn't use them.
 * Q3.2.6::      Can I have pixmap backgrounds in XEmacs?
 * Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
 * Q3.5.4::      Globally binding @kbd{Delete}?
 * Q3.5.5::      Scrolling one line at a time.
 * Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
 * Q3.5.7::      How can you type in special characters in XEmacs?
-* Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
+* Q3.5.8::      [This question intentionally left blank]
 * Q3.5.9::      How do I make the Delete key delete forward?
 * Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
 * Q3.5.11::     How do I map the arrow keys?
 The Cursor:
 Scrollbars:
 * Q3.9.1::      How can I disable the scrollbar?
 * Q3.9.2::      How can one use resources to change scrollbar colors?
 * Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
-* Q3.9.4::      How can I get automatic horizontal scrolling?
+* Q3.9.4::      How can I turn off automatic horizontal scrolling in specific modes?
 Text Selections:
 * Q3.10.1::     How can I turn off or change highlighted selections?
 * Q3.10.2::     How do I get that typing on an active region removes it?
 * Q3.10.3::     Can I turn off the highlight during isearch?
 The Miscellaneous Stuff
 * Q5.0.1::      How can I do source code highlighting using font-lock?
 * Q5.0.2::      I do not like cc-mode.  How do I use the old c-mode?
 * Q5.0.3::      How do I get @samp{More} Syntax Highlighting on by default?
-* Q5.0.4::      How can I enable auto-indent?
+* Q5.0.4::      How can I enable auto-indent and/or Filladapt?
 * Q5.0.5::      How can I get XEmacs to come up in text/auto-fill mode by default?
 * Q5.0.6::      How do I start up a second shell buffer?
 * Q5.0.7::      Telnet from shell filters too much.
 * Q5.0.8::      Why does edt emulation not work?
 * Q5.0.9::      How can I emulate VI and use it as my default mode?
 * Q5.0.10::     [This question intentionally left blank]
-* Q5.0.11::     How do I turn on filladapt for all buffers?
+* Q5.0.11::     [This question intentionally left blank]
 * 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.2.3::      What's NAS, how do I get it?
 * Q5.2.4::      Sunsite sounds don't play.
 Miscellaneous:
 * Q5.3.1::      How do you make XEmacs indent CL if-clauses correctly?
-* Q5.3.2::      Fontifying hangs when editing a postscript file.
+* Q5.3.2::      [This question intentionally left blank]
 * Q5.3.3::      How can I print WYSIWYG a font-locked buffer?
 * Q5.3.4::      Getting @kbd{M-x lpr} to work with postscript printer.
 * Q5.3.5::      How do I specify the paths that XEmacs uses for finding files?
 * Q5.3.6::      [This question intentionally left blank]
 * Q5.3.7::      Can I have the end of the buffer delimited in some way?
 XEmacs on MS Windows
 General Info:
 * Q6.0.1::      What is the status of the XEmacs port to Windows?
 * Q6.0.2::      What flavors of MS Windows are supported?
-* Q6.0.3::      Are binary kits available?
+* Q6.0.3::      Are binaries available?
-* Q6.0.4::      Does XEmacs on MS Windows require an X server to run?
+* Q6.0.4::      Can I build XEmacs on MS Windows with support for X or Cygwin?
 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.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?
+* Q6.2.3::      Where do I put my @file{init.el}/@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?
 * Q1.3.5::      Please explain the various input methods in MULE/XEmacs
 * 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.1::      What is an @file{init.el} or @file{.emacs} and is there a sample one?
-* Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
+* Q1.4.2::      Can I use the same @file{init.el}/@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?
 @end menu
 @node Q1.0.1, Q1.0.2, Introduction, Introduction
 @unnumberedsec 1.0: Introduction
 @unnumberedsubsec Q1.0.1: What is XEmacs?
-An alternative to GNU Emacs, originally based on an early alpha version
+XEmacs is a highly customizable open source text editor and application
-of FSF's version 19, and has diverged quite a bit since then.  XEmacs
+development system.  It is protected under the GNU Public License and
-was known as Lucid Emacs through version 19.10.  Almost all features of
+related to other versions of Emacs, in particular GNU Emacs.  Its
-GNU Emacs are supported in XEmacs.  The maintainers of XEmacs actively
+emphasis is on modern graphical user interface support and an open
-track changes to GNU Emacs while also working to add new features.
+software development model, similar to Linux.  XEmacs has an active
+development community numbering in the hundreds, and runs on Windows 95
+and NT, Linux and nearly every other version of Unix in
+existence.  Support for XEmacs has been supplied by Sun Microsystems,
+University of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
+Corporation, BeOpen, and others, as well as the unpaid time of a great
+number of individual developers.
 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
 XEmacs versions 21.1.* are releases made from the current stable
 @item
 The XEmacs maintainers are generally more receptive to suggestions than
 the GNU Emacs maintainers.
 @item
-Many more bundled packages than GNU Emacs
+Many more bundled packages than GNU Emacs.
 @item
 Binaries are available for many common operating systems.
 @item
 @item
 Better Motif compliance.
 @item
 Some internationalization support (including full MULE support, if
-compiled with it.)
+compiled with it).
 @item
 Variable-width fonts.
 @item
 The ability to embed arbitrary graphics in a buffer.
 @item
 Completely compatible (at the C level) with the Xt-based toolkits.
-@item
-First production Web Browser supporting Style Sheets.
 @end itemize
 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
 @unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
 @unnumberedsubsec Q1.0.6: Where can I get help?
 Probably the easiest way, if everything is installed, is to use Info, by
-pressing @kbd{C-h i}, or selecting @code{Manuals->Info} from the
+pressing @kbd{C-h i}, or looking for an Info item on the
 Help Menu.  @kbd{M-x apropos} can be used to look for particular commands.
 For items not found in the manual, try reading this FAQ
 @comment , examining the regular GNU Emacs FAQ (which can be
 @comment found with the Emacs 19 distribution) as well as at
 @samp{unsubscribe} to be removed.
 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
 @unnumberedsubsec Q1.0.7: Where are the mailing lists archived?
-The archives can be found at @uref{http://www.xemacs.org/Lists/Archive}
+The archives can be found at @uref{http://list-archive.xemacs.org}
 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
 The most common pronounciation is @samp{Eks eemax}.
 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
 Yes, @xref{MS Windows}.
-@comment Thanks to efforts of many people, coordinated by
-@comment @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
-@comment Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
-@comment (NT and 95).  The current betas require having an X server to run
-@comment XEmacs; however, a native NT/95 port is in alpha, thanks to
-@comment @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
-@comment
-@comment Although some features are still unimplemented, XEmacs 21.0 will support
-@comment MS-Windows.
-@comment
-@comment The NT development is now coordinated by a mailing list at
-@comment @email{xemacs-nt@@xemacs.org}.
-@comment
-@comment If you are willing to contribute or want to follow the progress, mail to
-@comment @iftex
-@comment @*
-@comment @end iftex
-@comment @email{xemacs-nt-request@@xemacs.org} to subscribe.
-@comment
-@comment Furthermore, Altrasoft is seeking corporate and government sponsors to
-@comment help fund a fully native port of XEmacs to Windows 95 and NT using
-@comment full-time, senior-level staff working under a professionally managed
-@comment project structure.  See @uref{http://www.altrasoft.com/, the Altrasoft
-@comment web site} for more details
-@comment or contact Altrasoft directly at 1-888-ALTSOFT.
-@comment
-@comment
-@comment The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
-@comment Emacs 19.6.  Available from @uref{http://www.pearlsoft.com/}.
-@comment
-@comment There's a port of GNU Emacs (not XEmacs) at
-@comment @example
-@comment @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
-@comment @end example
 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
 @unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
 @c changed
 @node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
 @unnumberedsec 1.2: Credits
 @unnumberedsubsec Q1.2.1: Who wrote XEmacs?
 XEmacs is the result of the time and effort of many people.  The
-developers responsible for the 19.16/20.x releases are:
+developers responsible for recent releases are:
 @itemize @bullet
 @item @email{martin@@xemacs.org, Martin Buchholz}
 @html
 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
 @end html
+@item @email{turnbull@@sk.tsukuba.ac.jp, Steven Turnbull}
+@item @email{ben@@xemacs.org, Ben Wing}
+@html
+<br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
+@end html
+@item @email{hniksic@@xemacs.org, Hrvoje Niksic}
+@html
+<br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
+@end html
+@end itemize
+The developers responsible for older releases were:
+@itemize @bullet
 @item @email{steve@@xemacs.org, Steve Baur}
 @html
 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
 @end html
-@item @email{hniksic@@xemacs.org, Hrvoje Niksic}
-@html
-<br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
-@end html
-@end itemize
-The developers responsible for the 19.14 release are:
-@itemize @bullet
 @item @email{cthomp@@xemacs.org, Chuck Thompson}
 @html
 <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
 @end html
-Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
-for XEmacs becoming a widely distributed program over the Internet.
-@item @email{ben@@xemacs.org, Ben Wing}
-@html
-<br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
-@end html
-@end itemize
-@itemize @bullet
 @item @email{jwz@@jwz.org, Jamie Zawinski}
 @html
 <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
 @end html
-Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the last
-release actually named Lucid Emacs.  Richard Mlynarik was crucial to
-most of those releases.
 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
+Steve Baur was the primary maintainer for 19.15 through 21.0.
+Chuck Thompson and Ben Wing were the maintainers for 19.11 through 19.14
+and heavy code contributors for 19.8 through 19.10.
+Jamie Zawinski was the maintainer for 19.0 through 19.10 (the entire
+history of Lucid Emacs).  Richard Mlynarik was a heavy code contributor
+to 19.6 through 19.8.
 @end itemize
 Along with many other contributors, partially enumerated in the
 @samp{About XEmacs} option in the Help menu.
 XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
 @end quotation
 @node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
 @unnumberedsec 1.4: Getting Started, Backing up & Recovery
-@unnumberedsubsec Q1.4.1: What is a @file{.emacs} and is there a sample one?
+@unnumberedsubsec Q1.4.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
-The @file{.emacs} file is used to customize XEmacs to your tastes.  No
+The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
-two are alike, nor are they expected to be alike, but that's the point.
+your tastes.  Starting in 21.4, the preferred location for the init file
-The XEmacs distribution contains an excellent starter example in the etc
+is @file{~/.xemacs/init.el}; in previous versions, it was
-directory called @file{sample.emacs}.  Copy this file from there to your
+@file{~/.emacs}.  21.4 still accepts the old location, but the first
-home directory and rename it @file{.emacs}.  Then edit it to suit.
+time you run it, it will ask to migrate your file to the new location.
+If you answer yes, the file will be moved, and a "compatibility"
-Starting with 19.14, you may bring the @file{sample.emacs} into an
+@file{.emacs} file will be placed in the old location so that you can
-XEmacs buffer by selecting @samp{Help->Sample .emacs} from the menubar.
+still run older versions of XEmacs, and versions of GNU Emacs, which
-To determine the location of the @file{etc} directory type the command
+expect the old location.  The @file{.emacs} file present is just a stub
+that loads the real file in @file{~/.xemacs/init.el}.
+No two init files are alike, nor are they expected to be alike, but
+that's the point.  The XEmacs distribution contains an excellent starter
+example in the @file{etc/} directory called @file{sample.init.el}
+(starting in 21.4) or @file{sample.emacs} in older versions.  Copy this
+file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
+@file{~/.emacs} in older versions, where @samp{~} means your home
+directory, of course.  Then edit it to suit.
+You may bring the @file{sample.init.el} or @file{sample.emacs} file into
+an XEmacs buffer from the menubar. (The menu entry for it is always
+under the @samp{Help} menu, but its location under that has changed in
+various versions.  Recently, look under the @samp{Samples} submenu.)  To
+determine the location of the @file{etc/} directory type the command
 @kbd{C-h v data-directory @key{RET}}.
 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
-@unnumberedsubsec Q1.4.2: Can I use the same @file{.emacs} with the other Emacs?
+@unnumberedsubsec Q1.4.2: Can I use the same @file{init.el}/@file{.emacs} with the other Emacs?
-Yes.  The sample @file{.emacs} included in the XEmacs distribution will
+Yes.  The sample @file{init.el}/@file{.emacs} included in the XEmacs
-show you how to handle different versions and flavors of Emacs.
+distribution will 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
 Now, during the dump itself, the executable (code+data+symbols) is
 written on disk using a special unexec() function. This function is
 obviously heavily system dependent. And on some systems, it leads to an
 executable which, although valid, cannot be stripped without damage. If
 memory serves, this is especially the case for AIX binaries. On other
-architecture it might work OK.
+architectures it might work OK.
 The Right Way to strip the emacs binary is to strip temacs prior to
 dumping xemacs. This will always work, although you can do that only if
 you install from sources (as temacs is @file{not} part of the binary
 kits).
 killed the XEmacs process using @code{kill -9}).  The next time you try
 to edit those files, you will be informed that a more recent auto-save
 file exists.  You can use @kbd{M-x recover-file} to retrieve the
 auto-saved version of the file.
-Starting with 19.14, you may use the command @kbd{M-x recover-session}
+You can use the command @kbd{M-x recover-session} after a crash to pick
-after a crash to pick up where you left off.
+up where you left off.
 Now, XEmacs is not perfect, and there may occasionally be times, or
 particular sequences of actions, that cause it to crash.  If you can
 come up with a reproducible way of doing this (or even if you have a
 pretty good memory of exactly what you were doing at the time), the
 @item
 Reproduce the error.
 @end enumerate
-Depending on the version of XEmacs, you may either select Edit->Show
+Depending on the version of XEmacs, you may either select View->Show
-Messages (19.13 and earlier) or Help->Recent Keystrokes/Messages (19.14
+Message Log (recent versions), Edit->Show Messages (some earlier
-and later) from the menubar to see the most recent messages.  This
+versions) or Help->Recent Keystrokes/Messages (other earlier versions)
-command is bound to @kbd{C-h l} by default.
+from the menubar to see the most recent messages.  This command is bound
+to @kbd{C-h l} by default.
 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
 @unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
 I get tons of translation table syntax error messages during startup.
 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
 @unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
 The OpenWindows 3.0 server is incredibly buggy.  Your best bet is to
 replace it with one from the generic MIT X11 release.  You might also
-try disabling parts of your @file{.emacs}, like enabling background
+try disabling parts of your @file{init.el}/@file{.emacs}, like those
-pixmaps.
+that enable background pixmaps.
 @node Q2.1.10, Q2.1.11, Q2.1.9, Installation
 @unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
 The following information comes from the @file{PROBLEMS} file that comes
 have no idea why GDB under Linux is so bogus.  Complain to the GDB
 authors, or to comp.os.linux.development.system).  Again, you'll have to
 use the narrowing-down process described above.
 @item
-If you compiled 19.14 with @samp{--debug} (or by default in later
+You will get a Lisp backtrace output when XEmacs crashes, so you'll have
-versions), you will get a Lisp backtrace output when XEmacs crashes, so
+something useful.
-you'll have something useful.
 @end enumerate
 @item
 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
 @lisp
 (set-time-zone-rule "MET")
 @end lisp
-to your @file{.emacs} or the @file{site-start.el} file if you can.
+to your @file{init.el}/@file{.emacs} or the @file{site-start.el} file if
-Replace @code{MET} with your local timezone.
+you can.  Replace @code{MET} with your local timezone.
 @node Q2.1.20, Q2.1.21, Q2.1.19, Installation
 @unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
 This is a problem with a partially loaded hyperbole.  Try adding:
 This is part 3 of the XEmacs Frequently Asked Questions list.  This
 section is devoted to Customization and screen settings.
 @menu
-Customization---Emacs Lisp and @file{.emacs}:
+Customization---Emacs Lisp and @file{init.el}/@file{.emacs}:
 * Q3.0.1::      What version of Emacs am I running?
 * Q3.0.2::      How do I evaluate Elisp expressions?
 * Q3.0.3::      @code{(setq tab-width 6)} behaves oddly.
 * Q3.0.4::      How can I add directories to the @code{load-path}?
 * Q3.0.5::      How to check if a lisp function is defined?
 * Q3.1.6::      How can I have the window title area display the full path?
 * Q3.1.7::      @samp{xemacs -name junk} doesn't work?
 * Q3.1.8::      @samp{-iconic} doesn't work.
 Textual Fonts & Colors:
-* Q3.2.1::      How can I set color options from @file{.emacs}?
+* Q3.2.1::      How can I set color options from @file{init.el}/@file{.emacs}?
 * Q3.2.2::      How do I set the text, menu and modeline fonts?
 * Q3.2.3::      How can I set the colors when highlighting a region?
 * Q3.2.4::      How can I limit color map usage?
 * Q3.2.5::      My tty supports color, but XEmacs doesn't use them.
 * Q3.2.6::      Can I have pixmap backgrounds in XEmacs?
 * Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
 * Q3.5.4::      Globally binding @kbd{Delete}?
 * Q3.5.5::      Scrolling one line at a time.
 * Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
 * Q3.5.7::      How can you type in special characters in XEmacs?
-* Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
+* Q3.5.8::      [This question intentionally left blank]
 * Q3.5.9::      How do I make the Delete key delete forward?
 * Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
 * Q3.5.11::     How do I map the arrow keys?
 The Cursor:
 Scrollbars:
 * Q3.9.1::      How can I disable the scrollbar?
 * Q3.9.2::      How can one use resources to change scrollbar colors?
 * Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
-* Q3.9.4::      How can I get automatic horizontal scrolling?
+* Q3.9.4::      How can I turn off automatic horizontal scrolling in specific modes?
 Text Selections:
 * Q3.10.1::     How can I turn off or change highlighted selections?
 * Q3.10.2::     How do I get that typing on an active region removes it?
 * Q3.10.3::     Can I turn off the highlight during isearch?
 * Q3.10.4::     How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
 * Q3.10.5::     The region disappears when I hit the end of buffer while scrolling.
 @end menu
 @node Q3.0.1, Q3.0.2, Customization, Customization
-@unnumberedsec 3.0: Customization -- Emacs Lisp and .emacs
+@unnumberedsec 3.0: Customization -- Emacs Lisp and @file{init.el}/@file{.emacs}
 @unnumberedsubsec Q3.0.1: What version of Emacs am I running?
-How can @file{.emacs} determine which of the family of Emacsen I am
+How can @file{init.el}/@file{.emacs} determine which of the family of
-using?
+Emacsen I am using?
 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
-example given in @file{etc/sample.emacs}.  There are other nifty things
+example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
-in there as well!
+XEmacs versions prior to 21.4).  There are other nifty things in there
+as well!
 For all new code, all you really need to do is:
 @lisp
 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
 with @kbd{C-j} after the expression.  How do I do it from another
 buffer?
 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
-enter the expression to the minibuffer.  In XEmacs prior to 19.15
+enter the expression to the minibuffer.
-@code{eval-expression} used to be a disabled command by default.  If
-this is the case, upgrade your XEmacs.
 @node Q3.0.3, Q3.0.4, Q3.0.2, Customization
 @unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
-If you put @code{(setq tab-width 6)} in your @file{.emacs} file it does
+If you put @code{(setq tab-width 6)} in your
-not work!  Is there a reason for this?  If you do it at the EVAL prompt
+@file{init.el}/@file{.emacs} file it does not work!  Is there a reason
-it works fine!! How strange.
+for this?  If you do it at the EVAL prompt it works fine!! How strange.
 Use @code{setq-default} instead, since @code{tab-width} is
 all-buffer-local.
 @node Q3.0.4, Q3.0.5, Q3.0.3, Customization
 simply press @kbd{C-h l} to get the former minibuffer contents in a
 buffer.
 @node Q3.0.7, Q3.0.8, Q3.0.6, Customization
 @unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
-For XEmacs 19.14 and previous:
 @email{mannj@@ll.mit.edu, John Mann} writes:
 @quotation
 You have to go to Options->Frame Appearance and unselect
 @samp{Frame-Local Font Menu}.  If this option is selected, font changes
 are only applied to the @emph{current} frame and do @emph{not} get saved
 when you save options.
 @end quotation
-For XEmacs 19.15 and later:
+Also, set the following in your @file{init.el}/@file{.emacs}:
-Implement the above as well as set the following in your @file{.emacs}
 @lisp
 (setq options-save-faces t)
 @end lisp
 @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
 the current file in it.
-Add the following line to your @file{.emacs}:
+Add the following line to your @file{init.el}/@file{.emacs}:
 @lisp
 (setq frame-icon-title-format "XEmacs")
 @end lisp
 @unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
 I'd like to have the window title area display the full directory/name
 of the current buffer file and not just the name.
-Add the following line to your @file{.emacs}:
+Add the following line to your @file{init.el}/@file{.emacs}:
 @lisp
 (setq frame-title-format "%S: %f")
 @end lisp
 bugs...
 @end quotation
 @node Q3.2.1, Q3.2.2, Q3.1.8, Customization
 @unnumberedsec 3.2: Textual Fonts & Colors
-@unnumberedsubsec Q3.2.1: How can I set color options from @file{.emacs}?
+@unnumberedsubsec Q3.2.1: How can I set color options from @file{init.el}/@file{.emacs}?
-How can I set the most commonly used color options from my @file{.emacs}
+How can I set the most commonly used color options from my
-instead of from my @file{.Xdefaults}?
+@file{init.el}/@file{.emacs} instead of from my @file{.Xdefaults}?
 Like this:
 @lisp
 (set-face-background 'default      "bisque") ; frame background
 @example
 Emacs.zmacs-region.attributeForeground: firebrick
 Emacs.zmacs-region.attributeBackground: lightseagreen
 @end example
-or in your @file{.emacs}:
+or in your @file{init.el}/@file{.emacs}:
 @lisp
 (set-face-background 'zmacs-region "red")
 (set-face-foreground 'zmacs-region "yellow")
 @end lisp
 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
 @unnumberedsubsec Q3.2.4: How can I limit color map usage?
 I'm using Netscape (or another color grabber like XEmacs);
-is there anyway to limit the number of available colors in the color map?
+is there any way to limit the number of available colors in the color map?
-XEmacs 19.13 didn't have such a mechanism (unlike netscape, or other
+Answer: No, but you can start Netscape before XEmacs, and it will use
-color-hogs).  One solution is to start XEmacs prior to netscape, since
+the closest available color if the colormap is full.  You can also limit
-this will prevent Netscape from grabbing all colors (but Netscape will
+the number of colors Netscape uses, using the flags -mono, -ncols <#> or
-complain).  You can use the flags for Netscape, like -mono, -ncols <#>
+-install (for mono, limiting to <#> colors, or for using a private color
-or -install (for mono, limiting to <#> colors, or for using a private
+map).
-color map).  Since Netscape will take the entire colormap and never
-release it, the only reasonable way to run it is with @samp{-install}.
 If you have the money, another solution would be to use a truecolor or
 direct color video.
-Starting with XEmacs 19.14, XEmacs uses the closest available color if
-the colormap is full, so it's O.K. now to start Netscape first.
 @node Q3.2.5, Q3.2.6, Q3.2.4, Customization
 @unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
 XEmacs tries to automatically determine whether your tty supports color,
 @lisp
 (set-specifier has-modeline-p nil)
 @end lisp
-Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
+@c Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
-you haven't liked or used the modeline in the past, you might want to
+@c you haven't liked or used the modeline in the past, you might want to
-try the new version out.
+@c try the new version out.
+@c
 @node Q3.3.2, Q3.3.3, Q3.3.1, Customization
 @unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
-Add the following line to your @file{.emacs} file to display the
+Add the following line to your @file{init.el}/@file{.emacs} file to
-line number:
+display the line number:
 @lisp
 (line-number-mode 1)
 @end lisp
 Or select from the @code{Options} menu
 @iftex
 @*
 @end iftex
-@code{Customize->Emacs->Editing->Basics->Line Number Mode}
+@code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
 and/or
 @iftex
 @*
 @end iftex
-@code{Customize->Emacs->Editing->Basics->Column Number Mode}
+@code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
 @node Q3.3.3, Q3.3.4, Q3.3.2, Customization
 @unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
-Add the following line to your @file{.emacs} file to display the
+Add the following line to your @file{init.el}/@file{.emacs} file to
-time:
+display the time:
 @lisp
 (display-time)
 @end lisp
 With AUC TeX, fast typing is hard because the current chapter, section
 etc. are given in the modeline.  How can I turn this off?
 It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
-Add this code to your @file{.emacs} to turn it off:
+@c Add this code to your @file{init.el}/@file{.emacs} to turn it off:
-@lisp
+@c
-(setq fume-display-in-modeline-p nil)
+@c @lisp
-@end lisp
+@c (setq fume-display-in-modeline-p nil)
+@c @end lisp
-Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
+@c
-mode:
+@c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
+@c mode:
-@lisp
+@c
-(add-hook 'TeX-mode-hook
+@c @lisp
-'(lambda () (setq fume-display-in-modeline-p nil)))
+@c (add-hook 'TeX-mode-hook
-@end lisp
+@c           '(lambda () (setq fume-display-in-modeline-p nil)))
+@c @end lisp
+@c
 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
 @quotation
-If you have 19.14 or later, try this instead; you'll still get the
+Try this; you'll still get the function name displayed in the modeline,
-function name displayed in the modeline, but it won't attempt to keep
+but it won't attempt to keep track when you modify the file. To refresh
-track when you modify the file. To refresh when it gets out of synch,
+when it gets out of synch, you simply need click on the @samp{Rescan
-you simply need click on the @samp{Rescan Buffer} option in the
+Buffer} option in the function-menu.
-function-menu.
 @lisp
 (setq-default fume-auto-rescan-buffer-p nil)
 @end lisp
 @end quotation
 (lambda ()
 (set-face-background 'modeline "red" (current-buffer))))
 @end lisp
 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
-colors change from the default set in your @file{.emacs}.  The change
+colors change from the default set in your @file{init.el}/@file{.emacs}.
-will only be made in the buffer you just entered (which contains the
+The change will only be made in the buffer you just entered (which
-Lisp file you are editing) and will not affect the modeline colors
+contains the Lisp file you are editing) and will not affect the modeline
-anywhere else.
+colors anywhere else.
 Notes:
 @itemize @bullet
-@item
+@item The hook is the mode name plus @code{-hook}.  eg. c-mode-hook,
-The hook is the mode name plus @code{-hook}.  eg. c-mode-hook,
+c++-mode-hook, emacs-lisp-mode-hook (used for your
-c++-mode-hook, emacs-lisp-mode-hook (used for your @file{.emacs} or a
+@file{init.el}/@file{.emacs} or a @file{xx.el} file),
-@file{xx.el} file), lisp-interaction-mode-hook (the @samp{*scratch*}
+lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
-buffer), text-mode-hook, etc.
+text-mode-hook, etc.
 @item
 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
 otherwise you will erase anything that anybody has already put on the
 hook.
 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
 (current-buffer))} if you wish the modeline font to vary based on the
 current mode.
 @end itemize
-This works in 19.15 as well, but there are additional modeline faces,
+There are additional modeline faces, @code{modeline-buffer-id},
-@code{modeline-buffer-id}, @code{modeline-mousable}, and
+@code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
-@code{modeline-mousable-minor-mode}, which you may want to customize.
+you may want to customize.
 @node Q3.4.1, Q3.4.2, Q3.3.5, Customization
 @unnumberedsec 3.4: Multiple Device Support
 @unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
-The support for this was revamped for 19.14.  Use the command
+Use the command @kbd{M-x make-frame-on-display}.  This command is also
-@kbd{M-x make-frame-on-display}.  This command is also on the File menu
+on the File menu in the menubar.
-in the menubar.
+The command @code{make-frame-on-tty} also exists, which will establish a
-XEmacs 19.14 and later also have the command @code{make-frame-on-tty}
+connection to any tty-like device.  Opening the TTY devices should be
-which will establish a connection to any tty-like device.  Opening the
+left to @code{gnuclient}, though.
-TTY devices should be left to @code{gnuclient}, though.
 @node Q3.4.2, Q3.5.1, Q3.4.1, Customization
 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem?  How?
-If you're not running at least XEmacs 19.14, you can't.  Otherwise check
+Yes.  Use @code{gnuclient -nw}. (Prior to 20.3, use the @code{gnuattach}
-out the @code{gnuattach} program supplied with XEmacs.  Starting with
+program supplied with XEmacs instead.)
-XEmacs 20.3, @code{gnuattach} and @code{gnudoit} functionality is
-provided by @code{gnuclient}.
 Also @xref{Q5.0.12}.
 @node Q3.5.1, Q3.5.2, Q3.4.2, Customization
 @unnumberedsec 3.5: The Keyboard
 question 3.5.3 (@pxref{Q3.5.3}).
 @node Q3.5.2, Q3.5.3, Q3.5.1, Customization
 @unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
-Add the following line to your @file{.emacs} file:
+Add the following line to your @file{init.el}/@file{.emacs} file:
 @lisp
 (setq next-line-add-newlines nil)
 @end lisp
 @unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
 I cannot manage to globally bind my @kbd{Delete} key to something other
 than the default.  How does one do this?
+Answer: The problem is that many modes explicitly bind @kbd{Delete}.  To
+get around this, try the following:
 @lisp
 (defun foo ()
 (interactive)
 (message "You hit DELETE"))
-(global-set-key 'delete 'foo)
+(define-key key-translation-map 'delete 'redirected-delete)
-@end lisp
+(global-set-key 'redirected-delete 'foo)
+@end lisp
-However, some modes explicitly bind @kbd{Delete}, so you would need to
-add a hook that does @code{local-set-key} for them.  If what you want to
-do is make the Backspace and Delete keys work more PC/Motif-like, then
-take a look at the @file{delbs.el} package.
-New in XEmacs 19.14 is a variable called @code{key-translation-map}
-which makes it easier to bind @kbd{Delete}.  @file{delbs.el} is a
-good example of how to do this correctly.
 Also @xref{Q3.5.10}.
 @node Q3.5.5, Q3.5.6, Q3.5.4, Customization
 @unnumberedsubsec Q3.5.5: Scrolling one line at a time.
 (setq scroll-step 1)
 @end lisp
 Starting with XEmacs-20.3 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Windows->Scroll Step...} or type
+@code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...} or type
 @kbd{M-x customize @key{RET} windows @key{RET}}.
 @node Q3.5.6, Q3.5.7, Q3.5.5, Customization
 @unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
 @lisp
 (global-set-key [help] 'help-command);; Help
 @end lisp
-The following works in XEmacs 19.15 with the addition of shift:
+The following works in XEmacs with the addition of shift:
 @lisp
 (global-set-key [(shift help)] 'help-command);; Help
 @end lisp
 @unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
 @c Changed
 One way is to use the package @code{x-compose}.  Then you can use
 sequences like @kbd{Compose " a} to get �, etc.
-Another way is to use the @code{iso-insert} package, provided in XEmacs
+Another way is to use the @code{iso-insert} package. Then you can use
-19.15 and later. Then you can use sequences like @kbd{C-x 8 " a} to get
+sequences like @kbd{C-x 8 " a} to get �, etc.
-�, etc.
 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
 @quotation
 It depends upon your X server.
 Running @samp{xmodmap -pk} will list all of the defined keysyms.
 @end quotation
 @node Q3.5.8, Q3.5.9, Q3.5.7, Customization
-@unnumberedsubsec Q3.5.8: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
+@unnumberedsubsec Q3.5.8: [This question intentionally left blank]
-Why does @code{(define-key global-map [ delete-forward ] 'delete-char)}
+Obsolete question, left blank to avoid renumbering.
-complain of not being able to bind an unknown key?
-Try this instead:
-@lisp
-(define-key global-map [delete_forward] 'delete-char)
-@end lisp
-and it will work.
-What you are seeing above is a bug due to code that is trying to check
-for GNU Emacs syntax like:
-(define-key global-map [C-M-a] 'delete-char)
-which otherwise would cause no errors but would not result in the
-expected behavior.
-This bug has been fixed in 19.14.
 @node Q3.5.9, Q3.5.10, Q3.5.8, Customization
 @unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
 With XEmacs-20.2 use the @code{delbs} package:
 ``normal'' behavior.  Note that @code{delbackspace} package is obsolete.
 Starting with XEmacs-20.3 better solution is to set variable
 @code{delete-key-deletes-forward} to t.  You can also change this with
 Customize. Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Basics->Delete Key Deletes Forward} or
+@code{Advanced (Customize)->Emacs->Editing->Basics->Delete Key Deletes Forward} or
 type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
 Also @xref{Q3.5.4}.
 @node Q3.5.10, Q3.5.11, Q3.5.9, Customization
 (setq bar-cursor 'anything-else)
 @end lisp
 Starting with XEmacs-20.3 you can also change these with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
+@code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
 @kbd{M-x customize @key{RET} display @key{RET}}.
 You can use a color to make it stand out better:
 @example
 @lisp
 (setq bar-cursor nil)
 @end lisp
-Starting with XEmacs-20.3 you can also change this with Customize.
+Starting with XEmacs 20.3 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
+@code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
 @kbd{M-x customize @key{RET} display @key{RET}}.
 @node Q3.6.3, Q3.7.1, Q3.6.2, Customization
 @unnumberedsubsec Q3.6.3: Can I make the cursor blink?
-If you are running a version of XEmacs older than 19.14, no.  Otherwise
+Yes, like this:
-you can do the following:
 @lisp
 (blink-cursor-mode)
 @end lisp
 do I disable this?
 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
 @key{RET}}.
-To get XEmacs to paste at the text cursor, add this your @file{.emacs}:
+To get XEmacs to paste at the text cursor, add this your @file{init.el}/@file{.emacs}:
 @lisp
 (setq mouse-yank-at-point t)
 @end lisp
 Starting with XEmacs-20.2 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Mouse->Yank At Point...} or type
+@code{Advanced (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type
 @kbd{M-x customize @key{RET} mouse @key{RET}}.
 @node Q3.7.7, Q3.7.8, Q3.7.6, Customization
 @unnumberedsubsec Q3.7.7: How do I select a rectangular region?
 (setq mouse-track-rectangle-p t)
 @end lisp
 Starting with XEmacs-20.2 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Editing->Mouse->Track Rectangle...} or type
+@code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
 @kbd{M-x customize @key{RET} mouse @key{RET}}.
 @example
 mouse-track-do-rectangle: (event)
 @node Q3.8.1, Q3.8.2, Q3.7.8, Customization
 @unnumberedsec 3.8: The Menubar and Toolbar
 @unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
-If you are running XEmacs 19.13 and earlier, add this command to your
+@c If you are running XEmacs 19.13 or earlier, add this command to your
-@file{.emacs}.
+@c @file{init.el}/@file{.emacs}.
+@c
-@lisp
+@c @lisp
-(set-menubar nil)
+@c (set-menubar nil)
-@end lisp
+@c @end lisp
+@c
-Starting with XEmacs 19.14 the preferred method is:
+@c Starting with XEmacs 19.14 the preferred method is:
+@c
 @lisp
 (set-specifier menubar-visible-p nil)
 @end lisp
 @node Q3.8.2, Q3.8.3, Q3.8.1, Customization
 @unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
-For an extensive menubar, add this line to your @file{.emacs}:
+For an extensive menubar, add this line to your @file{init.el}/@file{.emacs}:
 @lisp
 (load "big-menubar")
 @end lisp
 directory.
 @node Q3.8.3, Q3.8.4, Q3.8.2, Customization
 @unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
-Add the following to your @file{.emacs} (suit to fit):
+Add the following to your @file{init.el}/@file{.emacs} (suit to fit):
 @lisp
 (setq buffers-menu-max-size 20)
 @end lisp
 For no limit, use an argument of @samp{nil}.
 Starting with XEmacs-20.3 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
+@code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
 type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
 @node Q3.8.4, Q3.8.5, Q3.8.3, Customization
 @unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
 turn the scrollbars off only in a single buffer:
 @lisp
 (set-specifier scrollbar-width 0 (current-buffer))
 @end lisp
+@c
-In XEmacs versions prior to 19.14, you had to use the hairier construct:
+@c In XEmacs versions prior to 19.14, you had to use the hairier construct:
+@c
-@lisp
+@c @lisp
-(set-specifier scrollbar-width (cons (selected-frame) 0))
+@c (set-specifier scrollbar-width (cons (selected-frame) 0))
-@end lisp
+@c @end lisp
 @node Q3.9.2, Q3.9.3, Q3.9.1, Customization
 @unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
 Here's a recap of how to use resources to change your scrollbar colors:
 hand corner.
 This cannot be changed.
 @node Q3.9.4, Q3.10.1, Q3.9.3, Customization
-@unnumberedsubsec Q3.9.4: How can I get automatic horizontal scrolling?
+@unnumberedsubsec Q3.9.4: How can I turn off automatic horizontal scrolling in specific modes?
-By the same token, how can I turn it off in specific modes?
+Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
-To do this, add to your @file{.emacs} file:
-@lisp
-(require 'auto-show)
-@end lisp
-Then do @code{(setq truncate-lines t)} in the mode-hooks for any modes
 in which you want lines truncated.
 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
 will never appear.  Otherwise, they will appear only if the value of
 @code{scrollbar-height} for that buffer/window/etc. is non-zero.  If you
 @end lisp
 then horizontal scrollbars will not appear in truncated buffers unless
 the package specifically asked for them.
-Automatic horizontal scrolling is now standard, starting with 19.14.
 @node Q3.10.1, Q3.10.2, Q3.9.4, Customization
 @unnumberedsec 3.10: Text Selections
 @unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
 The @code{zmacs} mode allows for what some might call gratuitous
 highlighting for selected regions (either by setting mark or by using
 the mouse).  This is the default behavior.  To turn off, add the
-following line to your @file{.emacs} file:
+following line to your @file{init.el}/@file{.emacs} file:
 @lisp
 (setq zmacs-regions nil)
 @end lisp
 Starting with XEmacs-20.2 you can also change this with Customize. Select
-from the @code{Options} menu @code{Customize->Emacs->Editing->Basics->Zmacs
+from the @code{Options} menu @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs
 Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
 To change the face for selection, look at @code{Options->Customize} on
 the menubar.
 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 lines to your @file{init.el}/@file{.emacs}:
 @lisp
 (cond
 ((fboundp 'turn-on-pending-delete)
 (turn-on-pending-delete))
 @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
 able to see what's underneath.  How do I turn it off?
-Put the following in your @file{.emacs}:
+Put the following in your @file{init.el}/@file{.emacs}:
 @lisp
 (setq isearch-highlight nil)
 @end lisp
 examples of usage, the plethora of user options that @emph{fully}
 control VM's behavior.
 Enter vm-vars, @code{forward-search} for toolbar, find the variables
 that control the toolbar placement, appearance, existence, copy to your
-@file{.emacs} or @file{.vm} and modify according to the detailed
+@file{init.el}/@file{.emacs} or @file{.vm} and modify according to the
-instructions.
+detailed instructions.
 The above also applies to all the various features of VM: search for
 some keywords, maybe the first you conjure isn't appropriate, find the
 appropriate variables, copy and experiment.
 @end quotation
 @menu
 Major & Minor Modes:
 * Q5.0.1::      How can I do source code highlighting using font-lock?
 * Q5.0.2::      I do not like cc-mode.  How do I use the old c-mode?
 * Q5.0.3::      How do I get @samp{More} Syntax Highlighting on by default?
-* Q5.0.4::      How can I enable auto-indent?
+* Q5.0.4::      How can I enable auto-indent and/or Filladapt?
 * Q5.0.5::      How can I get XEmacs to come up in text/auto-fill mode by default?
 * Q5.0.6::      How do I start up a second shell buffer?
 * Q5.0.7::      Telnet from shell filters too much.
 * Q5.0.8::      Why does edt emulation not work?
 * Q5.0.9::      How can I emulate VI and use it as my default mode?
 * Q5.0.10::     [This question intentionally left blank]
-* Q5.0.11::     How do I turn on filladapt for all buffers?
+* Q5.0.11::     [This question intentionally left blank]
 * 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.2.3::      What's NAS, how do I get it?
 * Q5.2.4::      Sunsite sounds don't play.
 Miscellaneous:
 * Q5.3.1::      How do you make XEmacs indent CL if-clauses correctly?
-* Q5.3.2::      Fontifying hangs when editing a postscript file.
+* Q5.3.2::      [This question intentionally left blank]
 * Q5.3.3::      How can I print WYSIWYG a font-locked buffer?
 * Q5.3.4::      Getting @kbd{M-x lpr} to work with postscript printer.
 * Q5.3.5::      How do I specify the paths that XEmacs uses for finding files?
 * Q5.3.6::      [This question intentionally left blank]
 * Q5.3.7::      Can I have the end of the buffer delimited in some way?
 @node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
 @unnumberedsec 5.0: Major & Minor Modes
 @unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
 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
+on.  This can be done by adding the line:
-automatically start it by adding lines like:
+@lisp
-@lisp
+(require 'font-lock)
-(add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
+@end lisp
-(add-hook 'dired-mode-hook      'turn-on-font-lock)
-@end lisp
+to your @file{init.el}/@file{.emacs}. (You can turn it on for the
+current buffer and session only by @kbd{M-x font-lock-mode}.) See the
-to your @file{.emacs}.  See the file @file{etc/sample.emacs} for more
+file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
-examples.
+versions prior to 21.4) for more information.
+@c the old way:
+@c     (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
+@c     (add-hook 'dired-mode-hook      'turn-on-font-lock)
 See also @code{Syntax Highlighting} from the @code{Options} menu.
 Remember to save options.
 @node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
 Well, first off, consider if you really want to do this.  cc-mode is
 much more powerful than the old c-mode.  If you're having trouble
 getting your old offsets to work, try using @code{c-set-offset} instead.
 You might also consider using the package @code{cc-compat}.
-But, if you still insist, add the following lines to your @file{.emacs}:
+But, if you still insist, add the following lines to your @file{init.el}/@file{.emacs}:
 @lisp
 (fmakunbound 'c-mode)
 (makunbound 'c-mode-map)
 (fmakunbound 'c++-mode)
 c++-mode.
 @node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
 @unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
-Use the following code in your @file{.emacs}:
+Use the following code in your @file{init.el}/@file{.emacs}:
 @lisp
 (setq-default font-lock-maximum-decoration t)
 @end lisp
-In versions of XEmacs prior to 19.14, you had to use a kludgy solution
+@c In versions of XEmacs prior to 19.14, you had to use a kludgy solution
-like this:
+@c like this:
+@c
-@lisp
+@c @lisp
-(setq c-font-lock-keywords c-font-lock-keywords-2
+@c (setq c-font-lock-keywords c-font-lock-keywords-2
-c++-font-lock-keywords c++-font-lock-keywords-2
+@c       c++-font-lock-keywords c++-font-lock-keywords-2
-lisp-font-lock-keywords lisp-font-lock-keywords-2)
+@c       lisp-font-lock-keywords lisp-font-lock-keywords-2)
-@end lisp
+@c @end lisp
+@c
-It will work for C, C++ and Lisp.
+@c It will work for C, C++ and Lisp.
+@c
 See also @code{Syntax Highlighting} from the @code{Options} menu.
 Remember to save options.
 @node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
-@unnumberedsubsec Q5.0.4: How can I enable auto-indent?
+@unnumberedsubsec Q5.0.4: How can I enable auto-indent and/or Filladapt?
-Put the following line in your @file{.emacs}:
+Put the following line in your @file{init.el}/@file{.emacs}:
 @lisp
 (setq indent-line-function 'indent-relative-maybe)
 @end lisp
 If you want to get fancy, try the @code{filladapt} package available
-standard with XEmacs.  Put this into your @file{.emacs}:
+standard with XEmacs.  Put this into your @file{init.el}/@file{.emacs}:
 @lisp
 (require 'filladapt)
-(add-hook 'text-mode-hook    'turn-on-filladapt-mode)
+(setq-default filladapt-mode t)
-;;; and others ...
+(add-hook 'c-mode-hook 'turn-off-filladapt-mode)
+@end lisp
+This will enable Filladapt for all modes except C mode, where it doesn't
+work well.  To turn Filladapt on only in particular major modes, remove
+the @code{(setq-default ...)} line and use
+@code{turn-on-filladapt-mode}, like this:
+@lisp
+(add-hook 'text-mode-hook 'turn-on-filladapt-mode)
 @end lisp
 You can customize filling and adaptive filling with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->->Editing->Fill->Fill...}
+@code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
 Note that well-behaving text-lookalike modes will run
 @code{text-mode-hook} by default (e.g. that's what Message does).  For
 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
 Please note that the @code{fa-extras} package is no longer useful.
 @node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
 @unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
-Try the following lisp in your @file{.emacs}:
+Try the following lisp in your @file{init.el}/@file{.emacs}:
 @lisp
 (setq default-major-mode 'text-mode)
 (setq text-mode-hook 'turn-on-auto-fill)
 @end lisp
 @node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
 @unnumberedsubsec Q5.0.8: Why does edt emulation not work?
 We don't know, but you can use tpu-edt emulation instead, which works
 fine and is a little fancier than the standard edt emulation.  To do
-this, add the following line to your @file{.emacs}:
+this, add the following line to your @file{init.el}/@file{.emacs}:
 @lisp
 (tpu-edt)
 @end lisp
 @node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
 @unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
 Our recommended VI emulator is viper. To make viper-mode the default,
-add this to your @file{.emacs}:
+add this to your @file{init.el}/@file{.emacs}:
 @lisp
 (viper-mode)
 @end lisp
 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
 @quotation
-This should be added as close to the top of @file{.emacs} as you can get
+This should be added as close to the top of @file{init.el}/@file{.emacs} as you can get
 it, otherwise some minor modes may not get viper-ized.
 @end quotation
 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
 @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: [This question intentionally left blank]
-Filladapt is a minor mode and minor modes are traditionally off by
+Obsolete question, left blank to avoid renumbering
-default.  The following added to your @file{.emacs} will turn it on for
-all buffers:
-@lisp
-(setq-default filladapt-mode t)
-@end lisp
-Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
-major modes, like this:
-@lisp
-(add-hook 'text-mode-hook 'turn-on-filladapt-mode)
-@end lisp
 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
 @unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
 If you set the @code{gnuserv-frame} variable to the frame that should be
 @lisp
 (setq gnuserv-frame (selected-frame))
 @end lisp
-early on in your @file{.emacs}, to ensure that the first frame created
+early on in your @file{init.el}/@file{.emacs}, to ensure that the first frame created
 is the one used for your gnuserv buffers.
-Starting in 19.15, there is an option to set the gnuserv target to
+There is an option to set the gnuserv target to the current frame.  See
-the current frame.  See
+@code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
-@code{Options->"Other Window" Location->Make current frame gnuserv target}
 Starting with XEmacs-20.3 you can also change this with Customize.
 Select from the @code{Options} menu
-@code{Customize->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
+@code{Advanced (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...}
-@kbd{M-x customize @key{RET} gnuserv @key{RET}}.
+or type @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
 @node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
 @unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
-Put the following in your @file{.emacs} file to start the server:
+Put the following in your @file{init.el}/@file{.emacs} file to start the server:
 @lisp
 (gnuserv-start)
 @end lisp
 @unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting.  How do I turn it off?
 @code{auto-show-mode} controls whether or not a horizontal scrollbar
 magically appears when a line is too long to be displayed.  This is
 enabled by default.  To turn it off, put the following in your
-@file{.emacs}:
+@file{init.el}/@file{.emacs}:
 @lisp
 (setq auto-show-mode nil)
 (setq-default auto-show-mode nil)
 @end lisp
 @node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
-You can't.  The @code{info} package does not provide for multiple info buffers.
+Before 21.4, you can't.  The @code{info} package does not provide for
+multiple info buffers.  In 21.4, this should be fixed. #### how?
 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
 @unnumberedsubsec Q5.0.18: [This question intentionally left blank]
 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
 Instead of @samp{FILE}, use the image file name
 (e.g.
 @iftex
 @*
 @end iftex
-@file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
+@file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
 You can turn this to a function (that optionally prompts you for a file
 name), and inserts the glyph at @code{(point)} instead of
 @code{(point-min)}.
 @node Q5.1.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:
+@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
 @quotation
-Under XEmacs 20.4 and later  you can use @kbd{M-x profile-key-sequence}, press a key
+Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
-(say @key{RET} in the Gnus Group buffer), and get the results using
+press a key (say @key{RET} in the Gnus Group buffer), and get the
-@kbd{M-x profile-results}.  It should give you an idea of where the time
+results using @kbd{M-x profile-results}.  It should give you an idea of
-is being spent.
+where the time is being spent.
 @end quotation
 @node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
 @unnumberedsubsec Q5.2.1: How do I turn off the sound?
-Add the following line to your @file{.emacs}:
+Add the following line to your @file{init.el}/@file{.emacs}:
 @lisp
 (setq bell-volume 0)
 (setq sound-alist nil)
 @end lisp
 That will make your XEmacs totally silent---even the default ding sound
 (TTY beep on TTY-s) will be gone.
-Starting with XEmacs-20.2 you can also change these with Customize.
+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
+@code{Advanced (Customize)->Emacs->Environment->Sound->Sound...} or type
 @kbd{M-x customize @key{RET} sound @key{RET}}.
 @node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
 @unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
 Make sure your XEmacs was compiled with sound support, and then put this
-in your @file{.emacs}:
+in your @file{init.el}/@file{.emacs}:
 @lisp
 (load-default-sounds)
 @end lisp
-The sound support in XEmacs 19.14 was greatly improved over previous
+@c The sound support in XEmacs 19.14 was greatly improved over previous
-versions.
+@c versions.
+@c
 @node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
 @unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
 @xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
 same amount instead of indenting the 3rd clause differently from the
 first two.
-One way is to add, to @file{.emacs}:
+One way is to add, to @file{init.el}/@file{.emacs}:
 @lisp
 (put 'if 'lisp-indent-function nil)
 @end lisp
 comp.emacs.xemacs on 12/9/94.  This version includes more documentation
 than previous versions.  This may prove useful if you need to customize
 any indent-functions.
 @node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
-@unnumberedsubsec Q5.3.2: Fontifying hang when editing a postscript file.
+@unnumberedsubsec Q5.3.2: [This question intentionally left blank]
-When I try to edit a postscript file it gets stuck saying:
+Obsolete question, left blank to avoid renumbering.
-@samp{fontifying 'filename' (regexps....)} and it just sits there.  If I
-press @kbd{C-c} in the window where XEmacs was started, it suddenly
-becomes alive again.
-This was caused by a bug in the Postscript font-lock regular
-expressions.  It was fixed in 19.13.  For earlier versions of XEmacs,
-have a look at your @file{.emacs} file.  You will probably have a line
-like:
-@lisp
-(add-hook 'postscript-mode-hook 'turn-on-font-lock)
-@end lisp
-Take it out, restart XEmacs, and it won't try to fontify your postscript
-files anymore.
 @node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
 @unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
 Font-lock looks nice.  How can I print (WYSIWYG) the highlighted
 My printer is a Postscript printer and @code{lpr} only works for
 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
 lpr-buffer} to work?
-Put something like this in your @file{.emacs}:
+Put something like this in your @file{init.el}/@file{.emacs}:
 @lisp
 (setq lpr-command "a2ps")
 (setq lpr-switches '("-p" "-1"))
 @end lisp
 General Info
 * Q6.0.1::      What is the status of the XEmacs port to Windows?
 * Q6.0.2::      What flavors of MS Windows are supported?
 * Q6.0.3::      Where are the XEmacs on MS Windows binaries?
-* Q6.0.4::      Does XEmacs on MS Windows require an X server to run?
+* Q6.0.4::      Can I build XEmacs on MS Windows with support for X or Cygwin?
 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.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?
+* Q6.2.3::      Where do I put my @file{init.el}/@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?
 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
+list at @email{xemacs-nt@@xemacs.org} is dedicated to that effort
-the -request address to subscribe).
+(please use the -request address to subscribe).
-At this time, XEmacs on MS Windows is usable, but lacks some of the
+At this time, XEmacs on MS Windows is stable and full-featured.
-features of XEmacs on UNIX and UNIX-like systems.  Notably,
+However, the internationalization (Mule) support does not work --
-internationalization does not work.
+although this is being actively worked on.
 @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,
+The list name is misleading, as XEmacs will support Windows 95, Windows
-Windows 98 and Windows NT.  The MS Windows-specific code is based on
+98, Windows NT, Windows 2000, Windows ME, Windows XP, and all newer
-Microsoft Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
+versions of Windows.  The MS Windows-specific code is based on Microsoft
+Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
 @node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
-@unnumberedsubsec Q6.0.3: Are binary kits available?
+@unnumberedsubsec Q6.0.3: Are binaries available?
-Binary kits are available at
+Binaries are available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binary-kits/win32/} for the
+@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/win32/} for the native MS
-"plain" MS Windows version.
+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?
+@unnumberedsubsec Q6.0.4: Can I build XEmacs on MS Windows with support for X or Cygwin?
-Short answer: No.
+Yes.  XEmacs can be built in several ways in the MS Windows environment.
-Long answer: XEmacs can be built in several ways in the MS Windows
+The standard way is what we call the "native" port.  It uses the Win32
-environment, some of them requiring an X server and some not.
+API and has no connection with X whatsoever -- it does not require X
+libraries to build, nor does it require an X server to run.  The native
-One is what we call the "X" port---it requires X libraries to build
+port is the most reliable version and provides the best graphical
-and an X server to run.  Internally it uses the Xt event loop and
+support.  Almost all development is geared towards this version, and
-makes use of X toolkits.  Its look is quite un-Windowsy, but it works
+there is little reason not to use it.
-reliably and supports all of the graphical features of Unix XEmacs.
+You can also build XEmacs "X" port---it requires X libraries to build
-The other is what we call the "native" port.  It uses the Win32 API
+and an X server to run.  Internally it uses the Xt event loop and makes
-and does not require X libraries to build, nor does it require an X to
+use of X toolkits.  Its look is quite un-Windowsy, and it is not well
-run.  In fact, it has no connection with X whatsoever.  At this time,
+maintained, but it is being kept around for the time being because it
-the native port obsoletes the X port, providing almost all of its
+has a long history.
-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
+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
+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
+need X libraries.  If you want to build with TTY support you need
-ncurses.  MS gui requires no additional libraries.
+ncurses.  MS GUI requires no additional libraries.
-Some of the advantages of the Cygwin version are that it:
+The advantages of the Cygwin version are that it integrates well with
+Cygwin environment for existing Cygwin users; uses configure so building
-@itemize @bullet
+with different features is very easy; and has process support in X &
+tty.
-@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
 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
+make sure HOME is set. This controls where you
-from;
+@file{init.el}/@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;
+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
+static heap too small, adjust @file{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
 (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?
+@unnumberedsubsec Q6.2.3: Where do I put my @file{init.el}/@file{.emacs} file?
-If the HOME environment variable is set, @file{.emacs} will be looked for
+@file{init.el} is the name of the init file starting with 21.4, and is
-there.  Else the directory defaults to `c:\'.
+located in the subdirectory @file{.xemacs/} of your home directory.  In
+prior versions, the init file is called @file{.emacs} and is located in
+your home directory.  Your home directory under Windows is determined by
+the HOME environment variable.  If this is not set, it 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-*?
 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
+Architectural note: We believe that there should be a very small number
-number of window-systems-specific variables, and will try to provide
+of window-systems-specific variables, and we provide generic interfaces
-generic interfaces whenever possible.
+whenever possible.  Thus, most of the equivalents of GNU Emacs `w32-*'
+functions and variables (as well as the corresponding `x-*' versions)
+are non-window-system-specific in XEmacs, and the issue of `mswindows-*'
+vs. `w32-*' does not come up much.
 @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?
 @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?
+(as of March 2001)
 The porting team is continuing work on the MS Windows-specific code.
+Major projects are the development of Mule (internationalization)
+support for Windows and the improvement of the widget support (better
+support for dialog boxes, buttons, edit fields, and similar UI
+elements).
 @node Q6.4.1, ,Q6.3.3, MS Windows
 @unnumberedsec 6.3: Troubleshooting
 @unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 462:0784d089fdc9 r21-2-46