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

comparison man/xemacs-faq.texi @ 593:5fd7ba8b56e7

[xemacs-hg @ 2001-05-31 12:45:27 by ben] xemacs-faq.texi: Major rewrite. Update all MS Windows info to current. Redo section 6.1 almost completely. Incorporate sections 1 and 2 of Hrvoje's FAQ. etags.el: Fix infloop when going up to the root. s\cygwin32.h: Don't unilaterally include ntplay, but only when we're compiling with native sound (look in configure now). event-msw.c: Fix yet more problems with C-g handling. Implement debug-mswindows-events. event-stream.c, events.h, signal.c, sysdep.h: Rearrange the signal-handling code to eliminate the former spaghetti logic paths in it. Document clearly what "low-level" and "high-level" timeouts are. Rename some functions with unclear names (e.g. "...alarm...") to names that reflect what they actually do (e.g. "...async_timeout..."). Fix numerous bugs discovered in the process. console-x.h, event-Xt.c, event-msw.c, frame-x.c: Hopefully make XEmacs properly maintain the "iconified" state on frames at all times. This should fix the "can't delete a frame with C-x 5 0 when there's another iconified frame out there" bug. Put a notice in of further changes that should probably be made to clean up the frame-visibility support. (especially directed at Jan Vroonhof) lisp.h, miscplay.c: Rename SBufbyte to CBufbyte to avoid a misleading name. Eliminate UChar, which is not used anywhere and contributes no semantic info. Add a comment about the documentation-only properties of the char/unsigned char typedefs. Add SChar_Binary as an explicitly `signed' version of Char_Binary and put back the `signed' declarations in miscplay.c. alloc.c: Use char typedefs. console-msw.c, device-msw.c, dialog-msw.c, editfns.c, fileio.c, glyphs-eimage.c, menubar-msw.c, ntplay.c, objects-msw.c, realpath.c, redisplay-msw.c, select-msw.c, syswindows.h, win32.c: Eliminate numerous C++ errors. frame-msw.c: Eliminate numerous C++ errors and Mule-ize. glyphs-msw.c: Eliminate numerous C++ errors and use char typedefs. configure.in: Fix problems detecting both native and Linux sound on Cygwin when compiled with --with-msw=no. Rearrange file-coding handling a bit to avoid warning when compiling with Mule. configure.in, configure.usage, INSTALL: Document XEMACS_CC and corresponding compiler option --xemacs-compiler. Explain how to build xemacs using a C++ compiler.

author	ben
date	Thu, 31 May 2001 12:45:41 +0000
parents	183866b06e0b
children	38db05db9cb5

comparison

equal deleted inserted replaced

-:4f6ba8f1fb3d
+:5fd7ba8b56e7
 @setchapternewpage off
 @c %**end of header
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/05/24 07:50:53 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/05/31 12:45:30 $
 @sp 1
 @author Tony Rossini <rossini@@biostat.washington.edu>
 @author Ben Wing <ben@@xemacs.org>
 @author Chuck Thompson <cthomp@@xemacs.org>
 @author Steve Baur <steve@@xemacs.org>
 General Info:
 * Q6.0.1::      What is the status of the XEmacs port to Windows?
 * Q6.0.2::      What flavors of MS Windows are supported?
 * Q6.0.3::      Are 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.1::      What compiler/libraries do I need to compile XEmacs?
-* Q6.1.2::      What compiler do I need to compile XEmacs?
+* Q6.1.2::      How do I compile the native port?
-* Q6.1.3::      How do I compile for the native port?
+* Q6.1.3::      What do I need for Cygwin?
-* Q6.1.4::      How do I compile for the X port?
+* Q6.1.4::      How do I compile under Cygwin?
-* Q6.1.5::      How do I compile for Cygnus' Cygwin?
+* Q6.1.5::      How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q6.1.6::      What do I need for Cygwin?
+* 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?
 Miscellaneous:
-* Q6.3.1::      Will XEmacs rename all the win32-* symbols to w32-*?
+* Q6.3.1::      Does XEmacs rename all the win32-* symbols to w32-*?
 * Q6.3.2::      What are the differences between the various MS Windows emacsen?
 * Q6.3.3::      What is the porting team doing at the moment?
 Troubleshooting:
 * Q6.4.1::      XEmacs won't start on Windows. (NEW)
 @end example
 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
-Yes, @xref{MS Windows}.
+Yes, 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 changed
 @code{gdb}.  If you don't have any such debugger available, complain to
 your system administrator.
 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.
 When making a problem report make sure that:
 @enumerate
 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
 @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, @xref{Q2.1.15}.  Try to get both a C and Lisp
+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.
 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
 @node Customization, Subsystems, Installation, Top
 @unnumbered 3 Customization and Options
 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem?  How?
 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
 @unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
 (define-key key-translation-map 'delete 'redirected-delete)
 (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.
 Can the cursor keys scroll the screen a line at a time, rather than the
 @code{delete-key-deletes-forward} to t.  You can also change this with
 Customize. Select from the @code{Options} menu
 @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?
 Yes, with @code{(setq modifier-keys-are-sticky t)}.  This will give the
 (setq zmacs-regions nil)
 @end lisp
 @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
 @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.
 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?
+* 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.1::      What compiler/libraries do I need to compile XEmacs?
-* Q6.1.2::      What compiler do I need to compile XEmacs?
+* Q6.1.2::      How do I compile the native port?
-* Q6.1.3::      How do I compile for the native port?
+* Q6.1.3::      What do I need for Cygwin?
-* Q6.1.4::      How do I compile for the X port?
+* Q6.1.4::      How do I compile under Cygwin?
-* Q6.1.5::      How do I compile for Cygnus' Cygwin?
+* Q6.1.5::      How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
-* Q6.1.6::      What do I need for Cygwin?
+* 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?
 Miscellaneous
-* Q6.3.1::      Will XEmacs rename all the win32-* symbols to w32-*?
+* Q6.3.1::      Does XEmacs rename all the win32-* symbols to w32-*?
 * Q6.3.2::      What are the differences between the various MS Windows emacsen?
 * Q6.3.3::      What is the porting team doing at the moment?
 Troubleshooting:
 * Q6.4.1::      XEmacs won't start on Windows. (NEW)
 @node Q6.0.1, Q6.0.2, MS Windows, MS Windows
 @unnumberedsec 6.0: General Info
 @unnumberedsubsec Q6.0.1: What is the status of the XEmacs port to Windows?
-Is XEmacs really getting ported to MS Windows?  What is the status of the port?
+Is XEmacs really ported to MS Windows?  What is the status of the port?
-Yes, a group of volunteers actively works on making XEmacs code base
+Beginning with release 21.0, XEmacs has worked under MS Windows.  A
-cleanly compile and run on MS Windows operating systems.  The mailing
+group of dedicated developers actively maintains and improves the
-list at @email{xemacs-nt@@xemacs.org} is dedicated to that effort
+Windows-specific portions of the code.  The mailing list at
-(please use the -request address to subscribe).
+@email{xemacs-nt@@xemacs.org} is dedicated to that effort (please use
+the -request address to subscribe). (Despite its name, XEmacs actually
-At this time, XEmacs on MS Windows is stable and full-featured.
+works on all versions of Windows.)
-However, the internationalization (Mule) support does not work --
-although this is being actively worked on.
+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.
 @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
+The list name is misleading, as XEmacs supports and has been compiled on
-98, Windows NT, Windows 2000, Windows ME, Windows XP, and all newer
+Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
-versions of Windows.  The MS Windows-specific code is based on Microsoft
+XP, and all newer versions of Windows.  The MS Windows-specific code is
-Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
+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
+Binaries are available at @uref{http://www.xemacs.org/Download/win32/}
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/win32/} for the native MS
+for the native and Cygwin MS Windows versions of 21.4, and the native
-Windows version.
+version of 21.1.
-@node Q6.0.4, Q6.1.1, Q6.0.3, MS Windows
+The 21.4 binaries use a modified version of the Cygwin installer.  Run
-@unnumberedsubsec Q6.0.4: Can I build XEmacs on MS Windows with support for X or Cygwin?
+the provided @file{setup.exe}, and follow the instructions.
-Yes.  XEmacs can be built in several ways in the MS Windows environment.
+@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, 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
 libraries to build, nor does it require an X server to run.  The native
 port is the most reliable version and provides the best graphical
 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
+The second way to build is the Cygwin port.  It takes advantage of
-and an X server to run.  Internally it uses the Xt event loop and makes
+Cygnus emulation library under Win32.  @xref{Q6.0.6}, for more
-use of X toolkits.  Its look is quite un-Windowsy, and it is not well
+information.
-maintained, but it is being kept around for the time being because it
-has a long history.
+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
-There is also a third special case, the Cygwin port.  It takes
+information.
-advantage of Cygnus emulation library under Win32, which enables it to
-reuse much of the Unix XEmacs code base, such as processes and network
+Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
-support, or internal select() mechanisms.
+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
-Cygwin port supports all display types---TTY, X & MS GUI, and can be
+orphaned and it's unlikely it will compile without a lot of work.  If
-built with support for all three.  If you build with MS GUI support
+you want an MS Windows versin of XEmacs that supports X, use the Cygwin
-then the Cygwin version uses the majority of the msw code, which is
+version. (The X support there is actively maintained, so that Windows
-mostly related to display.  If you want to build with X support you
+developers can test the X support in XEmacs.)
-need X libraries.  If you want to build with TTY support you need
-ncurses.  MS GUI requires no additional libraries.
+@node Q6.1.1, Q6.1.2, Q6.0.7, MS Windows
-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.
-The disadvantage is that it requires several Unix utilities and the
-whole Cygwin environment, whereas the native port requires only a
-suitable MS Windows compiler.  Also, it follows the Unix filesystem and
-process model very closely (some will undoubtedly view this as an
-advantage).
-@node Q6.1.1, Q6.1.2, Q6.0.4, MS Windows
 @unnumberedsec 6.1: Building XEmacs on MS Windows
-@unnumberedsubsec Q6.1.1: I decided to run with X.  Where do I get an X server?
+@unnumberedsubsec Q6.1.1: What compiler/libraries do I need to compile XEmacs?
-Pointers to X servers can be found at
+You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
-@iftex
+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
-@end iftex
+versions, you need the Cygwin environment, which comes with GCC, the
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/};
+compiler used for those versions.  @xref{Q6.0.6}, for more information
+on Cygwin and MinGW.
-look for "Where to get an X server".  Also note that, although the above
-page talks about Cygnus gnu-win32 (Cygwin), the information on X servers
-is Cygwin-independent.  You don't have to be running/using Cygwin to use
-these X servers, and you don't have to compile XEmacs under Cygwin to
-use XEmacs with these X servers.  An "X port" XEmacs compiled under
-Visual C++ will work with these X servers (as will XEmacs running on a
-Unix box, redirected to the server running on your PC).
 @node Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
-@unnumberedsubsec Q6.1.2: What compiler do I need to compile XEmacs?
+@unnumberedsubsec Q6.1.2: How do I compile the native port?
-You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the Cygwin
-port, which uses Gcc.  There is also a MINGW32 port of XEmacs (using
-Gcc, but using native libraries rather than the Cygwin libraries).  ####
-More information about this should be provided.
-@node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
-@unnumberedsubsec Q6.1.3: How do I compile for the native port?
 Please read the file @file{nt/README} in the XEmacs distribution, which
 contains the full description.
+@node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
+@unnumberedsubsec Q6.1.3: What do I need for Cygwin?
+You can find the Cygwin tools and compiler at:
+@uref{http://sources.redhat.com/cygwin/}
+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.
+If you want to compile under X, you will also need the X libraries; see
+@ref{Q6.1.6}.
 @node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
-@unnumberedsubsec Q6.1.4: How do I compile for the X port?
+@unnumberedsubsec Q6.1.4: How do I compile under Cygwin?
-Again, it is described in @file{nt/README} in some detail.  Basically, you
-need to get X11 libraries from ftp.x.org, and compile them.  If the
-precompiled versions are available somewhere, I don't know of it.
-@node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
-@unnumberedsubsec Q6.1.5: How do I compile for Cygnus' Cygwin?
 Similar as on Unix; use the usual `configure' and `make' process.
 Some problems to watch out for:
 @itemize @bullet
 @item
 make sure HOME is set. This controls where you
 @file{init.el}/@file{.emacs} file comes from;
 @item
