@finalout
@titlepage
@title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/04/16 09:24:44 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2003/10/09 19:16:02 $
@sp 1
-@author Tony Rossini <rossini@@biostat.washington.edu>
+@author Tony Rossini <rossini@@u.washington.edu>
@author Ben Wing <ben@@xemacs.org>
@author Chuck Thompson <cthomp@@xemacs.org>
@author Steve Baur <steve@@xemacs.org>
@node Top, Introduction, (dir), (dir)
@top XEmacs FAQ
-@unnumbered Introduction
This is the guide to the XEmacs Frequently Asked Questions list---a
compendium of questions and answers pertaining to one of the finest
@iftex
@*
@end iftex
-@uref{http://www.xemacs.org/faq/xemacs-faq.html}
+@uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
@ifset CANONICAL
@html
* Miscellaneous:: The Miscellaneous Stuff.
* MS Windows:: XEmacs on Microsoft Windows.
* Current Events:: What the Future Holds.
+* Legacy Versions:: New information about old XEmacsen.
@detailmenu
* 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?
+* Q1.3.8:: Does XEmacs support Unicode?
+* Q1.3.9:: How does XEmacs display Unicode?
Getting Started:
* Q1.4.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
* Q2.0.10:: After I run configure I find a coredump, is something wrong?
* Q2.0.11:: XEmacs can't resolve host names.
* Q2.0.12:: Why can't I strip XEmacs?
-* Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
-* Q2.0.14:: How do I figure out which packages to install? (NEW)
+* Q2.0.13:: I don't need no steenkin' packages. Do I?
+* Q2.0.14:: How do I figure out which packages to install?
+* Q2.0.15:: EFS fails with "500 AUTH not understood" (NEW)
+* Q2.0.16:: Cygwin XEmacs won't start: cygXpm-noX4.dll was not found (NEW)
Trouble Shooting:
* Q2.1.1:: XEmacs just crashed on me!
* Q2.1.15:: How to debug an XEmacs problem with a debugger.
* Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
* Q2.1.17:: @samp{Marker does not point anywhere}.
-* Q2.1.18:: [This question intentionally left blank]
+* Q2.1.18:: XEmacs is outputting lots of X errors.
* Q2.1.19:: XEmacs does not follow the local timezone.
* Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
* Q2.1.21:: [This question intentionally left blank]
* Q2.1.22:: XEmacs seems to take a really long time to do some things.
* Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
-* Q2.1.24:: XEmacs won't start without network. (NEW)
-* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
+* Q2.1.24:: XEmacs won't start without network.
+* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more!
Customization and Options
* 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.
+* Q3.10.6:: Why is killing so slow?
Major Subsystems
* Q4.7.4:: Problems installing AUC TeX
* Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
* Q4.7.6:: Is there a MatLab mode?
+* Q4.7.7:: Can I edit files on other hosts?
The Miscellaneous Stuff
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.2:: What flavors of MS Windows are supported? The list name implies NT only.
* Q6.0.3:: Are binaries available?
-* Q6.0.4:: Can I build XEmacs on MS Windows with support for X or Cygwin?
+* Q6.0.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
+* Q6.0.5:: I'd like to help out. What do I do?
+* Q6.0.6:: What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q6.0.7:: What exactly are all the different ways to build XEmacs under Windows?
Building XEmacs on MS Windows:
-* Q6.1.1:: I decided to run with X. Where do I get an X server?
-* Q6.1.2:: What compiler do I need to compile XEmacs?
-* Q6.1.3:: How do I compile for the native port?
-* Q6.1.4:: How do I compile for the X port?
-* Q6.1.5:: How do I compile for Cygnus' Cygwin?
-* Q6.1.6:: What do I need for Cygwin?
+* Q6.1.1:: What compiler/libraries do I need to compile XEmacs?
+* Q6.1.2:: How do I compile the native port?
+* Q6.1.3:: What do I need for Cygwin?
+* Q6.1.4:: How do I compile under Cygwin?
+* Q6.1.5:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+* Q6.1.6:: I decided to run with X. Where do I get an X server?
+* Q6.1.7:: How do I compile with X support?
Customization and User Interface:
-* Q6.2.1:: How will the port cope with differences in the Windows user interface?
+* Q6.2.1:: How does 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{init.el}/@file{.emacs} file?
+* Q6.2.4:: How do I get Windows Explorer to associate a file type with XEmacs?
+* Q6.2.5:: Is it possible to print from XEmacs?
Miscellaneous:
-* Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
+* Q6.3.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{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?
+* Q6.3.3:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
+* Q6.3.4:: What is the porting team doing at the moment?
Troubleshooting:
-* Q6.4.1:: XEmacs won't start on Windows. (NEW)
+* Q6.4.1:: XEmacs won't start on Windows.
+* Q6.4.2:: Why do I get a blank toolbar on Windows 95?
+* Q6.4.3:: XEmacs complains "No such file or directory, diff"
-Current Events:
+What the Future Holds
+
+* Q7.0.1:: What new features will be in XEmacs soon?
+* Q7.0.2:: What's new in XEmacs 21.4?
+* Q7.0.3:: What's new in XEmacs 21.1?
+* Q7.0.4:: What's new in XEmacs 20.4?
+* Q7.0.5:: What's new in XEmacs 20.3?
+* Q7.0.6:: What's new in XEmacs 20.2?
+
+New information about old XEmacsen.
+
+XEmacs 21.1:
+* Q8.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
-* Q7.0.1:: What is new in 20.2?
-* Q7.0.2:: What is new in 20.3?
-* Q7.0.3:: What is new in 20.4?
-* Q7.0.4:: Procedural changes in XEmacs development.
@end detailmenu
@end menu
* 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?
+* Q1.3.8:: Does XEmacs support Unicode?
+* Q1.3.9:: How does XEmacs display Unicode?
Getting Started:
* Q1.4.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
gnu.emacs.help.
If you cannot post or read Usenet news, there is a corresponding mailing
-list which is available. It can be subscribed to by sending a message
-to @email{xemacs-request@@xemacs.org} with @samp{subscribe} in the
-body of the message. Send to the list at @email{xemacs@@xemacs.org}.
-list. To cancel a subscription, you @strong{must} use the
-xemacs-request address. Send a message with a subject of
+list @email{xemacs-news@@xemacs.org} which is available. It can be
+subscribed to via the Mailman Web interface or by sending mail to to
+@email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
+body of the message. See also
+@uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
+subscription, you may use the @email{xemacs-news-request@@xemacs.org}
+address or the Web interface. Send a message with a subject of
@samp{unsubscribe} to be removed.
@node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
@node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
@unnumberedsubsec Q1.0.9: What does XEmacs look like?
-Screen snapshots are available in the WWW version of the FAQ.
-@example
-@uref{http://www.xemacs.org/faq/xemacs-faq.html}
-@end example
+Screen snapshots are available at
+@uref{http://www.xemacs.org/About/Screenshots/index.html}
+as part of the XEmacs website.
@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}.
+Yes. XEmacs can be built under MS Windows and is fully-featured and
+actively developed. See @ref{MS Windows}.
@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 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 @email{pjarvis@@ispchannel.com, Pitts Jarvis}. It's available
-at @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
+Yes.
+
+XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
+will not feel very much like a Mac application as it has no Mac-specific
+code in it.
+
+There is also a port of XEmacs 19.14 that works on all recent versions
+of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
+Pitts Jarvis}. It runs in an equivalent of TTY mode only (one single
+Macintosh window, 25 colors), but has a large number of Mac-specific
+additions. It's available at
+@uref{http://homepage.mac.com/pjarvis/xemacs.html}.
@node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
@unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
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. Send requests to @email{faq@@xemacs.org}.
+HTML and Postscript versions of XEmacs manuals are available from the
+XEmacs web site at
+@uref{http://www.xemacs.org/Documentation/index.html}.
@node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
@unnumberedsec 1.1: Policies
@end html
-@item @email{turnbull@@sk.tsukuba.ac.jp, Steven Turnbull}
+@item @email{stephen@@xemacs.org, Stephen Turnbull}
@item @email{ben@@xemacs.org, Ben Wing}
@unnumberedsubsec Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
Both the stable and development versions of XEmacs include
-internationalization support (aka MULE). MULE currently works on UNIX
-and Linux systems; work for supporting MULE on Windows operating systems
-is in progress. Binaries compiled without MULE support run faster than
-MULE capable XEmacsen.
+internationalization support (aka MULE). MULE currently (21.4) works on
+UNIX and Linux systems. It is possible to build with MULE on Windows
+systems, but if you really need MULE on Windows, it is recommended that
+you build and use the development (21.5) version, and deal with the
+instability of the development tree. Binaries compiled without MULE
+support run faster than MULE capable XEmacsen.
@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
@unnumberedsubsec Q1.3.2: How can I help with internationalization?
people who speak/write languages other than English, who are willing to
use XEmacs/MULE regularly, and have some experience with Elisp.
+Translations of the TUTORIAL and man page are welcome, and XEmacs does
+support multilingual menus, but we have few current translations.
+
@xref{Q1.1.2}.
@node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
@unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
-See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
+See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ for some
+simple methods that also work in non-MULE builds of XEmacs (but only for
+one-octet coded character sets, and mostly for ISO 8859/1). Many of the
+methods available for Cyrillic (@pxref{Q1.3.7}) work without MULE.
+MULE has more general capabilities. @xref{Q1.3.5}.
+
+@xref{Q3.2.7}, which covers display of non-ASCII characters.
@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. To
-enable it, add to your @file{Emacs} file entries like this:
+The message-catalog support was written but is badly bit-rotted. XEmacs
+20 and 21 did @emph{not} support it, and early releases of XEmacs 22
+will not either.
+
+However, menubar localization @emph{does} work. To enable it, add to
+your @file{Emacs} file entries like this:
@example
Emacs*XlwMenu.resourceLabels: True
@node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
@unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs
-@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
+Mule supports a wide variety of input methods. There are three basic
+classes: Lisp implementations, generic platform support, and library
+interfaces.
+
+@emph{Lisp implementations} include Quail, which provides table-driven input
+methods for almost all the character sets that Mule supports (including
+all of the ISO 8859 family, the Indic languages, Thai, and so on), and
+SKK, for Japanese. (SKK also supports an interface to an external
+"dictionary server" process.) Quail supports both typical "dead-key"
+methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
+SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
+methods used for Asian ideographic languages like Chinese.
+
+Lisp implementations can be less powerful (but they are not perceptibly
+inefficient), and of course are not portable to non-Emacs applications.
+The incompatibility can be very annoying. On the other hand, they
+require no special platform support or external libraries, so if you can
+display the characters, Mule can input them for you and you can edit,
+anywhere.
+
+@emph{Generic platform support} is currently limited to the X Input
+Method (XIM) framework, although support for MSIME (for MS Windows) is
+planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
+support is extremely desirable. XIM is enabled at build time by use of
+the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
+your platform documentation. However, normally the input method you use
+is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
+variables.
-@quotation
-Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
-and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
-interface. Interface for Canna does not use @samp{egg}. I don't know
-about XIM. It is to support ATOK, of course, it may work for another
-servers.
+Of course, input skills are portable across most applications. However,
+especially in modern GUI systems the habit of using bucky bits has
+fallen into sad disuse, and many XIM systems are poorly configured for
+use with Emacs. For example, the kinput2 input manager (a separate
+process providing an interface between Japanese dictionary servers such
+as Canna and Wnn, and the application) tends to gobble up keystrokes
+generating Meta characters. This means that to edit while using an XIM
+input method, you must toggle the input method off every time you want
+to use @kbd{M-f}. Your mileage may vary.
+
+@emph{Library interfaces} are most common for Japanese, although Wnn
+supports Chinese (traditional and simplified) and Korean. There are
+Chinese and Korean input servers available, but we do not know of any
+patches for XEmacs to use them directly. You can use them via
+IM-enabled terminals, by manipulating the terminal coding systems. We
+describe only the Japanese-oriented systems here. The advantage of
+these systems is that they are very powerful, and on platforms where
+they are available there is typically a wide range of applications that
+support them. Thus your input skills are portable across applications.
+
+Mule provides built-in interfaces to the following input methods: Wnn4,
+Wnn6, Canna, and SJ3. These can be configured at build time. There are
+patches available (no URL, sorry) to support the SKK server, as well.
+Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
+is specialized to Canna.
Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
-university. It is a powerful and complex system. Wnn4 is free and Wnn6
-is not free.
+University. It is a powerful and complex system. Wnn4 is free and Wnn6
+is not. Wnn uses grammatical hints and probability of word association,
+so in principle Wnn can be cleverer than other methods.
-Canna supports only Japanese. It is made by NEC. It is a simple and
-powerful system. Canna uses only grammar (Wnn uses grammar and
-probability between words), so I think Wnn is cleverer than Canna,
-however Canna users made a good grammar and dictionary. So for standard
-modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
-version of Canna is free (now there is a Microsoft Windows version).
+Canna, made by NEC, supports only Japanese. It is a simple and powerful
+system. Canna uses only grammar, but its grammar and dictionary are
+quite sophisticated. So for standard modern Japanese, Canna seems
+cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
+there is a Microsoft Windows version).
-SJ3 supports only Japanese. It is made by Sony. XIM supports was made
-to use ATOK (a major input method in personal computer world). XIM is
-the standard for accessing input methods bundled in Japanese versions of
-Solaris. (XEmacs 20 will support XIM input).
+SJ3, by Sony, supports only Japanese.
Egg consists of following parts:
@item
Kana/PinYin/Hangul to Kanji transfer layer.
-It is interface layer for network Kana-Kanji server (Wnn and Sj3).
+The interface layer to network Kana-Kanji server (Wnn and Sj3).
@end enumerate
-These input methods are modal, namely there are mode, alphabet mode and
-Kana-Kanji transfer mode. However there are mode-less input methods for
-Egg and Canna. @samp{Boiled-egg} is a mode-less input method running on
-Egg. For Canna, @samp{canna.el} has a tiny boiled-egg like command,
-@code{(canna-boil)}, and there are some boiled-egg like utilities. In
-addition, it was planned to make an abstraction for all transfer type
-input methods. However authors of input methods are busy, so maybe this
-plan is stopped. Perhaps after Mule merged GNU Emacs will be released,
-it will be continued.
-@end quotation
+These input methods are modal. They have a raw (alphabet) mode, a
+phonetic input mode, and Kana-Kanji transfer mode. However there are
+mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
+mode-less input method running on Egg. For Canna, @samp{canna.el} has a
+tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
+boiled-egg-like utilities.
+
+Much of this information was provided by @email{morioka@@jaist.ac.jp,
+MORIOKA Tomohiko}.
@node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
@unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs?
+MULE has evolved rapidly over the last few years, and the original third
+party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
+different implementations. The APIs also vary although recent versions
+of XEmacs have tended to converge to the GNU Emacs standard.
+
+MULE implementations are going to continue to evolve. Both GNU Emacs
+and XEmacs are working hard on Unicode support, which will involve new
+APIs and probably variations on old ones. For XEmacs 22, the old ISO
+2022-based system for recognizing encodings will be replaced by a much
+more flexible system, which should improve accuracy of automatic coding
+detections, but will also involve new APIs.
+
@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
@quotation
-MULE and XEmacs are quite different. So the application
-implementor must write separate code for these mule variants.
+The application implementor must write separate code for these mule
+variants. [Please don't hesitate to report these variants to us; they
+are not, strictly speaking, bugs, but they give third-party developers
+the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
MULE and the next version of Emacs are similar but the symbols are very
different---requiring separate code as well.
Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
-@code{emu} to provide a common interface.
+@code{emu} to provide a common interface. [There is an XEmacs package
+of APEL which provides much more comprehensive coverage. Be careful,
+however; APEL has problems of its own. -- Ed.]
I have the following suggestions about dealing with mule variants:
@end lisp
@end quotation
-@node Q1.3.7, Q1.4.1, Q1.3.6, Introduction
+@node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
@unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
@email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
which can be obtained from
@end quotation
-@uref{http://ftpsearch.ntnu.no/?query=russian.el.Z}.
-@c dead link above
+@uref{http://www.math.uga.edu/~valery/russian.el}.
@email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
@quotation
The fullest resource I found on Russian language use (in and out of
-XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
+XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
@end quotation
-@node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
+@node Q1.3.8, Q1.3.9, Q1.3.7, Introduction
+@unnumberedsubsec Q1.3.8: Does XEmacs support Unicode?
+
+Partially, as an external encoding for files, processes, and terminals.
+It does not yet support Unicode fonts @ref{Q1.3.9, Does XEmacs support
+Unicode Fonts?}
+
+To get Unicode support, you need a Mule-enabled XEmacs. Install
+Mule-UCS from packages in the usual way. Put
+
+@example
+(require 'un-define)
+(set-coding-priority-list '(utf-8))
+(set-coding-category-system 'utf-8 'utf-8)
+@end example
+
+in your init file to enable the UTF-8 coding system. You may wish to
+view the documentation of @code{set-coding-priority-list} if you find
+that files that are not UTF-8 are being mis-recognized as UTF-8.
+
+Install standard national fonts (not Unicode fonts) for all
+character sets you use. See @ref{Q1.3.9}.
+
+Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
+support 31-bit forms of Unicode (UTF-32 or UCS-4).
+
+@node Q1.3.9, Q1.4.1, Q1.3.8, Introduction
+@unnumberedsubsec Q1.3.9: How does XEmacs display Unicode?
+
+Mule doesn't have a Unicode charset internally, so there's nothing to
+bind a Unicode registry to. It would not be straightforward to create,
+either, because Unicode is not ISO 2022-compatible. You'd have to
+translate it to multiple 96x96 pages.
+
+This means that Mule-UCS uses ordinary national fonts for display. This
+is not really a problem, except for those languages that use the Unified
+Han characters. The problem here is that Mule-UCS maps from Unicode
+code points to national character sets in a deterministic way. By
+default, this means that Japanese fonts are tried first, then Chinese,
+then Korean. To change the priority ordering, use the command
+`un-define-change-charset-order'.
+
+It also means you can't use Unicode fonts directly, at least not without
+extreme hackery. You can run -nw with (set-terminal-coding-system
+'utf-8) if you really want a Unicode font for some reason.
+
+Real Unicode support will be introduced in XEmacs 22.0.
+
+@node Q1.4.1, Q1.4.2, Q1.3.9, Introduction
@unnumberedsec 1.4: Getting Started, Backing up & Recovery
@unnumberedsubsec Q1.4.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
* Q2.0.10:: After I run configure I find a coredump, is something wrong?
* Q2.0.11:: XEmacs can't resolve host names.
* Q2.0.12:: Why can't I strip XEmacs?
-* Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
-* Q2.0.14:: I don't want to install a million .els one at a time! (NEW)
+* Q2.0.13:: I don't need no steenkin' packages. Do I?
+* Q2.0.14:: I don't want to install a million .els one at a time!
+* Q2.0.15:: EFS fails with "500 AUTH not understood" (NEW)
+* Q2.0.16:: Cygwin XEmacs won't start: cygXpm-noX4.dll was not found (NEW)
Trouble Shooting:
* Q2.1.1:: XEmacs just crashed on me!
* Q2.1.15:: How to debug an XEmacs problem with a debugger.
* Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
* Q2.1.17:: @samp{Marker does not point anywhere}.
-* Q2.1.18:: [This question intentionally left blank]
+* Q2.1.18:: XEmacs is outputting lots of X errors.
* Q2.1.19:: XEmacs does not follow the local timezone.
* Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
* Q2.1.21:: [This question intentionally left blank]
* Q2.1.22:: XEmacs seems to take a really long time to do some things.
* Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
-* Q2.1.24:: XEmacs won't start without network. (NEW)
-* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
+* Q2.1.24:: XEmacs won't start without network.
+* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more!
@end menu
@node Q2.0.1, Q2.0.2, Installation, Installation
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.
+the support lisp.
These are all Emacs Lisp source code and bytecompiled object code. You
may safely gzip everything named *.el here. You may remove any package
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, games, hyperbole, mh-e,
-hm-html-menus, vm, viper, oobr, gnus, etc. Ask yourself, @emph{Do I
-ever want to use this package?} If the answer is no, then it is a
-candidate for removal.
+Any package with the possible exceptions of xemacs-base, and EFS are
+candidates for removal. Ask yourself, @emph{Do I ever want to use this
+package?} If the answer is no, then it is a candidate for removal.
First, gzip all the .el files. Then go about package by package and
start gzipping the .elc files. Then run XEmacs and do whatever it is
-you normally do. If nothing bad happens, then delete the directory. Be
-conservative about deleting directories, and it would be handy to have a
-backup around in case you get too zealous.
+you normally do. If nothing bad happens, then remove the package. You
+can remove a package via the PUI interface
+(@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
+you wish to delete, and then @kbd{x} to delete them.
-@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.
-
-Online texinfo sources in the @file{info} can either be compressed them
-or remove them. In either case, @kbd{C-h i} (info mode) will no longer
-work.
+Another method is to do @code{M-x package-get-delete-package}.
@node Q2.0.3, Q2.0.4, Q2.0.2, Installation
@unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
buggy optimizers. Please see the @file{PROBLEMS} file that comes with
XEmacs to read what it says about your platform.
+If you compiled XEmacs using @samp{--use-union-type} (or the option
+@samp{USE_UNION_TYPE} in @file{config.inc} under Windows), try
+recompiling again without it. The union type has been known to trigger
+compiler errors in a number of cases.
+
@node Q2.0.7, Q2.0.8, Q2.0.6, Installation
@unnumberedsubsec Q2.0.7: Libraries in non-standard locations
@*
@end iftex
@uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
+[These tarballs and this FAQ are wa-a-ay out of date. Sorry, I'm not
+currently network-capable, and I will probably forgot to update this
+before submitting the patch. -- Ed.]
@c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
@c This list is a pain in the you-know-what to keep in synch with the
@end quotation
@node Q2.0.13, Q2.0.14, Q2.0.12, Installation
-@unnumberedsubsec Q2.0.13: I don't need no steenkin' packages. Do I? (NEW)
+@unnumberedsubsec Q2.0.13: I don't need no steenkin' packages. Do I?
Strictly speaking, no. XEmacs will build and install just fine without
any packages installed. However, only the most basic editing functions
will be available with no packages installed, so installing packages is
an essential part of making your installed XEmacs _useful_.
-@node Q2.0.14, Q2.1.1, Q2.0.13, Installation
-@unnumberedsubsec Q2.0.12: How do I figure out which packages to install? (NEW)
+@node Q2.0.14, Q2.0.15, Q2.0.13, Installation
+@unnumberedsubsec Q2.0.14: How do I figure out which packages to install?
Many people really liked the old way that packages were bundled and do
not want to mess with packages at all. You can grab all the packages at
packages, it is recommended that you use the automatic package tools
afterwards to pick up any recent updates.
-@node Q2.1.1, Q2.1.2, Q2.0.14, Installation
+@node Q2.0.15, Q2.0.16, Q2.0.14, Installation
+@unnumberedsubsec Q2.0.15: EFS fails with "500 AUTH not understood" (NEW)
+
+A typical error: FTP Error: USER request failed; 500 AUTH not understood.
+
+Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
+on comp.emacs.xemacs:
+
+ tell your ftp client to not attempt AUTH authentication (or do not
+ use FTP servers that don't understand AUTH)
+
+and notes that you need to add an element (often "-u") to
+`efs-ftp-program-args'. Use M-x customize-variable, and verify the
+needed flag with `man ftp' or other local documentation.
+
+@node Q2.0.16, Q2.1.1, Q2.0.15, Installation
+@unnumberedsubsec Q2.0.16: Cygwin XEmacs won't start: cygXpm-noX4.dll was not found (NEW)
+
+The Cygwin binary distributed with the netinstaller uses an external DLL
+to handle XPM images (such as toolbar buttons). You may get an error like
+
+ This application has failed to start because cygXpm-noX4.dll was not found.
+ Re-installing the application may fix this problem.
+
+Andy Piper <andy@@xemacs.org> sez:
+
+ cygXpm-noX4 is part of the cygwin distribution under libraries or
+ graphics, but is not installed by default. You need to run the
+ cygwin setup again and select this package.
+
+Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
+distribution.
+
+@node Q2.1.1, Q2.1.2, Q2.0.16, Installation
@unnumberedsec 2.1: Trouble Shooting
@unnumberedsubsec Q2.1.1: Help! XEmacs just crashed on me!
particular sequences of actions, that cause it to crash. If you can
come up with a reproducible way of doing this (or even if you have a
pretty good memory of exactly what you were doing at the time), the
-maintainers would be very interested in knowing about it. Post a
-message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
-Please note that the @samp{crashes} address is exclusively for crash
+maintainers would be very interested in knowing about it. The best way
+to report a bug is using @kbd{M-x report-emacs-bug} (or by selecting
+@samp{Send Bug Report...} from the Help menu). If that won't work
+(e.g. you can't get XEmacs working at all), send ordinary mail to
+@email{crashes@@xemacs.org}. @emph{MAKE SURE} to include the output from
+the crash, especially including the Lisp backtrace, as well as the
+XEmacs configuration from @kbd{M-x describe-installation} (or
+equivalently, the file @file{Installation} in the top of the build
+tree). Please note that the @samp{crashes} address is exclusively for
+crash reports. The best way to report bugs in general is through the
+@kbd{M-x report-emacs-bug} interface just mentioned, or if necessary by
+emailing @email{xemacs-beta@@xemacs.org}. Note that the developers do
+@emph{not} usually follow @samp{comp.emacs.xemacs} on a regular basis;
+thus, this is better for general questions about XEmacs than bug
reports.
-If at all possible, include a stack backtrace of the core dump that was
-produced. This shows where exactly things went wrong, and makes it much
-easier to diagnose problems. To do this, you need to locate the core
-file (it's called @file{core}, and is usually sitting in the directory
-that you started XEmacs from, or your home directory if that other
-directory was not writable). Then, go to that directory and execute a
-command like:
+If at all possible, include a C stack backtrace of the core dump that
+was produced. This shows where exactly things went wrong, and makes it
+much easier to diagnose problems. To do this under Unix, you need to
+locate the core file (it's called @file{core}, and is usually sitting in
+the directory that you started XEmacs from, or your home directory if
+that other directory was not writable). Then, go to that directory and
+execute a command like:
@example
gdb `which xemacs` core
It's possible that a core file didn't get produced, in which case you're
out of luck. Go complain to your system administrator and tell him not
-to disable core files by default. Also @xref{Q2.1.15}, for tips and
+to disable core files by default. Also see @ref{Q2.1.15}, for tips and
techniques for dealing with a debugger.
+If you're under Microsoft Windows, you're out of luck unless you happen
+to have a debugging aid installed on your system, for example Visual
+C++. In this case, the crash will result in a message giving you the
+option to enter a debugger (for example, by pressing @samp{Cancel}). Do
+this and locate the stack-trace window. (If your XEmacs was built
+without debugging information, the stack trace may not be very useful.)
+
When making a problem report make sure that:
@enumerate
What build options you are using.
@item
-If the problem is related to graphics, we will also need to know what
-version of the X Window System you are running, and what window manager
-you are using.
+If the problem is related to graphics and you are running Unix, we will
+also need to know what version of the X Window System you are running,
+and what window manager you are using.
@item
-If the problem happened on a tty, please include the terminal type.
+If the problem happened on a TTY, please include the terminal type.
@end enumerate
+Much of the information above is automatically generated by @kbd{M-x
+report-emacs-bug}. Even more, and often useful, information can be
+generated by redirecting the output of @code{make} and @code{make check}
+to a file (@file{beta.err} is the default used by @code{build-report}),
+and executing @kbd{M-x build-report}.
+
@node Q2.1.2, Q2.1.3, Q2.1.1, Installation
@unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
The binary cannot find the @file{XKeysymDB} file. The location is
hardcoded at compile time so if the system the binary was built on puts
it a different place than your system does, you have problems. To fix,
-set the environment variable @var{XKEYSYMDB} to the location of the
+set the environment variable @code{XKEYSYMDB} to the location of the
@file{XKeysymDB} file on your system or to the location of the one
included with XEmacs which should be at
@iftex
and does not contain the necessary lines. Either ask your system
administrator to replace it with the one which comes with XEmacs (which
is the stock R6 version and is backwards compatible) or set your
-@var{XKEYSYMDB} variable to the location of XEmacs's described above.
+@code{XKEYSYMDB} variable to the location of XEmacs's described above.
@end itemize
@node Q2.1.4, Q2.1.5, Q2.1.3, Installation
Help! I can not get XEmacs to display on my Envizex X-terminal!
-Try setting the @var{DISPLAY} variable using the numeric IP address of
+Try setting the @code{DISPLAY} variable using the numeric IP address of
the host you are running XEmacs from.
@node Q2.1.6, Q2.1.7, Q2.1.5, Installation
@end quotation
@node Q2.1.15, Q2.1.16, Q2.1.14, Installation
-@unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
+@unnumberedsubsec Q2.1.15: How to debug an XEmacs problem with a debugger
If XEmacs does crash on you, one of the most productive things you can
do to help get the bug fixed is to poke around a bit with the debugger.
@itemize @bullet
@item
First of all, if the crash is at all reproducible, consider very
-strongly recompiling your XEmacs with debugging symbols, with no
-optimization, and with the configure options @samp{--debug=yes} and
-@samp{--error-checking=all}. This will make your XEmacs run somewhat
-slower but make it a lot more likely to catch the problem earlier
-(closer to its source), and a lot easier to determine what's going on
-with a debugger.
+strongly recompiling your XEmacs with debugging symbols and with no
+optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
+that's an "oh" followed by a zero), and with the configure options
+@samp{--debug=yes} and @samp{--error-checking=all}. This will make your
+XEmacs run somewhat slower, but you are a lot more likely to catch the
+problem earlier (closer to its source). It makes it a lot easier to
+determine what's going on with a debugger.
@item
-If you're able to run XEmacs under a debugger and reproduce the crash
-(if it's inconvenient to do this because XEmacs is already running or is
-running in batch mode as part of a bunch of scripts, consider attaching
-to the existing process with your debugger; most debuggers let you do
-this by substituting the process ID for the core file when you invoke
-the debugger from the command line, or by using the @code{attach}
-command or something similar), here are some things you can do:
+If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
+process), or it's inconvenient to run XEmacs again because XEmacs is
+already running or is running in batch mode as part of a bunch of
+scripts, you may be able to attach to the existing process with your
+debugger. Most debuggers let you do this by substituting the process ID
+for the core file when you invoke the debugger from the command line, or
+by using the @code{attach} command or something similar.
+
+@item
+If you're able to run XEmacs under a debugger and reproduce the crash,
+here are some things you can do:
@item
If XEmacs is hitting an assertion failure, put a breakpoint on
declared static in eval.c.
@item
+If XEmacs is outputting lots of X errors, put a breakpoint on
+@code{x_error_handler()}; that will tell you which call is causing them.
+
+@item
Internally, you will probably see lots of variables that hold objects of
-type @code{Lisp_Object}. These are exactly what they appear to be,
-i.e. references to Lisp objects. Printing them out with the debugger
-probably won't be too useful---you'll likely just see a number. To
-decode them, do this:
+type @code{Lisp_Object}. These are references to Lisp objects.
+Printing them out with the debugger probably won't be too
+useful---you'll likely just see a number. To decode them, do this:
@example
-call debug_print (OBJECT)
+call dp (OBJECT)
@end example
where @var{OBJECT} is whatever you want to decode (it can be a variable,
-a function call, etc.). This will print out a readable representation
-on the TTY from which the xemacs process was invoked.
+a function call, etc.). This uses the Lisp printing routines to out a
+readable representation on the TTY from which the xemacs process was
+invoked.
@item
If you want to get a Lisp backtrace showing the Lisp call
stack, do this:
@example
-call debug_backtrace ()
+call db ()
@end example
@item
-Using @code{debug_print} and @code{debug_backtrace} has two
-disadvantages - it can only be used with a running xemacs process, and
-it cannot display the internal C structure of a Lisp Object. Even if
-all you've got is a core dump, all is not lost.
+Using @code{dp} and @code{db} has two disadvantages - they can only be
+used with a running (including hung or zombie) xemacs process, and they
+do not display the internal C structure of a Lisp Object. Even if all
+you've got is a core dump, all is not lost.
If you're using GDB, there are some macros in the file
@file{src/.gdbinit} in the XEmacs source distribution that should make
@item lbt
Usage: lbt @*
Print the current Lisp stack trace.
-Requires a running xemacs process.
+Requires a running xemacs process. (It works by calling the db
+routine described above.)
@item ldp
Usage: ldp lisp_object @*
Print a Lisp Object value using the Lisp printer.
-Requires a running xemacs process.
+Requires a running xemacs process. (It works by calling the dp
+routine described above.)
@item run-temacs
Usage: run-temacs @*
running the XEmacs process under a debugger, the stack trace should be
clean.
-@email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
-if dynamic linking and debugging is a problem on Linux.
+@email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
+version 1.8 if dynamic linking and debugging is a problem on Linux.
@item
If you're using a debugger to get a C stack backtrace and you're
Your stack is getting trashed. Debugging this is hard; you have to do a
binary-search type of narrowing down where the crash occurs, until you
figure out exactly which line is causing the problem. Of course, this
-only works if the bug is highly reproducible.
+only works if the bug is highly reproducible. Also, in many cases if
+you run XEmacs from the debugger, the debugger can protect the stack
+somewhat. However, if the stack is being smashed, it is typically the
+case that there is a wild pointer somewhere in the program, often quite
+far from where the crash occurs.
@item
If your stack trace has exactly one frame in it, with address 0x0, this
could simply mean that XEmacs attempted to execute code at that address,
e.g. through jumping to a null function pointer. Unfortunately, under
those circumstances, GDB under Linux doesn't know how to get a stack
-trace. (Yes, this is the third Linux-related problem I've mentioned. I
+trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
have no idea why GDB under Linux is so bogus. Complain to the GDB
-authors, or to comp.os.linux.development.system). Again, you'll have to
+authors, or to comp.os.linux.development.system.) Again, you'll have to
use the narrowing-down process described above.
@item
@file{src/gdbinit}. This had the disadvantage of not being sourced
automatically by gdb, so you had to set that up yourself.
+@item
+If you are running Microsoft Windows, the the file @file{nt/README} for
+further information about debugging XEmacs.
+
@end itemize
@node Q2.1.16, Q2.1.17, Q2.1.15, Installation
@end enumerate
@node Q2.1.18, Q2.1.19, Q2.1.17, Installation
-@unnumberedsubsec Q2.1.18: removed
+@unnumberedsubsec Q2.1.18: XEmacs is outputting lots of X errors.
+
+If this is happening, we would very much like to know what's causing
+them. To find this out, see @ref{Q2.1.15}. Try to get both a C and Lisp
+backtrace, and send them to @email{xemacs-beta@@xemacs.org}.
@node Q2.1.19, Q2.1.20, Q2.1.18, Installation
@unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
@end quotation
@node Q2.1.24, Q2.1.25, Q2.1.23, Installation
-@unnumberedsubsec Q2.1.24: XEmacs won't start without network. (NEW)
+@unnumberedsubsec Q2.1.24: XEmacs won't start without network.
If XEmacs starts when you're on the network, but fails when you're not
on the network, you may be missing a "localhost" entry in your
Add that line, and XEmacs will be happy.
@node Q2.1.25, , Q2.1.24, Installation
-@unnumberedsubsec Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
+@unnumberedsubsec Q2.1.25:: After upgrading, XEmacs won't do `foo' any more!
You have been used to doing `foo', but now when you invoke it (or click
the toolbar button or select the menu item), nothing (or an error)
happens. The simplest explanation is that you are missing a package
that is essential to you. You can either track it down and install it
(there is a list of packages and brief descriptions of their contents in
-@file{etc/PACKAGES}), or install the `Sumo Tarball' (see @pxref{Q2.0.14}).
+@file{etc/PACKAGES}), or install the `Sumo Tarball' (@pxref{Q2.0.14}).
@c #### should xref to XEmacs manual here
* 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.2.7:: How do I display non-ASCII characters?
The Modeline:
* Q3.3.1:: How can I make the modeline go away?
* 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.
+* Q3.10.6:: Why is killing so slow?
@end menu
@node Q3.0.1, Q3.0.2, Customization, Customization
Search through the @file{NEWS} file for @samp{X Resources}. A fairly
comprehensive list is given after it.
-In addition, an @file{app-defaults} file is supplied,
-@file{etc/Emacs.ad} listing the defaults. The file
-@file{etc/sample.Xdefaults} gives a set of defaults that you might
-consider. It is essentially the same as @file{etc/Emacs.ad} but some
-entries are slightly altered. Be careful about installing the contents
-of this file into your @file{.Xdefaults} or @file{.Xresources} file if
-you use GNU Emacs under X11 as well.
+In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
+supplied, listing the defaults. The file @file{etc/sample.Xresources}
+gives a different set of defaults that you might consider for
+installation in your @file{~/.Xresources} file. It is nearly the same
+as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
+installing the contents of this file into your @file{.Xresources} (or
+legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
@node Q3.1.2, Q3.1.3, Q3.1.1, Customization
@unnumberedsubsec Q3.1.2: How can I detect a color display?
@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{init.el}/@file{.emacs} instead of from my @file{.Xdefaults}?
+@file{init.el}/@file{.emacs} instead of from my @file{.Xresources}?
Like this:
Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
setting face values.
-In @file{.Xdefaults}:
+In @file{.Xresources}:
@example
Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
Emacs.modeline.attributeFont: fixed
@end example
-This is confusing because modeline is a face, and can be found listed
-with all faces in the current mode by using @kbd{M-x set-face-font
-(enter) ?}. It uses the face specification of @code{attributeFont},
-while menubar is a normal X thing that uses the specification
-@code{font}. With Motif it may be necessary to use @code{fontList}
-instead of @code{font}.
+This is confusing because @samp{default} and @samp{modeline} are face
+names, and can be found listed with all faces in the current mode by
+using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
+resource @samp{attributeFont}.
+
+On the other hand, @samp{menubar} is a normal X thing that uses the
+resource @samp{font}. With Motif it @emph{may be} necessary to use
+@samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
+configurations with Mule it @emph{is} necessary to use @samp{fontSet}
+instead of @samp{font}. (Sorry, there just is no simple recipe here.)
@node Q3.2.3, Q3.2.4, Q3.2.2, Customization
@unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
region?
You can change the face @code{zmacs-region} either in your
-@file{.Xdefaults}:
+@file{.Xresources}:
@example
Emacs.zmacs-region.attributeForeground: firebrick
(set-device-class nil 'color))
@end lisp
-@node Q3.2.6, Q3.3.1, Q3.2.5, Customization
+@node Q3.2.6, Q3.2.7, Q3.2.5, Customization
@unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
@c New
@email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
@end quotation
-@node Q3.3.1, Q3.3.2, Q3.2.6, Customization
+@node Q3.2.7, Q3.3.1, Q3.2.6, Customization
+@unnumberedsubsec Q3.2.7: How do I display non-ASCII characters?
+@c New
+
+If you're using a Mule-enabled XEmacs, then display is automatic. If
+you're not seeing the characters you expect, either (1) you don't have
+appropriate fonts available or (2) XEmacs did not correctly detect the
+coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
+install fonts as is customary for your platform. In case (2), you
+need to tell XEmacs explicitly what coding systems you're using.
+@ref{Specify Coding, , , xemacs}.
+
+If your XEmacs is not Mule-enabled, and for some reason getting a
+Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
+You can arrange it by brute force. In @file{event-Xt.c} (suppress the
+urge to look in this file---play Doom instead, because you'll survive
+longer), it is written:
+
+@quotation
+In a non-Mule world, a user can still have a multi-lingual editor, by
+doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
+their Latin-2 buffers, etc.
+@end quotation
+
+For the related problem of @emph{inputting} non-ASCII characters in a
+non-Mule XEmacs, @xref{Q3.5.7}.
+
+@node Q3.3.1, Q3.3.2, Q3.2.7, Customization
@unnumberedsec 3.3: The Modeline
@unnumberedsubsec Q3.3.1: How can I make the modeline go away?
@c Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
@c you haven't liked or used the modeline in the past, you might want to
@c try the new version out.
-@c
+@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?
It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
@c Add this code to your @file{init.el}/@file{.emacs} to turn it off:
-@c
+@c
@c @lisp
@c (setq fume-display-in-modeline-p nil)
@c @end lisp
-@c
+@c
@c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
@c mode:
-@c
+@c
@c @lisp
@c (add-hook 'TeX-mode-hook
@c '(lambda () (setq fume-display-in-modeline-p nil)))
@c @end lisp
-@c
+@c
@email{dhughes@@origin-at.co.uk, David Hughes} writes:
@quotation
Yes. Use @code{gnuclient -nw}. (Prior to 20.3, use the @code{gnuattach}
program supplied with XEmacs instead.)
-Also @xref{Q5.0.12}.
+Also see @ref{Q5.0.12}.
@node Q3.5.1, Q3.5.2, Q3.4.2, Customization
@unnumberedsec 3.5: The Keyboard
(global-set-key 'redirected-delete 'foo)
@end lisp
-Also @xref{Q3.5.10}.
+Also see @ref{Q3.5.10}.
@node Q3.5.5, Q3.5.6, Q3.5.4, Customization
@unnumberedsubsec Q3.5.5: Scrolling one line at a time.
Running @samp{xmodmap -pk} will list all of the defined keysyms.
@end quotation
+For the related problem of @emph{displaying} non-ASCII characters in a
+non-Mule XEmacs, @xref{Q3.2.7}.
+
@node Q3.5.8, Q3.5.9, Q3.5.7, Customization
@unnumberedsubsec Q3.5.8: [This question intentionally left blank]
@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}.
+Also see @ref{Q3.5.4}.
@node Q3.5.10, Q3.5.11, Q3.5.9, Customization
@unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
@c If you are running XEmacs 19.13 or earlier, add this command to your
@c @file{init.el}/@file{.emacs}.
-@c
+@c
@c @lisp
@c (set-menubar nil)
@c @end lisp
-@c
+@c
@c Starting with XEmacs 19.14 the preferred method is:
-@c
+@c
@lisp
(set-specifier menubar-visible-p nil)
@end lisp
@end lisp
If you'd like to write your own, this file provides as good a set of
-examples as any to start from. The file is located in
-@file{lisp/packages/big-menubar.el} in the XEmacs installation
-directory.
+examples as any to start from. The file is located in edit-utils
+package.
@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}?
I am trying to use a resource like @code{Emacs*menubar*font} to set the
font of the menubar but it's not working.
-If you are using the real Motif menubar, this resource is not
-recognized; you have to say:
+In Motif, the use of @samp{font} resources is obsoleted in order to
+support internationalization. If you are using the real Motif menubar,
+this resource is not recognized at all; you have to say:
@example
Emacs*menubar*fontList: FONT
@end example
-If you are using the Lucid menubar, the former resource will be
-recognized only if the latter resource is unset. This means that the
-resource
+If you are using the Lucid menubar, for backward compatibility with
+existing user configurations, the @samp{font} resource is recognized.
+Since this is not supported by Motif itself, the code is a kludge and
+the @samp{font} resource will be recognized only if the @samp{fontList}
+resource resource is unset. This means that the resource
@example
*fontList: FONT
even though the latter is more specific.
+In non-Motif configurations using @samp{--with-mule} and
+@samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
+resource @emph{instead of} the @code{font} resource. The backward
+compatibility kludge was never implemented for non-Motif builds.
+Example:
+
+@example
+*fontSet: FONT
+@end example
+
@node Q3.8.5, Q3.9.1, Q3.8.4, Customization
@unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
@unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
To disable them for all frames, add the following line to
-your @file{.Xdefaults}:
+your @file{.Xresources}:
@example
Emacs.scrollBarWidth: 0
@lisp
(set-specifier scrollbar-width 0 (current-buffer))
@end lisp
-@c
+@c
@c In XEmacs versions prior to 19.14, you had to use the hairier construct:
-@c
+@c
@c @lisp
@c (set-specifier scrollbar-width (cons (selected-frame) 0))
@c @end lisp
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{init.el}/@file{.emacs}:
+To get this behavior, ensure that you have the @file{pc} package
+installed, and add the following lines to your
+@file{init.el}/@file{.emacs}:
@lisp
(cond
(pending-delete-on t)))
@end lisp
-Note that this will work with both Backspace and Delete. This code is a
+Note that this will work with both Backspace and Delete. This code is a
tad more complicated than it has to be for XEmacs in order to make it
more portable.
@strong{Warning: This command turns off all region highlighting.}
-Also @xref{Q3.10.1}.
+Also see @ref{Q3.10.1}.
-@node Q3.10.5, , Q3.10.4, Customization
+@node Q3.10.5, Q3.10.6, Q3.10.4, Customization
@unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
This has been fixed by default starting with XEmacs-20.3.
Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
answer.
+@node Q3.10.6, , Q3.10.5, Customization
+@unnumberedsubsec Q3.10.6: Why is killing so slow?
+
+This actually is an X Windows question, although you'll notice it with
+keyboard operations as well as while using the GUI. Basically, there
+are four ways to communicate interprogram via the X server:
+
+@table @strong
+@item Primary selection
+a transient selection that gets replaced every time a new selection is made
+
+@item Secondary selection
+for "exchanging" with the primary selection
+
+@item Cut buffers
+a clipboard internal to the X server (deprecated)
+
+@item Clipboard selection
+a selection with a notification protocol that allows a separate app to
+manage the clipboard
+@end table
+
+The cut buffers are deprecated because managing them is even more
+inefficient than the clipboard notification protocol. The primary
+selection works fine for many users and applications, but is not very
+robust under intensive or sophisticated use.
+
+In Motif and MS Windows, a clipboard has become the primary means for
+managing cut and paste. These means that "modern" applications tend to
+be oriented toward a true clipboard, rather than the primary selection.
+(On Windows, there is nothing equivalent to the primary selection.)
+It's not that XEmacs doesn't support the simple primary selection
+method, it's that more and more other applications don't.
+
+So the slowdown occurs because XEmacs now engages in the clipboard
+notification protocol on @emph{every} kill. This is especially slow on
+Motif.
+
+With most people running most clients and server on the same host, and
+many of the rest working over very fast communication, you may expect
+that the situation is not going to improve.
+
+There are a number of workarounds. The most effective is to use a
+special command to do selection ownership only when you intend to paste
+to another application. Useful commands are @code{kill-primary-selection}
+and @code{copy-primary-selection}. These work only on text selected
+with the mouse (probably; experiment), and are bound by default to the
+@kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
+@code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
+yank the clipboard contents with @code{yank-primary-selection}, bound to
+the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
+
+If you are communicating by cut and paste with applications that use the
+primary selection, then you can customize
+@code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
+version 20 behavior. How can you tell if a program will support this?
+Motifly-correct programs require the clipboard; you lose. For others,
+only by trying it. You also need to customize the complementary
+@code{interprogram-paste-function} to @code{nil}. (Otherwise
+XEmacs-to-XEmacs pastes will not work correctly.)
+
+You may get some relief on Motif by setting
+@code{x-selection-strict-motif-ownership} to nil, but this means you will
+only intermittently be able to paste XEmacs kills to Motif applications.
+
+Thanks to Jeff Mincy and Glynn Clements for corrections.
+
@node Subsystems, Miscellaneous, Customization, Top
@unnumbered 4 Major Subsystems
* Q4.7.4:: Problems installing AUC TeX
* Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
* Q4.7.6:: Is there a MatLab mode?
+* Q4.7.7:: Can I edit files on other hosts?
@end menu
@node Q4.0.1, Q4.0.2, Subsystems, Subsystems
@node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
@unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
-A FAQ for VM exists at @uref{http://www.cyberpass.net/~gorkab/vmfaq.htm}.
+A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
this package out---it's much simpler than it looks, and once installed,
trivial to use.
+@email{youngs@@xemacs.org, Steve Youngs} writes:
+
+@quotation
+All the major Emacs Lisp based MUAs (Gnus, MH-E, and VM) all do their
+own thing when it comes to MIME so you won't need TM to get MIME support
+in these packages.
+@end quotation
+
@node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
@unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
@unnumberedsec 4.6: Infodock
@unnumberedsubsec Q4.6.1: What is Infodock?
-InfoDock is an integrated productivity toolset, mainly aimed at
-technical people. It is developed and supported by InfoDock
-Associates, a firm that offers custom support and development
-for InfoDock, XEmacs and GNU Emacs. ( @uref{http://www.infodock.com},
-@email{info@@infodock.com}, +1 408 243 3300).
+@uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
+integrated productivity toolset, mainly aimed at technical people,
+hosted at SourceForge.
InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
the power of Emacs, but with an easier to use and more comprehensive
@iftex
@*
@end iftex
-@uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}.
+@uref{ftp://sunsite.dk/packages/auctex/auctex.tar.gz}.
In case you don't have access to anonymous ftp, you can get it by an
email request to @email{ftpmail@@decwrl.dec.com}.
@iftex
@*
@end iftex
-@uref{http://sunsite.auc.dk/auctex/}.
+@uref{http://sunsite.dk/auctex/}.
@node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
@unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
appreciated.
@end enumerate
-@node Q4.7.6, , Q4.7.5, Subsystems
+@node Q4.7.6, Q4.7.7, Q4.7.5, Subsystems
@unnumberedsubsec Q4.7.5: Is there a MatLab mode?
Yes, a matlab mode and other items are available at the
@uref{ftp://ftp.mathworks.com/pub/contrib/emacs_add_ons,
MathWorks' emacs_add_ons ftp directory}.
+@node Q4.7.7, , Q4.7.6, Subsystems
+@unnumberedsubsec Q4.7.7: Can I edit files on other hosts?
+
+Yes. Of course XEmacs can use any network file system (such as NFS or
+Windows file sharing) you have available, and includes some
+optimizations and safety features appropriate to those environments.
+
+It is also possible to transparently edit files via FTP, ssh, or rsh. That
+is, XEmacs makes a local copy using the transport in the background, and
+automatically refreshes the remote original from that copy when you save
+it. XEmacs also is capable of doing file system manipulations like
+creating and removing directories and files. The FTP interface is
+provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
+ssh/rsh interface is provided by the optional @samp{tramp} package
+@ref{Top, TRAMP, , tramp}.
+
@node Miscellaneous, MS Windows, Subsystems, Top
@unnumbered 5 The Miscellaneous Stuff
@c In versions of XEmacs prior to 19.14, you had to use a kludgy solution
@c like this:
-@c
+@c
@c @lisp
@c (setq c-font-lock-keywords c-font-lock-keywords-2
@c c++-font-lock-keywords c++-font-lock-keywords-2
@c lisp-font-lock-keywords lisp-font-lock-keywords-2)
@c @end lisp
-@c
+@c
@c It will work for C, C++ and Lisp.
-@c
+@c
See also @code{Syntax Highlighting} from the @code{Options} menu.
Remember to save options.
@c The sound support in XEmacs 19.14 was greatly improved over previous
@c versions.
-@c
+@c
@node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
@unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
The package @code{ps-print}, which is now included with XEmacs, provides
the ability to do this. The source code contains complete instructions
-on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
+on its use, in
+@file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
+being the default location of an installed ps-print package.
@node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
@unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
port of XEmacs.
@menu
-
General Info
* Q6.0.1:: What is the status of the XEmacs port to Windows?
-* Q6.0.2:: What flavors of MS Windows are supported?
-* Q6.0.3:: Where are the XEmacs on MS Windows binaries?
-* Q6.0.4:: 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.4:: How do I compile for the X port?
-* Q6.1.5:: How do I compile for Cygnus' Cygwin?
-* Q6.1.6:: What do I need for Cygwin?
-
-Customization and User Interface
-* Q6.2.1:: How will the port cope with differences in the Windows user interface?
+* Q6.0.2:: What flavors of MS Windows are supported? The list name implies NT only.
+* Q6.0.3:: Are binaries available?
+* Q6.0.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
+* Q6.0.5:: I'd like to help out. What do I do?
+* Q6.0.6:: What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q6.0.7:: What exactly are all the different ways to build XEmacs under Windows?
+
+Building XEmacs on MS Windows:
+* Q6.1.1:: What compiler/libraries do I need to compile XEmacs?
+* Q6.1.2:: How do I compile the native port?
+* Q6.1.3:: What do I need for Cygwin?
+* Q6.1.4:: How do I compile under Cygwin?
+* Q6.1.5:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
+* Q6.1.6:: I decided to run with X. Where do I get an X server?
+* Q6.1.7:: How do I compile with X support?
+
+Customization and User Interface:
+* Q6.2.1:: How does 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{init.el}/@file{.emacs} file?
+* Q6.2.4:: How do I get Windows Explorer to associate a file type with XEmacs?
+* Q6.2.5:: Is it possible to print from XEmacs?
-Miscellaneous
-* Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
+Miscellaneous:
+* Q6.3.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{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?
+* Q6.3.3:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
+* Q6.3.4:: What is the porting team doing at the moment?
Troubleshooting:
-* Q6.4.1:: XEmacs won't start on Windows. (NEW)
+* Q6.4.1:: XEmacs won't start on Windows.
+* Q6.4.2:: Why do I get a blank toolbar on Windows 95?
+* Q6.4.3:: XEmacs complains "No such file or directory, diff"
@end menu
@unnumberedsec 6.0: General Info
@unnumberedsubsec Q6.0.1: What is the status of the XEmacs port to Windows?
-Is XEmacs really getting ported to MS Windows? What is the status of the port?
+Is XEmacs really ported to MS Windows? What is the status of the port?
+
+Beginning with release 21.0, XEmacs has worked under MS Windows. A
+group of dedicated developers actively maintains and improves the
+Windows-specific portions of the code. The mailing list at
+@email{xemacs-nt@@xemacs.org} is dedicated to that effort (please use
+the -request address to subscribe). (Despite its name, XEmacs actually
+works on all versions of Windows.)
-Yes, a group of volunteers actively works on making XEmacs code base
-cleanly compile and run on MS Windows operating systems. The mailing
-list at @email{xemacs-nt@@xemacs.org} is dedicated to that effort
-(please use the -request address to subscribe).
+As of May 2001, XEmacs on MS Windows is stable and full-featured, and
+has been so for a year or more -- in fact, some features, such as
+printing, actually work better on Windows than native Unix. However,
+the internationalization (Mule) support does not work -- although this
+is being actively worked on.
-At this time, XEmacs on MS Windows is stable and full-featured.
-However, the internationalization (Mule) support 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 Windows 95, Windows
-98, Windows NT, Windows 2000, Windows ME, Windows XP, and all newer
-versions of Windows. The MS Windows-specific code is based on Microsoft
-Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
+The list name is misleading, as XEmacs supports and has been compiled on
+Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
+XP, and all newer versions of Windows. The MS Windows-specific code is
+based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
+MS-DOS.
+
+XEmacs also supports the Cygwin and MinGW development and runtime
+environments, where it also uses native Windows code for graphical
+features.
@node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
@unnumberedsubsec Q6.0.3: Are binaries available?
-Binaries are available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/win32/} for the native MS
-Windows version.
+Binaries are available at @uref{http://www.xemacs.org/Download/win32/}
+for the native and Cygwin MS Windows versions of 21.4, and the native
+version of 21.1.
+
+The 21.4 binaries use a modified version of the Cygwin installer. Run
+the provided @file{setup.exe}, and follow the instructions.
+
-@node Q6.0.4, Q6.1.1, Q6.0.3, MS Windows
-@unnumberedsubsec Q6.0.4: Can I build XEmacs on MS Windows with support for X or Cygwin?
+@node Q6.0.4, Q6.0.5, Q6.0.3, MS Windows
+@unnumberedsubsec Q6.0.4: Can I build XEmacs on MS Windows with X support? Do I need to?
-Yes. XEmacs can be built in several ways in the MS Windows environment.
+Yes, you can, but no you do not need to. In fact, we recommend that you
+use a native-GUI version unless you have a specific need for an X
+version.
+
+@node Q6.0.5, Q6.0.6, Q6.0.4, MS Windows
+@unnumberedsubsec Q6.0.5: I'd like to help out. What do I do?
+
+It depends on the knowledge and time you possess. If you are a
+programmer, try to build XEmacs and see if you can improve it.
+Windows-specific improvements like integration with established
+Windows environments are especially sought after.
+
+Otherwise, you can still help by downloading the binaries, using
+XEmacs as your everyday editor and reporting bugs you find to the
+mailing list.
+
+Another area where we need help is the documentation: We need good
+documentation for building XEmacs and for using it. This FAQ is a
+small step in that direction.
+
+@node Q6.0.6, Q6.0.7, Q6.0.5, MS Windows
+@unnumberedsubsec Q6.0.6: What are Cygwin and MinGW, and do I need them to run XEmacs?
+
+To answer the second part of the question: No, you, you don't need
+Cygwin or MinGW to build or to run XEmacs. But if you have them and
+want to use them, XEmacs supports these environments.
+
+(One important reason to support Cygwin is that it lets the MS Windows
+developers test out their code in a Unix environment without actually
+having to have a Unix machine around. For this reason alone, Cygwin
+support is likely to remain supported for a long time in XEmacs. Same
+goes for the X support under Cygwin, for the same reasons. MinGW
+support, on the other hand, depends on volunteers to keep it up to date;
+but this is generally not hard.)
+
+Cygwin is a set of tools providing Unix-like API on top of Win32.
+It makes it easy to port large Unix programs without significant
+changes to their source code. It is a development environment as well
+as a runtime environment.
+
+When built with Cygwin, XEmacs supports all display types -- TTY, X &
+Win32 GUI, and can be built with support for all three simultaneously.
+If you build with Win32 GUI support then the Cygwin version uses the
+majority of the Windows-specific code, which is mostly related to
+display. If you want to build with X support you need X libraries (and
+an X server to display XEmacs on); see @ref{Q6.1.4}. TTY and Win32 GUI
+require no additional libraries beyond what comes standard with Cygwin.
+
+The advantages of the Cygwin version are that it integrates well with
+the Cygwin environment for existing Cygwin users; uses configure so
+building with different features is very easy; and actively supports X &
+TTY. Furthermore, the entire Cygwin environment and compiler are free,
+whereas Visual C++ costs money.
+
+The disadvantage is that it requires the whole Cygwin environment,
+whereas the native port requires only a suitable MS Windows compiler.
+Also, it follows the Unix filesystem and process model very closely
+(some will undoubtedly view this as an advantage).
+
+See @uref{http://sources.redhat.com/cygwin/} for more information on
+Cygwin.
+
+MinGW is a collection of header files and import libraries that allow
+one to use GCC under the Cygwin environment to compile and produce
+exactly the same native Win32 programs that you can using Visual C++.
+Programs compiled with MinGW make use of the standard Microsoft runtime
+library @file{MSVCRT.DLL}, present on all Windows systems, and look,
+feel, and act like a standard Visual-C-produced application. (The only
+difference is the compiler.) This means that, unlike a
+standardly-compiled Cygwin application, no extra runtime support
+(e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
+fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
+environment, for those die-hard Unix hackers out there), is the main
+advantage of MinGW. It is also potentially faster than Cygwin because
+it has less overhead when calling Windows, but you lose the POSIX
+emulation layer, which makes Unix programs harder to port. (But this is
+irrelevant for XEmacs since it's already ported to Win32.)
+
+See @uref{http://www.mingw.org/} for more information on MinGW.
+
+@node Q6.0.7, Q6.1.1, Q6.0.6, MS Windows
+@unnumberedsubsec Q6.0.7: What exactly are all the different ways to build XEmacs under Windows?
+
+XEmacs can be built in several ways in the MS Windows environment.
The standard way is what we call the "native" port. It uses the Win32
API and has no connection with X whatsoever -- it does not require X
support. Almost all development is geared towards this version, and
there is little reason not to use it.
-You can also build XEmacs "X" port---it requires X libraries to build
-and an X server to run. Internally it uses the Xt event loop and makes
-use of X toolkits. Its look is quite un-Windowsy, and it is not well
-maintained, but it is being kept around for the time being because it
-has a long history.
-
-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.
+The second way to build is the Cygwin port. It takes advantage of
+Cygnus emulation library under Win32. @xref{Q6.0.6}, for more
+information.
-Cygwin port supports all display types---TTY, X & MS GUI, and can be
-built with support for all three. If you build with MS GUI support
-then the Cygwin version uses the majority of the msw code, which is
-mostly related to display. If you want to build with X support you
-need X libraries. If you want to build with TTY support you need
-ncurses. MS GUI requires no additional libraries.
+A third way is the MinGW port. It uses the Cygwin environment to build
+but does not require it at runtime. @xref{Q6.0.6}, for more
+information.
-The advantages of the Cygwin version are that it integrates well with
-Cygwin environment for existing Cygwin users; uses configure so building
-with different features is very easy; and has process support in X &
-tty.
+Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
+port. This was actually the first version of XEmacs that ran under MS
+Windows, and although the code is still in XEmacs, it's essentially
+orphaned and it's unlikely it will compile without a lot of work. If
+you want an MS Windows versin of XEmacs that supports X, use the Cygwin
+version. (The X support there is actively maintained, so that Windows
+developers can test the X support in XEmacs.)
-The disadvantage is that it requires several Unix utilities and the
-whole Cygwin environment, whereas the native port requires only a
-suitable MS Windows compiler. Also, it follows the Unix filesystem and
-process model very closely (some will undoubtedly view this as an
-advantage).
-@node Q6.1.1, Q6.1.2, Q6.0.4, MS Windows
+@node Q6.1.1, Q6.1.2, Q6.0.7, MS Windows
@unnumberedsec 6.1: Building XEmacs on MS Windows
-@unnumberedsubsec Q6.1.1: I decided to run with X. Where do I get an X server?
-
-Pointers to X servers can be found at
-@iftex
-@*
-@end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/};
-
-look for "Where to get an X server". Also note that, although the above
-page talks about Cygnus gnu-win32 (Cygwin), the information on X servers
-is Cygwin-independent. You don't have to be running/using Cygwin to use
-these X servers, and you don't have to compile XEmacs under Cygwin to
-use XEmacs with these X servers. An "X port" XEmacs compiled under
-Visual C++ will work with these X servers (as will XEmacs running on a
-Unix box, redirected to the server running on your PC).
+@unnumberedsubsec Q6.1.1: What compiler/libraries do I need to compile XEmacs?
+You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
+some beta testers currently trying to compile with VC.NET, aka version
+7.0, but we can't yet report complete success.) For the Cygwin and MinGW
+versions, you need the Cygwin environment, which comes with GCC, the
+compiler used for those versions. @xref{Q6.0.6}, for more information
+on Cygwin and MinGW.
@node Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
-@unnumberedsubsec Q6.1.2: What compiler do I need to compile XEmacs?
-
-You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the Cygwin
-port, which uses Gcc. There is also a MINGW32 port of XEmacs (using
-Gcc, but using native libraries rather than the Cygwin libraries). ####
-More information about this should be provided.
+@unnumberedsubsec Q6.1.2: How do I compile the native port?
+Please read the file @file{nt/README} in the XEmacs distribution, which
+contains the full description.
@node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
-@unnumberedsubsec Q6.1.3: How do I compile for the native port?
+@unnumberedsubsec Q6.1.3: What do I need for Cygwin?
-Please read the file @file{nt/README} in the XEmacs distribution, which
-contains the full description.
+You can find the Cygwin tools and compiler at:
+@uref{http://sources.redhat.com/cygwin/}
-@node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
-@unnumberedsubsec Q6.1.4: How do I compile for the X port?
+Click on the @samp{Install now!} link, which will download a file
+@file{setup.exe}, which you can use to download everything else. (You
+will need to pick a mirror site; @samp{mirrors.rcn.net} is probably the
+best.) You should go ahead and install everything -- you'll get various
+ancillary libraries that XEmacs needs or likes, e.g. XPM, PNG, JPEG,
+TIFF, etc.
-Again, it is described in @file{nt/README} in some detail. Basically, you
-need to get X11 libraries from ftp.x.org, and compile them. If the
-precompiled versions are available somewhere, I don't know of it.
+If you want to compile under X, you will also need the X libraries; see
+@ref{Q6.1.6}.
+If you want to compile without X, you will need the @file{xpm-nox}
+library, which must be specifically selected in the Cygwin netinstaller;
+it is not selected by default. The package has had various names.
+Currently it is called @file{cygXpm-noX4.dll}.
-@node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
-@unnumberedsubsec Q6.1.5: How do I compile for Cygnus' Cygwin?
+
+@node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
+@unnumberedsubsec Q6.1.4: How do I compile under Cygwin?
Similar as on Unix; use the usual `configure' and `make' process.
Some problems to watch out for:
@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.)
+CYGWIN needs to be set to tty for process support to work, e.g. CYGWIN=tty;
@item
picking up some other grep or other UNIX-like tools can kill configure;
number;
@item
-The Cygwin version doesn't understand @file{//machine/path} type paths so you
-will need to manually mount a directory of this form under a unix style
-directory for a build to work on the directory.
+(Unconfirmed) The Cygwin version doesn't understand
+@file{//machine/path} type paths so you will need to manually mount a
+directory of this form under a unix style directory for a build to work
+on the directory;
-@end itemize
+@item
+If you're building @strong{WITHOUT} X11, don't forget to change symlinks
+@file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
+the non-X versions of these libraries. By default they point to the X
+versions. So:
-@node Q6.1.6, Q6.2.1, Q6.1.5, MS Windows
-@unnumberedsubsec Q6.1.6: What do I need for Cygwin?
+@example
+/usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
+/usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
+@end example
-You can find the Cygwin tools and compiler at:
+(This advice may now be obsolete because of the availability of the
+cygXpm-noX4.dll package from Cygwin. Send confirmation to
+@email{faq@@xemacs.org}.)
-@uref{http://sourceware.cygnus.com/cygwin/}
+@item
+Other problems are listed in the @file{PROBLEMS} file, in the top-level
+directory of the XEmacs sources.
-You will need version b19 or later.
-The latest current version is 1.1.1.
-Other common versions you will see are b20.1.
+@end itemize
-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/}
+@node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
+@unnumberedsubsec Q6.1.5: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-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.
+Similar to the method for Unix. Things to remember:
-@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.}
+@itemize @bullet
+@item
+Specify the target host on the command line for @file{./configure}, e.g.
+@samp{./configure i586-pc-mingw32}.
-You will also need the X libraries. You can get them on the XEmacs FTP
-site at
+@item
+Be sure that your build directory is mounted such that it has the
+same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
+path (@file{c:\build\xemacs}).
-@uref{ftp://ftp.xemacs.org/pub/xemacs/aux/cygwin/}
+@item
+Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
+@file{compface}, etc.
-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.)
+@item
+Specify the target location of the extra libs on the command line
+to @file{configure}, e.g.
+@samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
+@end itemize
-(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.
+@node Q6.1.6, Q6.1.7, Q6.1.5, MS Windows
+@unnumberedsubsec Q6.1.6: I decided to run with X. Where do I get an X server?
-Please see @uref{http://www.xemacs.freeserve.co.uk/} (Andy Piper's home
-page) for more information.
+As of May 2001, we are recommending that you use the port of XFree86 to
+Cygwin. This has recently stabilized, and will undoubtedly soon make
+most other MS Windows X servers obsolete. It is what the Windows
+developers use to test the MS Windows X support.
-BTW There are also libraries at
-@iftex
-@*
-@end iftex
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}, but
-these are not b19 compatible, and may in fact be native-compiled.
+To install, go to @uref{http://xfree86.cygwin.com/}. There is a
+detailed description on that site of exactly how to install it. This
+installation also provides the libraries, include files, and other stuff
+needed for development; a large collection of internationalized fonts;
+the standard X utilities (xterm, twm, etc.) -- in a word, the works.
+NOTE: As of late May 2001, there is a bug in the file
+@file{startxwin.bat}, used to start X Windows. It passes the option
+@samp{-engine -4} to the X server, which is bogus -- you need to edit
+the file and change it to @samp{-engine 4}.
-@node Q6.2.1, Q6.2.2, Q6.1.6, MS Windows
-@unnumberedsec 6.2: Customization and User Interface
-@unnumberedsubsec Q6.2.1: How will the port cope with differences in the Windows user interface?
-XEmacs (and Emacs in general) UI is pretty
-different from what is expected of a typical MS Windows program. How will
-the MS Windows port cope with it?
+@node Q6.1.7, Q6.2.1, Q6.1.6, MS Windows
+@unnumberedsubsec Q6.1.7: How do I compile with X support?
-Fortunately, Emacs is also one of the most configurable editor beasts
-in the world. The MS Windows "look and feel" (mark via shift-arrow,
-self-inserting deletes region, etc.) can be easily configured via
-various packages distributed with XEmacs. The `pending-delete'
-package is an example of such a utility.
+To compile under Cygwin, all you need to do is install XFree86
+(@pxref{Q6.1.6}). Once installed, @file{configure} should automatically
+find the X libraries and compile with X support.
-In future versions, some of these packages might be turned on by
+As noted above, the non-Cygwin X support is basically orphaned, and
+probably won't work. But if it want to try, it's described in
+@file{nt/README} in some detail. Basically, you need to get X11
+libraries from ftp.x.org, and compile them. If the precompiled versions
+are available somewhere, we don't know of it.
+
+
+@node Q6.2.1, Q6.2.2, Q6.1.7, MS Windows
+@unnumberedsec 6.2: Customization and User Interface
+@unnumberedsubsec Q6.2.1: How does the port cope with differences in the Windows user interface?
+
+The XEmacs (and Emacs in general) user interface is pretty different
+from what is expected of a typical MS Windows program. How does the MS
+Windows port cope with it?
+
+As a general rule, we follow native MS Windows conventions as much as
+possible. 21.4 is a fairly complete Windows application, supporting
+native printing, system file dialog boxes, tool tips, etc. In cases
+where there's a clear UI conflict, we currently use normal Unix XEmacs
+behavior by default, but make sure the MS Windows "look and feel" (mark
+via shift-arrow, self-inserting deletes region, Alt selects menu items,
+etc.) is easily configurable (respectively: using the variable
+@code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
+the default in these versions], or the @file{pc-select} package; using
+the @file{pending-del} package; and setting the variable
+@code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
+In fact, if you use the sample @file{init.el} file as your init file,
+you will get all these behaviors automatically turned on.
+
+In future versions, some of these features might be turned on by
default in the MS Windows environment.
@node Q6.2.2, Q6.2.3, Q6.2.1, MS Windows
@unnumberedsubsec Q6.2.2: How do I change fonts in XEmacs on MS Windows?
-In 21.2.*, use the font menu. In 21.1.*, you can change font
-manually. For example:
+In 21.4 and above, you can use the "Options" menu to change the font.
+You can also do it in your init file, e.g. like this:
@display
(set-face-font 'default "Lucida Console:Regular:10")
@end display
-@node Q6.2.3, Q6.3.1, Q6.2.2, MS Windows
+@node Q6.2.3, Q6.2.4, Q6.2.2, MS Windows
@unnumberedsubsec Q6.2.3: Where do I put my @file{init.el}/@file{.emacs} file?
@file{init.el} is the name of the init file starting with 21.4, and is
located in the subdirectory @file{.xemacs/} of your home directory. In
prior versions, the init file is called @file{.emacs} and is located in
your home directory. Your home directory under Windows is determined by
-the HOME environment variable. If this is not set, it defaults to
-`C:\'.
+the @samp{HOME} environment variable. If this is not set, it defaults to
+@samp{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-*?
+To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
+select @samp{Control Panel->System->Advanced->Environment Variables...}
+under Windows NT/2000.
+
+
+@node Q6.2.4, Q6.2.5, Q6.2.3, MS Windows
+@unnumberedsubsec Q6.2.4: How do I get Windows Explorer to associate a file type with XEmacs?
+
+@unnumberedsubsubsec Associating a new file type with XEmacs.
+
+In Explorer select @samp{View/Options/File Types}, press @samp{[New
+Type...]} and fill in the dialog box, e.g.:
+
+@example
+ Description of type: Emacs Lisp source
+ Associated extension: el
+ Content Type (MIME): text/plain
+@end example
+
+then press @samp{[New...]} and fill in the @samp{Action} dialog box as
+follows:
+
+@example
+ Action:
+ Open
+
+ Application used to perform action:
+ D:\Full\path\for\xemacs.exe "%1"
+
+ [x] Use DDE
+
+ DDE Message:
+ open("%1")
+
+ Application:
+ <leave blank>
+
+ DDE Application Not Running:
+ <leave blank>
+
+ Topic:
+ <leave blank>
+@end example
+
+@unnumberedsubsubsec Associating an existing file type with XEmacs.
+
+In Explorer select @samp{View/Options/File Types}. Click on the file
+type in the list and press @samp{[Edit...]}. If the file type already
+has an @samp{Open} action, double click on it and fill in the
+@samp{Action} dialog box as described above; otherwise create a new
+action.
+
+If the file type has more than one action listed, you probably want to
+make the @samp{Open} action that you just edited the default by clicking on
+it and pressing @samp{Set Default}.
-In his flavor of Emacs 20, Richard Stallman has renamed all the win32-*
-symbols to w32-*. Will XEmacs do the same?
+Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
+using @samp{Control Panel->Folder Options->File Types}.
-We consider such a move counter-productive, thus we will not use the
-`w32' prefix. However, we do recognize that Win32 name is little more
-than a marketing buzzword (will it be Win64 in the next release?), so
-we decided not to use it. Using `windows-' would be wrong because the
-term is too generic, which is why we settled on a compromise
-`mswindows' term.
-Thus all the XEmacs variables and functions directly related to Win32
-are prefixed `mswindows-'. The user-variables shared with NT Emacs
-will be provided as compatibility aliases.
+@node Q6.2.5, Q6.3.1, Q6.2.4, MS Windows
+@unnumberedsubsec Q6.2.5: Is it possible to print from XEmacs?
-Architectural note: We believe that there should be a very small number
-of window-systems-specific variables, and we provide generic interfaces
-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.
+As of 21.4, printing works on Windows, using simply @samp{File->Print},
+and can be configured with @samp{File->Page Setup}.
+
+Prior to 21.4, there is no built-in support, but there are some clever
+hacks out there. If you know how, please let us know and we'll put it
+here.
+
+
+@node Q6.3.1, Q6.3.2, Q6.2.5, MS Windows
+@unnumberedsec 6.3: Miscellaneous
+@unnumberedsubsec Q6.3.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
+
+In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
+symbols to @samp{w32-*}. Does XEmacs do the same?
+
+We consider such a move counter-productive, thus we do not use the
+@samp{w32} prefix. (His rather questionable justification was that he
+did not consider Windows to be a "winning" platform.) However, the name
+@samp{Win32} is not particularly descriptive outside the Windows world,
+and using just @samp{windows-} would be too generic. So we chose a
+compromise, the prefix @samp{mswindows-} for Windows-related variables
+and functions.
+
+Thus all the XEmacs variables and functions directly related to either
+the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
+couple of debugging variables, prefixed @samp{debug-mswindows-}). From
+an architectural perspective, however, we believe that this is mostly a
+non-issue because there should be a very small number of
+window-systems-specific variables anyway. Whenever possible, we try to
+provide generic interfaces that apply to all window systems.
+
+@c not true:
+@c The user variables
+@c that share functionality with existing NT Emacs variables are be named
+@c with our convention, but we provide the GNU Emacs names as
+@c compatibility aliases.
@node Q6.3.2, Q6.3.3, Q6.3.1, MS Windows
@itemize @bullet
@item
-Win-Emacs
-
-@itemize @minus
-
-@item
-Win-Emacs is a port of Lucid Emacs 19.6 to MS Windows using X
-compatibility libraries. Win-Emacs has been written by Ben Wing. The
-MS Windows code has not made it back to Lucid Emacs, which left Win-Emacs
-pretty much dead for our purposes. Win-Emacs used to be available at
-Pearlsoft, but not anymore, since Pearlsoft went out of business.
-@end itemize
-
-@item
-GNU Emacs for DOS
+XEmacs
@itemize @minus
@item
-GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
-port of Gcc). Such an Emacs is heavily underfeatured, because it does
-not supports long file names, lacks proper subprocesses support, and
-is far too big compared to typical DOS editors.
-@end itemize
+Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
+in such a way to allow clean support of multiple window systems. At
+this time the TTY support was added, making X and TTY the first two
+"window systems" supported by XEmacs. The 19.12 design is the basis for
+the current native MS Windows code.
@item
-GNU Emacs compiled with Win32
-
-@itemize @minus
+Some time during 1997, David Hobley (soon joined by Marc Paquette)
+imported some of the NT-specific portions of GNU Emacs, making XEmacs
+with X support compile under Windows NT, and creating the "X" port.
@item
-Starting with version 19.30, it has been possible to compile GNU Emacs
-under MS Windows using the DJGPP compiler and X libraries. The result
-is is very similar to GNU Emacs compiled under MS DOS, only it
-supports longer file names, etc. This "port" is similar to the "X"
-flavor of XEmacs on MS Windows.
+Several months later, Jonathan Harris sent out initial patches to use
+the Win32 API, thus creating the native port. Since then, various
+people have contributed, including Kirill M. Katsnelson (contributed
+support for menubars, subprocesses and network, as well as loads of
+other code), Andy Piper (ported XEmacs to Cygwin environment,
+contributed Windows unexec, Windows-specific glyphs and toolbars code,
+and more), Ben Wing (loads of improvements; primary MS Windows developer
+since 2000), Jeff Sparkes (contributed scrollbars support) and many
+others.
@end itemize
@item
@itemize @minus
@item
-NT Emacs is a version of GNU Emacs modified to compile and run under
-MS MS Windows 95 and NT using the native Win32 API. As such, it is close
-in spirit to the XEmacs "native" port.
+NT Emacs is a version of GNU Emacs modified to compile and run under MS
+Windows 95 and NT using the native Win32 API. As such, it is close in
+spirit to the XEmacs "native" port.
@item
NT Emacs has been written by Geoff Voelker, and more information can be
@iftex
@*
@end iftex
-@uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
-
+@uref{http://www.gnu.org/software/emacs/windows/ntemacs.html}.
@end itemize
@item
-XEmacs
+Win-Emacs
@itemize @minus
@item
-Beginning with XEmacs 19.12, XEmacs' architecture has been redesigned
-in such a way to allow clean support of multiple window systems. At
-this time the TTY support was added, making X and TTY the first two
-"window systems" XEmacs supported. The 19.12 design is the basis for
-the current native MS Windows code.
+Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
+compatibility libraries. Win-Emacs was written by Ben Wing. The MS
+Windows code never made it back to Lucid Emacs, and its creator (Pearl
+Software) has long since gone out of business.
+@end itemize
@item
-Some time during 1997, David Hobley (soon joined by Marc Paquette)
-imported some of the NT-specific portions of GNU Emacs, making XEmacs
-with X support compile under Windows NT, and creating the "X" port.
+GNU Emacs for DOS
-@item
-Several months later, Jonathan Harris sent out initial patches to use
-the Win32 API, thus creating the native port. Since then, various
-people have contributed, including Kirill M. Katsnelson (contributed
-support for menubars, subprocesses and network, as well as loads of
-other code), Andy Piper (ported XEmacs to Cygwin environment,
-contributed Windows unexec, Windows-specific glyphs and toolbars code,
-and more), Jeff Sparkes (contributed scrollbars support) and many
-others.
+@itemize @minus
+@item
+GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
+port of GCC). Such an Emacs is heavily underfeatured, because it does
+not support long file names, lacks proper subprocesses support, and
+is far too big compared with typical DOS editors.
@end itemize
+@item
+GNU Emacs compiled with Win32
+
+@itemize @minus
+
+@item
+Starting with version 19.30, it has been possible to compile GNU Emacs
+under MS Windows using the DJGPP compiler and X libraries. The result
+is very similar to GNU Emacs compiled under MS DOS, only it works
+somewhat better because it runs in 32-bit mode, makes use of all the
+system memory, supports long file names, etc.
@end itemize
+@end itemize
-@node Q6.3.3, Q6.4.1, Q6.3.2, MS Windows
-@unnumberedsubsec Q6.3.3: What is the porting team doing at the moment?
-(as of March 2001)
+@node Q6.3.3, Q6.3.4, Q6.3.2, MS Windows
+@unnumberedsubsec Q6.3.3: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
+
+Yes.
+
+The console was there because @file{temacs} (and in turn, @file{xemacs})
+was a console application, and Windows typically creates a new
+console for a console process unless the creating process requests that
+one isn't created. This used to be fixed with @file{runemacs}, a small
+Windows application that existed merely to start @file{xemacs}, stating
+that it didn't want a console.
+
+XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
+application. The explanation of what that means is included for
+educational value.
+
+When building an application to be run in a Win32 environment, you must
+state which sub-system it is to run in. Valid subsystems include
+"console" and "gui". The subsystem you use affects the run time
+libraries linked into your application, the start up function that is
+run before control is handed over to your application, the entry point
+to your program, and how Windows normally invokes your program. (Console
+programs automatically get a console created for them at startup if
+their stdin/stdout don't point anywhere useful, which is the case when
+run from the GUI. This is a stupid design, of course -- instead, the
+console should get created only when the first I/O actually occurs!
+GUI programs have an equally stupid design: When called from
+@file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
+point nowhere useful, even though the command shell has its own
+stdin/stdout. It's as if someone who had learned a bit about stdio but
+had no actual knowledge of interprocess communication designed the
+scheme; unfortunately, the whole process-communication aspect of the
+Win32 API is equally badly designed.) For example, the entry point for a
+console app is "main" (which is what you'd expect for a C/C++ program),
+but the entry point for a "gui" app is "WinMain". This confuses and
+annoys a lot of programmers who've grown up on Unix systems, where the
+kernel doesn't really care whether your application is a gui program or
+not.
+
+For reasons not altogether clear, and are lost in the mists of time and
+tradition, XEmacs on Win32 started out as a console application, and
+therefore a console was automatically created for it. (It may have been
+made a console application partly because a console is needed in some
+circumstances, especially under Win95, to interrupt, terminate, or send
+signals to a child process, and because of the bogosity mentioned above
+with GUI programs and the standard command shell. Currently, XEmacs
+just creates and immediately hides a console when necessary, and
+works around the "no useful stdio" problem by creating its own console
+window as necessary to display messages in.)
+
+
+@node Q6.3.4, Q6.4.1, Q6.3.3, MS Windows
+@unnumberedsubsec Q6.3.4: What is the porting team doing at the moment?
+
+(as of June 2001)
The porting team is continuing work on the MS Windows-specific code.
Major projects are the development of Mule (internationalization)
support for dialog boxes, buttons, edit fields, and similar UI
elements).
-@node Q6.4.1, ,Q6.3.3, MS Windows
+
+
+@node Q6.4.1, Q6.4.2, Q6.3.4, MS Windows
@unnumberedsec 6.3: Troubleshooting
-@unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)
+@unnumberedsubsec Q6.4.1 XEmacs won't start on Windows.
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
+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
+problem for most people. 21.4 implements "portable dumping", which
+eliminates the problem altogether. We recommend you use the 21.4
+binaries, but you can use the 21.1 binaries if you are very paranoid
+about stability. @xref{Q6.0.3}.
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/}.
+@node Q6.4.2, Q6.4.3, Q6.4.1, MS Windows
+@unnumberedsubsec Q6.4.2 Why do I get a blank toolbar on Windows 95?
-21.2 implements "portable dumping" which will eliminate the problem
-altogether. You might have better luck with the 21.2 beta binary,
-available at
+You need at least version 4.71 of the system file @file{comctl32.dll}.
+The updated version is supplied with Internet Explorer 4 and later but if
+you are avoiding IE you can also download it from the Microsoft web
+site. Go into support and search for @file{comctl32.dll}. The download
+is a self-installing executable.
-@uref{ftp://ftp.xemacs.org/pub/xemacs/beta/binaries/}.
+@node Q6.4.3, , Q6.4.2, MS Windows
+@unnumberedsubsec Q6.4.3 XEmacs complains "No such file or directory, diff"
+or "ispell" or other commands that seem related to whatever you just
+tried to do (M-x ediff or M-$, for example).
-@node Current Events, , MS Windows, Top
+There are a large number of common (in the sense that "everyone has
+these, they really do") Unix utilities that are not provided with
+XEmacs. The GNU Project's implementations are available for Windows in
+the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
+provides a complete Unix emulation environment (and thus makes ports of
+Unix utilities nearly trivial). Another implementation is that from
+MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
+please let us know!
+
+
+
+@node Current Events, Legacy Versions, MS Windows, Top
@unnumbered 7 What the Future Holds
This is part 7 of the XEmacs Frequently Asked Questions list. This
-section will change monthly, and contains any interesting items that have
-transpired over the previous month. If you are reading this from the
-XEmacs distribution, please see the version on the Web or archived at the
-various FAQ FTP sites, as this file is surely out of date.
+section will change frequently, and (in theory) should contain any
+interesting items that have transpired recently. (But in practice it's
+not getting updated like this.)
+
+This section also contains descriptions of the new features in all the
+recent releases of XEmacs. For the most part, the information below is
+a synopsis of the more complete information that can be found in the
+file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
+You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
+menu.
+
+Information on older versions of XEmacs can be find in @file{ONEWS} in
+the same directory, or @file{OONEWS} for really old versions.
+
@menu
-* Q7.0.1:: What is new in 20.2?
-* Q7.0.2:: What is new in 20.3?
-* Q7.0.3:: What is new in 20.4?
-* Q7.0.4:: Procedural changes in XEmacs development.
+* Q7.0.1:: What new features will be in XEmacs soon?
+* Q7.0.2:: What's new in XEmacs 21.4?
+* Q7.0.3:: What's new in XEmacs 21.1?
+* Q7.0.4:: What's new in XEmacs 20.4?
+* Q7.0.5:: What's new in XEmacs 20.3?
+* Q7.0.6:: What's new in XEmacs 20.2?
@end menu
@node Q7.0.1, Q7.0.2, Current Events, Current Events
@unnumberedsec 7.0: Changes
-@unnumberedsubsec Q7.0.1: What is new in 20.2?
+@unnumberedsubsec Q7.0.1: What new features will be in XEmacs soon?
-The biggest changes in 20.2 include integration of EFS (the next
-generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
-major mode for editing Tex and LaTeX, and a lot of other stuff). Many
-bugs from 20.0 have been fixed for this release. 20.2 also contains a
-new system for customizing XEmacs options, invoked via @kbd{M-x
-customize}.
-
-XEmacs 20.2 is the development release (20.0 was beta), and is no longer
-considered unstable.
+Not yet written.
@node Q7.0.2, Q7.0.3, Q7.0.1, Current Events
-@unnumberedsubsec Q7.0.2: What is new in 20.3?
+@unnumberedsubsec Q7.0.2: What's new in XEmacs 21.4?
+
+21.4 was the "stable" version of the 21.2 series, which was considered
+"experimental" throughout its life; thus there were no "official"
+releases at all. In essence, XEmacs is now following the "alternating"
+scheme of Linux, where at any point there are at least two different
+development branches, one "stable" and one "experimental". Periodic
+releases happen in both branches, but those in the experimental branch
+are not tested as well, and there's no guarantee they will work at all.
+The experiemental branch is open to any and all code that's acceptable
+to the developers; the stable branch, however, is in general limited
+only to bug fixes, and all contributions are carefully reviewed to make
+sure they will increase and not decrease stability.
+
+21.3 never existed at all; it was decided to follow the Linux scheme
+exactly, where odd-numbered series are experimental and even-numbered
+ones stable.
+
+The following lists summarizes the essential changes made in this
+version. For a fuller list, see the @file{NEWS} in the @file{etc}
+directory of the XEmacs distribution, or use @kbd{C-h n} or the
+@samp{Help} menu to view this file inside of XEmacs.
+
+@unnumberedsubsubsec User-visible changes in XEmacs 21.4
+
+@itemize @bullet
+
+@item
+The delete key now deletes forward by default.
+@item
+Shifted motion keys now select text by default.
+@item
+You can now build XEmacs with support for GTK+ widget set.
+@item
+~/.xemacs/init.el is now the preferred location for the init
+file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
+file will move to ~/.xemacs/custom.el.)
+@item
+Much-improved sample init.el, showing how to use many useful features.
+@item
+XEmacs support for menu accelerators has been much improved.
+@item
+Default menubar improvements. (Default menubar has many new commands and
+better organization. The font-menu is now available under MS Windows.)
+@item
+Dialog box improvements, including a real file dialog box. (XEmacs now has a proper file dialog box under MS Windows (and GTK)! The old clunky file dialog box is improved. Keyboard traversal now works correctly in MS Windows dialog boxes. There is a Search dialog box available from Edit->Find...)
+@item
+New buffer tabs.
+@item
+There is a new MS Windows installer, netinstall, ported from Cygwin.
+@item
+The subprocess quote-handling mechanism under Windows is much improved.
+@item
+Printing support now available under MS Windows.
+@item
+Selection improvements. (Kill and yank now interact with the clipboard under Windows. MS Windows support for selection is now much more robust. Motif selection support is now more correct (but slower).)
+@item
+Mail spool locking now works correctly.
+@item
+International support changes. (The default coding-priority-list is now
+safer. International keysyms are now supported under X. MS Windows
+1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
+Ethiopic now supported. Proper support for words in Latin 3 and Latin
+4.)
+@item
+Help buffers contain hyperlinks, and other changes.
+@item
+The modeline's text is now scrollable.
+@item
+The mouse wheel under MS Windows now functions correctly.
+@item
+Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
+@item
+Rectangle functions rewritten to avoid inserting extra spaces.
+@item
+New command `kill-entire-line' that always kills the entire line.
+@item
+Default values correctly stored in minibuffer histories.
+@item
+You can now create "indirect buffers", like in GNU Emacs.
+@item
+Pixel-based scrolling has been implemented.
+@item
+Operation progress can be displayed using graphical widgets.
+@item
+User names following a tilde can now be completed at file name prompts.
+@item
+XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
+@item
+X-Face support is now available under MS Windows.
+@item
+The PostgreSQL Relational Database Management System is now supported.
+@item
+Indentation no longer indents comments that begin at column zero.
+@item
+Face and variable settings can have comments in Customize.
+@item
+New locations for early package hierarchies.
+@item
+The `auto-save' library has been greatly improved.
+@item
+New variable `mswindows-alt-by-itself-activates-menu'.
+@item
+Other init-file-related changes. (Init file in your home directory may be called `.emacs.el'. New command-line switches -user-init-file and -user-init-directory.)
+@item
+Etags changes. See @file{NEWS} for full details.
+@end itemize
+
+@unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
+
+Not yet written.
+
+@c APA: Texi2html produces invalid HTML from an empty list of bullets!
+@c Please uncomment following list when it does contain bullets.
+@c @itemize @bullet
+@c @end itemize
+
+@node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
+@unnumberedsubsec Q7.0.3: What's new in XEmacs 21.1?
+
+21.1 was the "stable" version of "experimental" 21.0 series.
+@xref{Q7.0.2}.
+
+The following lists summarizes the essential changes made in this
+version. For a fuller list, see the @file{NEWS} in the @file{etc}
+directory of the XEmacs distribution, or use @kbd{C-h n} or the
+@samp{Help} menu to view this file inside of XEmacs.
+
+@unnumberedsubsubsec User-visible changes in XEmacs 21.1
+
+@itemize @bullet
+
+@item
+XEmacs is now supported under Microsoft Windows 95/98 and Windows NT
+operating systems. To discuss Windows-specific issues, subscribe to the
+mailing list at @email{xemacs-nt-request@@xemacs.org}.
+
+@item
+XEmacs has been unbundled into constituent installable packages.
+
+@item
+@strong{Other notable changes}: The @samp{Options} menu has been ported to
+Custom; XEmacs now is able to choose X visuals and use private
+colormaps; You can drag the vertical divider of "horizontally"
+(side-by-side) split windows.
+
+@item
+@strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
+integers and 32-bit pointers (previously, it was 28-bit integers and
+pointers); XEmacs can be built with LDAP support; @file{dir} files can be
+removed in the Info subsystem, and will be regenerated on-the-fly.
+
+@item
+@strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
+
+@item
+@strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
+@file{gnuclient}. See @file{NEWS} for full details.
+
+@item
+@strong{New commands, variables and functions}:
+@code{center-to-window-line} (like @code{recenter} but doesn't force a
+redisplay); variable @code{user-full-name} (customize what your full
+name looks like in mail); @kbd{M-x customize-changed-options} (customize
+options whose default values changes because you upgraded your XEmacs);
+@kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
+new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
+doesn't delete the char searched for); commands to store, retrieve and
+increment numbers in registers, useful for macros.
+
+@item
+@strong{Changes to commands, variables, and functions}: @kbd{M-x
+query-replace} and friends operate only on the region when it's active;
+@code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
+searches exact tag matches before inexact ones; function
+@code{user-full-name} with no arguments returns the var
+@code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
+the result in the current buffer.
+
+@item
+@strong{Other changes}: Under X, new application class @samp{XEmacs};
+byte-compilation of user-specs now works.
+
+@item
+@strong{XEmacs/Mule (internationalization) changes}: Mule support now
+works on TTY's; Egg/SJ3 input method now officially supported (Quail and
+Egg/Skk already available through LEIM since 20.3); localized Japanese
+menubars if XEmacs is built with the right support.
+
+@end itemize
+
+@unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
+
+@itemize @bullet
+
+@item
+@strong{Specifier changes}: The window locale now has a higher
+precedence than the buffer locale when instantiating; new macro
+@code{let-specifier}; new specifiers
+@code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
+@code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
+@code{vertical-divider-always-visible-p},
+@code{vertical-divider-shadow-thickness},
+@code{vertical-divider-line-width}, @code{vertical-divider-spacing};
+specifiers and symbols whose value is a specifier allowed as modeline
+specifications.
+
+@item
+@strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
+prevents any attempt to permanently change the selected frame; new
+function @code{focus-frame} sets the window system focus a frame; new
+special forms @code{save-selected-frame} and @code{with-selected-frame}.
+
+@item
+@strong{Window function changes}: @code{select-window} now has optional
+argument @var{NORECORD} to inhibit recording a buffer change;
+@code{vertical-motion} now correctly handles optional @var{WINDOW}
+argument and has new optional argument @var{PIXELS}, to have the
+returned values be in pixels; new function
+@code{vertical-motion-pixels}; new functions
+@code{window-text-area-pixel-@{width,height,edges@}}; new functions
+@code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
+function @code{window-displayed-text-pixel-height}.
+
+@item
+@strong{Other function changes}: Arithmetic comparison functions
+@code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
+arguments; hashtables now have a consistent read/print syntax; keyword
+symbols cannot be set to a value other than themselves; @code{concat} no
+longer accepts integer arguments; new function @code{string}, like
+@code{list}, @code{vector}, etc.; new function @code{temp-directory}
+(OS-independent way to get a temp directory); @code{load-average} has
+optional argument @var{USE-FLOATS}; @code{make-event} implemented
+completely; new function @code{function-interactive} (returns a
+function's interactive spec); new functions @code{lmessage},
+@code{lwarn} (printf-like versions of @code{display-wessage},
+@code{display-warning}); new keyword @code{:version} to
+@code{defcustom}.
+
+@item
+@strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
+available, it will be used (better performance on libc6 Linux systems);
+tracking line-numbers in modeline is now efficient; profiling records a
+call-count of all called functions, retrievable through
+@code{profile-call-count-results}.
+
+@item
+@strong{Startup and path searching}: code to assemble paths at startup
+rewritten for new package system; new function @code{split-path} (splits
+by @code{path-separator}); @code{Info-default-directory-list} obsolete,
+use @code{Info-directory-list} instead; site-lisp is deprecated and no
+longer on the load-path by default.
+
+@end itemize
+
+@node Q7.0.4, Q7.0.5, Q7.0.3, Current Events
+@unnumberedsubsec Q7.0.4: What's new in XEmacs 20.4?
+
+XEmacs 20.4 is a bugfix release with no user-visible changes.
+@c Filled in from NEWS file of 20.5-b33
+
+@node Q7.0.5, Q7.0.6, Q7.0.4, Current Events
+@unnumberedsubsec Q7.0.5: What's new in XEmacs 20.3?
XEmacs 20.3 was released in November 1997. It contains many bugfixes,
and a number of new features, including Autoconf 2 based configuration,
XEmacs 20.3 is the first non-beta v20 release, and will be the
basis for all further development.
-@node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
-@unnumberedsubsec Q7.0.3: What's new in XEmacs 20.4?
+@node Q7.0.6, , Q7.0.5, Current Events
+@unnumberedsubsec Q7.0.6: What's new in XEmacs 20.2?
-XEmacs 20.4 is a bugfix release with no user-visible changes.
-@c Filled in from NEWS file of 20.5-b33
+The biggest changes in 20.2 include integration of EFS (the next
+generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
+major mode for editing Tex and LaTeX, and a lot of other stuff). Many
+bugs from 20.0 have been fixed for this release. 20.2 also contains a
+new system for customizing XEmacs options, invoked via @kbd{M-x
+customize}.
+XEmacs 20.2 is the development release (20.0 was beta), and is no longer
+considered unstable.
-@node Q7.0.4, , Q7.0.3, Current Events
-@unnumberedsubsec Q7.0.4: Procedural changes in XEmacs development.
+For older news, see the file @file{ONEWS} in the @file{etc} directory of
+the XEmacs distribution.
-@enumerate
-@item
-Discussion about the development of XEmacs occurs on the xemacs-beta
-mailing list. Subscriptions to this list will now be fully automated
-instead of being handled by hand. Send a mail message to
-@email{xemacs-beta-request@@xemacs.org} with @samp{subscribe} as the
-BODY of the message to join the list. Please note this is a developers
-mailing list for people who have an active interest in the development
-process.
-The discussion of NT XEmacs development is taking place on a separate
-mailing list. Send mail to
-@iftex
-@*
-@end iftex
-@email{xemacs-nt-request@@xemacs.org} to
-subscribe.
-@item
-Due to the long development cycle in between releases, it has been
-decided that intermediate versions will be made available in source only
-form for the truly interested.
+@node Legacy Versions, , Current Events, Top
+@unnumbered 8 New information about old XEmacsen
-XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
-the collected bugfixes.
+This is part 8 of the XEmacs Frequently Asked Questions list. It will
+occasionally be updated to reflect new information about versions which
+are no longer being revised by the XEmacs Project. The primary purpose
+is advice on compatibility of older XEmacsen with new packages and
+updated versions of packages, but bug fixes (which will not be applied
+to released XEmacsen, but users can apply themselves) are also accepted.
+
+
+@menu
+* Q8.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
+@end menu
+
+@node Q8.0.1, , , Legacy Versions
+@unnumberedsubsec Q8.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
+
+@email{eeide@@cs.utah.edu, Eric Eide} wrote:
+
+@quotation
+Previously I wrote:
+
+ Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
+ Eric> any smileys :-(.
+
+After a bit of sleuthing, I discovered the essence of the problem.
+For me, the form:
+
+@lisp
+ (with-temp-buffer
+ (insert-file-contents "foo.xpm")
+ (buffer-string))
+@end lisp
+
+returns the empty string. This is because something somewhere
+replaces the XPM data with a glyph --- I haven't figured out where
+this occurs.
+@end quotation
+
+@email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
+
+@quotation
+Do this:
+
+@lisp
+ (setq format-alist nil)
+@end lisp
+
+The image-mode stuff is gone from format-alist in the 21.4
+branch, praise be.
+@end quotation
-@item
-As of December 1996, @email{steve@@xemacs.org, Steve Baur} has become
-the lead maintainer of XEmacs.
-@end enumerate
@bye
projects / chise / xemacs-chise.git.1 / blobdiff