-CYGWIN needs to be set to tty for process support work. e.g. CYGWIN=tty;
+CYGWIN needs to be set to tty for process support to work, e.g. CYGWIN=tty;
-(use CYGWIN32=tty under b19 and older.)
 @item
 picking up some other grep or other UNIX-like tools can kill configure;
 @item
 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
 number;
 @item
-The Cygwin version doesn't understand @file{//machine/path} type paths so you
+(Unconfirmed) The Cygwin version doesn't understand
-will need to manually mount a directory of this form under a unix style
+@file{//machine/path} type paths so you will need to manually mount a
-directory for a build to work on the directory.
+directory of this form under a unix style directory for a build to work
+on the directory;
+@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:
+@example
+/usr/lib/libXpm.a     -> /usr/lib/libXpm-noX.a
+/usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
+@end example
+@item
+Other problems are listed in the @file{PROBLEMS} file, in the top-level
+directory of the XEmacs sources.
 @end itemize
-@node Q6.1.6, Q6.2.1, Q6.1.5, MS Windows
-@unnumberedsubsec Q6.1.6: What do I need for 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 find the Cygwin tools and compiler at:
+Similar to the method for Unix.  Things to remember:
-@uref{http://sourceware.cygnus.com/cygwin/}
+@itemize @bullet
-You will need version b19 or later.
+@item
-The latest current version is 1.1.1.
+Specify the target host on the command line for @file{./configure}, e.g.
-Other common versions you will see are b20.1.
+@samp{./configure i586-pc-mingw32}.
-Another location, one of the mirror sites of the site just mentioned,
+@item
-is usually a last faster:
+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
-@uref{ftp://ftp.freesoftware.com/pub/sourceware/cygwin/}
+path (@file{c:\build\xemacs}).
-You can obtain the latest version (currently 1.1.1) from the
+@item
-@samp{latest/} subdirectory of either of the above two just-mentioned
+Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
-URL's.
+@file{compface}, etc.
-@strong{WARNING: The version of GCC supplied under @samp{latest/}, as of
+@item
-June 6th, 2000, does not appear to work.  It generates loads of spurious
+Specify the target location of the extra libs on the command line
-preprocessor warnings and errors, which makes it impossible to compile
+to @file{configure}, e.g.
-XEmacs with it.}
+@samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
+@end itemize
-You will also need the X libraries.  You can get them on the XEmacs FTP
-site at
+@node Q6.1.6, Q6.1.7, Q6.1.5, MS Windows
-@uref{ftp://ftp.xemacs.org/pub/xemacs/aux/cygwin/}
+@unnumberedsubsec Q6.1.6: I decided to run with X.  Where do I get an X server?
-You will find b19 and b20 versions of the X libraries, plus b19 and b20
+As of May 2001, we are recommending that you use the port of XFree86 to
-versions of stuff that should go into @samp{/usr/local/}, donated by
+Cygwin.  This has recently stabilized, and will undoubtedly soon make
-Andy Piper.  This includes pre-built versions of various graphics libraries,
+most other MS Windows X servers obsolete.  It is what the Windows
-such as PNG, JPEG, TIFF, and XPM. (Remember, GIF support is built-in to
+developers use to test the MS Windows X support.
-XEmacs.)
+To install, go to @uref{http://xfree86.cygwin.com/}.  There is a
-(X libraries for v1 and beyond of Cygwin can be found on the Cygwin site
+detailed description on that site of exactly how to install it.  This
-itself -- look in the @samp{xfree/} subdirectory.)
+installation also provides the libraries, include files, and other stuff
+needed for development; a large collection of internationalized fonts;
-@emph{NOTE:} There are two versions of the XPM library provided in
+the standard X utilities (xterm, twm, etc.) -- in a word, the works.
-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
+NOTE: As of late May 2001, there is a bug in the file
-both X and Windows support.  The two files are called @file{libXpm-X.a}
+@file{startxwin.bat}, used to start X Windows.  It passes the option
-and @file{libXpm-noX.a} respectively, and you must symlink the
+@samp{-engine -4} to the X server, which is bogus -- you need to edit
-appropriate one to @file{libXpm.a}. @strong{CAREFUL:} By default, the
+the file and change it to @samp{-engine 4}.
-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.7, Q6.2.1, Q6.1.6, MS Windows
+@unnumberedsubsec Q6.1.7: How do I compile with X support?
-Please see @uref{http://www.xemacs.freeserve.co.uk/} (Andy Piper's home
-page) for more information.
+To compile under Cygwin, all you need to do is install XFree86
+(@pxref{Q6.1.6}).  Once installed, @file{configure} should automatically
-BTW There are also libraries at
+find the X libraries and compile with X support.
-@iftex
-@*
+As noted above, the non-Cygwin X support is basically orphaned, and
-@end iftex
+probably won't work.  But if it want to try, it's described in
-@uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}, but
+@file{nt/README} in some detail.  Basically, you need to get X11
-these are not b19 compatible, and may in fact be native-compiled.
+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.6, MS Windows
+@node Q6.2.1, Q6.2.2, Q6.1.7, 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?
+@unnumberedsubsec Q6.2.1: How does the port cope with differences in the Windows user interface?
-XEmacs (and Emacs in general) UI is pretty
+XEmacs (and Emacs in general) UI is pretty different from what is
-different from what is expected of a typical MS Windows program.  How will
+expected of a typical MS Windows program.  How does the MS Windows port
-the MS Windows port cope with it?
+cope with it?
-Fortunately, Emacs is also one of the most configurable editor beasts
+As a general rule, we follow native MS Windows conventions as much as
-in the world.  The MS Windows "look and feel" (mark via shift-arrow,
+possible.  In cases where there's a clear UI conflict, we currently use
-self-inserting deletes region, etc.) can be easily configured via
+normal Unix XEmacs behavior by default, but make sure the MS Windows
-various packages distributed with XEmacs.  The `pending-delete'
+"look and feel" (mark via shift-arrow, self-inserting deletes region,
-package is an example of such a utility.
+Alt selects menu items, etc.) is easily configurable (respectively:
+using the variable @code{shifted-motion-keys-select-region} in 21.4 and
-In future versions, some of these packages might be turned on by
+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
+In 21.4 and above, use the font menu.  In all versions, you can change
-manually. For example:
+font manually. For example:
 @display
 (set-face-font 'default "Lucida Console:Regular:10")
 (set-face-font 'modeline "MS Sans Serif:Regular:10")
 @end display
 the HOME environment variable.  If this is not set, it defaults to
 `C:\'.
 @node Q6.3.1, Q6.3.2, Q6.2.3, MS Windows
 @unnumberedsec 6.3: Miscellaneous
-@unnumberedsubsec Q6.3.1: Will XEmacs rename all the win32-* symbols to w32-*?
+@unnumberedsubsec Q6.3.1: Does XEmacs rename all the win32-* symbols to w32-*?
 In his flavor of Emacs 20, Richard Stallman has renamed all the win32-*
-symbols to w32-*.  Will XEmacs do the same?
+symbols to w32-*.  Does XEmacs do the same?
 We consider such a move counter-productive, thus we will not use the
 `w32' prefix.  However, we do recognize that Win32 name is little more
 than a marketing buzzword (will it be Win64 in the next release?), so
 we decided not to use it.  Using `windows-' would be wrong because the
 Here is a recount of various Emacs versions running on MS Windows:
 @itemize @bullet
 @item
+XEmacs
+@itemize @minus
+@item
+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" XEmacs supported.  The 19.12 design is the basis for
+the current native MS Windows code.
+@item
+Some time during 1997, David Hobley (soon joined by Marc Paquette)
+imported some of the NT-specific portions of GNU Emacs, making XEmacs
+with X support compile under Windows NT, and creating the "X" port.
+@item
+Several months later, Jonathan Harris sent out initial patches to use
+the Win32 API, thus creating the native port.  Since then, various
+people have contributed, including Kirill M. Katsnelson (contributed
+support for menubars, subprocesses and network, as well as loads of
+other code), Andy Piper (ported XEmacs to Cygwin environment,
+contributed Windows unexec, Windows-specific glyphs and toolbars code,
+and more), Ben Wing (loads of improvements; currently the most active MS
+Windows developer), Jeff Sparkes (contributed scrollbars support) and
+many others.
+@end itemize
+@item
+NT Emacs
+@itemize @minus
+@item
+NT Emacs is a version of GNU Emacs modified to compile and run under
+MS MS Windows 95 and NT using the native Win32 API.  As such, it is close
+in spirit to the XEmacs "native" port.
+@item
+NT Emacs has been written by Geoff Voelker, and more information can be
+found at
+@iftex
+@*
+@end iftex
+@uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
+@end itemize
+@item
 Win-Emacs
 @itemize @minus
 @item
-Win-Emacs is a port of Lucid Emacs 19.6 to MS Windows using X
+Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
-compatibility libraries.  Win-Emacs has been written by Ben Wing.  The
+compatibility libraries.  Win-Emacs was written by Ben Wing.  The MS
-MS Windows code has not made it back to Lucid Emacs, which left Win-Emacs
+Windows code never made it back to Lucid Emacs, and its creator (Pearl
-pretty much dead for our purposes.  Win-Emacs used to be available at
+Software) has long since gone out of business.
-Pearlsoft, but not anymore, since Pearlsoft went out of business.
 @end itemize
 @item
 GNU Emacs for DOS
 @itemize @minus
 @item
 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
 port of Gcc).  Such an Emacs is heavily underfeatured, because it does
-not supports long file names, lacks proper subprocesses support, and
+not support long file names, lacks proper subprocesses support, and
 is far too big compared to typical DOS editors.
 @end itemize
 @item
 GNU Emacs compiled with Win32
 is is very similar to GNU Emacs compiled under MS DOS, only it
 supports longer file names, etc.  This "port" is similar to the "X"
 flavor of XEmacs on MS Windows.
 @end itemize
-@item
-NT Emacs
-@itemize @minus
-@item
-NT Emacs is a version of GNU Emacs modified to compile and run under
-MS MS Windows 95 and NT using the native Win32 API.  As such, it is close
-in spirit to the XEmacs "native" port.
-@item
-NT Emacs has been written by Geoff Voelker, and more information can be
-found at
-@iftex
-@*
-@end iftex
-@uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
-@end itemize
-@item
-XEmacs
-@itemize @minus
-@item
-Beginning with XEmacs 19.12, XEmacs' architecture has been redesigned
-in such a way to allow clean support of multiple window systems.  At
-this time the TTY support was added, making X and TTY the first two
-"window systems" XEmacs supported.  The 19.12 design is the basis for
-the current native MS Windows code.
-@item
-Some time during 1997, David Hobley (soon joined by Marc Paquette)
-imported some of the NT-specific portions of GNU Emacs, making XEmacs
-with X support compile under Windows NT, and creating the "X" port.
-@item
-Several months later, Jonathan Harris sent out initial patches to use
-the Win32 API, thus creating the native port.  Since then, various
-people have contributed, including Kirill M. Katsnelson (contributed
-support for menubars, subprocesses and network, as well as loads of
-other code), Andy Piper (ported XEmacs to Cygwin environment,
-contributed Windows unexec, Windows-specific glyphs and toolbars code,
-and more), Jeff Sparkes (contributed scrollbars support) and many
-others.
-@end itemize
 @end itemize
 @node Q6.3.3, Q6.4.1, Q6.3.2, MS Windows
 @unnumberedsubsec Q6.3.3: What is the porting team doing at the moment?
-(as of March 2001)
+(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 Windows and the improvement of the widget support (better
 support for dialog boxes, buttons, edit fields, and similar UI
 elements).
 @node Q6.4.1, ,Q6.3.3, MS Windows
 @unnumberedsec 6.3: Troubleshooting
 @unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)
 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.
+reversed -- putting the information back at the correct addresses.
-Unfortunately some .dlls (For instance the soundblaster driver) occupy
+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
+problem for most people.  21.4 implements "portable dumping", which
-this version.  Check back periodically at
+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
-@uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/}.
+about stability.  @xref{Q6.0.3}.
-21.2 implements "portable dumping" which will eliminate the problem
-altogether.  You might have better luck with the 21.2 beta binary,
-available at
-@uref{ftp://ftp.xemacs.org/pub/xemacs/beta/binaries/}.
 @node Current Events,  , MS Windows, Top
 @unnumbered 7 What the Future Holds

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 593:5fd7ba8b56e7