Mercurial > emacs

--- a/etc/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,18 @@
+2004-08-22  David Kastrup  <dak@gnu.org>
+
+	* PROBLEMS, MAILINGLISTS: Update AUCTeX information.
+
+2004-08-21  Bill Wohler  <wohler@newt.com>
+
+	* NEWS, MH-E-NEWS: Upgraded to MH-E version 7.81.
+
+2004-08-21  Eric S. Raymond  <esr@thyrsus.com>
+
+	* PROBLEMS: Massively rearranged by category, to make environment
+	features and symptoms easier to find.  Bugs relating to
+	20th-century systems moved to the end.  Most problem headers
+	changed to "object: variation" format.
+
 2004-08-15  Bill Wohler  <wohler@newt.com>

 	* NEWS, MH-E-NEWS: Upgraded to MH-E version 7.4.80.
--- a/etc/MAILINGLISTS	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/MAILINGLISTS	Mon Aug 23 10:12:04 2004 +0000
@@ -1224,13 +1224,14 @@
 The supercite mailing list covers issues related to the advanced
 mail/news citation package called Supercite for GNU Emacs.

-* auc-tex-request@iesd.auc.dk to subscribe
+* auc-tex-request@sunsite.dk to subscribe
 ** USENET newsgroup: NONE YET
-** Send contributions to: auc-tex@iesd.auc.dk
+** Send contributions to: auc-tex@sunsite.dk

-The list is intended to exchange information about AUC TeX, such as
+The list is intended to exchange information about AUCTeX, such as
 bug reports, request for help, and information on current
-developments.  AUC TeX is a much enhanced LaTeX mode for GNU Emacs.
+developments.  AUCTeX is a much enhanced TeX/LaTeX/ConTeXt/Texinfo mode
+for GNU Emacs.

 The list is unmoderated.
--- a/etc/MH-E-NEWS	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/MH-E-NEWS	Mon Aug 23 10:12:04 2004 +0000
@@ -6,6 +6,17 @@
 are permitted in any medium without royalty provided the copyright
 notice and this notice are preserved.

+* Changes in MH-E 7.81
+
+Version 7.81 fixes a `wrong-type-argument' argument error that
+sometimes occurred when processing the Message-ID, adds the ";
+(mh-toggle-mh-decode-mime-flag)" command, and uses ":default" instead
+of "default" in `mh-identity-handlers' to avoid problems with
+"Default:" as a user defined field. If you have modified
+`mh-identity-handlers' in your .emacs, you'll need to rename "default"
+to ":default". This release also corrects the release numbering; the
+previous version number was intended to be 7.80.
+
 * Changes in MH-E 7.4.80

 Version 7.4.80 now supports GNU mailutils, S/MIME, picons,
--- a/etc/NEWS	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/NEWS	Mon Aug 23 10:12:04 2004 +0000
@@ -98,6 +98,8 @@

 * Changes in Emacs 21.4

+** global-whitespace-mode is a new alias for whitespace-global-mode.
+
 +++
 ** There are now two new regular expression operators, \_< and \_>,
 for matching the beginning and end of a symbol.  A symbol is a
@@ -658,7 +660,7 @@

 ** MH-E changes.

-Upgraded to MH-E version 7.4.80. There have been major changes since
+Upgraded to MH-E version 7.81. There have been major changes since
 version 5.0.2; see MH-E-NEWS for details.

 +++
--- a/etc/PROBLEMS	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/PROBLEMS	Mon Aug 23 10:12:04 2004 +0000
@@ -1,45 +1,782 @@
 This file describes various problems that have been encountered
-in compiling, installing and running GNU Emacs.
-
-* Environment Variables from dotfiles are ignored with Mac OS X (Carbon).
-
-When starting Emacs from the Dock or the Finder on Mac OS X, the
-environment variables that are set up in dotfiles, such as .cshrc or
-.profile, are ignored.  This is because the Finder and Dock are not
-started from a shell, but instead from the Window Manager itself.
-
-The workaround for this is to create a .MacOSX/environment.plist file to
-setup these environment variables.  These environment variables will
-apply to all processes regardless of where they are started.
-For me information, see http://developer.apple.com/qa/qa2001/qa1067.html.
-
-* Segfault on GNU/Linux using certain recent versions of the Linux kernel.
-
-With certain recent Linux kernels (like the one of Redhat Fedora Core
-1), the new "Exec-shield" functionality is enabled by default, which
-creates a different memory layout that breaks the emacs dumper.
-
-You can check the Exec-shield state like this:
-
-    cat /proc/sys/kernel/exec-shield
-
-It returns 1 or 2 when Exec-shield is enabled, 0 otherwise.  Please
-read your system documentation for more details on Exec-shield and
-associated commands.
-
-When Exec-shield is enabled, building Emacs will segfault during the
-execution of this command:
-
-temacs --batch --load loadup [dump|bootstrap]
-
-To work around this problem, it is necessary to temporarily disable
-Exec-shield while building Emacs, using the `setarch' command like
-this:
-
-    setarch i386 ./configure <configure parameters>
-    setarch i386 make <make parameters>
-
-* Characters are displayed as empty boxes or with wrong font under X.
+in compiling, installing and running GNU Emacs.  Try doing Ctl t
+and browsing through the outline headers.
+
+* Emacs startup failures
+
+** Emacs fails to start, complaining about missing fonts.
+
+A typical error message might be something like
+
+  No fonts match `-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1'
+
+This happens because some X resource specifies a bad font family for
+Emacs to use.  The possible places where this specification might be
+are:
+
+  - in your ~/.Xdefaults file
+
+  - client-side X resource file, such as  ~/Emacs or
+    /usr/X11R6/lib/app-defaults/Emacs or
+    /usr/X11R6/lib/X11/app-defaults/Emacs
+
+One of these files might have bad or malformed specification of a
+fontset that Emacs should use.  To fix the problem, you need to find
+the problematic line(s) and correct them.
+
+** Emacs aborts while starting up, only when run without X.
+
+This problem often results from compiling Emacs with GCC when GCC was
+installed incorrectly.  The usual error in installing GCC is to
+specify --includedir=/usr/include.  Installation of GCC makes
+corrected copies of the system header files.  GCC is supposed to use
+the corrected copies in preference to the original system headers.
+Specifying --includedir=/usr/include causes the original system header
+files to be used.  On some systems, the definition of ioctl in the
+original system header files is invalid for ANSI C and causes Emacs
+not to work.
+
+The fix is to reinstall GCC, and this time do not specify --includedir
+when you configure it.  Then recompile Emacs.  Specifying --includedir
+is appropriate only in very special cases and it should *never* be the
+same directory where system header files are kept.
+
+** Emacs does not start, complaining that it cannot open termcap database file.
+
+If your system uses Terminfo rather than termcap (most modern
+systems do), this could happen if the proper version of
+ncurses is not visible to the Emacs configure script (i.e. it
+cannot be found along the usual path the linker looks for
+libraries). It can happen because your version of ncurses is
+obsolete, or is available only in form of binaries.
+
+The solution is to install an up-to-date version of ncurses in
+the developer's form (header files, static libraries and
+symbolic links); in some GNU/Linux distributions (e.g. Debian)
+it constitutes a separate package.
+
+** Emacs 20 and later fails to load Lisp files at startup.
+
+The typical error message might be like this:
+
+  "Cannot open load file: fontset"
+
+This could happen if you compress the file lisp/subdirs.el.  That file
+tells Emacs what are the directories where it should look for Lisp
+files.  Emacs cannot work with subdirs.el compressed, since the
+Auto-compress mode it needs for this will not be loaded until later,
+when your .emacs file is processed.  (The package `fontset.el' is
+required to set up fonts used to display text on window systems, and
+it's loaded very early in the startup procedure.)
+
+Similarly, any other .el file for which there's no corresponding .elc
+file could fail to load if it is compressed.
+
+The solution is to uncompress all .el files which don't have a .elc
+file.
+
+Another possible reason for such failures is stale *.elc files
+lurking somewhere on your load-path.  The following command will
+print any duplicate Lisp files that are present in load-path:
+
+    emacs -q -batch -f list-load-path-shadows
+
+If this command prints any file names, some of these files are stale,
+and should be deleted or their directories removed from your
+load-path.
+
+** Emacs prints an error at startup after upgrading from an earlier version.
+
+An example of such an error is:
+
+  x-complement-fontset-spec: "Wrong type argument: stringp, nil"
+
+This can be another symptom of stale *.elc files in your load-path.
+The following command will print any duplicate Lisp files that are
+present in load-path:
+
+    emacs -q -batch -f list-load-path-shadows
+
+If this command prints any file names, some of these files are stale,
+and should be deleted or their directories removed from your
+load-path.
+
+** With X11R6.4, public-patch-3, Emacs crashes at startup.
+
+Reportedly this patch in X fixes the problem.
+
+    --- xc/lib/X11/imInt.c~	Wed Jun 30 13:31:56 1999
+    +++ xc/lib/X11/imInt.c	Thu Jul  1 15:10:27 1999
+    @@ -1,4 +1,4 @@
+    -/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */
+    +/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $  */
+     /******************************************************************
+
+		Copyright 1992, 1993, 1994 by FUJITSU LIMITED
+    @@ -166,8 +166,8 @@
+     _XimMakeImName(lcd)
+	 XLCd	   lcd;
+     {
+    -    char* begin;
+    -    char* end;
+    +    char* begin = NULL;
+    +    char* end = NULL;
+	 char* ret;
+	 int	i = 0;
+	 char* ximmodifier = XIMMODIFIER;
+    @@ -182,7 +182,11 @@
+	 }
+	 ret = Xmalloc(end - begin + 2);
+	 if (ret != NULL) {
+    -    	(void)strncpy(ret, begin, end - begin + 1);
+    +	if (begin != NULL) {
+    +      	  (void)strncpy(ret, begin, end - begin + 1);
+    +        } else {
+    +	  ret[0] = '\0';
+    +	}
+	    ret[end - begin + 1] = '\0';
+	 }
+	 return ret;
+
+* Crash bugs
+
+** Emacs crashes in x-popup-dialog.
+
+This can happen if the dialog widget cannot find the font it wants to
+use.  You can work around the problem by specifying another font with
+an X resource--for example, `Emacs.dialog*.font: 9x15' (or any font that
+happens to exist on your X server).
+
+** Emacs crashes when you use Bibtex mode.
+
+This happens if your system puts a small limit on stack size.  You can
+prevent the problem by using a suitable shell command (often `ulimit')
+to raise the stack size limit before you run Emacs.
+
+Patches to raise the stack size limit automatically in `main'
+(src/emacs.c) on various systems would be greatly appreciated.
+
+** Emacs crashes with SIGBUS or SIGSEGV on HPUX 9 after you delete a frame.
+
+We think this is due to a bug in the X libraries provided by HP.  With
+the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem
+does not happen.
+
+** Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
+
+We suspect that this is a similar bug in the X libraries provided by
+Sun.  There is a report that one of these patches fixes the bug and
+makes the problem stop:
+
+105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
+105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
+106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
+105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
+
+Another person using a newer system (kernel patch level Generic_105181-06)
+suspects that the bug was fixed by one of these more recent patches:
+
+106040-07  SunOS 5.6: X Input & Output Method patch
+106222-01  OpenWindows 3.6: filemgr (ff.core) fixes
+105284-12  Motif 1.2.7: sparc Runtime library patch
+
+** Error message `Symbol's value as variable is void: x', followed by
+a segmentation fault and core dump.
+
+This has been tracked to a bug in tar!  People report that tar erroneously
+added a line like this at the beginning of files of Lisp code:
+
+   x FILENAME, N bytes, B tape blocks
+
+If your tar has this problem, install GNU tar--if you can manage to
+untar it :-).
+
+** Crashes when displaying GIF images in Emacs built with version
+libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
+Configure checks for the correct version, but this problem could occur
+if a binary built against a shared libungif is run on a system with an
+older version.
+
+** Emacs aborts inside the function `tparam1'.
+
+This can happen if Emacs was built without terminfo support, but the
+terminal's capabilities use format that is only supported by terminfo.
+If your system has ncurses installed, this might happen if your
+version of ncurses is broken; upgrading to a newer version of ncurses
+and reconfiguring and rebuilding Emacs should solve this.
+
+All modern systems support terminfo, so even if ncurses is not the
+problem, you should look for a way to configure Emacs so that it uses
+terminfo when built.
+
+** Emacs crashes when using the Exceed 6.0 X server.
+
+If you are using Exceed 6.1, upgrade to a later version.  This was
+reported to prevent the crashes.
+
+** Emacs crashes with SIGSEGV in XtInitializeWidgetClass.
+
+It crashes on X, but runs fine when called with option "-nw".
+
+This has been observed when Emacs is linked with GNU ld but without passing
+the -z nocombreloc flag.  Emacs normally knows to pass the -z nocombreloc
+flag when needed, so if you come across a situation where the flag is
+necessary but missing, please report it via M-x report-emacs-bug.
+
+On platforms such as Solaris, you can also work around this problem by
+configuring your compiler to use the native linker instead of GNU ld.
+
+* General runtime problems
+
+** Lisp problems
+
+*** Changes made to .el files do not take effect.
+
+You may have forgotten to recompile them into .elc files.
+Then the old .elc files will be loaded, and your changes
+will not be seen.  To fix this, do M-x byte-recompile-directory
+and specify the directory that contains the Lisp files.
+
+Emacs should print a warning when loading a .elc file which is older
+than the corresponding .el file.
+
+*** Watch out for .emacs files and EMACSLOADPATH environment vars.
+
+These control the actions of Emacs.
+~/.emacs is your Emacs init file.
+EMACSLOADPATH overrides which directories the function
+"load" will search.
+
+If you observe strange problems, check for these and get rid
+of them, then try again.
+
+*** Using epop3.el package causes Emacs to signal an error.
+
+The error message might be something like this:
+
+  "Lisp nesting exceeds max-lisp-eval-depth"
+
+This happens because epop3 redefines the function gethash, which is a
+built-in primitive beginning with Emacs 21.1.  We don't have a patch
+for epop3 that fixes this, but perhaps a newer version of epop3
+corrects that.
+
+*** Buffers from `with-output-to-temp-buffer' get set up in Help mode.
+
+Changes in Emacs 20.4 to the hooks used by that function cause
+problems for some packages, specifically BBDB.  See the function's
+documentation for the hooks involved.  BBDB 2.00.06 fixes the problem.
+
+*** The Hyperbole package causes *Help* buffers not to be displayed in
+Help mode due to setting `temp-buffer-show-hook' rather than using
+`add-hook'.  Using `(add-hook 'temp-buffer-show-hook
+'help-mode-maybe)' after loading Hyperbole should fix this.
+
+** Keyboard problems
+
+*** "Compose Character" key does strange things when used as a Meta key.
+
+If you define one key to serve as both Meta and Compose Character, you
+will get strange results.  In previous Emacs versions, this "worked"
+in that the key acted as Meta--that's because the older Emacs versions
+did not try to support Compose Character.  Now Emacs tries to do
+character composition in the standard X way.  This means that you
+must pick one meaning or the other for any given key.
+
+You can use both functions (Meta, and Compose Character) if you assign
+them to two different keys.
+
+*** C-z just refreshes the screen instead of suspending Emacs.
+
+You are probably using a shell that doesn't support job control, even
+though the system itself is capable of it.  Either use a different shell,
+or set the variable `cannot-suspend' to a non-nil value.
+
+*** With M-x enable-flow-control, you need to type C-\ twice
+to do incremental search--a single C-\ gets no response.
+
+This has been traced to communicating with your machine via kermit,
+with C-\ as the kermit escape character.  One solution is to use
+another escape character in kermit.  One user did
+
+   set escape-character 17
+
+in his .kermrc file, to make C-q the kermit escape character.
+
+** Mailers and other helper programs
+
+*** movemail compiled with POP support can't connect to the POP server.
+
+Make sure that the `pop' entry in /etc/services, or in the services
+NIS map if your machine uses NIS, has the same port number as the
+entry on the POP server.  A common error is for the POP server to be
+listening on port 110, the assigned port for the POP3 protocol, while
+the client is trying to connect on port 109, the assigned port for the
+old POP protocol.
+
+*** RMAIL gets error getting new mail.
+
+RMAIL gets new mail from /usr/spool/mail/$USER using a program
+called `movemail'.  This program interlocks with /bin/mail using
+the protocol defined by /bin/mail.
+
+There are two different protocols in general use.  One of them uses
+the `flock' system call.  The other involves creating a lock file;
+`movemail' must be able to write in /usr/spool/mail in order to do
+this.  You control which one is used by defining, or not defining,
+the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes.
+IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
+SYSTEM, YOU CAN LOSE MAIL!
+
+If your system uses the lock file protocol, and fascist restrictions
+prevent ordinary users from writing the lock files in /usr/spool/mail,
+you may need to make `movemail' setgid to a suitable group such as
+`mail'.  You can use these commands (as root):
+
+	chgrp mail movemail
+	chmod 2755 movemail
+
+If your system uses the lock file protocol, and fascist restrictions
+prevent ordinary users from writing the lock files in /usr/spool/mail,
+you may need to make `movemail' setgid to a suitable group such as
+`mail'.  To do this,  use the following commands (as root) after doing the
+make install.
+
+	chgrp mail movemail
+	chmod 2755 movemail
+
+Installation normally copies movemail from the build directory to an
+installation directory which is usually under /usr/local/lib.  The
+installed copy of movemail is usually in the directory
+/usr/local/lib/emacs/VERSION/TARGET.  You must change the group and
+mode of the installed copy; changing the group and mode of the build
+directory copy is ineffective.
+
+*** rcs2log gives you the awk error message "too many fields".
+
+This is due to an arbitrary limit in certain versions of awk.
+The solution is to use gawk (GNU awk).
+
+** Problems with hostname resolution
+
+*** Emacs fails to understand most Internet host names, even though
+the names work properly with other programs on the same system.
+*** Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
+*** GNUs can't make contact with the specified host for nntp.
+
+This typically happens on Suns and other systems that use shared
+libraries.  The cause is that the site has installed a version of the
+shared library which uses a name server--but has not installed a
+similar version of the unshared library which Emacs uses.
+
+The result is that most programs, using the shared library, work with
+the nameserver, but Emacs does not.
+
+The fix is to install an unshared library that corresponds to what you
+installed in the shared library, and then relink Emacs.
+
+On SunOS 4.1, simply define HAVE_RES_INIT.
+
+If you have already installed the name resolver in the file libresolv.a,
+then you need to compile Emacs to use that library.  The easiest way to
+do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
+or LIB_STANDARD which uses -lresolv.  Watch out!  If you redefine a macro
+that is already in use in your configuration to supply some other libraries,
+be careful not to lose the others.
+
+Thus, you could start by adding this to config.h:
+
+#define LIBS_SYSTEM -lresolv
+
+Then if this gives you an error for redefining a macro, and you see that
+the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
+again to say this:
+
+#define LIBS_SYSTEM -lresolv -lfoo -lbar
+
+*** Emacs does not know your host's fully-qualified domain name.
+
+You need to configure your machine with a fully qualified domain name,
+either in /etc/hosts, /etc/hostname, the NIS, or wherever your system
+calls for specifying this.
+
+If you cannot fix the configuration, you can set the Lisp variable
+mail-host-address to the value you want.
+
+** NFS and RFS
+
+*** Emacs says it has saved a file, but the file does not actually
+appear on disk.
+
+This can happen on certain systems when you are using NFS, if the
+remote disk is full.  It is due to a bug in NFS (or certain NFS
+implementations), and there is apparently nothing Emacs can do to
+detect the problem.  Emacs checks the failure codes of all the system
+calls involved in writing a file, including `close'; but in the case
+where the problem occurs, none of those system calls fails.
+
+*** Editing files through RFS gives spurious "file has changed" warnings.
+It is possible that a change in Emacs 18.37 gets around this problem,
+but in case not, here is a description of how to fix the RFS bug that
+causes it.
+
+    There was a serious pair of bugs in the handling of the fsync() system
+    call in the RFS server.
+
+    The first is that the fsync() call is handled as another name for the
+    close() system call (!!).  It appears that fsync() is not used by very
+    many programs; Emacs version 18 does an fsync() before closing files
+    to make sure that the bits are on the disk.
+
+    This is fixed by the enclosed patch to the RFS server.
+
+    The second, more serious problem, is that fsync() is treated as a
+    non-blocking system call (i.e., it's implemented as a message that
+    gets sent to the remote system without waiting for a reply).  Fsync is
+    a useful tool for building atomic file transactions.  Implementing it
+    as a non-blocking RPC call (when the local call blocks until the sync
+    is done) is a bad idea; unfortunately, changing it will break the RFS
+    protocol.  No fix was supplied for this problem.
+
+    (as always, your line numbers may vary)
+
+    % rcsdiff -c -r1.2 serversyscall.c
+    RCS file: RCS/serversyscall.c,v
+    retrieving revision 1.2
+    diff -c -r1.2 serversyscall.c
+    *** /tmp/,RCSt1003677   Wed Jan 28 15:15:02 1987
+    --- serversyscall.c     Wed Jan 28 15:14:48 1987
+    ***************
+    *** 163,169 ****
+	    /*
+	     * No return sent for close or fsync!
+	     */
+    !       if (syscall == RSYS_close || syscall == RSYS_fsync)
+		    proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
+	    else
+	    {
+    --- 166,172 ----
+	    /*
+	     * No return sent for close or fsync!
+	     */
+    !       if (syscall == RSYS_close)
+		    proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
+	    else
+	    {
+
+** PSGML
+
+*** Old versions of the PSGML package use the obsolete variables
+`before-change-function' and `after-change-function', which are no
+longer used by Emacs.  Please use PSGML 1.2.3 or later.
+
+*** PSGML conflicts with sgml-mode.
+
+PSGML package uses the same names of some variables (like keymap)
+as built-in sgml-mode.el because it was created as a replacement
+of that package.  The conflict will be shown if you load
+sgml-mode.el before psgml.el.  E.g. this could happen if you edit
+HTML page and then start to work with SGML or XML file.  html-mode
+(from sgml-mode.el) is used for HTML file and loading of psgml.el
+(for sgml-mode or xml-mode) will cause an error.
+
+*** Versions of the PSGML package earlier than 1.0.3 (stable) or 1.1.2
+(alpha) fail to parse DTD files correctly in Emacs 20.3 and later.
+Here is a patch for psgml-parse.el from PSGML 1.0.1 and, probably,
+earlier versions.
+
+--- psgml-parse.el	1998/08/21 19:18:18	1.1
++++ psgml-parse.el	1998/08/21 19:20:00
+@@ -2383,7 +2383,7 @@ (defun sgml-push-to-entity (entity &opti
+       (setq sgml-buffer-parse-state nil))
+     (cond
+      ((stringp entity)			; a file name
+-      (save-excursion (insert-file-contents entity))
++      (insert-file-contents entity)
+       (setq default-directory (file-name-directory entity)))
+      ((consp (sgml-entity-text entity)) ; external id?
+       (let* ((extid (sgml-entity-text entity))
+
+** AUCTeX
+
+You should not be using a version older than 11.52 if you can avoid
+it.
+
+*** Emacs 21 freezes when visiting a TeX file with AUCTeX installed.
+
+Emacs 21 needs version 10 or later of AUCTeX; upgrading should solve
+these problems.
+
+*** No colors in AUCTeX with Emacs 21.
+
+Upgrade to AUC TeX version 10 or later, and make sure it is
+byte-compiled with Emacs 21.
+
+** Miscellaneous problems
+
+*** Self-documentation messages are garbled.
+
+This means that the file `etc/DOC-...' doesn't properly correspond
+with the Emacs executable.  Redumping Emacs and then installing the
+corresponding pair of files should fix the problem.
+
+*** Programs running under terminal emulator do not recognize `emacs'
+terminal type.
+
+The cause of this is a shell startup file that sets the TERMCAP
+environment variable.  The terminal emulator uses that variable to
+provide the information on the special terminal type that Emacs
+emulates.
+
+Rewrite your shell startup file so that it does not change TERMCAP
+in such a case.  You could use the following conditional which sets
+it only if it is undefined.
+
+    if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
+
+Or you could set TERMCAP only when you set TERM--which should not
+happen in a non-login shell.
+
+*** In Shell mode, you get a ^M at the end of every line.
+
+This happens to people who use tcsh, because it is trying to be too
+smart.  It sees that the Shell uses terminal type `unknown' and turns
+on the flag to output ^M at the end of each line.  You can fix the
+problem by adding this to your .cshrc file:
+
+    if ($?EMACS) then
+        if ($EMACS == "t") then
+            unset edit
+            stty  -icrnl -onlcr -echo susp ^Z
+        endif
+    endif
+
+*** Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
+
+This can happen if the system is misconfigured and Emacs can't get the
+full qualified domain name, FQDN.  You should have your FQDN in the
+/etc/hosts file, something like this:
+
+127.0.0.1	localhost
+129.187.137.82	nuc04.t30.physik.tu-muenchen.de	nuc04
+
+The way to set this up may vary on non-GNU systems.
+
+*** Attempting to visit remote files via ange-ftp fails.
+
+If the error message is "ange-ftp-file-modtime: Specified time is not
+representable", then this could happen when `lukemftp' is used as the
+ftp client.  This was reported to happen on Debian GNU/Linux, kernel
+version 2.4.3, with `lukemftp' 1.5-5, but might happen on other
+systems as well.  To avoid this problem, switch to using the standard
+ftp client.  On a Debian system, type
+
+  update-alternatives --config ftp
+
+and then choose /usr/bin/netkit-ftp.
+
+*** JPEG images aren't displayed.
+
+This has been reported when Emacs is built with jpeg-6a library.
+Upgrading to jpeg-6b solves the problem.  Configure checks for the
+correct version, but this problem could occur if a binary built
+against a shared libjpeg is run on a system with an older version.
+
+*** Dired is very slow.
+
+This could happen if invocation of the `df' program takes a long
+time.  Possible reasons for this include:
+
+  - ClearCase mounted filesystems (VOBs) that sometimes make `df'
+    response time extremely slow (dozens of seconds);
+
+  - slow automounters on some old versions of Unix;
+
+  - slow operation of some versions of `df'.
+
+To work around the problem, you could either (a) set the variable
+`directory-free-space-program' to nil, and thus prevent Emacs from
+invoking `df'; (b) use `df' from the GNU Fileutils package; or
+(c) use CVS, which is Free Software, instead of ClearCase.
+
+*** Versions of the W3 package released before Emacs 21.1 don't run
+under Emacs 21.  This fixed in W3 version 4.0pre.47.
+
+*** The LDAP support rely on ldapsearch program from OpenLDAP version 2.
+
+It can fail to work with ldapsearch program from OpenLDAP version 1.
+Version 1 of OpenLDAP is now deprecated.  If you are still using it,
+please upgrade to version 2.  As a temporary workaround, remove
+argument "-x" from the variable `ldap-ldapsearch-args'.
+
+*** ps-print commands fail to find prologue files ps-prin*.ps.
+
+This can happen if you use an old version of X-Symbol package: it
+defines compatibility functions which trick ps-print into thinking it
+runs in XEmacs, and look for the prologue files in a wrong directory.
+
+The solution is to upgrade X-Symbol to a later version.
+
+*** On systems with shared libraries you might encounter run-time errors
+from the dynamic linker telling you that it is unable to find some
+shared libraries, for instance those for Xaw3d or image support.
+These errors mean Emacs has been linked with a library whose shared
+library is not in the default search path of the dynamic linker.
+
+Similar problems could prevent Emacs from building, since the build
+process invokes Emacs several times.
+
+On many systems, it is possible to set LD_LIBRARY_PATH in your
+environment to specify additional directories where shared libraries
+can be found.
+
+Other systems allow to set LD_RUN_PATH in a similar way, but before
+Emacs is linked.  With LD_RUN_PATH set, the linker will include a
+specified run-time search path in the executable.
+
+On some systems, Emacs can crash due to problems with dynamic
+linking.  Specifically, on SGI Irix 6.5, crashes were reported with
+backtraces like this:
+
+  (dbx) where
+   0 strcmp(0xf49239d, 0x4031184, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2) ["/xlv22/ficus-jan23/work/irix/lib/libc/libc_n32_M3_ns/strings/strcmp.s":35, 0xfb7e480]
+   1 general_find_symbol(0xf49239d, 0x0, 0x0, 0x0, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
+ ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":2140, 0xfb65a98]
+   2 resolve_symbol(0xf49239d, 0x4031184, 0x0, 0xfbdd438, 0x0, 0xf4923aa, 0x0, 0x492ddb2)
+ ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":1947, 0xfb657e4]
+   3 lazy_text_resolve(0xd18, 0x1a3, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
+ ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":997, 0xfb64d44]
+   4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
+ ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
+
+(`rld' is the dynamic linker.)  We don't know yet why this
+happens, but setting the environment variable LD_BIND_NOW to 1 (which
+forces the dynamic linker to bind all shared objects early on) seems
+to work around the problem.
+
+Please refer to the documentation of your dynamic linker for details.
+
+*** You request inverse video, and the first Emacs frame is in inverse
+video, but later frames are not in inverse video.
+
+This can happen if you have an old version of the custom library in
+your search path for Lisp packages.  Use M-x list-load-path-shadows to
+check whether this is true.  If it is, delete the old custom library.
+
+*** When you run Ispell from Emacs, it reports a "misalignment" error.
+
+This can happen if you compiled the Ispell program to use ASCII
+characters only and then try to use it from Emacs with non-ASCII
+characters, like Latin-1.  The solution is to recompile Ispell with
+support for 8-bit characters.
+
+To see whether your Ispell program supports 8-bit characters, type
+this at your shell's prompt:
+
+     ispell -vv
+
+and look in the output for the string "NO8BIT".  If Ispell says
+"!NO8BIT (8BIT)", your speller supports 8-bit characters; otherwise it
+does not.
+
+To rebuild Ispell with 8-bit character support, edit the local.h file
+in the Ispell distribution and make sure it does _not_ define NO8BIT.
+Then rebuild the speller.
+
+Another possible cause for "misalignment" error messages is that the
+version of Ispell installed on your machine is old.  Upgrade.
+
+Yet another possibility is that you are trying to spell-check a word
+in a language that doesn't fit the dictionary you choose for use by
+Ispell.  (Ispell can only spell-check one language at a time, because
+it uses a single dictionary.)  Make sure that the text you are
+spelling and the dictionary used by Ispell conform to each other.
+
+If your spell-checking program is Aspell, it has been reported that if
+you have a personal configuration file (normally ~/.aspell.conf), it
+can cause this error.  Remove that file, execute `ispell-kill-ispell'
+in Emacs, and then try spell-checking again.
+
+* Runtime problems related to font handling
+
+** Under X11, some characters appear as hollow boxes.
+
+Each X11 font covers just a fraction of the characters that Emacs
+supports.  To display the whole range of Emacs characters requires
+many different fonts, collected into a fontset.
+
+If some of the fonts called for in your fontset do not exist on your X
+server, then the characters that have no font appear as hollow boxes.
+You can remedy the problem by installing additional fonts.
+
+The intlfonts distribution includes a full spectrum of fonts that can
+display all the characters Emacs supports.
+
+Another cause of this for specific characters is fonts which have a
+missing glyph and no default character.  This is known to occur for
+character number 160 (no-break space) in some fonts, such as Lucida
+but Emacs sets the display table for the unibyte and Latin-1 version
+of this character to display a space.
+
+** Under X11, some characters appear improperly aligned in their lines.
+
+You may have bad X11 fonts; try installing the intlfonts distribution.
+
+** Certain fonts make each line take one pixel more than it "should".
+
+This is because these fonts contain characters a little taller
+than the font's nominal height.  Emacs needs to make sure that
+lines do not overlap.
+
+** Loading fonts is very slow.
+
+You might be getting scalable fonts instead of precomputed bitmaps.
+Known scalable font directories are "Type1" and "Speedo".  A font
+directory contains scalable fonts if it contains the file
+"fonts.scale".
+
+If this is so, re-order your X windows font path to put the scalable
+font directories last.  See the documentation of `xset' for details.
+
+With some X servers, it may be necessary to take the scalable font
+directories out of your path entirely, at least for Emacs 19.26.
+Changes in the future may make this unnecessary.
+
+** Font Lock displays portions of the buffer in incorrect faces.
+
+By far the most frequent cause of this is a parenthesis `(' or a brace
+`{' in column zero.  Font Lock assumes that such a paren is outside of
+any comment or string.  This is of course not true in general, but the
+vast majority of well-formatted program source files don't have such
+parens, and therefore this assumption is used to allow optimizations
+in Font Lock's syntactical analysis.  These optimizations avoid some
+pathological cases where jit-lock, the Just-in-Time fontification
+introduced with Emacs 21.1, could significantly slow down scrolling
+through the buffer, especially scrolling backwards, and also jumping
+to the end of a very large buffer.
+
+Beginning with version 21.4, a parenthesis or a brace in column zero
+is highlighted in bold-red face if it is inside a string or a comment,
+to indicate that it could interfere with Font Lock (and also with
+indentation) and should be moved or escaped with a backslash.
+
+If you don't use large buffers, or have a very fast machine which
+makes the delays insignificant, you can avoid the incorrect
+fontification by setting the variable
+`font-lock-beginning-of-syntax-function' to a nil value.  (This must
+be done _after_ turning on Font Lock.)
+
+Another alternative is to avoid a paren in column zero.  For example,
+in a Lisp string you could precede the paren with a backslash.
+
+** With certain fonts, when the cursor appears on a character, the
+character doesn't appear--you get a solid box instead.
+
+One user on a Linux-based GNU system reported that this problem went
+away with installation of a new X server.  The failing server was
+XFree86 3.1.1.  XFree86 3.1.2 works.
+
+** Characters are displayed as empty boxes or with wrong font under X.

 This can occur when two different versions of FontConfig are used.
 For example, XFree86 4.3.0 has one version and Gnome usually comes
@@ -53,25 +790,50 @@
 of FontConfig as the rest of the system uses.  For KDE, it is
 sufficient to recompile Qt.

-* Process output truncated on Mac OS X (Carbon) when using pty's.
-
-There appears to be a problem with the implementation of pty's on the
-Mac OS X that causes process output to be truncated.  To avoid this,
-leave process-connection-type set to its default value of nil.
-
-* Emacs crashes with SIGSEGV in XtInitializeWidgetClass
-
-It crashes on X, but runs fine when called with option "-nw".
-
-This has been observed when Emacs is linked with GNU ld but without passing
-the -z nocombreloc flag.  Emacs normally knows to pass the -z nocombreloc
-flag when needed, so if you come across a situation where the flag is
-necessary but missing, please report it via M-x report-emacs-bug.
-
-On platforms such as Solaris, you can also work around this problem by
-configuring your compiler to use the native linker instead of GNU ld.
-
-* Characters from the mule-unicode charsets aren't displayed under X.
+** Emacs pauses for several seconds when changing the default font.
+
+This has been reported for fvwm 2.2.5 and the window manager of KDE
+2.1.  The reason for the pause is Xt waiting for a ConfigureNotify
+event from the window manager, which the window manager doesn't send.
+Xt stops waiting after a default timeout of usually 5 seconds.
+
+A workaround for this is to add something like
+
+emacs.waitForWM: false
+
+to your X resources.  Alternatively, add `(wait-for-wm . nil)' to a
+frame's parameter list, like this:
+
+   (modify-frame-parameters nil '((wait-for-wm . nil)))
+
+(this should go into your `.emacs' file).
+
+** Underlines appear at the wrong position.
+
+This is caused by fonts having a wrong UNDERLINE_POSITION property.
+Examples are the font 7x13 on XFree prior to version 4.1, or the jmk
+neep font from the Debian xfonts-jmk package.  To circumvent this
+problem, set x-use-underline-position-properties to nil in your
+`.emacs'.
+
+To see what is the value of UNDERLINE_POSITION defined by the font,
+type `xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION
+property.
+
+** When using Exceed, fonts sometimes appear too tall.
+
+When the display is set to an Exceed X-server and fonts are specified
+(either explicitly with the -fn option or implicitly with X resources)
+then the fonts may appear "too tall".  The actual character sizes are
+correct but there is too much vertical spacing between rows,  which
+gives the appearance of "double spacing".
+
+To prevent this, turn off the Exceed's "automatic font substitution"
+feature (in the font part of the configuration window).
+
+* Internationalization problems
+
+** Characters from the mule-unicode charsets aren't displayed under X.

 XFree86 4 contains many fonts in iso10646-1 encoding which have
 minimal character repertoires (whereas the encoding part of the font
@@ -87,7 +849,7 @@
 mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
 mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1

-* The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
+** The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.

 Emacs by default only supports the parts of the Unicode BMP whose code
 points are in the ranges 0000-33ff and e000-ffff.  This excludes: most
@@ -108,26 +870,7 @@
 japanese- and korean- coding systems, e.g. cut and pasted from
 elsewhere.

-* Problems with file dialogs in Emacs built with Open Motif.
-
-When Emacs 21 is built with Open Motif 2.1, it can happen that the
-graphical file dialog boxes do not work properly.  The "OK", "Filter"
-and "Cancel" buttons do not respond to mouse clicks.  Dragging the
-file dialog window usually causes the buttons to work again.
-
-The solution is to use LessTif instead.  LessTif is a free replacement
-for Motif.  See the file INSTALL for information on how to do this.
-
-Another workaround is not to use the mouse to trigger file prompts,
-but to use the keyboard.  This way, you will be prompted for a file in
-the minibuffer instead of a graphical file dialog.
-
-* Emacs reports a BadAtom error (from X) running on Solaris 7 or 8.
-
-This happens when Emacs was built on some other version of Solaris.
-Rebuild it on Solaris 8.
-
-* Mule-UCS loads very slowly.
+** Mule-UCS loads very slowly.

 Changes to Emacs internals interact badly with Mule-UCS's `un-define'
 library, which is the usual interface to Mule-UCS.  Apply the
@@ -170,488 +913,7 @@
 Note that Emacs has native support for Unicode, roughly equivalent to
 Mule-UCS's, so you may not need it.

-* Building Emacs with GCC 2.9x fails in the `src' directory.
-
-This may happen if you use a development version of GNU `cpp' from one
-of the GCC snapshots between Oct 2000 and Feb 2001, or from a released
-version of GCC newer than 2.95.2 which was prepared around those
-dates; similar problems were reported with some snapshots of GCC 3.1
-around Sep 30 2001.  The preprocessor in those versions is
-incompatible with a traditional Unix cpp (e.g., it expands ".." into
-". .", which breaks relative file names that reference the parent
-directory; or inserts TAB characters before lines that set Make
-variables).
-
-The solution is to make sure the preprocessor is run with the
-`-traditional' option.  The `configure' script does that automatically
-when it detects the known problems in your cpp, but you might hit some
-unknown ones.  To force the `configure' script to use `-traditional',
-run the script like this:
-
-  CPP='gcc -E -traditional' ./configure ...
-
-(replace the ellipsis "..." with any additional arguments you pass to
-the script).
-
-Note that this problem does not pertain to the MS-Windows port of
-Emacs, since it doesn't use the preprocessor to generate Makefiles.
-
-* Building Emacs with a system compiler fails to link because of an
-undefined symbol such as __eprintf which does not appear in Emacs.
-
-This can happen if some of the libraries linked into Emacs were built
-with GCC, but Emacs itself is being linked with a compiler other than
-GCC.  Object files compiled with GCC might need some helper functions
-from libgcc.a, the library which comes with GCC, but the system
-compiler does not instruct the linker to search libgcc.a during the
-link stage.
-
-A solution is to link with GCC, like this:
-
-  	make CC=gcc
-
-Since the .o object files already exist, this will not recompile Emacs
-with GCC, but just restart by trying again to link temacs.
-
-* Building the MS-Windows port with Cygwin GCC can fail.
-
-Emacs may not build using recent Cygwin builds of GCC, such as Cygwin
-version 1.1.8, using the default configure settings.  It appears to be
-necessary to specify the -mwin32 flag when compiling, and define
-__MSVCRT__, like so:
-
-  configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__
-
-* Building the MS-Windows port fails with a CreateProcess failure.
-
-Some versions of mingw32 make on some versions of Windows do not seem
-to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
-fails, try running make from Cygwin bash instead.
-
-* Building the MS-Windows port with Leim fails in the `leim' directory.
-
-The error message might be something like this:
-
- Converting d:/emacs-21.3/leim/CXTERM-DIC/4Corner.tit to quail-package...
- Invalid ENCODE: value in TIT dictionary
- NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
-       '0xffffffff'
- Stop.
-
-This can happen if the Leim distribution is unpacked with a program
-which converts the `*.tit' files to DOS-style CR-LF text format.  The
-`*.tit' files in the leim/CXTERM-DIC directory require Unix-style line
-endings to compile properly, because Emacs reads them without any code
-or EOL conversions.
-
-The solution is to make sure the program used to unpack Leim does not
-change the files' line endings behind your back.  The GNU FTP site has
-in the `/gnu/emacs/windows' directory a program called `djtarnt.exe'
-which can be used to unpack `.tar.gz' and `.zip' archives without
-mangling them.
-
-* Emacs crashes when dumping itself on Mac PPC running Yellow Dog GNU/Linux.
-
-The crashes happen inside the function Fmake_symbol; here's a typical
-C backtrace printed by GDB:
-
-  0x190c0c0 in Fmake_symbol ()
-  (gdb) where
-  #0  0x190c0c0 in Fmake_symbol ()
-  #1  0x1942ca4 in init_obarray ()
-  #2  0x18b3500 in main ()
-  #3  0x114371c in __libc_start_main (argc=5, argv=0x7ffff5b4, envp=0x7ffff5cc,
-
-This could happen because GCC version 2.95 and later changed the base
-of the load address to 0x10000000.  Emacs needs to be told about this,
-but we currently cannot do that automatically, because that breaks
-other versions of GNU/Linux on the MacPPC.  Until we find a way to
-distinguish between the Yellow Dog and the other varieties of
-GNU/Linux systems on the PPC, you will have to manually uncomment the
-following section near the end of the file src/m/macppc.h in the Emacs
-distribution:
-
-  #if 0  /* This breaks things on PPC GNU/Linux except for Yellowdog,
-	    even with identical GCC, as, ld.  Let's take it out until we
-	    know what's really going on here.  */
-  /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to
-     0x10000000.  */
-  #if defined __linux__
-  #if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95)
-  #define DATA_SEG_BITS  0x10000000
-  #endif
-  #endif
-  #endif /* 0 */
-
-Remove the "#if 0" and "#endif" directives which surround this, save
-the file, and then reconfigure and rebuild Emacs.  The dumping process
-should now succeed.
-
-* JPEG images aren't displayed.
-
-This has been reported when Emacs is built with jpeg-6a library.
-Upgrading to jpeg-6b solves the problem.  Configure checks for the
-correct version, but this problem could occur if a binary built
-against a shared libjpeg is run on a system with an older version.
-
-* Building `ctags' for MS-Windows with the MinGW port of GCC fails.
-
-This might happen due to a bug in the MinGW header assert.h, which
-defines the `assert' macro with a trailing semi-colon.  The following
-patch to assert.h should solve this:
-
-*** include/assert.h.orig	Sun Nov  7 02:41:36 1999
---- include/assert.h	Mon Jan 29 11:49:10 2001
-***************
-*** 41,47 ****
-  /*
-   * If not debugging, assert does nothing.
-   */
-! #define assert(x)	((void)0);
-
-  #else /* debugging enabled */
-
---- 41,47 ----
-  /*
-   * If not debugging, assert does nothing.
-   */
-! #define assert(x)	((void)0)
-
-  #else /* debugging enabled */
-
-
-
-* Improving performance with slow X connections
-
-There are several ways to improve this performance, any subset of which can
-be carried out at the same time:
-
-1) If you don't need X Input Methods (XIM) for entering text in some
-   language you use, you can improve performance on WAN links by using
-   the X resource useXIM to turn off use of XIM.  This does not affect
-   the use of Emacs' own input methods, which are part of the Leim
-   package.
-
-2) If the connection is very slow, you might also want to consider
-   switching off scroll bars, menu bar, and tool bar.
-
-3) Use ssh to forward the X connection, and enable compression on this
-   forwarded X connection (ssh -XC remotehostname emacs ...).
-
-4) Use lbxproxy on the remote end of the connection.  This is an interface
-   to the low bandwidth X extension in most modern X servers, which
-   improves performance dramatically, at the slight expense of correctness
-   of the X protocol.  lbxproxy acheives the performance gain by grouping
-   several X requests in one TCP packet and sending them off together,
-   instead of requiring a round-trip for each X request in a seperate
-   packet.  The switches that seem to work best for emacs are:
-    -noatomsfile  -nowinattr  -cheaterrors -cheatevents
-   Note that the -nograbcmap option is known to cause problems.
-   For more about lbxproxy, see:
-   http://www.xfree86.org/4.3.0/lbxproxy.1.html
-
-* Getting a Meta key on the FreeBSD console
-
-By default, neither Alt nor any other key acts as a Meta key on
-FreeBSD, but this can be changed using kbdcontrol(1).  Dump the
-current keymap to a file with the command
-
-  $ kbdcontrol -d >emacs.kbd
-
-Edit emacs.kbd, and give the key you want to be the Meta key the
-definition `meta'.  For instance, if your keyboard has a ``Windows''
-key with scan code 105, change the line for scan code 105 in emacs.kbd
-to look like this
-
-  105   meta   meta   meta   meta   meta   meta   meta   meta    O
-
-to make the Windows key the Meta key.  Load the new keymap with
-
-  $ kbdcontrol -l emacs.kbd
-
-* Emacs' xterm-mouse-mode doesn't work on the Gnome terminal.
-
-A symptom of this bug is that double-clicks insert a control sequence
-into the buffer.  The reason this happens is an apparent
-incompatibility of the Gnome terminal with Xterm, which also affects
-other programs using the Xterm mouse interface.  A problem report has
-been filed.
-
-* Emacs pauses for several seconds when changing the default font
-
-This has been reported for fvwm 2.2.5 and the window manager of KDE
-2.1.  The reason for the pause is Xt waiting for a ConfigureNotify
-event from the window manager, which the window manager doesn't send.
-Xt stops waiting after a default timeout of usually 5 seconds.
-
-A workaround for this is to add something like
-
-emacs.waitForWM: false
-
-to your X resources.  Alternatively, add `(wait-for-wm . nil)' to a
-frame's parameter list, like this:
-
-   (modify-frame-parameters nil '((wait-for-wm . nil)))
-
-(this should go into your `.emacs' file).
-
-* Underlines appear at the wrong position.
-
-This is caused by fonts having a wrong UNDERLINE_POSITION property.
-Examples are the font 7x13 on XFree prior to version 4.1, or the jmk
-neep font from the Debian xfonts-jmk package.  To circumvent this
-problem, set x-use-underline-position-properties to nil in your
-`.emacs'.
-
-To see what is the value of UNDERLINE_POSITION defined by the font,
-type `xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION
-property.
-
-* When using Xaw3d scroll bars without arrows, the very first mouse
-click in a scroll bar might be ignored by the scroll bar widget.  This
-is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
-problem disappears.
-
-* There are known binary incompatibilities between Xaw, Xaw3d, neXtaw,
-XawM and the few other derivatives of Xaw.  So when you compile with
-one of these, it may not work to dynamically link with another one.
-For example, strange problems, such as Emacs exiting when you type
-"C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was
-used with neXtaw at run time.
-
-The solution is to rebuild Emacs with the toolkit version you actually
-want to use, or set LD_PRELOAD to preload the same toolkit version you
-built Emacs with.
-
-* Clicking C-mouse-2 in the scroll bar doesn't split the window.
-
-This currently doesn't work with scroll-bar widgets (and we don't know
-a good way of implementing it with widgets).  If Emacs is configured
---without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
-
-* Emacs aborts inside the function `tparam1'.
-
-This can happen if Emacs was built without terminfo support, but the
-terminal's capabilities use format that is only supported by terminfo.
-If your system has ncurses installed, this might happen if your
-version of ncurses is broken; upgrading to a newer version of ncurses
-and reconfiguring and rebuilding Emacs should solve this.
-
-All modern systems support terminfo, so even if ncurses is not the
-problem, you should look for a way to configure Emacs so that it uses
-terminfo when built.
-
-* Error messages about undefined colors on X.
-
-The messages might say something like this:
-
-   Unable to load color "grey95"
-
-(typically, in the `*Messages*' buffer), or something like this:
-
-  Error while displaying tooltip: (error Undefined color lightyellow)
-
-These problems could happen if some other X program has used up too
-many colors of the X palette, leaving Emacs with insufficient system
-resources to load all the colors it needs.
-
-A solution is to exit the offending X programs before starting Emacs.
-
-* Colors are not available on a tty or in xterm.
-
-Emacs 21 supports colors on character terminals and terminal
-emulators, but this support relies on the terminfo or termcap database
-entry to specify that the display supports color.  Emacs looks at the
-"Co" capability for the terminal to find out how many colors are
-supported; it should be non-zero to activate the color support within
-Emacs.  (Most color terminals support 8 or 16 colors.)  If your system
-uses terminfo, the name of the capability equivalent to "Co" is
-"colors".
-
-In addition to the "Co" capability, Emacs needs the "op" (for
-``original pair'') capability, which tells how to switch the terminal
-back to the default foreground and background colors.  Emacs will not
-use colors if this capability is not defined.  If your terminal entry
-doesn't provide such a capability, try using the ANSI standard escape
-sequence \E[00m (that is, define a new termcap/terminfo entry and make
-it use your current terminal's entry plus \E[00m for the "op"
-capability).
-
-Finally, the "NC" capability (terminfo name: "ncv") tells Emacs which
-attributes cannot be used with colors.  Setting this capability
-incorrectly might have the effect of disabling colors; try setting
-this capability to `0' (zero) and see if that helps.
-
-Emacs uses the database entry for the terminal whose name is the value
-of the environment variable TERM.  With `xterm', a common terminal
-entry that supports color is `xterm-color', so setting TERM's value to
-`xterm-color' might activate the color support on an xterm-compatible
-emulator.
-
-Beginning with version 21.4, Emacs supports the --color command-line
-option which may be used to force Emacs to use one of a few popular
-modes for getting colors on a tty.  For example, --color=ansi8 sets up
-for using the ANSI-standard escape sequences that support 8 colors.
-
-Some modes do not use colors unless you turn on the Font-lock mode.
-Some people have long ago set their `~/.emacs' files to turn on
-Font-lock on X only, so they won't see colors on a tty.  The
-recommended way of turning on Font-lock is by typing "M-x
-global-font-lock-mode RET" or by customizing the variable
-`global-font-lock-mode'.
-
-* Emacs on a tty switches the cursor to large blinking block.
-
-This was reported to happen on some GNU/Linux systems which use
-ncurses version 5.0, but could be relevant for other versions as well.
-These versions of ncurses come with a `linux' terminfo entry, where
-the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c"
-(show cursor, change size).  This escape sequence switches on a
-blinking hardware text-mode cursor whose size is a full character
-cell.  This blinking cannot be stopped, since a hardware cursor
-always blinks.
-
-A work-around is to redefine the "cvvis" capability so that it
-enables a *software* cursor.  The software cursor works by inverting
-the colors of the character at point, so what you see is a block
-cursor that doesn't blink.  For this to work, you need to redefine
-the "cnorm" capability as well, so that it operates on the software
-cursor instead of the hardware cursor.
-
-To this end, run "infocmp linux > linux-term", edit the file
-`linux-term' to make both the "cnorm" and "cvvis" capabilities send
-the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
-produce a modified terminfo entry.
-
-Alternatively, if you want a blinking underscore as your Emacs cursor,
-change the "cvvis" capability to send the "\E[?25h\E[?0c" command.
-
-* Problems in Emacs built with LessTif.
-
-The problems seem to depend on the version of LessTif and the Motif
-emulation for which it is set up.
-
-Only the Motif 1.2 emulation seems to be stable enough in LessTif.
-Lesstif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.
-On GNU/Linux systems, lesstif-0.92.6 configured with "./configure
---enable-build-12 --enable-default-12" is reported to be the most
-successful.  The binary GNU/Linux package
-lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with
-menu placement.
-
-On some systems, even with Motif 1.2 emulation, Emacs occasionally
-locks up, grabbing all mouse and keyboard events.  We still don't know
-what causes these problems; they are not reproducible by Emacs
-developers.
-
-* Known problems with the MS-Windows port of Emacs 21.2.
-
-Frames are not refreshed while the File or Font dialog or a pop-up menu
-is displayed. This also means help text for pop-up menus is not
-displayed at all.  This is because message handling under Windows is
-synchronous, so we cannot handle repaint (or any other) messages while
-waiting for a system function to return the result of the dialog or
-pop-up menu interaction.
-
-Windows 95 and Windows NT up to version 4.0 do not support help text
-for menus.  Help text is only available in later versions of Windows.
-
-There are problems with display if mouse-tracking is enabled and the
-mouse is moved off a frame, over another frame then back over the first
-frame.  A workaround is to click the left mouse button inside the frame
-after moving back into it.
-
-Some minor flickering still persists during mouse-tracking, although
-not as severely as in 21.1.
-
-Emacs can sometimes abort when non-ASCII text, possibly with null
-characters, is copied and pasted into a buffer.
-
-An inactive cursor remains in an active window after the Windows
-Manager driven switch of the focus, until a key is pressed.
-
-Windows input methods are not recognized by Emacs (as of v21.2).  Some
-of these input methods cause the keyboard to send characters encoded
-in the appropriate coding system (e.g., ISO 8859-1 for Latin-1
-characters, ISO 8859-8 for Hebrew characters, etc.).  To make this
-work, set the keyboard coding system to the appropriate value after
-you activate the Windows input method.  For example, if you activate
-the Hebrew input method, type "C-x RET k iso-8859-8 RET".  (Emacs
-ought to recognize the Windows language-change event and set up the
-appropriate keyboard encoding automatically, but it doesn't do that
-yet.)
-
-The %b specifier for format-time-string does not produce abbreviated
-month names with consistent widths for some locales on some versions
-of Windows. This is caused by a deficiency in the underlying system
-library function.
-
-* The `configure' script doesn't find the jpeg library.
-
-There are reports that this happens on some systems because the linker
-by default only looks for shared libraries, but jpeg distribution by
-default only installs a nonshared version of the library, `libjpeg.a'.
-
-If this is the problem, you can configure the jpeg library with the
-`--enable-shared' option and then rebuild libjpeg.  This produces a
-shared version of libjpeg, which you need to install.  Finally, rerun
-the Emacs configure script, which should now find the jpeg library.
-Alternatively, modify the generated src/Makefile to link the .a file
-explicitly, and edit src/config.h to define HAVE_JPEG.
-
-* Building Emacs over NFS fails with ``Text file busy''.
-
-This was reported to happen when building Emacs on a GNU/Linux system
-(RedHat Linux 6.2) using a build directory automounted from Solaris
-(SunOS 5.6) file server, but it might not be limited to that
-configuration alone.  Presumably, the NFS server doesn't commit the
-files' data to disk quickly enough, and the Emacs executable file is
-left ``busy'' for several seconds after Emacs has finished dumping
-itself.  This causes the subsequent commands which invoke the dumped
-Emacs executable to fail with the above message.
-
-In some of these cases, a time skew between the NFS server and the
-machine where Emacs is built is detected and reported by GNU Make
-(it says that some of the files have modification time in the future).
-This might be a symptom of NFS-related problems.
-
-If the NFS server runs on Solaris, apply the Solaris patch 105379-05
-(Sunos 5.6: /kernel/misc/nfssrv patch).  If that doesn't work, or if
-you have a different version of the OS or the NFS server, you can
-force the NFS server to use 1KB blocks, which was reported to fix the
-problem albeit at a price of slowing down file I/O.  You can force 1KB
-blocks by specifying the "-o  rsize=1024,wsize=1024" options to the
-`mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
-options in the appropriate system configuration file, such as
-`/etc/auto.home'.
-
-Alternatively, when Make fails due to this problem, you could wait for
-a few seconds and then invoke Make again.  In one particular case,
-waiting for 10 or more seconds between the two Make invocations seemed
-to work around the problem.
-
-Similar problems can happen if your machine NFS-mounts a directory
-onto itself.  Suppose the Emacs sources live in `/usr/local/src' and
-you are working on the host called `marvin'.  Then an entry in the
-`/etc/fstab' file like the following is asking for trouble:
-
-    marvin:/usr/local/src /usr/local/src ...options.omitted...
-
-The solution is to remove this line from `etc/fstab'.
-
-* Emacs binary is not in executable format, and cannot be run.
-
-This was reported to happen when Emacs is built in a directory mounted
-via NFS, for some combinations of NFS client and NFS server.
-Usually, the file `emacs' produced in these cases is full of
-binary null characters, and the `file' utility says:
-
-    emacs: ASCII text, with no line terminators
-
-We don't know what exactly causes this failure.  A work-around is to
-build Emacs in a directory on a local disk.
-
-* Accented ISO-8859-1 characters are displayed as | or _.
+** Accented ISO-8859-1 characters are displayed as | or _.

 Try other font set sizes (S-mouse-1).  If the problem persists with
 other sizes as well, your text is corrupted, probably through software
@@ -671,152 +933,7 @@
 `fonts.alias' file, then run `mkfontdir' in that directory, and then run
 `xset fp rehash'.

-* Large file support is disabled on HP-UX.  See the comments in
-src/s/hpux10.h.
-
-* Crashes when displaying GIF images in Emacs built with version
-libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
-Configure checks for the correct version, but this problem could occur
-if a binary built against a shared libungif is run on a system with an
-older version.
-
-* Font Lock displays portions of the buffer in incorrect faces.
-
-By far the most frequent cause of this is a parenthesis `(' or a brace
-`{' in column zero.  Font Lock assumes that such a paren is outside of
-any comment or string.  This is of course not true in general, but the
-vast majority of well-formatted program source files don't have such
-parens, and therefore this assumption is used to allow optimizations
-in Font Lock's syntactical analysis.  These optimizations avoid some
-pathological cases where jit-lock, the Just-in-Time fontification
-introduced with Emacs 21.1, could significantly slow down scrolling
-through the buffer, especially scrolling backwards, and also jumping
-to the end of a very large buffer.
-
-Beginning with version 21.4, a parenthesis or a brace in column zero
-is highlighted in bold-red face if it is inside a string or a comment,
-to indicate that it could interfere with Font Lock (and also with
-indentation) and should be moved or escaped with a backslash.
-
-If you don't use large buffers, or have a very fast machine which
-makes the delays insignificant, you can avoid the incorrect
-fontification by setting the variable
-`font-lock-beginning-of-syntax-function' to a nil value.  (This must
-be done _after_ turning on Font Lock.)
-
-Another alternative is to avoid a paren in column zero.  For example,
-in a Lisp string you could precede the paren with a backslash.
-
-* When running on KDE, colors or fonts are not as specified for Emacs,
-or messed up.
-
-For example, you could see background you set for Emacs only in the
-empty portions of the Emacs display, while characters have some other
-background.
-
-This happens because KDE's defaults apply its color and font
-definitions even to applications that weren't compiled for KDE.  The
-solution is to uncheck the "Apply fonts and colors to non-KDE apps"
-option in Preferences->Look&Feel->Style (KDE 2).  In KDE 3, this option
-is in the "Colors" section, rather than "Style".
-
-Alternatively, if you do want the KDE defaults to apply to other
-applications, but not to Emacs, you could modify the file `Emacs.ad'
-(should be in the `/usr/share/apps/kdisplay/app-defaults/' directory)
-so that it doesn't set the default background and foreground only for
-Emacs.  For example, make sure the following resources are either not
-present or commented out:
-
-   Emacs.default.attributeForeground
-   Emacs.default.attributeBackground
-   Emacs*Foreground
-   Emacs*Background
-
-* Interrupting Cygwin port of Bash from Emacs doesn't work.
-
-Cygwin 1.x builds of the ported Bash cannot be interrupted from the
-MS-Windows version of Emacs.  This is due to some change in the Bash
-port or in the Cygwin library which apparently make Bash ignore the
-keyboard interrupt event sent by Emacs to Bash.  (Older Cygwin ports
-of Bash, up to b20.1, did receive SIGINT from Emacs.)
-
-* Dired is very slow.
-
-This could happen if invocation of the `df' program takes a long
-time.  Possible reasons for this include:
-
-  - ClearCase mounted filesystems (VOBs) that sometimes make `df'
-    response time extremely slow (dozens of seconds);
-
-  - slow automounters on some old versions of Unix;
-
-  - slow operation of some versions of `df'.
-
-To work around the problem, you could either (a) set the variable
-`directory-free-space-program' to nil, and thus prevent Emacs from
-invoking `df'; (b) use `df' from the GNU Fileutils package; or
-(c) use CVS, which is Free Software, instead of ClearCase.
-
-* Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
-
-If the FTP client is the Cygwin port of GNU `ftp', this appears to be
-due to some bug in the Cygwin DLL or some incompatibility between it
-and the implementation of asynchronous subprocesses in the Windows
-port of Emacs.  Specifically, some parts of the FTP server responses
-are not flushed out, apparently due to buffering issues, which
-confuses ange-ftp.
-
-The solution is to downgrade to an older version of the Cygwin DLL
-(version 1.3.2 was reported to solve the problem), or use the stock
-Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
-directory.  To force ange-ftp use the stock Windows client, set the
-variable `ange-ftp-ftp-program-name' to the absolute file name of the
-client's executable.  For example:
-
- (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
-
-If you want to stick with the Cygwin FTP client, you can work around
-this problem by putting this in your `.emacs' file:
-
- (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
-
-* Versions of the W3 package released before Emacs 21.1 don't run
-under Emacs 21.  This fixed in W3 version 4.0pre.47.
-
-* On AIX, if linking fails because libXbsd isn't found, check if you
-are compiling with the system's `cc' and CFLAGS containing `-O5'.  If
-so, you have hit a compiler bug.  Please make sure to re-configure
-Emacs so that it isn't compiled with `-O5'.
-
-* Compiling on AIX 4.3.x or 4.4 fails.
-
-This could happen if you use /bin/c89 as your compiler, instead of
-the default `cc'.  /bin/c89 treats certain warnings, such as benign
-redefinitions of macros, as errors, and fails the build.  A solution
-is to use the default compiler `cc'.
-
-* Old versions of the PSGML package use the obsolete variables
-`before-change-function' and `after-change-function', which are no
-longer used by Emacs.  Please use PSGML 1.2.3 or later.
-
-* PSGML conflicts with sgml-mode.
-
-PSGML package uses the same names of some variables (like keymap)
-as built-in sgml-mode.el because it was created as a replacement
-of that package.  The conflict will be shown if you load
-sgml-mode.el before psgml.el.  E.g. this could happen if you edit
-HTML page and then start to work with SGML or XML file.  html-mode
-(from sgml-mode.el) is used for HTML file and loading of psgml.el
-(for sgml-mode or xml-mode) will cause an error.
-
-* The LDAP support rely on ldapsearch program from OpenLDAP version 2.
-
-It can fail to work with ldapsearch program from OpenLDAP version 1.
-Version 1 of OpenLDAP is now deprecated.  If you are still using it,
-please upgrade to version 2.  As a temporary workaround, remove
-argument "-x" from the variable `ldap-ldapsearch-args'.
-
-* The `oc-unicode' package doesn't work with Emacs 21.
+** The `oc-unicode' package doesn't work with Emacs 21.

 This package tries to define more private charsets than there are free
 slots now.  The current built-in Unicode support is actually more
@@ -824,1805 +941,18 @@
 support.)  Files encoded as emacs-mule using oc-unicode aren't
 generally read correctly by Emacs 21.

-* Using epop3.el package causes Emacs to signal an error.
-
-The error message might be something like this:
-
-  "Lisp nesting exceeds max-lisp-eval-depth"
-
-This happens because epop3 redefines the function gethash, which is a
-built-in primitive beginning with Emacs 21.1.  We don't have a patch
-for epop3 that fixes this, but perhaps a newer version of epop3
-corrects that.
-
-* ps-print commands fail to find prologue files ps-prin*.ps.
-
-This can happen if you use an old version of X-Symbol package: it
-defines compatibility functions which trick ps-print into thinking it
-runs in XEmacs, and look for the prologue files in a wrong directory.
-
-The solution is to upgrade X-Symbol to a later version.
-
-* lpr commands don't work on MS-Windows with some cheap printers.
-
-This problem may also strike other platforms, but the solution is
-likely to be a global one, and not Emacs specific.
-
-Many cheap inkjet, and even some cheap laser printers, do not
-print plain text anymore, they will only print through graphical
-printer drivers. A workaround on MS-Windows is to use Windows' basic
-built in editor to print (this is possibly the only useful purpose it
-has):
-
-(setq printer-name "")         ;; notepad takes the default
-(setq lpr-command "notepad")   ;; notepad
-(setq lpr-switches nil)        ;; not needed
-(setq lpr-printer-switch "/P") ;; run notepad as batch printer
-
-* On systems with shared libraries you might encounter run-time errors
-from the dynamic linker telling you that it is unable to find some
-shared libraries, for instance those for Xaw3d or image support.
-These errors mean Emacs has been linked with a library whose shared
-library is not in the default search path of the dynamic linker.
-
-Similar problems could prevent Emacs from building, since the build
-process invokes Emacs several times.
-
-On many systems, it is possible to set LD_LIBRARY_PATH in your
-environment to specify additional directories where shared libraries
-can be found.
-
-Other systems allow to set LD_RUN_PATH in a similar way, but before
-Emacs is linked.  With LD_RUN_PATH set, the linker will include a
-specified run-time search path in the executable.
-
-On some systems, Emacs can crash due to problems with dynamic
-linking.  Specifically, on SGI Irix 6.5, crashes were reported with
-backtraces like this:
-
-  (dbx) where
-   0 strcmp(0xf49239d, 0x4031184, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2) ["/xlv22/ficus-jan23/work/irix/lib/libc/libc_n32_M3_ns/strings/strcmp.s":35, 0xfb7e480]
-   1 general_find_symbol(0xf49239d, 0x0, 0x0, 0x0, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
- ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":2140, 0xfb65a98]
-   2 resolve_symbol(0xf49239d, 0x4031184, 0x0, 0xfbdd438, 0x0, 0xf4923aa, 0x0, 0x492ddb2)
- ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":1947, 0xfb657e4]
-   3 lazy_text_resolve(0xd18, 0x1a3, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
- ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":997, 0xfb64d44]
-   4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
- ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
-
-(`rld' is the dynamic linker.)  We don't know yet why this
-happens, but setting the environment variable LD_BIND_NOW to 1 (which
-forces the dynamic linker to bind all shared objects early on) seems
-to work around the problem.
-
-Please refer to the documentation of your dynamic linker for details.
-
-* On Solaris 2.7, building Emacs with WorkShop Compilers 5.0 98/12/15
-C 5.0 failed, apparently with non-default CFLAGS, most probably due to
-compiler bugs.  Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C
-release was reported to work without problems.  It worked OK on
-another system with Solaris 8 using apparently the same 5.0 compiler
-and the default CFLAGS.
-
-* Compiling syntax.c with the OPENSTEP 4.2 compiler gcc 2.7.2.1 fails.
-
-The compiler was reported to crash while compiling syntax.c with the
-following message:
-
-   cc: Internal compiler error: program cc1obj got fatal signal 11
-
-To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD,
-INC_BOTH, and INC_FROM with functions.  To this end, first define 3
-functions, one each for every macro.  Here's an example:
-
-    static int update_syntax_table_forward(int from)
-    {
-        return(UPDATE_SYNTAX_TABLE_FORWARD(from));
-    }/*update_syntax_table_forward*/
-
-Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c
-with a call to the function update_syntax_table_forward.
-
-* Emacs fails to start, complaining about missing fonts.
-
-A typical error message might be something like
-
-  No fonts match `-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1'
-
-This happens because some X resource specifies a bad font family for
-Emacs to use.  The possible places where this specification might be
-are:
-
-  - in your ~/.Xdefaults file
-
-  - client-side X resource file, such as  ~/Emacs or
-    /usr/X11R6/lib/app-defaults/Emacs or
-    /usr/X11R6/lib/X11/app-defaults/Emacs
-
-One of these files might have bad or malformed specification of a
-fontset that Emacs should use.  To fix the problem, you need to find
-the problematic line(s) and correct them.
-
-* Emacs 20 and later fails to load Lisp files at startup.
-
-The typical error message might be like this:
-
-  "Cannot open load file: fontset"
-
-This could happen if you compress the file lisp/subdirs.el.  That file
-tells Emacs what are the directories where it should look for Lisp
-files.  Emacs cannot work with subdirs.el compressed, since the
-Auto-compress mode it needs for this will not be loaded until later,
-when your .emacs file is processed.  (The package `fontset.el' is
-required to set up fonts used to display text on window systems, and
-it's loaded very early in the startup procedure.)
-
-Similarly, any other .el file for which there's no corresponding .elc
-file could fail to load if it is compressed.
-
-The solution is to uncompress all .el files which don't have a .elc
-file.
-
-Another possible reason for such failures is stale *.elc files
-lurking somewhere on your load-path.  The following command will
-print any duplicate Lisp files that are present in load-path:
-
-    emacs -q -batch -f list-load-path-shadows
-
-If this command prints any file names, some of these files are stale,
-and should be deleted or their directories removed from your
-load-path.
-
-* Emacs prints an error at startup after upgrading from an earlier version.
-
-An example of such an error is:
-
-  x-complement-fontset-spec: "Wrong type argument: stringp, nil"
-
-This can be another symptom of stale *.elc files in your load-path.
-The following command will print any duplicate Lisp files that are
-present in load-path:
-
-    emacs -q -batch -f list-load-path-shadows
-
-If this command prints any file names, some of these files are stale,
-and should be deleted or their directories removed from your
-load-path.
-
-* Attempting to visit remote files via ange-ftp fails.
-
-If the error message is "ange-ftp-file-modtime: Specified time is not
-representable", then this could happen when `lukemftp' is used as the
-ftp client.  This was reported to happen on Debian GNU/Linux, kernel
-version 2.4.3, with `lukemftp' 1.5-5, but might happen on other
-systems as well.  To avoid this problem, switch to using the standard
-ftp client.  On a Debian system, type
-
-  update-alternatives --config ftp
-
-and then choose /usr/bin/netkit-ftp.
-
-* Antivirus software interacts badly with the MS-Windows version of Emacs.
-
-The usual manifestation of these problems is that subprocesses don't
-work or even wedge the entire system.  In particular, "M-x shell RET"
-was reported to fail to work.  But other commands also sometimes don't
-work when an antivirus package is installed.
-
-The solution is to switch the antivirus software to a less aggressive
-mode (e.g., disable the ``auto-protect'' feature), or even uninstall
-or disable it entirely.
-
-* On MS-Windows 95/98/ME, subprocesses do not terminate properly.
-
-This is a limitation of the Operating System, and can cause problems
-when shutting down Windows. Ensure that all subprocesses are exited
-cleanly before exiting Emacs. For more details, see the FAQ at
-http://www.gnu.org/software/emacs/windows/.
-
-* MS-Windows 95/98/ME crashes when Emacs invokes non-existent programs.
-
-When a program you are trying to run is not found on the PATH,
-Windows might respond by crashing or locking up your system.  In
-particular, this has been reported when trying to compile a Java
-program in JDEE when javac.exe is installed, but not on the system
-PATH.
-
-* Pressing the mouse button on MS-Windows does not give a mouse-2 event.
-
-This is usually a problem with the mouse driver. Because most Windows
-programs do not do anything useful with the middle mouse button, many
-mouse drivers allow you to define the wheel press to do something
-different. Some drivers do not even have the option to generate a
-middle button press. In such cases, setting the wheel press to
-"scroll" sometimes works if you press the button twice. Trying a
-generic mouse driver might help.
-
-* Scrolling the mouse wheel on MS-Windows always scrolls the top window.
-
-This is another common problem with mouse drivers. Instead of
-generating scroll events, some mouse drivers try to fake scroll bar
-movement. But they are not intelligent enough to handle multiple
-scroll bars within a frame. Trying a generic mouse driver might help.
-
-* Mail sent through Microsoft Exchange in some encodings appears to be
-mangled and is not seen correctly in Rmail or Gnus.  We don't know
-exactly what happens, but it isn't an Emacs problem in cases we've
-seen.
-
-* After upgrading to a newer version of Emacs, the Meta key stops working.
-
-This was reported to happen on a GNU/Linux system distributed by
-Mandrake.  The reason is that the previous version of Emacs was
-modified by Mandrake to make the Alt key act as the Meta key, on a
-keyboard where the Windows key is the one which produces the Meta
-modifier.  A user who started using a newer version of Emacs, which
-was not hacked by Mandrake, expected the Alt key to continue to act as
-Meta, and was astonished when that didn't happen.
-
-The solution is to find out what key on your keyboard produces the Meta
-modifier, and use that key instead.  Try all of the keys to the left
-and to the right of the space bar, together with the `x' key, and see
-which combination produces "M-x" in the echo area.  You can also use
-the `xmodmap' utility to show all the keys which produce a Meta
-modifier:
-
-         xmodmap -pk | egrep -i "meta|alt"
-
-A more convenient way of finding out which keys produce a Meta modifier
-is to use the `xkbprint' utility, if it's available on your system:
-
-         xkbprint 0:0 /tmp/k.ps
-
-This produces a PostScript file `/tmp/k.ps' with a picture of your
-keyboard; printing that file on a PostScript printer will show what
-keys can serve as Meta.
-
-The `xkeycaps' also shows a visual representation of the current
-keyboard settings.  It also allows to modify them.
-
-* On OSF/Dec Unix/Tru64/<whatever it is this year> under X locally or
-remotely, M-SPC acts as a `compose' key with strange results.  See
-keyboard(5).
-
-Changing Alt_L to Meta_L fixes it:
-% xmodmap -e 'keysym Alt_L = Meta_L Alt_L'
-% xmodmap -e 'keysym Alt_R = Meta_R Alt_R'
-
-* Error "conflicting types for `initstate'" compiling with GCC on Irix 6.
-
-Install GCC 2.95 or a newer version, and this problem should go away.
-It is possible that this problem results from upgrading the operating
-system without reinstalling GCC; so you could also try reinstalling
-the same version of GCC, and telling us whether that fixes the problem.
-
-* Emacs dumps core on Solaris in function IMCheckWindow.
-
-This was reported to happen when Emacs runs with more than one frame,
-and one of them is closed, either with "C-x 5 0" or from the window
-manager.
-
-This bug was reported to Sun as
-
-    Gtk apps dump core in ximlocal.so.2:IMCheckIMWindow()
-    Bug Reports: 4463537
-
-Installing Solaris 8 patch 108773-12 for Sparc and 108774-12 for x86
-reportedly fixes the bug, which appears to be inside the shared
-library xiiimp.so.
-
-Alternatively, you can configure Emacs with `--with-xim=no' to prevent
-the core dump, but will loose X input method support, of course.  (You
-can use Emacs's own input methods instead, if you install Leim.)
-
-* On Solaris 7, Emacs gets a segmentation fault when starting up using X.
-
-This results from Sun patch 107058-01 (SunOS 5.7: Patch for
-assembler) if you use GCC version 2.7 or later.
-To work around it, either install patch 106950-03 or later,
-or uninstall patch 107058-01, or install the GNU Binutils.
-Then recompile Emacs, and it should work.
-
-* With X11R6.4, public-patch-3, Emacs crashes at startup.
-
-Reportedly this patch in X fixes the problem.
-
-    --- xc/lib/X11/imInt.c~	Wed Jun 30 13:31:56 1999
-    +++ xc/lib/X11/imInt.c	Thu Jul  1 15:10:27 1999
-    @@ -1,4 +1,4 @@
-    -/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */
-    +/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $  */
-     /******************************************************************
-
-		Copyright 1992, 1993, 1994 by FUJITSU LIMITED
-    @@ -166,8 +166,8 @@
-     _XimMakeImName(lcd)
-	 XLCd	   lcd;
-     {
-    -    char* begin;
-    -    char* end;
-    +    char* begin = NULL;
-    +    char* end = NULL;
-	 char* ret;
-	 int	i = 0;
-	 char* ximmodifier = XIMMODIFIER;
-    @@ -182,7 +182,11 @@
-	 }
-	 ret = Xmalloc(end - begin + 2);
-	 if (ret != NULL) {
-    -    	(void)strncpy(ret, begin, end - begin + 1);
-    +	if (begin != NULL) {
-    +      	  (void)strncpy(ret, begin, end - begin + 1);
-    +        } else {
-    +	  ret[0] = '\0';
-    +	}
-	    ret[end - begin + 1] = '\0';
-	 }
-	 return ret;
-
-
-* Emacs crashes on Irix 6.5 on the SGI R10K, when compiled with GCC.
-
-This seems to be fixed in GCC 2.95.
-
-* Emacs crashes in utmpname on Irix 5.3.
-
-This problem is fixed in Patch 3175 for Irix 5.3.
-It is also fixed in Irix versions 6.2 and up.
-
-* The S-C-t key combination doesn't get passed to Emacs on X.
-
-This happens because some X configurations assign the Ctrl-Shift-t
-combination the same meaning as the Multi_key.  The offending
-definition is in the file `...lib/X11/locale/iso8859-1/Compose'; there
-might be other similar combinations which are grabbed by X for similar
-purposes.
-
-We think that this can be countermanded with the `xmodmap' utility, if
-you want to be able to bind one of these key sequences within Emacs.
-
-* On Solaris, CTRL-t is ignored by Emacs when you use
-the fr.ISO-8859-15 locale (and maybe other related locales).
-
-You can fix this by editing the file:
-
-	/usr/openwin/lib/locale/iso8859-15/Compose
-
-Near the bottom there is a line that reads:
-
-	Ctrl<t> <quotedbl> <Y>                  : "\276"        threequarters
-
-that should read:
-
-	Ctrl<T> <quotedbl> <Y>                  : "\276"        threequarters
-
-Note the lower case <t>.  Changing this line should make C-t work.
-
-* Emacs on Digital Unix 4.0 fails to build, giving error message
-     Invalid dimension for the charset-ID 160
-
-This is due to a bug or an installation problem in GCC 2.8.0.
-Installing a more recent version of GCC fixes the problem.
-
-* Buffers from `with-output-to-temp-buffer' get set up in Help mode.
-
-Changes in Emacs 20.4 to the hooks used by that function cause
-problems for some packages, specifically BBDB.  See the function's
-documentation for the hooks involved.  BBDB 2.00.06 fixes the problem.
-
-* Under X, C-v and/or other keys don't work.
-
-These may have been intercepted by your window manager.  In
-particular, AfterStep 1.6 is reported to steal C-v in its default
-configuration.  Various Meta keys are also likely to be taken by the
-configuration of the `feel'.  See the WM's documentation for how to
-change this.
-
-* When using Exceed, fonts sometimes appear too tall.
-
-When the display is set to an Exceed X-server and fonts are specified
-(either explicitly with the -fn option or implicitly with X resources)
-then the fonts may appear "too tall".  The actual character sizes are
-correct but there is too much vertical spacing between rows,  which
-gives the appearance of "double spacing".
-
-To prevent this, turn off the Exceed's "automatic font substitution"
-feature (in the font part of the configuration window).
-
-* Failure in unexec while dumping emacs on Digital Unix 4.0
-
-This problem manifests itself as an error message
-
-    unexec: Bad address, writing data section to ...
-
-The user suspects that this happened because his X libraries
-were built for an older system version,
-
-    ./configure --x-includes=/usr/include --x-libraries=/usr/shlib
-
-made the problem go away.
-
-* No visible display on mips-sgi-irix6.2 when compiling with GCC 2.8.1.
-
-This problem went away after installing the latest IRIX patches
-as of 8 Dec 1998.
-
-The same problem has been reported on Irix 6.3.
-
-* As of version 20.4, Emacs doesn't work properly if configured for
-the Motif toolkit and linked against the free LessTif library.  The
-next Emacs release is expected to work with LessTif.
-
-* Emacs gives the error, Couldn't find per display information.
-
-This can result if the X server runs out of memory because Emacs uses
-a large number of fonts.  On systems where this happens, C-h h is
-likely to cause it.
-
-We do not know of a way to prevent the problem.
-
-* Emacs makes HPUX 11.0 crash.
-
-This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it.
-
-* Emacs crashes during dumping on the HPPA machine (HPUX 10.20).
-
-This seems to be due to a GCC bug; it is fixed in GCC 2.8.1.
-
-* The Hyperbole package causes *Help* buffers not to be displayed in
-Help mode due to setting `temp-buffer-show-hook' rather than using
-`add-hook'.  Using `(add-hook 'temp-buffer-show-hook
-'help-mode-maybe)' after loading Hyperbole should fix this.
-
-* Versions of the PSGML package earlier than 1.0.3 (stable) or 1.1.2
-(alpha) fail to parse DTD files correctly in Emacs 20.3 and later.
-Here is a patch for psgml-parse.el from PSGML 1.0.1 and, probably,
-earlier versions.
-
---- psgml-parse.el	1998/08/21 19:18:18	1.1
-+++ psgml-parse.el	1998/08/21 19:20:00
-@@ -2383,7 +2383,7 @@ (defun sgml-push-to-entity (entity &opti
-       (setq sgml-buffer-parse-state nil))
-     (cond
-      ((stringp entity)			; a file name
--      (save-excursion (insert-file-contents entity))
-+      (insert-file-contents entity)
-       (setq default-directory (file-name-directory entity)))
-      ((consp (sgml-entity-text entity)) ; external id?
-       (let* ((extid (sgml-entity-text entity))
-
-* Emacs 21 freezes when visiting a TeX file with AUC TeX installed.
-
-Emacs 21 needs version 10 or later of AUC TeX; upgrading should solve
-these problems.
-
-* No colors in AUC TeX with Emacs 21.
-
-Upgrade to AUC TeX version 10 or later, and make sure it is
-byte-compiled with Emacs 21.
-
-* Running TeX from AUC TeX package with Emacs 20.3 gives a Lisp error
-about a read-only tex output buffer.
-
-This problem appeared for AUC TeX version 9.9j and some earlier
-versions.  Here is a patch for the file tex-buf.el in the AUC TeX
-package.
-
-diff -c auctex/tex-buf.el~ auctex/tex-buf.el
-*** auctex/tex-buf.el~	Wed Jul 29 18:35:32 1998
---- auctex/tex-buf.el	Sat Sep  5 15:20:38 1998
-***************
-*** 545,551 ****
-  	(dir (TeX-master-directory)))
-      (TeX-process-check file)		; Check that no process is running
-      (setq TeX-command-buffer (current-buffer))
-!     (with-output-to-temp-buffer buffer)
-      (set-buffer buffer)
-      (if dir (cd dir))
-      (insert "Running `" name "' on `" file "' with ``" command "''\n")
-- --- 545,552 ----
-  	(dir (TeX-master-directory)))
-      (TeX-process-check file)		; Check that no process is running
-      (setq TeX-command-buffer (current-buffer))
-!     (let (temp-buffer-show-function temp-buffer-show-hook)
-!       (with-output-to-temp-buffer buffer))
-      (set-buffer buffer)
-      (if dir (cd dir))
-      (insert "Running `" name "' on `" file "' with ``" command "''\n")
-
-* On Irix 6.3, substituting environment variables in file names
-in the minibuffer gives peculiar error messages such as
-
-   Substituting nonexistent environment variable ""
-
-This is not an Emacs bug; it is caused by something in SGI patch
-003082 August 11, 1998.
-
-* After a while, Emacs slips into unibyte mode.
+** After a while, Emacs slips into unibyte mode.

 The VM mail package, which is not part of Emacs, sometimes does
   (standard-display-european t)
 That should be changed to
   (standard-display-european 1 t)

-* Installing Emacs gets an error running `install-info'.
-
-You need to install a recent version of Texinfo; that package
-supplies the `install-info' command.
-
-* Emacs does not recognize the AltGr key, on HPUX.
-
-To fix this, set up a file ~/.dt/sessions/sessionetc with executable
-rights, containing this text:
-
---------------------------------
-xmodmap 2> /dev/null - << EOF
-keysym Alt_L = Meta_L
-keysym Alt_R = Meta_R
-EOF
-
-xmodmap - << EOF
-clear mod1
-keysym Mode_switch = NoSymbol
-add mod1 = Meta_L
-keysym Meta_R = Mode_switch
-add mod2 = Mode_switch
-EOF
---------------------------------
-
-* Emacs hangs on KDE when a large portion of text is killed.
-
-This is caused by a bug in the KDE applet `klipper' which periodically
-requests the X clipboard contents from applications.  Early versions
-of klipper don't implement the ICCM protocol for large selections,
-which leads to Emacs being flooded with selection requests.  After a
-while, Emacs will print a message:
-
-  Timed out waiting for property-notify event
-
-A workaround is to not use `klipper'.
-
-* Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files
-in the directory with the special name `dev' under the root of any
-drive, e.g. `c:/dev'.
-
-This is an unfortunate side-effect of the support for Unix-style
-device names such as /dev/null in the DJGPP runtime library.  A
-work-around is to rename the problem directory to another name.
-
-* M-SPC seems to be ignored as input.
-
-See if your X server is set up to use this as a command
-for character composition.
-
-* Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
-
-This can happen if the system is misconfigured and Emacs can't get the
-full qualified domain name, FQDN.  You should have your FQDN in the
-/etc/hosts file, something like this:
-
-127.0.0.1	localhost
-129.187.137.82	nuc04.t30.physik.tu-muenchen.de	nuc04
-
-The way to set this up may vary on non-GNU systems.
-
-* Garbled display on non-X terminals when Emacs runs on Digital Unix 4.0.
-
-So far it appears that running `tset' triggers this problem (when TERM
-is vt100, at least).  If you do not run `tset', then Emacs displays
-properly.  If someone can tell us precisely which effect of running
-`tset' actually causes the problem, we may be able to implement a fix
-in Emacs.
-
-* When you run Ispell from Emacs, it reports a "misalignment" error.
-
-This can happen if you compiled the Ispell program to use ASCII
-characters only and then try to use it from Emacs with non-ASCII
-characters, like Latin-1.  The solution is to recompile Ispell with
-support for 8-bit characters.
-
-To see whether your Ispell program supports 8-bit characters, type
-this at your shell's prompt:
-
-     ispell -vv
-
-and look in the output for the string "NO8BIT".  If Ispell says
-"!NO8BIT (8BIT)", your speller supports 8-bit characters; otherwise it
-does not.
-
-To rebuild Ispell with 8-bit character support, edit the local.h file
-in the Ispell distribution and make sure it does _not_ define NO8BIT.
-Then rebuild the speller.
-
-Another possible cause for "misalignment" error messages is that the
-version of Ispell installed on your machine is old.  Upgrade.
-
-Yet another possibility is that you are trying to spell-check a word
-in a language that doesn't fit the dictionary you choose for use by
-Ispell.  (Ispell can only spell-check one language at a time, because
-it uses a single dictionary.)  Make sure that the text you are
-spelling and the dictionary used by Ispell conform to each other.
-
-If your spell-checking program is Aspell, it has been reported that if
-you have a personal configuration file (normally ~/.aspell.conf), it
-can cause this error.  Remove that file, execute `ispell-kill-ispell'
-in Emacs, and then try spell-checking again.
-
-* On Linux-based GNU systems using libc versions 5.4.19 through
-5.4.22, Emacs crashes at startup with a segmentation fault.
-
-This problem happens if libc defines the symbol __malloc_initialized.
-One known solution is to upgrade to a newer libc version.  5.4.33 is
-known to work.
-
-* On MS-Windows, you cannot use the right-hand ALT key and the left-hand
-CTRL key together to type a Control-Meta character.
-
-This is a consequence of a misfeature beyond Emacs's control.
-
-Under Windows, the AltGr key on international keyboards generates key
-events with the modifiers Right-Alt and Left-Ctrl.  Since Emacs cannot
-distinguish AltGr from an explicit Right-Alt and Left-Ctrl
-combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
-AltGr has been pressed.  The variable `w32-recognize-altgr' can be set
-to nil to tell Emacs that AltGr is really Ctrl and Alt.
-
-* Emacs crashes when using the Exceed 6.0 X server
-
-If you are using Exceed 6.1, upgrade to a later version.  This was
-reported to prevent the crashes.
-
-* Under some X-servers running on MS-Windows, Emacs' display is incorrect
-
-The symptoms are that Emacs does not completely erase blank areas of the
-screen during scrolling or some other screen operations (e.g., selective
-display or when killing a region).  M-x recenter will cause the screen
-to be completely redisplayed and the "extra" characters will disappear.
-
-This is known to occur under Exceed 6, and possibly earlier versions
-as well; it is reportedly solved in version 6.2.0.16 and later.  The
-problem lies in the X-server settings.
-
-There are reports that you can solve the problem with Exceed by
-running `Xconfig' from within NT, choosing "X selection", then
-un-checking the boxes "auto-copy X selection" and "auto-paste to X
-selection".
-
-Of this does not work, please inform bug-gnu-emacs@gnu.org.  Then
-please call support for your X-server and see if you can get a fix.
-If you do, please send it to bug-gnu-emacs@gnu.org so we can list it
-here.
-
-* On Solaris 2, Emacs dumps core when built with Motif.
-
-The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1.
-Install the current Motif runtime library patch appropriate for your host.
-(Make sure the patch is current; some older patch versions still have the bug.)
-You should install the other patches recommended by Sun for your host, too.
-You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/;
-look for files with names ending in `.PatchReport' to see which patches
-are currently recommended for your host.
-
-On Solaris 2.6, Emacs is said to work with Motif when Solaris patch
-105284-12 is installed, but fail when 105284-15 is installed.
-105284-18 might fix it again.
-
-* On Solaris 2.6 and 7, the Compose key does not work.
-
-This is a bug in Motif in Solaris.  Supposedly it has been fixed for
-the next major release of Solaris.  However, if someone with Sun
-support complains to Sun about the bug, they may release a patch.
-If you do this, mention Sun bug #4188711.
-
-One workaround is to use a locale that allows non-ASCII characters.
-For example, before invoking emacs, set the LC_ALL environment
-variable to "en_US" (American English).  The directory /usr/lib/locale
-lists the supported locales; any locale other than "C" or "POSIX"
-should do.
-
-pen@lysator.liu.se says (Feb 1998) that the Compose key does work
-if you link with the MIT X11 libraries instead of the Solaris X11
-libraries.
-
-* Frames may cover dialogs they created when using CDE.
-
-This can happen if you have "Allow Primary Windows On Top" enabled which
-seems to be the default in the Common Desktop Environment.
-To change, go in to "Desktop Controls" -> "Window Style Manager"
-and uncheck "Allow Primary Windows On Top".
-
-* Emacs does not know your host's fully-qualified domain name.
-
-You need to configure your machine with a fully qualified domain name,
-either in /etc/hosts, /etc/hostname, the NIS, or wherever your system
-calls for specifying this.
-
-If you cannot fix the configuration, you can set the Lisp variable
-mail-host-address to the value you want.
-
-* Error 12 (virtual memory exceeded) when dumping Emacs, on UnixWare 2.1
-
-Paul Abrahams (abrahams@acm.org) reports that with the installed
-virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
-the "make" that builds Emacs, when running temacs to dump emacs.  That
-error indicates that the per-process virtual memory limit has been
-exceeded.  The default limit is probably 32MB.  Raising the virtual
-memory limit to 40MB should make it possible to finish building Emacs.
-
-You can do this with the command `ulimit' (sh) or `limit' (csh).
-But you have to be root to do it.
-
-According to Martin Sohnius, you can also retune this in the kernel:
-
-    # /etc/conf/bin/idtune SDATLIM 33554432         ## soft data size limit
-    # /etc/conf/bin/idtune HDATLIM 33554432         ## hard "
-    # /etc/conf/bin/idtune SVMMSIZE unlimited       ## soft process size limit
-    # /etc/conf/bin/idtune HVMMSIZE unlimited       ## hard "
-    # /etc/conf/bin/idbuild -B
-
-(He recommends you not change the stack limit, though.)
-These changes take effect when you reboot.
-
-* Redisplay using X11 is much slower than previous Emacs versions.
-
-We've noticed that certain X servers draw the text much slower when
-scroll bars are on the left.  We don't know why this happens.  If this
-happens to you, you can work around it by putting the scroll bars
-on the right (as they were in Emacs 19).
-
-Here's how to do this:
-
-  (set-scroll-bar-mode 'right)
-
-If you're not sure whether (or how much) this problem affects you,
-try that and see how much difference it makes.  To set things back
-to normal, do
-
-  (set-scroll-bar-mode 'left)
-
-* Under X11, some characters appear as hollow boxes.
-
-Each X11 font covers just a fraction of the characters that Emacs
-supports.  To display the whole range of Emacs characters requires
-many different fonts, collected into a fontset.
-
-If some of the fonts called for in your fontset do not exist on your X
-server, then the characters that have no font appear as hollow boxes.
-You can remedy the problem by installing additional fonts.
-
-The intlfonts distribution includes a full spectrum of fonts that can
-display all the characters Emacs supports.
-
-Another cause of this for specific characters is fonts which have a
-missing glyph and no default character.  This is known ot occur for
-character number 160 (no-break space) in some fonts, such as Lucida
-but Emacs sets the display table for the unibyte and Latin-1 version
-of this character to display a space.
-
-* Under X11, some characters appear improperly aligned in their lines.
-
-You may have bad X11 fonts; try installing the intlfonts distribution.
-
-* Certain fonts make each line take one pixel more than it "should".
-
-This is because these fonts contain characters a little taller
-than the font's nominal height.  Emacs needs to make sure that
-lines do not overlap.
-
-* You request inverse video, and the first Emacs frame is in inverse
-video, but later frames are not in inverse video.
-
-This can happen if you have an old version of the custom library in
-your search path for Lisp packages.  Use M-x list-load-path-shadows to
-check whether this is true.  If it is, delete the old custom library.
-
-* In FreeBSD 2.1.5, useless symbolic links remain in /tmp or other
-directories that have the +t bit.
-
-This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2).
-Emacs uses symbolic links to implement file locks.  In a directory
-with +t bit, the directory owner becomes the owner of the symbolic
-link, so that it cannot be removed by anyone else.
-
-If you don't like those useless links, you can let Emacs not to using
-file lock by adding #undef CLASH_DETECTION to config.h.
-
-* When using M-x dbx with the SparcWorks debugger, the `up' and `down'
-commands do not move the arrow in Emacs.
-
-You can fix this by adding the following line to `~/.dbxinit':
-
- dbxenv output_short_file_name off
-
-* Emacs says it has saved a file, but the file does not actually
-appear on disk.
-
-This can happen on certain systems when you are using NFS, if the
-remote disk is full.  It is due to a bug in NFS (or certain NFS
-implementations), and there is apparently nothing Emacs can do to
-detect the problem.  Emacs checks the failure codes of all the system
-calls involved in writing a file, including `close'; but in the case
-where the problem occurs, none of those system calls fails.
-
-* "Compose Character" key does strange things when used as a Meta key.
-
-If you define one key to serve as both Meta and Compose Character, you
-will get strange results.  In previous Emacs versions, this "worked"
-in that the key acted as Meta--that's because the older Emacs versions
-did not try to support Compose Character.  Now Emacs tries to do
-character composition in the standard X way.  This means that you
-must pick one meaning or the other for any given key.
-
-You can use both functions (Meta, and Compose Character) if you assign
-them to two different keys.
-
-* Emacs gets a segmentation fault at startup, on AIX4.2.
-
-If you are using IBM's xlc compiler, compile emacs.c
-without optimization; that should avoid the problem.
-
-* movemail compiled with POP support can't connect to the POP server.
-
-Make sure that the `pop' entry in /etc/services, or in the services
-NIS map if your machine uses NIS, has the same port number as the
-entry on the POP server.  A common error is for the POP server to be
-listening on port 110, the assigned port for the POP3 protocol, while
-the client is trying to connect on port 109, the assigned port for the
-old POP protocol.
-
-* Emacs crashes in x-popup-dialog.
-
-This can happen if the dialog widget cannot find the font it wants to
-use.  You can work around the problem by specifying another font with
-an X resource--for example, `Emacs.dialog*.font: 9x15' (or any font that
-happens to exist on your X server).
-
-* Emacs crashes when you use Bibtex mode.
-
-This happens if your system puts a small limit on stack size.  You can
-prevent the problem by using a suitable shell command (often `ulimit')
-to raise the stack size limit before you run Emacs.
-
-Patches to raise the stack size limit automatically in `main'
-(src/emacs.c) on various systems would be greatly appreciated.
-
-* Emacs crashes with SIGBUS or SIGSEGV on HPUX 9 after you delete a frame.
-
-We think this is due to a bug in the X libraries provided by HP.  With
-the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem
-does not happen.
-
-* Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
-
-We suspect that this is a similar bug in the X libraries provided by
-Sun.  There is a report that one of these patches fixes the bug and
-makes the problem stop:
-
-105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
-105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
-106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
-105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
-
-Another person using a newer system (kernel patch level Generic_105181-06)
-suspects that the bug was fixed by one of these more recent patches:
-
-106040-07  SunOS 5.6: X Input & Output Method patch
-106222-01  OpenWindows 3.6: filemgr (ff.core) fixes
-105284-12  Motif 1.2.7: sparc Runtime library patch
-
-* Problems running Perl under Emacs on MS-Windows NT/95.
-
-`perl -de 0' just hangs when executed in an Emacs subshell.
-The fault lies with Perl (indirectly with Windows NT/95).
-
-The problem is that the Perl debugger explicitly opens a connection to
-"CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
-with the user.
-
-On Unix, this is okay, because Emacs (or the shell?) creates a
-pseudo-tty so that /dev/tty is really the pipe Emacs is using to
-communicate with the subprocess.
-
-On NT, this fails because CON always refers to the handle for the
-relevant console (approximately equivalent to a tty), and cannot be
-redirected to refer to the pipe Emacs assigned to the subprocess as
-stdin.
-
-A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
-
-For Perl 4:
-
-    *** PERL/LIB/PERLDB.PL.orig	Wed May 26 08:24:18 1993
-    --- PERL/LIB/PERLDB.PL	Mon Jul 01 15:28:16 1996
-    ***************
-    *** 68,74 ****
-	  $rcfile=".perldb";
-      }
-      else {
-    !     $console = "con";
-	  $rcfile="perldb.ini";
-      }
-
-    --- 68,74 ----
-	  $rcfile=".perldb";
-      }
-      else {
-    !     $console = "";
-	  $rcfile="perldb.ini";
-      }
-
-
-    For Perl 5:
-    *** perl/5.001/lib/perl5db.pl.orig	Sun Jun 04 21:13:40 1995
-    --- perl/5.001/lib/perl5db.pl	Mon Jul 01 17:00:08 1996
-    ***************
-    *** 22,28 ****
-	  $rcfile=".perldb";
-      }
-      elsif (-e "con") {
-    !     $console = "con";
-	  $rcfile="perldb.ini";
-      }
-      else {
-    --- 22,28 ----
-	  $rcfile=".perldb";
-      }
-      elsif (-e "con") {
-    !     $console = "";
-	  $rcfile="perldb.ini";
-      }
-      else {
-
-* Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs:
-
-There are two DJGPP library bugs which cause problems:
-
-  * Running `shell-command' (or `compile', or `grep') you get
-    `Searching for program: permission denied (EACCES), c:/command.com';
-  * After you shell to DOS, Ctrl-Break kills Emacs.
-
-To work around these bugs, you can use two files in the msdos
-subdirectory: `is_exec.c' and `sigaction.c'.  Compile them and link
-them into the Emacs executable `temacs'; then they will replace the
-incorrect library functions.
-
-* When compiling with DJGPP on MS-Windows NT, "config msdos" fails.
-
-If the error message is "VDM has been already loaded", this is because
-Windows has a program called `redir.exe' that is incompatible with a
-program by the same name supplied with DJGPP, which is used by
-config.bat.  To resolve this, move the DJGPP's `bin' subdirectory to
-the front of your PATH environment variable.
-
-* When compiling with DJGPP on MS-Windows 95, Make fails for some targets
-like make-docfile.
-
-This can happen if long file name support (the setting of environment
-variable LFN) when Emacs distribution was unpacked and during
-compilation are not the same.  See the MSDOG section of INSTALL for
-the explanation of how to avoid this problem.
-
-* Emacs compiled for MSDOS cannot find some Lisp files, or other
-run-time support files, when long filename support is enabled.
-
-Usually, this problem will manifest itself when Emacs exits
-immediately after flashing the startup screen, because it cannot find
-the Lisp files it needs to load at startup.  Redirect Emacs stdout
-and stderr to a file to see the error message printed by Emacs.
-
-Another manifestation of this problem is that Emacs is unable to load
-the support for editing program sources in languages such as C and
-Lisp.
-
-This can happen if the Emacs distribution was unzipped without LFN
-support, thus causing long filenames to be truncated to the first 6
-characters and a numeric tail that Windows 95 normally attaches to it.
-You should unzip the files again with a utility that supports long
-filenames (such as djtar from DJGPP or InfoZip's UnZip program
-compiled with DJGPP v2).  The MSDOG section of the file INSTALL
-explains this issue in more detail.
-
-Another possible reason for such failures is that Emacs compiled for
-MSDOS is used on Windows NT, where long file names are not supported
-by this version of Emacs, but the distribution was unpacked by an
-unzip program that preserved the long file names instead of truncating
-them to DOS 8+3 limits.  To be useful on NT, the MSDOS port of Emacs
-must be unzipped by a DOS utility, so that long file names are
-properly truncated.
-
-* Emacs compiled with DJGPP complains at startup:
-
-  "Wrong type of argument: internal-facep, msdos-menu-active-face"
-
-This can happen if you define an environment variable `TERM'.  Emacs
-on MSDOS uses an internal terminal emulator which is disabled if the
-value of `TERM' is anything but the string "internal".  Emacs then
-works as if its terminal were a dumb glass teletype that doesn't
-support faces.  To work around this, arrange for `TERM' to be
-undefined when Emacs runs.  The best way to do that is to add an
-[emacs] section to the DJGPP.ENV file which defines an empty value for
-`TERM'; this way, only Emacs gets the empty value, while the rest of
-your system works as before.
-
-* On MS-Windows 95, Alt-f6 does not get through to Emacs.
-
-This character seems to be trapped by the kernel in Windows 95.
-You can enter M-f6 by typing ESC f6.
-
-* Typing Alt-Shift has strange effects on MS-Windows.
-
-This combination of keys is a command to change keyboard layout.  If
-you proceed to type another non-modifier key before you let go of Alt
-and Shift, the Alt and Shift act as modifiers in the usual way.  A
-more permanent work around is to change it to another key combination,
-or disable it in the keyboard control panel.
-
-* `tparam' reported as a multiply-defined symbol when linking with ncurses.
-
-This problem results from an incompatible change in ncurses, in
-version 1.9.9e approximately.  This version is unable to provide a
-definition of tparm without also defining tparam.  This is also
-incompatible with Terminfo; as a result, the Emacs Terminfo support
-does not work with this version of ncurses.
-
-The fix is to install a newer version of ncurses, such as version 4.2.
-
-* Emacs does not start, complaining that it cannot open termcap database file.
-
-If your system uses Terminfo rather than termcap (most modern
-systems do), this could happen if the proper version of
-ncurses is not visible to the Emacs configure script (i.e. it
-cannot be found along the usual path the linker looks for
-libraries). It can happen because your version of ncurses is
-obsolete, or is available only in form of binaries.
-
-The solution is to install an up-to-date version of ncurses in
-the developer's form (header files, static libraries and
-symbolic links); in some GNU/Linux distributions (e.g. Debian)
-it constitutes a separate package.
-
-* Strange results from format %d in a few cases, on a Sun.
-
-Sun compiler version SC3.0 has been found to miscompile part of
-editfns.c.  The workaround is to compile with some other compiler such
-as GCC.
-
-* Output from subprocess (such as man or diff) is randomly truncated
-on GNU/Linux systems.
-
-This is due to a kernel bug which seems to be fixed in Linux version
-1.3.75.
-
-* Error messages `internal facep []' happen on GNU/Linux systems.
-
-There is a report that replacing libc.so.5.0.9 with libc.so.5.2.16
-caused this to start happening.  People are not sure why, but the
-problem seems unlikely to be in Emacs itself.  Some suspect that it
-is actually Xlib which won't work with libc.so.5.2.16.
-
-Using the old library version is a workaround.
-
-* On Solaris, Emacs crashes if you use (display-time).
-
-This can happen if you configure Emacs without specifying the precise
-version of Solaris that you are using.
-
-* Emacs dumps core on startup, on Solaris.
-
-Bill Sebok says that the cause of this is Solaris 2.4 vendor patch
-102303-05, which extends the Solaris linker to deal with the Solaris
-Common Desktop Environment's linking needs.  You can fix the problem
-by removing this patch and installing patch 102049-02 instead.
-However, that linker version won't work with CDE.
-
-Solaris 2.5 comes with a linker that has this bug.  It is reported that if
-you install all the latest patches (as of June 1996), the bug is fixed.
-We suspect the crucial patch is one of these, but we don't know
-for certain.
-
-        103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes)
-        102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes)
-	103242-04: [README] SunOS 5.5: linker patch (595363 bytes)
-
-(One user reports that the bug was fixed by those patches together
-with patches 102980-04, 103279-01, 103300-02, and 103468-01.)
-
-If you can determine which patch does fix the bug, please tell
-bug-gnu-emacs@gnu.org.
-
-Meanwhile, the GNU linker links Emacs properly on both Solaris 2.4 and
-Solaris 2.5.
-
-* Emacs dumps core if lisp-complete-symbol is called, on Solaris.
-
-If you compile Emacs with the -fast or -xO4 option with version 3.0.2
-of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is
-called.  The problem does not happen if you compile with GCC.
-
-* "Cannot find callback list" messages from dialog boxes on HPUX, in
-Emacs built with Motif.
-
-This problem resulted from a bug in GCC 2.4.5.  Newer GCC versions
-such as 2.7.0 fix the problem.
-
-* On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
-
-A compiler bug inserts spaces into the string "unexelfsgi . o"
-in src/Makefile.  Edit src/Makefile, after configure is run,
-find that string, and take out the spaces.
-
-Compiler fixes in Irix 6.0.1 should eliminate this problem.
-
-* "out of virtual swap space" on Irix 5.3
-
-This message occurs when the system runs out of swap space due to too
-many large programs running.  The solution is either to provide more
-swap space or to reduce the number of large programs being run.  You
-can check the current status of the swap space by executing the
-command `swap -l'.
-
-You can increase swap space by changing the file /etc/fstab.  Adding a
-line like this:
-
-/usr/swap/swap.more     swap    swap    pri=3 0 0
-
-where /usr/swap/swap.more is a file previously created (for instance
-by using /etc/mkfile), will increase the swap space by the size of
-that file.  Execute `swap -m' or reboot the machine to activate the
-new swap area.  See the manpages for `swap' and `fstab' for further
-information.
-
-The objectserver daemon can use up lots of memory because it can be
-swamped with NIS information.  It collects information about all users
-on the network that can log on to the host.
-
-If you want to disable the objectserver completely, you can execute
-the command `chkconfig objectserver off' and reboot.  That may disable
-some of the window system functionality, such as responding CDROM
-icons.
-
-You can also remove NIS support from the objectserver.  The SGI `admin'
-FAQ has a detailed description on how to do that; see question 35
-("Why isn't the objectserver working?").  The admin FAQ can be found at
-ftp://viz.tamu.edu/pub/sgi/faq/.
-
-* With certain fonts, when the cursor appears on a character, the
-character doesn't appear--you get a solid box instead.
-
-One user on a Linux-based GNU system reported that this problem went
-away with installation of a new X server.  The failing server was
-XFree86 3.1.1.  XFree86 3.1.2 works.
-
-* On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
-
-This happens if you configure Emacs specifying just `sparc-sun-sunos4'
-on a system that is version 4.1.3.  You must specify the precise
-version number (or let configure figure out the configuration, which
-it can do perfectly well for SunOS).
-
-* On SunOS 4, Emacs processes keep going after you kill the X server
-(or log out, if you logged in using X).
-
-Someone reported that recompiling with GCC 2.7.0 fixed this problem.
-
-* On AIX 4, some programs fail when run in a Shell buffer
-with an error message like   No terminfo entry for "unknown".
-
-On AIX, many terminal type definitions are not installed by default.
-`unknown' is one of them.  Install the "Special Generic Terminal
-Definitions" to make them defined.
-
-* On SunOS, you get linker errors
-   ld: Undefined symbol
-      _get_wmShellWidgetClass
-      _get_applicationShellWidgetClass
-
-The fix to this is to install patch 100573 for OpenWindows 3.0
-or link libXmu statically.
-
-* On AIX 4.1.2, linker error messages such as
-  ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
-	of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
-
-This is a problem in libIM.a.  You can work around it by executing
-these shell commands in the src subdirectory of the directory where
-you build Emacs:
-
-    cp /usr/lib/libIM.a .
-    chmod 664 libIM.a
-    ranlib libIM.a
-
-Then change -lIM to ./libIM.a in the command to link temacs (in
-Makefile).
-
-* Unpredictable segmentation faults on Solaris 2.3 and 2.4.
-
-A user reported that this happened in 19.29 when it was compiled with
-the Sun compiler, but not when he recompiled with GCC 2.7.0.
-
-We do not know whether something in Emacs is partly to blame for this.
-
-* Emacs exits with "X protocol error" when run with an X server for
-MS-Windows.
-
-A certain X server for Windows had a bug which caused this.
-Supposedly the newer 32-bit version of this server doesn't have the
-problem.
-
-* Emacs crashes at startup on MSDOS.
-
-Some users report that Emacs 19.29 requires dpmi memory management,
-and crashes on startup if the system does not have it.  We don't yet
-know why this happens--perhaps these machines don't have enough real
-memory, or perhaps something is wrong in Emacs or the compiler.
-However, arranging to use dpmi support is a workaround.
-
-You can find out if you have a dpmi host by running go32 without
-arguments; it will tell you if it uses dpmi memory.  For more
-information about dpmi memory, consult the djgpp FAQ.  (djgpp
-is the GNU C compiler as packaged for MSDOS.)
-
-Compiling Emacs under MSDOS is extremely sensitive for proper memory
-configuration.  If you experience problems during compilation, consider
-removing some or all memory resident programs (notably disk caches)
-and make sure that your memory managers are properly configured.  See
-the djgpp faq for configuration hints.
-
-* A position you specified in .Xdefaults is ignored, using twm.
-
-twm normally ignores "program-specified" positions.
-You can tell it to obey them with this command in your `.twmrc' file:
-
-  UsePPosition	"on"		#allow clients to request a position
-
-* Compiling lib-src says there is no rule to make test-distrib.c.
-
-This results from a bug in a VERY old version of GNU Sed.  To solve
-the problem, install the current version of GNU Sed, then rerun
-Emacs's configure script.
-
-* Compiling wakeup, in lib-src, says it can't make wakeup.c.
-
-This results from a bug in GNU Sed version 2.03.  To solve the
-problem, install the current version of GNU Sed, then rerun Emacs's
-configure script.
-
-* On Sunos 4.1.1, there are errors compiling sysdep.c.
-
-If you get errors such as
-
-    "sysdep.c", line 2017: undefined structure or union
-    "sysdep.c", line 2017: undefined structure or union
-    "sysdep.c", line 2019: nodename undefined
-
-This can result from defining LD_LIBRARY_PATH.  It is very tricky
-to use that environment variable with Emacs.  The Emacs configure
-script links many test programs with the system libraries; you must
-make sure that the libraries available to configure are the same
-ones available when you build Emacs.
-
-* The right Alt key works wrong on German HP keyboards (and perhaps
-other non-English HP keyboards too).
-
-This is because HPUX defines the modifiers wrong in X.  Here is a
-shell script to fix the problem; be sure that it is run after VUE
-configures the X server.
-
-    xmodmap 2> /dev/null - << EOF
-    keysym Alt_L = Meta_L
-    keysym Alt_R = Meta_R
-    EOF
-
-    xmodmap - << EOF
-    clear mod1
-    keysym Mode_switch = NoSymbol
-    add mod1 = Meta_L
-    keysym Meta_R = Mode_switch
-    add mod2 = Mode_switch
-    EOF
-
-* The Emacs window disappears when you type M-q.
-
-Some versions of the Open Look window manager interpret M-q as a quit
-command for whatever window you are typing at.  If you want to use
-Emacs with that window manager, you should try to configure the window
-manager to use some other command.   You can disable the
-shortcut keys entirely by adding this line to ~/.OWdefaults:
-
-    OpenWindows.WindowMenuAccelerators: False
-
-* Emacs does not notice when you release the mouse.
-
-There are reports that this happened with (some) Microsoft mice and
-that replacing the mouse made it stop.
-
-* Trouble using ptys on IRIX, or running out of ptys.
-
-The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
-be set-UID to root, or non-root programs like Emacs will not be able
-to allocate ptys reliably.
-
-* On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
-
-The file cmplrs/stsupport.h was included in the wrong file set in the
-Irix 5.2 distribution.  You can find it in the optional fileset
-compiler_dev, or copy it from some other Irix 5.2 system.  A kludgy
-workaround is to change unexelfsgi.c to include sym.h instead of
-syms.h.
-
-* Slow startup on Linux-based GNU systems.
-
-People using systems based on the Linux kernel sometimes report that
-startup takes 10 to 15 seconds longer than `usual'.
-
-This is because Emacs looks up the host name when it starts.
-Normally, this takes negligible time; the extra delay is due to
-improper system configuration.  This problem can occur for both
-networked and non-networked machines.
-
-Here is how to fix the configuration.  It requires being root.
-
-** Networked Case
-
-First, make sure the files `/etc/hosts' and `/etc/host.conf' both
-exist.  The first line in the `/etc/hosts' file should look like this
-(replace HOSTNAME with your host name):
-
-    127.0.0.1      HOSTNAME
-
-Also make sure that the `/etc/host.conf' files contains the following
-lines:
-
-    order hosts, bind
-    multi on
-
-Any changes, permanent and temporary, to the host name should be
-indicated in the `/etc/hosts' file, since it acts a limited local
-database of addresses and names (e.g., some SLIP connections
-dynamically allocate ip addresses).
-
-** Non-Networked Case
-
-The solution described in the networked case applies here as well.
-However, if you never intend to network your machine, you can use a
-simpler solution: create an empty `/etc/host.conf' file.  The command
-`touch /etc/host.conf' suffices to create the file.  The `/etc/hosts'
-file is not necessary with this approach.
-
-* On Solaris 2.4, Dired hangs and C-g does not work.  Or Emacs hangs
-forever waiting for termination of a subprocess that is a zombie.
-
-casper@fwi.uva.nl says the problem is in X11R6.  Rebuild libX11.so
-after changing the file xc/config/cf/sunLib.tmpl.  Change the lines
-
-    #if ThreadedX
-    #define SharedX11Reqs -lthread
-    #endif
-
-to:
-
-    #if OSMinorVersion < 4
-    #if ThreadedX
-    #define SharedX11Reqs -lthread
-    #endif
-    #endif
-
-Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
-(as it should be for Solaris 2.4).  The file has three definitions for
-OSMinorVersion: the first is for x86, the second for SPARC under
-Solaris, and the third for SunOS 4.  Make sure to update the
-definition for your type of machine and system.
-
-Then do `make Everything' in the top directory of X11R6, to rebuild
-the makefiles and rebuild X.  The X built this way work only on
-Solaris 2.4, not on 2.3.
-
-For multithreaded X to work it is necessary to install patch
-101925-02 to fix problems in header files [2.4].  You need
-to reinstall gcc or re-run just-fixinc after installing that
-patch.
-
-However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
-he changed
-    #define ThreadedX          YES
-to
-    #define ThreadedX          NO
-in sun.cf and did `make World' to rebuild X11R6.  Removing all
-`-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
-typing 'make install' in that directory also seemed to work.
-
-* With M-x enable-flow-control, you need to type C-\ twice
-  to do incremental search--a single C-\ gets no response.
-
-This has been traced to communicating with your machine via kermit,
-with C-\ as the kermit escape character.  One solution is to use
-another escape character in kermit.  One user did
-
-   set escape-character 17
-
-in his .kermrc file, to make C-q the kermit escape character.
-
-* The Motif version of Emacs paints the screen a solid color.
-
-This has been observed to result from the following X resource:
-
-   Emacs*default.attributeFont:	-*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
-
-That the resource has this effect indicates a bug in something, but we
-do not yet know what.  If it is an Emacs bug, we hope someone can
-explain what the bug is so we can fix it.  In the mean time, removing
-the resource prevents the problem.
-
-* Emacs gets hung shortly after startup, on Sunos 4.1.3.
-
-We think this is due to a bug in Sunos.  The word is that
-one of these Sunos patches fixes the bug:
-
-100075-11  100224-06  100347-03  100482-05  100557-02  100623-03  100804-03  101080-01
-100103-12  100249-09             100496-02  100564-07  100630-02  100891-10  101134-01
-100170-09  100296-04  100377-09  100507-04  100567-04  100650-02  101070-01  101145-01
-100173-10  100305-15  100383-06  100513-04  100570-05  100689-01  101071-03  101200-02
-100178-09  100338-05  100421-03  100536-02  100584-05  100784-01  101072-01  101207-01
-
-We don't know which of these patches really matter.  If you find out
-which ones, please inform bug-gnu-emacs@gnu.org.
-
-* Emacs aborts while starting up, only when run without X.
-
-This problem often results from compiling Emacs with GCC when GCC was
-installed incorrectly.  The usual error in installing GCC is to
-specify --includedir=/usr/include.  Installation of GCC makes
-corrected copies of the system header files.  GCC is supposed to use
-the corrected copies in preference to the original system headers.
-Specifying --includedir=/usr/include causes the original system header
-files to be used.  On some systems, the definition of ioctl in the
-original system header files is invalid for ANSI C and causes Emacs
-not to work.
-
-The fix is to reinstall GCC, and this time do not specify --includedir
-when you configure it.  Then recompile Emacs.  Specifying --includedir
-is appropriate only in very special cases and it should *never* be the
-same directory where system header files are kept.
-
-* On Solaris 2.x, GCC complains "64 bit integer types not supported"
-
-This suggests that GCC is not installed correctly.  Most likely you
-are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this
-does not work without patching.  To run GCC 2.7.2.3 on Solaris 2.6 or
-later, you must patch fixinc.svr4 and reinstall GCC from scratch as
-described in the Solaris FAQ
-<http://www.wins.uva.nl/pub/solaris/solaris2.html>.  A better fix is
-to upgrade to GCC 2.8.1 or later.
-
-* The Compose key on a DEC keyboard does not work as Meta key.
-
-This shell command should fix it:
-
-  xmodmap -e 'keycode 0xb1 = Meta_L'
-
-* Regular expressions matching bugs on SCO systems.
-
-On SCO, there are problems in regexp matching when Emacs is compiled
-with the system compiler.  The compiler version is "Microsoft C
-version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
-C Compiler Version 1.00.46 (Beta).  The solution is to compile with
-GCC.
-
-* On Sunos 4, you get the error ld: Undefined symbol __lib_version.
-
-This is the result of using cc or gcc with the shared library meant
-for acc (the Sunpro compiler).  Check your LD_LIBRARY_PATH and delete
-/usr/lang/SC2.0.1 or some similar directory.
-
-* You can't select from submenus (in the X toolkit version).
-
-On certain systems, mouse-tracking and selection in top-level menus
-works properly with the X toolkit, but neither of them works when you
-bring up a submenu (such as Bookmarks or Compare or Apply Patch, in
-the Files menu).
-
-This works on most systems.  There is speculation that the failure is
-due to bugs in old versions of X toolkit libraries, but no one really
-knows.  If someone debugs this and finds the precise cause, perhaps a
-workaround can be found.
-
-* Unusable default font on SCO 3.2v4.
-
-The Open Desktop environment comes with default X resource settings
-that tell Emacs to use a variable-width font.  Emacs cannot use such
-fonts, so it does not work.
-
-This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
-the application-specific resource file for the `scoterm' terminal
-emulator program.  It contains several extremely general X resources
-that affect other programs besides `scoterm'.  In particular, these
-resources affect Emacs also:
-
-	*Font: -*-helvetica-medium-r-*--12-*-p-*
-	*Background:			scoBackground
-	*Foreground:			scoForeground
-
-The best solution is to create an application-specific resource file for
-Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents:
-
-	Emacs*Font:	-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
-	Emacs*Background:	white
-	Emacs*Foreground:	black
-
-(These settings mimic the Emacs defaults, but you can change them to
-suit your needs.)  This resource file is only read when the X server
-starts up, so you should restart it by logging out of the Open Desktop
-environment or by running `scologin stop; scologin start` from the shell
-as root.  Alternatively, you can put these settings in the
-/usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs,
-but then they will not affect remote invocations of Emacs that use the
-Open Desktop display.
-
-These resource files are not normally shared across a network of SCO
-machines; you must create the file on each machine individually.
-
-* rcs2log gives you the awk error message "too many fields".
-
-This is due to an arbitrary limit in certain versions of awk.
-The solution is to use gawk (GNU awk).
-
-* Emacs is slow using X11R5 on HP/UX.
-
-This happens if you use the MIT versions of the X libraries--it
-doesn't run as fast as HP's version.  People sometimes use the version
-because they see the HP version doesn't have the libraries libXaw.a,
-libXmu.a, libXext.a and others.  HP/UX normally doesn't come with
-those libraries installed.  To get good performance, you need to
-install them and rebuild Emacs.
-
-* Loading fonts is very slow.
-
-You might be getting scalable fonts instead of precomputed bitmaps.
-Known scalable font directories are "Type1" and "Speedo".  A font
-directory contains scalable fonts if it contains the file
-"fonts.scale".
-
-If this is so, re-order your X windows font path to put the scalable
-font directories last.  See the documentation of `xset' for details.
-
-With some X servers, it may be necessary to take the scalable font
-directories out of your path entirely, at least for Emacs 19.26.
-Changes in the future may make this unnecessary.
-
-* On AIX 3.2.4, releasing Ctrl/Act key has no effect, if Shift is down.
-
-Due to a feature of AIX, pressing or releasing the Ctrl/Act key is
-ignored when the Shift, Alt or AltGr keys are held down.  This can
-lead to the keyboard being "control-locked"--ordinary letters are
-treated as control characters.
-
-You can get out of this "control-locked" state by pressing and
-releasing Ctrl/Act while not pressing or holding any other keys.
-
-* display-time causes kernel problems on ISC systems.
-
-Under Interactive Unix versions 3.0.1 and 4.0 (and probably other
-versions), display-time causes the loss of large numbers of STREVENT
-cells.  Eventually the kernel's supply of these cells is exhausted.
-This makes emacs and the whole system run slow, and can make other
-processes die, in particular pcnfsd.
-
-Other emacs functions that communicate with remote processes may have
-the same problem.  Display-time seems to be far the worst.
-
-The only known fix: Don't run display-time.
-
-* On Solaris, C-x doesn't get through to Emacs when you use the console.
-
-This is a Solaris feature (at least on Intel x86 cpus).  Type C-r
-C-r C-t, to toggle whether C-x gets through to Emacs.
-
-* Error message `Symbol's value as variable is void: x', followed by
-  segmentation fault and core dump.
-
-This has been tracked to a bug in tar!  People report that tar erroneously
-added a line like this at the beginning of files of Lisp code:
-
-   x FILENAME, N bytes, B tape blocks
-
-If your tar has this problem, install GNU tar--if you can manage to
-untar it :-).
-
-* Link failure when using acc on a Sun.
-
-To use acc, you need additional options just before the libraries, such as
-
-   /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
-
-and you need to add -lansi just before -lc.
-
-The precise file names depend on the compiler version, so we
-cannot easily arrange to supply them.
-
-* Link failure on IBM AIX 1.3 ptf 0013.
-
-There is a real duplicate definition of the function `_slibc_free' in
-the library /lib/libc_s.a (just do nm on it to verify).  The
-workaround/fix is:
-
-    cd /lib
-    ar xv libc_s.a NLtmtime.o
-    ar dv libc_s.a NLtmtime.o
-
-* Undefined symbols _dlopen, _dlsym and/or _dlclose on a Sun.
-
-If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking
-with -lX11, compile and link against the file mit/util/misc/dlsym.c in
-the MIT X11R5 distribution.  Alternatively, link temacs using shared
-libraries with s/sunos4shr.h.  (This doesn't work if you use the X
-toolkit.)
-
-If you get the additional error that the linker could not find
-lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in
-X11R4, then use it in the link.
-
-* Error messages `Wrong number of arguments: #<subr where-is-internal>, 5'
-
-This typically results from having the powerkey library loaded.
-Powerkey was designed for Emacs 19.22.  It is obsolete now because
-Emacs 19 now has this feature built in; and powerkey also calls
-where-is-internal in an obsolete way.
-
-So the fix is to arrange not to load powerkey.
-
-* In Shell mode, you get a ^M at the end of every line.
-
-This happens to people who use tcsh, because it is trying to be too
-smart.  It sees that the Shell uses terminal type `unknown' and turns
-on the flag to output ^M at the end of each line.  You can fix the
-problem by adding this to your .cshrc file:
-
-    if ($?EMACS) then
-        if ($EMACS == "t") then
-            unset edit
-            stty  -icrnl -onlcr -echo susp ^Z
-        endif
-    endif
-
-* An error message such as `X protocol error: BadMatch (invalid
-parameter attributes) on protocol request 93'.
-
-This comes from having an invalid X resource, such as
-   emacs*Cursor:   black
-(which is invalid because it specifies a color name for something
-that isn't a color.)
-
-The fix is to correct your X resources.
-
-* Undefined symbols when linking on Sunos 4.1 using --with-x-toolkit.
-
-If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
-_iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
--lXaw in the command that links temacs.
-
-This problem seems to arise only when the international language
-extensions to X11R5 are installed.
-
-* Typing C-c C-c in Shell mode kills your X server.
-
-This happens with Linux kernel 1.0 thru 1.04, approximately.  The workaround is
-to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs.
-Newer Linux kernel versions don't have this problem.
-
-* src/Makefile and lib-src/Makefile are truncated--most of the file missing.
-
-This can happen if configure uses GNU sed version 2.03.  That version
-had a bug.  GNU sed version 2.05 works properly.
-
-* Slow startup on X11R6 with X windows.
-
-If Emacs takes two minutes to start up on X11R6, see if your X
-resources specify any Adobe fonts.  That causes the type-1 font
-renderer to start up, even if the font you asked for is not a type-1
-font.
-
-One way to avoid this problem is to eliminate the type-1 fonts from
-your font path, like this:
-
-	xset -fp /usr/X11R6/lib/X11/fonts/Type1/
-
-* Pull-down menus appear in the wrong place, in the toolkit version of Emacs.
-
-An X resource of this form can cause the problem:
-
-   Emacs*geometry:	80x55+0+0
-
-This resource is supposed to apply, and does apply, to the menus
-individually as well as to Emacs frames.  If that is not what you
-want, rewrite the resource.
-
-To check thoroughly for such resource specifications, use `xrdb
--query' to see what resources the X server records, and also look at
-the user's ~/.Xdefaults and ~/.Xdefaults-* files.
-
-* --with-x-toolkit version crashes when used with shared libraries.
-
-On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others,
-unexec doesn't work properly with the shared library for the X
-toolkit.  You might be able to work around this by using a nonshared
-libXt.a library.  The real fix is to upgrade the various versions of
-unexec and/or ralloc.  We think this has been fixed on Sunos 4
-and Solaris in version 19.29.
-
-* `make install' fails on install-doc with `Error 141'.
-
-This happens on Ultrix 4.2 due to failure of a pipeline of tar
-commands.  We don't know why they fail, but the bug seems not to be in
-Emacs.  The workaround is to run the shell command in install-doc by
-hand.
-
-* --with-x-toolkit option configures wrong on BSD/386.
-
-This problem is due to bugs in the shell in version 1.0 of BSD/386.
-The workaround is to edit the configure file to use some other shell,
-such as bash.
-
-* Subprocesses remain, hanging but not zombies, on Sunos 5.3.
-
-A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
-exits.  Sun patch # 101415-02 is part of the fix for this, but it only
-applies to ptys, and doesn't fix the problem with subprocesses
-communicating through pipes.
-
-* Mail is lost when sent to local aliases.
-
-Many emacs mail user agents (VM and rmail, for instance) use the
-sendmail.el library.  This library can arrange for mail to be
-delivered by passing messages to the /usr/lib/sendmail (usually)
-program .  In doing so, it passes the '-t' flag to sendmail, which
-means that the name of the recipient of the message is not on the
-command line and, therefore, that sendmail must parse the message to
-obtain the destination address.
-
-There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
-In short, when given the -t flag, the SunOS sendmail won't recognize
-non-local (i.e. NIS) aliases.  It has been reported that the Solaris
-2.x versions of sendmail do not have this bug.  For those using SunOS
-4.1, the best fix is to install sendmail V8 or IDA sendmail (which
-have other advantages over the regular sendmail as well).  At the time
-of this writing, these official versions are available:
-
- Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
-   sendmail.8.6.9.base.tar.Z (the base system source & documentation)
-   sendmail.8.6.9.cf.tar.Z   (configuration files)
-   sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
-   sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
-
- IDA sendmail on vixen.cso.uiuc.edu in /pub:
-   sendmail-5.67b+IDA-1.5.tar.gz
-
-* On AIX, you get this message when running Emacs:
-
-    Could not load program emacs
-    Symbol smtcheckinit in csh is undefined
-    Error was: Exec format error
-
-or this one:
-
-    Could not load program .emacs
-    Symbol _system_con in csh is undefined
-    Symbol _fp_trapsta in csh is undefined
-    Error was: Exec format error
-
-These can happen when you try to run on AIX 3.2.5 a program that was
-compiled with 3.2.4.  The fix is to recompile.
-
-* On AIX, you get this compiler error message:
-
-    Processing include file ./XMenuInt.h
-        1501-106: (S) Include file X11/Xlib.h not found.
-
-This means your system was installed with only the X11 runtime i.d
-libraries.  You have to find your sipo (bootable tape) and install
-X11Dev... with smit.
-
-* You "lose characters" after typing Compose Character key.
+* X runtime problems
+
+** X keyboard problems
+
+*** You "lose characters" after typing Compose Character key.

 This is because the Compose Character key is defined as the keysym
 Multi_key, and Emacs (seeing that) does the proper X11
@@ -2637,37 +967,41 @@
 Compose, you can make the remapping happen automatically by adding the
 xmodmap command to the xdm setup script for that display.

-* C-z just refreshes the screen instead of suspending Emacs.
-
-You are probably using a shell that doesn't support job control, even
-though the system itself is capable of it.  Either use a different shell,
-or set the variable `cannot-suspend' to a non-nil value.
-
-* Watch out for .emacs files and EMACSLOADPATH environment vars
-
-These control the actions of Emacs.
-~/.emacs is your Emacs init file.
-EMACSLOADPATH overrides which directories the function
-"load" will search.
-
-If you observe strange problems, check for these and get rid
-of them, then try again.
-
-* After running emacs once, subsequent invocations crash.
-
-Some versions of SVR4 have a serious bug in the implementation of the
-mmap () system call in the kernel; this causes emacs to run correctly
-the first time, and then crash when run a second time.
-
-Contact your vendor and ask for the mmap bug fix; in the mean time,
-you may be able to work around the problem by adding a line to your
-operating system description file (whose name is reported by the
-configure script) that reads:
-#define SYSTEM_MALLOC
-This makes Emacs use memory less efficiently, but seems to work around
-the kernel bug.
-
-* Inability to send an Alt-modified key, when Emacs is communicating
+*** Using X Windows, control-shift-leftbutton makes Emacs hang.
+
+Use the shell command `xset bc' to make the old X Menu package work.
+
+*** M-SPC seems to be ignored as input.
+
+See if your X server is set up to use this as a command
+for character composition.
+
+*** The S-C-t key combination doesn't get passed to Emacs on X.
+
+This happens because some X configurations assign the Ctrl-Shift-t
+combination the same meaning as the Multi_key.  The offending
+definition is in the file `...lib/X11/locale/iso8859-1/Compose'; there
+might be other similar combinations which are grabbed by X for similar
+purposes.
+
+We think that this can be countermanded with the `xmodmap' utility, if
+you want to be able to bind one of these key sequences within Emacs.
+
+*** Under X, C-v and/or other keys don't work.
+
+These may have been intercepted by your window manager.  In
+particular, AfterStep 1.6 is reported to steal C-v in its default
+configuration.  Various Meta keys are also likely to be taken by the
+configuration of the `feel'.  See the WM's documentation for how to
+change this.
+
+*** Clicking C-mouse-2 in the scroll bar doesn't split the window.
+
+This currently doesn't work with scroll-bar widgets (and we don't know
+a good way of implementing it with widgets).  If Emacs is configured
+--without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
+
+*** Inability to send an Alt-modified key, when Emacs is communicating
 directly with an X server.

 If you have tried to bind an Alt-modified key as a command, and it
@@ -2700,139 +1034,261 @@
 Note that if you have Alt keys but no Meta keys, Emacs translates Alt
 into Meta.  This is because of the great importance of Meta in Emacs.

-* `Pid xxx killed due to text modification or page I/O error'
-
-On HP/UX, you can get that error when the Emacs executable is on an NFS
-file system.  HP/UX responds this way if it tries to swap in a page and
-does not get a response from the server within a timeout whose default
-value is just ten seconds.
-
-If this happens to you, extend the timeout period.
-
-* `expand-file-name' fails to work on any but the machine you dumped Emacs on.
-
-On Ultrix, if you use any of the functions which look up information
-in the passwd database before dumping Emacs (say, by using
-expand-file-name in site-init.el), then those functions will not work
-in the dumped Emacs on any host but the one Emacs was dumped on.
-
-The solution?  Don't use expand-file-name in site-init.el, or in
-anything it loads.  Yuck - some solution.
-
-I'm not sure why this happens; if you can find out exactly what is
-going on, and perhaps find a fix or a workaround, please let us know.
-Perhaps the YP functions cache some information, the cache is included
-in the dumped Emacs, and is then inaccurate on any other host.
-
-* On some variants of SVR4, Emacs does not work at all with X.
-
-Try defining BROKEN_FIONREAD in your config.h file.  If this solves
-the problem, please send a bug report to tell us this is needed; be
-sure to say exactly what type of machine and system you are using.
-
-* Linking says that the functions insque and remque are undefined.
-
-Change oldXMenu/Makefile by adding insque.o to the variable OBJS.
-
-* Emacs fails to understand most Internet host names, even though
-the names work properly with other programs on the same system.
-* Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
-* GNUs can't make contact with the specified host for nntp.
-
-This typically happens on Suns and other systems that use shared
-libraries.  The cause is that the site has installed a version of the
-shared library which uses a name server--but has not installed a
-similar version of the unshared library which Emacs uses.
-
-The result is that most programs, using the shared library, work with
-the nameserver, but Emacs does not.
-
-The fix is to install an unshared library that corresponds to what you
-installed in the shared library, and then relink Emacs.
-
-On SunOS 4.1, simply define HAVE_RES_INIT.
-
-If you have already installed the name resolver in the file libresolv.a,
-then you need to compile Emacs to use that library.  The easiest way to
-do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
-or LIB_STANDARD which uses -lresolv.  Watch out!  If you redefine a macro
-that is already in use in your configuration to supply some other libraries,
-be careful not to lose the others.
-
-Thus, you could start by adding this to config.h:
-
-#define LIBS_SYSTEM -lresolv
-
-Then if this gives you an error for redefining a macro, and you see that
-the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
-again to say this:
-
-#define LIBS_SYSTEM -lresolv -lfoo -lbar
-
-* On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
-
-    /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
-
-The problem is in the Sun shared C library, not in GNU ld.
-
-The solution is to install Patch-ID# 100267-03 from Sun.
-
-* Self documentation messages are garbled.
-
-This means that the file `etc/DOC-...' doesn't properly correspond
-with the Emacs executable.  Redumping Emacs and then installing the
-corresponding pair of files should fix the problem.
-
-* Trouble using ptys on AIX.
-
-People often install the pty devices on AIX incorrectly.
-Use `smit pty' to reinstall them properly.
-
-* Shell mode on HP/UX gives the message, "`tty`: Ambiguous".
-
-christos@theory.tn.cornell.edu says:
-
-The problem is that in your .cshrc you have something that tries to
-execute `tty`. If you are not running the shell on a real tty then
-tty will print "not a tty". Csh expects one word in some places,
-but tty is giving it back 3.
-
-The solution is to add a pair of quotes around `tty` to make it a single
-word:
-
-if (`tty` == "/dev/console")
-
-should be changed to:
-
-if ("`tty`" == "/dev/console")
-
-Even better, move things that set up terminal sections out of .cshrc
-and into .login.
-
-* Using X Windows, control-shift-leftbutton makes Emacs hang.
-
-Use the shell command `xset bc' to make the old X Menu package work.
-
-* Emacs running under X Windows does not handle mouse clicks.
-* `emacs -geometry 80x20' finds a file named `80x20'.
+** Window-manager and toolkit-related problems
+
+*** Gnome: Emacs' xterm-mouse-mode doesn't work on the Gnome terminal.
+
+A symptom of this bug is that double-clicks insert a control sequence
+into the buffer.  The reason this happens is an apparent
+incompatibility of the Gnome terminal with Xterm, which also affects
+other programs using the Xterm mouse interface.  A problem report has
+been filed.
+
+*** KDE: When running on KDE, colors or fonts are not as specified for Emacs,
+or messed up.
+
+For example, you could see background you set for Emacs only in the
+empty portions of the Emacs display, while characters have some other
+background.
+
+This happens because KDE's defaults apply its color and font
+definitions even to applications that weren't compiled for KDE.  The
+solution is to uncheck the "Apply fonts and colors to non-KDE apps"
+option in Preferences->Look&Feel->Style (KDE 2).  In KDE 3, this option
+is in the "Colors" section, rather than "Style".
+
+Alternatively, if you do want the KDE defaults to apply to other
+applications, but not to Emacs, you could modify the file `Emacs.ad'
+(should be in the `/usr/share/apps/kdisplay/app-defaults/' directory)
+so that it doesn't set the default background and foreground only for
+Emacs.  For example, make sure the following resources are either not
+present or commented out:
+
+   Emacs.default.attributeForeground
+   Emacs.default.attributeBackground
+   Emacs*Foreground
+   Emacs*Background
+
+*** KDE: Emacs hangs on KDE when a large portion of text is killed.
+
+This is caused by a bug in the KDE applet `klipper' which periodically
+requests the X clipboard contents from applications.  Early versions
+of klipper don't implement the ICCM protocol for large selections,
+which leads to Emacs being flooded with selection requests.  After a
+while, Emacs will print a message:
+
+  Timed out waiting for property-notify event
+
+A workaround is to not use `klipper'.
+
+*** CDE: Frames may cover dialogs they created when using CDE.
+
+This can happen if you have "Allow Primary Windows On Top" enabled which
+seems to be the default in the Common Desktop Environment.
+To change, go in to "Desktop Controls" -> "Window Style Manager"
+and uncheck "Allow Primary Windows On Top".
+
+*** Xaw3d : When using Xaw3d scroll bars without arrows, the very first mouse
+click in a scroll bar might be ignored by the scroll bar widget.  This
+is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
+problem disappears.
+
+*** Xaw: There are known binary incompatibilities between Xaw, Xaw3d, neXtaw,
+XawM and the few other derivatives of Xaw.  So when you compile with
+one of these, it may not work to dynamically link with another one.
+For example, strange problems, such as Emacs exiting when you type
+"C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was
+used with neXtaw at run time.
+
+The solution is to rebuild Emacs with the toolkit version you actually
+want to use, or set LD_PRELOAD to preload the same toolkit version you
+built Emacs with.
+
+*** Open Motif: Problems with file dialogs in Emacs built with Open Motif.
+
+When Emacs 21 is built with Open Motif 2.1, it can happen that the
+graphical file dialog boxes do not work properly.  The "OK", "Filter"
+and "Cancel" buttons do not respond to mouse clicks.  Dragging the
+file dialog window usually causes the buttons to work again.
+
+The solution is to use LessTif instead.  LessTif is a free replacement
+for Motif.  See the file INSTALL for information on how to do this.
+
+Another workaround is not to use the mouse to trigger file prompts,
+but to use the keyboard.  This way, you will be prompted for a file in
+the minibuffer instead of a graphical file dialog.
+
+*** LessTif: Problems in Emacs built with LessTif.
+
+The problems seem to depend on the version of LessTif and the Motif
+emulation for which it is set up.
+
+Only the Motif 1.2 emulation seems to be stable enough in LessTif.
+Lesstif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.
+On GNU/Linux systems, lesstif-0.92.6 configured with "./configure
+--enable-build-12 --enable-default-12" is reported to be the most
+successful.  The binary GNU/Linux package
+lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with
+menu placement.
+
+On some systems, even with Motif 1.2 emulation, Emacs occasionally
+locks up, grabbing all mouse and keyboard events.  We still don't know
+what causes these problems; they are not reproducible by Emacs
+developers.
+
+*** Motif: The Motif version of Emacs paints the screen a solid color.
+
+This has been observed to result from the following X resource:
+
+   Emacs*default.attributeFont:	-*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
+
+That the resource has this effect indicates a bug in something, but we
+do not yet know what.  If it is an Emacs bug, we hope someone can
+explain what the bug is so we can fix it.  In the mean time, removing
+the resource prevents the problem.
+
+** General X problems
+
+*** Redisplay using X11 is much slower than previous Emacs versions.
+
+We've noticed that certain X servers draw the text much slower when
+scroll bars are on the left.  We don't know why this happens.  If this
+happens to you, you can work around it by putting the scroll bars
+on the right (as they were in Emacs 19).
+
+Here's how to do this:
+
+  (set-scroll-bar-mode 'right)
+
+If you're not sure whether (or how much) this problem affects you,
+try that and see how much difference it makes.  To set things back
+to normal, do
+
+  (set-scroll-bar-mode 'left)
+
+*** Error messages about undefined colors on X.
+
+The messages might say something like this:
+
+   Unable to load color "grey95"
+
+(typically, in the `*Messages*' buffer), or something like this:
+
+  Error while displaying tooltip: (error Undefined color lightyellow)
+
+These problems could happen if some other X program has used up too
+many colors of the X palette, leaving Emacs with insufficient system
+resources to load all the colors it needs.
+
+A solution is to exit the offending X programs before starting Emacs.
+
+*** Improving performance with slow X connections.
+
+There are several ways to improve this performance, any subset of which can
+be carried out at the same time:
+
+1) If you don't need X Input Methods (XIM) for entering text in some
+   language you use, you can improve performance on WAN links by using
+   the X resource useXIM to turn off use of XIM.  This does not affect
+   the use of Emacs' own input methods, which are part of the Leim
+   package.
+
+2) If the connection is very slow, you might also want to consider
+   switching off scroll bars, menu bar, and tool bar.
+
+3) Use ssh to forward the X connection, and enable compression on this
+   forwarded X connection (ssh -XC remotehostname emacs ...).
+
+4) Use lbxproxy on the remote end of the connection.  This is an interface
+   to the low bandwidth X extension in most modern X servers, which
+   improves performance dramatically, at the slight expense of correctness
+   of the X protocol.  lbxproxy acheives the performance gain by grouping
+   several X requests in one TCP packet and sending them off together,
+   instead of requiring a round-trip for each X request in a seperate
+   packet.  The switches that seem to work best for emacs are:
+    -noatomsfile  -nowinattr  -cheaterrors -cheatevents
+   Note that the -nograbcmap option is known to cause problems.
+   For more about lbxproxy, see:
+   http://www.xfree86.org/4.3.0/lbxproxy.1.html
+
+*** Emacs gives the error, Couldn't find per display information.
+
+This can result if the X server runs out of memory because Emacs uses
+a large number of fonts.  On systems where this happens, C-h h is
+likely to cause it.
+
+We do not know of a way to prevent the problem.
+
+*** Emacs does not notice when you release the mouse.
+
+There are reports that this happened with (some) Microsoft mice and
+that replacing the mouse made it stop.
+
+*** You can't select from submenus (in the X toolkit version).
+
+On certain systems, mouse-tracking and selection in top-level menus
+works properly with the X toolkit, but neither of them works when you
+bring up a submenu (such as Bookmarks or Compare or Apply Patch, in
+the Files menu).
+
+This works on most systems.  There is speculation that the failure is
+due to bugs in old versions of X toolkit libraries, but no one really
+knows.  If someone debugs this and finds the precise cause, perhaps a
+workaround can be found.
+
+*** An error message such as `X protocol error: BadMatch (invalid
+parameter attributes) on protocol request 93'.
+
+This comes from having an invalid X resource, such as
+   emacs*Cursor:   black
+(which is invalid because it specifies a color name for something
+that isn't a color.)
+
+The fix is to correct your X resources.
+
+*** Slow startup on X11R6 with X windows.
+
+If Emacs takes two minutes to start up on X11R6, see if your X
+resources specify any Adobe fonts.  That causes the type-1 font
+renderer to start up, even if the font you asked for is not a type-1
+font.
+
+One way to avoid this problem is to eliminate the type-1 fonts from
+your font path, like this:
+
+	xset -fp /usr/X11R6/lib/X11/fonts/Type1/
+
+*** Pull-down menus appear in the wrong place, in the toolkit version of Emacs.
+
+An X resource of this form can cause the problem:
+
+   Emacs*geometry:	80x55+0+0
+
+This resource is supposed to apply, and does apply, to the menus
+individually as well as to Emacs frames.  If that is not what you
+want, rewrite the resource.
+
+To check thoroughly for such resource specifications, use `xrdb
+-query' to see what resources the X server records, and also look at
+the user's ~/.Xdefaults and ~/.Xdefaults-* files.
+
+*** --with-x-toolkit version crashes when used with shared libraries.
+
+On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others,
+unexec doesn't work properly with the shared library for the X
+toolkit.  You might be able to work around this by using a nonshared
+libXt.a library.  The real fix is to upgrade the various versions of
+unexec and/or ralloc.  We think this has been fixed on Sunos 4
+and Solaris in version 19.29.
+
+*** Emacs running under X Windows does not handle mouse clicks.
+*** `emacs -geometry 80x20' finds a file named `80x20'.

 One cause of such problems is having (setq term-file-prefix nil) in
 your .emacs file.  Another cause is a bad value of EMACSLOADPATH in
 the environment.

-* Emacs gets error message from linker on Sun.
-
-If the error message says that a symbol such as `f68881_used' or
-`ffpa_used' or `start_float' is undefined, this probably indicates
-that you have compiled some libraries, such as the X libraries,
-with a floating point option other than the default.
-
-It's not terribly hard to make this work with small changes in
-crt0.c together with linking with Fcrt1.o, Wcrt1.o or Mcrt1.o.
-However, the easiest approach is to build Xlib with the default
-floating point option: -fsoft.
-
-* Emacs fails to get default settings from X Windows server.
+*** Emacs fails to get default settings from X Windows server.

 The X library in X11R4 has a bug; it interchanges the 2nd and 3rd
 arguments to XGetDefaults.  Define the macro XBACKWARDS in config.h to
@@ -2841,35 +1297,7 @@
 I don't believe there is any way Emacs can determine for itself
 whether this problem is present on a given system.

-* Keyboard input gets confused after a beep when using a DECserver
-  as a concentrator.
-
-This problem seems to be a matter of configuring the DECserver to use
-7 bit characters rather than 8 bit characters.
-
-* M-x shell persistently reports "Process shell exited abnormally with code 1".
-
-This happened on Suns as a result of what is said to be a bug in Sunos
-version 4.0.x.  The only fix was to reboot the machine.
-
-* Programs running under terminal emulator do not recognize `emacs'
-  terminal type.
-
-The cause of this is a shell startup file that sets the TERMCAP
-environment variable.  The terminal emulator uses that variable to
-provide the information on the special terminal type that Emacs
-emulates.
-
-Rewrite your shell startup file so that it does not change TERMCAP
-in such a case.  You could use the following conditional which sets
-it only if it is undefined.
-
-    if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
-
-Or you could set TERMCAP only when you set TERM--which should not
-happen in a non-login shell.
-
-* X Windows doesn't work if DISPLAY uses a hostname.
+*** X Windows doesn't work if DISPLAY uses a hostname.

 People have reported kernel bugs in certain systems that cause Emacs
 not to work with X Windows if DISPLAY is set using a host name.  But
@@ -2886,188 +1314,9 @@

 in your site-init.el file.

-* Problem with remote X server on Suns.
-
-On a Sun, running Emacs on one machine with the X server on another
-may not work if you have used the unshared system libraries.  This
-is because the unshared libraries fail to use YP for host name lookup.
-As a result, the host name you specify may not be recognized.
-
-* Shell mode ignores interrupts on Apollo Domain
-
-You may find that M-x shell prints the following message:
-
-   Warning: no access to tty; thus no job control in this shell...
-
-This can happen if there are not enough ptys on your system.
-Here is how to make more of them.
-
-    % cd /dev
-    % ls pty*
-    # shows how many pty's you have. I had 8, named pty0 to pty7)
-    % /etc/crpty 8
-    # creates eight new pty's
-
-* Fatal signal in the command  temacs -l loadup inc dump
-
-This command is the final stage of building Emacs.  It is run by the
-Makefile in the src subdirectory, or by build.com on VMS.
-
-It has been known to get fatal errors due to insufficient swapping
-space available on the machine.
-
-On 68000's, it has also happened because of bugs in the
-subroutine `alloca'.  Verify that `alloca' works right, even
-for large blocks (many pages).
-
-* test-distrib says that the distribution has been clobbered
-* or, temacs prints "Command key out of range 0-127"
-* or, temacs runs and dumps emacs, but emacs totally fails to work.
-* or, temacs gets errors dumping emacs
-
-This can be because the .elc files have been garbled.  Do not be
-fooled by the fact that most of a .elc file is text: these are
-binary files and can contain all 256 byte values.
-
-In particular `shar' cannot be used for transmitting GNU Emacs.
-It typically truncates "lines".  What appear to be "lines" in
-a binary file can of course be of any length.  Even once `shar'
-itself is made to work correctly, `sh' discards null characters
-when unpacking the shell archive.
-
-I have also seen character \177 changed into \377.  I do not know
-what transfer means caused this problem.  Various network
-file transfer programs are suspected of clobbering the high bit.
-
-If you have a copy of Emacs that has been damaged in its
-nonprinting characters, you can fix them:
-
- 1) Record the names of all the .elc files.
- 2) Delete all the .elc files.
- 3) Recompile alloc.c with a value of PURESIZE twice as large.
-     (See puresize.h.)  You might as well save the old alloc.o.
- 4) Remake emacs.  It should work now.
- 5) Running emacs, do Meta-x byte-compile-file repeatedly
-  to recreate all the .elc files that used to exist.
-  You may need to increase the value of the variable
-  max-lisp-eval-depth to succeed in running the compiler interpreted
-  on certain .el files.  400 was sufficient as of last report.
- 6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
-  and remake temacs.
- 7) Remake emacs.  It should work now, with valid .elc files.
-
-* temacs prints "Pure Lisp storage exhausted"
-
-This means that the Lisp code loaded from the .elc and .el
-files during  temacs -l loadup inc dump  took up more
-space than was allocated.
-
-This could be caused by
- 1) adding code to the preloaded Lisp files
- 2) adding more preloaded files in loadup.el
- 3) having a site-init.el or site-load.el which loads files.
-   Note that ANY site-init.el or site-load.el is nonstandard;
-   if you have received Emacs from some other site
-   and it contains a site-init.el or site-load.el file, consider
-   deleting that file.
- 4) getting the wrong .el or .elc files
-   (not from the directory you expected).
- 5) deleting some .elc files that are supposed to exist.
-   This would cause the source files (.el files) to be
-   loaded instead.  They take up more room, so you lose.
- 6) a bug in the Emacs distribution which underestimates
-   the space required.
-
-If the need for more space is legitimate, change the definition
-of PURESIZE in puresize.h.
-
-But in some of the cases listed above, this problem is a consequence
-of something else that is wrong.  Be sure to check and fix the real
-problem.
-
-* Changes made to .el files do not take effect.
-
-You may have forgotten to recompile them into .elc files.
-Then the old .elc files will be loaded, and your changes
-will not be seen.  To fix this, do M-x byte-recompile-directory
-and specify the directory that contains the Lisp files.
-
-Emacs should print a warning when loading a .elc file which is older
-than the corresponding .el file.
-
-* The dumped Emacs crashes when run, trying to write pure data.
-
-Two causes have been seen for such problems.
-
-1) On a system where getpagesize is not a system call, it is defined
-as a macro.  If the definition (in both unexec.c and malloc.c) is wrong,
-it can cause problems like this.  You might be able to find the correct
-value in the man page for a.out (5).
-
-2) Some systems allocate variables declared static among the
-initialized variables.  Emacs makes all initialized variables in most
-of its files pure after dumping, but the variables declared static and
-not initialized are not supposed to be pure.  On these systems you
-may need to add "#define static" to the m- or the s- file.
-
-* Compilation errors on VMS.
-
-You will get warnings when compiling on VMS because there are
-variable names longer than 32 (or whatever it is) characters.
-This is not an error.  Ignore it.
-
-VAX C does not support #if defined(foo).  Uses of this construct
-were removed, but some may have crept back in.  They must be rewritten.
-
-There is a bug in the C compiler which fails to sign extend characters
-in conditional expressions.  The bug is:
-	char c = -1, d = 1;
-	int i;
-
-	i = d ? c : d;
-The result is i == 255;  the fix is to typecast the char in the
-conditional expression as an (int).  Known occurrences of such
-constructs in Emacs have been fixed.
-
-* rmail gets error getting new mail
-
-rmail gets new mail from /usr/spool/mail/$USER using a program
-called `movemail'.  This program interlocks with /bin/mail using
-the protocol defined by /bin/mail.
-
-There are two different protocols in general use.  One of them uses
-the `flock' system call.  The other involves creating a lock file;
-`movemail' must be able to write in /usr/spool/mail in order to do
-this.  You control which one is used by defining, or not defining,
-the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes.
-IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
-SYSTEM, YOU CAN LOSE MAIL!
-
-If your system uses the lock file protocol, and fascist restrictions
-prevent ordinary users from writing the lock files in /usr/spool/mail,
-you may need to make `movemail' setgid to a suitable group such as
-`mail'.  You can use these commands (as root):
-
-	chgrp mail movemail
-	chmod 2755 movemail
-
-If your system uses the lock file protocol, and fascist restrictions
-prevent ordinary users from writing the lock files in /usr/spool/mail,
-you may need to make `movemail' setgid to a suitable group such as
-`mail'.  To do this,  use the following commands (as root) after doing the
-make install.
-
-	chgrp mail movemail
-	chmod 2755 movemail
-
-Installation normally copies movemail from the build directory to an
-installation directory which is usually under /usr/local/lib.  The
-installed copy of movemail is usually in the directory
-/usr/local/lib/emacs/VERSION/TARGET.  You must change the group and
-mode of the installed copy; changing the group and mode of the build
-directory copy is ineffective.
-
-* Emacs spontaneously displays "I-search: " at the bottom of the screen.
+* Runtime problems on character termunals
+
+** Emacs spontaneously displays "I-search: " at the bottom of the screen.

 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
 used.  C-s/C-q flow control is bad for Emacs editors because it takes
@@ -3151,7 +1400,7 @@
 will not make Emacs worse for properly designed systems for the sake
 of inferior systems.

-* Control-S and Control-Q commands are ignored completely.
+** Control-S and Control-Q commands are ignored completely.

 For some reason, your system is using brain-damaged C-s/C-q flow
 control despite Emacs's attempts to turn it off.  Perhaps your
@@ -3166,33 +1415,7 @@
 into C-s and C-q using keyboard-translate-table.  The example above
 shows how to do this with C-^ and C-\.

-* Control-S and Control-Q commands are ignored completely on a net connection.
-
-Some versions of rlogin (and possibly telnet) do not pass flow
-control characters to the remote system to which they connect.
-On such systems, emacs on the remote system cannot disable flow
-control on the local system.
-
-One way to cure this is to disable flow control on the local host
-(the one running rlogin, not the one running rlogind) using the
-stty command, before starting the rlogin process.  On many systems,
-"stty start u stop u" will do this.
-
-Some versions of tcsh will prevent even this from working.  One way
-around this is to start another shell before starting rlogin, and
-issue the stty command to disable flow control from that shell.
-
-If none of these methods work, the best solution is to type
-M-x enable-flow-control at the beginning of your emacs session, or
-if you expect the problem to continue, add a line such as the
-following to your .emacs (on the host running rlogind):
-
-(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
-
-See the entry about spontaneous display of I-search (above) for more
-info.
-
-* Screen is updated wrong, but only on one kind of terminal.
+** Screen is updated wrong, but only on one kind of terminal.

 This could mean that the termcap entry you are using for that
 terminal is wrong, or it could mean that Emacs has a bug handing
@@ -3234,7 +1457,33 @@
 This is unambiguously an Emacs bug, and can probably be fixed
 in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.

-* Output from Control-V is slow.
+** Control-S and Control-Q commands are ignored completely on a net connection.
+
+Some versions of rlogin (and possibly telnet) do not pass flow
+control characters to the remote system to which they connect.
+On such systems, emacs on the remote system cannot disable flow
+control on the local system.
+
+One way to cure this is to disable flow control on the local host
+(the one running rlogin, not the one running rlogind) using the
+stty command, before starting the rlogin process.  On many systems,
+"stty start u stop u" will do this.
+
+Some versions of tcsh will prevent even this from working.  One way
+around this is to start another shell before starting rlogin, and
+issue the stty command to disable flow control from that shell.
+
+If none of these methods work, the best solution is to type
+M-x enable-flow-control at the beginning of your emacs session, or
+if you expect the problem to continue, add a line such as the
+following to your .emacs (on the host running rlogind):
+
+(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
+
+See the entry about spontaneous display of I-search (above) for more
+info.
+
+** Output from Control-V is slow.

 On many bit-map terminals, scrolling operations are fairly slow.
 Often the termcap entry for the type of terminal in use fails
@@ -3277,16 +1526,7 @@
 A `cs' string to set the scrolling region will reduce the amount
 of motion you see on the screen when part of the screen is scrolled.

-* Your Delete key sends a Backspace to the terminal, using an AIXterm.
-
-The solution is to include in your .Xdefaults the lines:
-
-   *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
-   aixterm*ttyModes: erase ^?
-
-This makes your Backspace key send DEL (ASCII 127).
-
-* You type Control-H (Backspace) expecting to delete characters.
+** You type Control-H (Backspace) expecting to delete characters.

 Put `stty dec' in your .login file and your problems will disappear
 after a day or two.
@@ -3310,56 +1550,1850 @@
   (global-set-key "\b" 'delete-backward-char)
 You can probably access  help-command  via f1.

-* Editing files through RFS gives spurious "file has changed" warnings.
-It is possible that a change in Emacs 18.37 gets around this problem,
-but in case not, here is a description of how to fix the RFS bug that
-causes it.
-
-    There was a serious pair of bugs in the handling of the fsync() system
-    call in the RFS server.
-
-    The first is that the fsync() call is handled as another name for the
-    close() system call (!!).  It appears that fsync() is not used by very
-    many programs; Emacs version 18 does an fsync() before closing files
-    to make sure that the bits are on the disk.
-
-    This is fixed by the enclosed patch to the RFS server.
-
-    The second, more serious problem, is that fsync() is treated as a
-    non-blocking system call (i.e., it's implemented as a message that
-    gets sent to the remote system without waiting for a reply).  Fsync is
-    a useful tool for building atomic file transactions.  Implementing it
-    as a non-blocking RPC call (when the local call blocks until the sync
-    is done) is a bad idea; unfortunately, changing it will break the RFS
-    protocol.  No fix was supplied for this problem.
-
-    (as always, your line numbers may vary)
-
-    % rcsdiff -c -r1.2 serversyscall.c
-    RCS file: RCS/serversyscall.c,v
-    retrieving revision 1.2
-    diff -c -r1.2 serversyscall.c
-    *** /tmp/,RCSt1003677   Wed Jan 28 15:15:02 1987
-    --- serversyscall.c     Wed Jan 28 15:14:48 1987
+** Colors are not available on a tty or in xterm.
+
+Emacs 21 supports colors on character terminals and terminal
+emulators, but this support relies on the terminfo or termcap database
+entry to specify that the display supports color.  Emacs looks at the
+"Co" capability for the terminal to find out how many colors are
+supported; it should be non-zero to activate the color support within
+Emacs.  (Most color terminals support 8 or 16 colors.)  If your system
+uses terminfo, the name of the capability equivalent to "Co" is
+"colors".
+
+In addition to the "Co" capability, Emacs needs the "op" (for
+``original pair'') capability, which tells how to switch the terminal
+back to the default foreground and background colors.  Emacs will not
+use colors if this capability is not defined.  If your terminal entry
+doesn't provide such a capability, try using the ANSI standard escape
+sequence \E[00m (that is, define a new termcap/terminfo entry and make
+it use your current terminal's entry plus \E[00m for the "op"
+capability).
+
+Finally, the "NC" capability (terminfo name: "ncv") tells Emacs which
+attributes cannot be used with colors.  Setting this capability
+incorrectly might have the effect of disabling colors; try setting
+this capability to `0' (zero) and see if that helps.
+
+Emacs uses the database entry for the terminal whose name is the value
+of the environment variable TERM.  With `xterm', a common terminal
+entry that supports color is `xterm-color', so setting TERM's value to
+`xterm-color' might activate the color support on an xterm-compatible
+emulator.
+
+Beginning with version 21.4, Emacs supports the --color command-line
+option which may be used to force Emacs to use one of a few popular
+modes for getting colors on a tty.  For example, --color=ansi8 sets up
+for using the ANSI-standard escape sequences that support 8 colors.
+
+Some modes do not use colors unless you turn on the Font-lock mode.
+Some people have long ago set their `~/.emacs' files to turn on
+Font-lock on X only, so they won't see colors on a tty.  The
+recommended way of turning on Font-lock is by typing "M-x
+global-font-lock-mode RET" or by customizing the variable
+`global-font-lock-mode'.
+
+* Runtime problems specific to individual Unix variants
+
+** GNU/Linux
+
+*** GNU/Linux: On Linux-based GNU systems using libc versions 5.4.19 through
+5.4.22, Emacs crashes at startup with a segmentation fault.
+
+This problem happens if libc defines the symbol __malloc_initialized.
+One known solution is to upgrade to a newer libc version.  5.4.33 is
+known to work.
+
+*** GNU/Linux: After upgrading to a newer version of Emacs,
+the Meta key stops working.
+
+This was reported to happen on a GNU/Linux system distributed by
+Mandrake.  The reason is that the previous version of Emacs was
+modified by Mandrake to make the Alt key act as the Meta key, on a
+keyboard where the Windows key is the one which produces the Meta
+modifier.  A user who started using a newer version of Emacs, which
+was not hacked by Mandrake, expected the Alt key to continue to act as
+Meta, and was astonished when that didn't happen.
+
+The solution is to find out what key on your keyboard produces the Meta
+modifier, and use that key instead.  Try all of the keys to the left
+and to the right of the space bar, together with the `x' key, and see
+which combination produces "M-x" in the echo area.  You can also use
+the `xmodmap' utility to show all the keys which produce a Meta
+modifier:
+
+         xmodmap -pk | egrep -i "meta|alt"
+
+A more convenient way of finding out which keys produce a Meta modifier
+is to use the `xkbprint' utility, if it's available on your system:
+
+         xkbprint 0:0 /tmp/k.ps
+
+This produces a PostScript file `/tmp/k.ps' with a picture of your
+keyboard; printing that file on a PostScript printer will show what
+keys can serve as Meta.
+
+The `xkeycaps' also shows a visual representation of the current
+keyboard settings.  It also allows to modify them.
+
+*** GNU/Linux: low startup on Linux-based GNU systems.
+
+People using systems based on the Linux kernel sometimes report that
+startup takes 10 to 15 seconds longer than `usual'.
+
+This is because Emacs looks up the host name when it starts.
+Normally, this takes negligible time; the extra delay is due to
+improper system configuration.  This problem can occur for both
+networked and non-networked machines.
+
+Here is how to fix the configuration.  It requires being root.
+
+**** Networked Case.
+
+First, make sure the files `/etc/hosts' and `/etc/host.conf' both
+exist.  The first line in the `/etc/hosts' file should look like this
+(replace HOSTNAME with your host name):
+
+    127.0.0.1      HOSTNAME
+
+Also make sure that the `/etc/host.conf' files contains the following
+lines:
+
+    order hosts, bind
+    multi on
+
+Any changes, permanent and temporary, to the host name should be
+indicated in the `/etc/hosts' file, since it acts a limited local
+database of addresses and names (e.g., some SLIP connections
+dynamically allocate ip addresses).
+
+**** Non-Networked Case.
+
+The solution described in the networked case applies here as well.
+However, if you never intend to network your machine, you can use a
+simpler solution: create an empty `/etc/host.conf' file.  The command
+`touch /etc/host.conf' suffices to create the file.  The `/etc/hosts'
+file is not necessary with this approach.
+
+*** GNU/Linux: Emacs on a tty switches the cursor to large blinking block.
+
+This was reported to happen on some GNU/Linux systems which use
+ncurses version 5.0, but could be relevant for other versions as well.
+These versions of ncurses come with a `linux' terminfo entry, where
+the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c"
+(show cursor, change size).  This escape sequence switches on a
+blinking hardware text-mode cursor whose size is a full character
+cell.  This blinking cannot be stopped, since a hardware cursor
+always blinks.
+
+A work-around is to redefine the "cvvis" capability so that it
+enables a *software* cursor.  The software cursor works by inverting
+the colors of the character at point, so what you see is a block
+cursor that doesn't blink.  For this to work, you need to redefine
+the "cnorm" capability as well, so that it operates on the software
+cursor instead of the hardware cursor.
+
+To this end, run "infocmp linux > linux-term", edit the file
+`linux-term' to make both the "cnorm" and "cvvis" capabilities send
+the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
+produce a modified terminfo entry.
+
+Alternatively, if you want a blinking underscore as your Emacs cursor,
+change the "cvvis" capability to send the "\E[?25h\E[?0c" command.
+
+*** GNU/Linux: Error messages `internal facep []' happen on GNU/Linux systems.
+
+There is a report that replacing libc.so.5.0.9 with libc.so.5.2.16
+caused this to start happening.  People are not sure why, but the
+problem seems unlikely to be in Emacs itself.  Some suspect that it
+is actually Xlib which won't work with libc.so.5.2.16.
+
+Using the old library version is a workaround.
+
+** Mac OS X
+
+*** Mac OS X (Carbon): Environment Variables from dotfiles are ignored.
+
+When starting Emacs from the Dock or the Finder on Mac OS X, the
+environment variables that are set up in dotfiles, such as .cshrc or
+.profile, are ignored.  This is because the Finder and Dock are not
+started from a shell, but instead from the Window Manager itself.
+
+The workaround for this is to create a .MacOSX/environment.plist file to
+setup these environment variables.  These environment variables will
+apply to all processes regardless of where they are started.
+For me information, see http://developer.apple.com/qa/qa2001/qa1067.html.
+
+*** Mac OS X (Carbon): Process output truncated when using ptys.
+
+There appears to be a problem with the implementation of pty's on the
+Mac OS X that causes process output to be truncated.  To avoid this,
+leave process-connection-type set to its default value of nil.
+
+** FreeBSD
+
+*** FreeBSD 2.1.5: useless symbolic links remain in /tmp or other
+directories that have the +t bit.
+
+This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2).
+Emacs uses symbolic links to implement file locks.  In a directory
+with +t bit, the directory owner becomes the owner of the symbolic
+link, so that it cannot be removed by anyone else.
+
+If you don't like those useless links, you can let Emacs not to using
+file lock by adding #undef CLASH_DETECTION to config.h.
+
+*** FreeBSD: Getting a Meta key on the console.
+
+By default, neither Alt nor any other key acts as a Meta key on
+FreeBSD, but this can be changed using kbdcontrol(1).  Dump the
+current keymap to a file with the command
+
+  $ kbdcontrol -d >emacs.kbd
+
+Edit emacs.kbd, and give the key you want to be the Meta key the
+definition `meta'.  For instance, if your keyboard has a ``Windows''
+key with scan code 105, change the line for scan code 105 in emacs.kbd
+to look like this
+
+  105   meta   meta   meta   meta   meta   meta   meta   meta    O
+
+to make the Windows key the Meta key.  Load the new keymap with
+
+  $ kbdcontrol -l emacs.kbd
+
+** HP-UX
+
+*** HP/UX : Shell mode gives the message, "`tty`: Ambiguous".
+
+christos@theory.tn.cornell.edu says:
+
+The problem is that in your .cshrc you have something that tries to
+execute `tty`. If you are not running the shell on a real tty then
+tty will print "not a tty". Csh expects one word in some places,
+but tty is giving it back 3.
+
+The solution is to add a pair of quotes around `tty` to make it a single
+word:
+
+if (`tty` == "/dev/console")
+
+should be changed to:
+
+if ("`tty`" == "/dev/console")
+
+Even better, move things that set up terminal sections out of .cshrc
+and into .login.
+
+*** HP/UX: `Pid xxx killed due to text modification or page I/O error'.
+
+On HP/UX, you can get that error when the Emacs executable is on an NFS
+file system.  HP/UX responds this way if it tries to swap in a page and
+does not get a response from the server within a timeout whose default
+value is just ten seconds.
+
+If this happens to you, extend the timeout period.
+
+*** HP/UX: Emacs is slow using X11R5.
+
+This happens if you use the MIT versions of the X libraries--it
+doesn't run as fast as HP's version.  People sometimes use the version
+because they see the HP version doesn't have the libraries libXaw.a,
+libXmu.a, libXext.a and others.  HP/UX normally doesn't come with
+those libraries installed.  To get good performance, you need to
+install them and rebuild Emacs.
+
+*** HP/UX: The right Alt key works wrong on German HP keyboards (and perhaps
+other non-English HP keyboards too).
+
+This is because HP-UX defines the modifiers wrong in X.  Here is a
+shell script to fix the problem; be sure that it is run after VUE
+configures the X server.
+
+    xmodmap 2> /dev/null - << EOF
+    keysym Alt_L = Meta_L
+    keysym Alt_R = Meta_R
+    EOF
+
+    xmodmap - << EOF
+    clear mod1
+    keysym Mode_switch = NoSymbol
+    add mod1 = Meta_L
+    keysym Meta_R = Mode_switch
+    add mod2 = Mode_switch
+    EOF
+
+*** HP/UX: "Cannot find callback list" messages from dialog boxes in
+Emacs built with Motif.
+
+This problem resulted from a bug in GCC 2.4.5.  Newer GCC versions
+such as 2.7.0 fix the problem.
+
+*** HP/UX: Emacs does not recognize the AltGr key.
+
+To fix this, set up a file ~/.dt/sessions/sessionetc with executable
+rights, containing this text:
+
+--------------------------------
+xmodmap 2> /dev/null - << EOF
+keysym Alt_L = Meta_L
+keysym Alt_R = Meta_R
+EOF
+
+xmodmap - << EOF
+clear mod1
+keysym Mode_switch = NoSymbol
+add mod1 = Meta_L
+keysym Meta_R = Mode_switch
+add mod2 = Mode_switch
+EOF
+--------------------------------
+
+*** HP/UX: Large file support is disabled.
+
+See the comments in src/s/hpux10.h.
+
+*** HP/UX 11.0: Emacs makes HP/UX 11.0 crash.
+
+This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it.
+
+** AIX
+
+*** AIX: Trouble using ptys.
+
+People often install the pty devices on AIX incorrectly.
+Use `smit pty' to reinstall them properly.
+
+*** AIXterm: Your Delete key sends a Backspace to the terminal.
+
+The solution is to include in your .Xdefaults the lines:
+
+   *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
+   aixterm*ttyModes: erase ^?
+
+This makes your Backspace key send DEL (ASCII 127).
+
+*** AIX: You get this message when running Emacs:
+
+    Could not load program emacs
+    Symbol smtcheckinit in csh is undefined
+    Error was: Exec format error
+
+or this one:
+
+    Could not load program .emacs
+    Symbol _system_con in csh is undefined
+    Symbol _fp_trapsta in csh is undefined
+    Error was: Exec format error
+
+These can happen when you try to run on AIX 3.2.5 a program that was
+compiled with 3.2.4.  The fix is to recompile.
+
+*** AIX 3.2.4: Releasing Ctrl/Act key has no effect, if Shift is down.
+
+Due to a feature of AIX, pressing or releasing the Ctrl/Act key is
+ignored when the Shift, Alt or AltGr keys are held down.  This can
+lead to the keyboard being "control-locked"--ordinary letters are
+treated as control characters.
+
+You can get out of this "control-locked" state by pressing and
+releasing Ctrl/Act while not pressing or holding any other keys.
+
+*** AIX 4.2: Emacs gets a segmentation fault at startup.
+
+If you are using IBM's xlc compiler, compile emacs.c
+without optimization; that should avoid the problem.
+
+*** AIX: If linking fails because libXbsd isn't found, check if you
+are compiling with the system's `cc' and CFLAGS containing `-O5'.  If
+so, you have hit a compiler bug.  Please make sure to re-configure
+Emacs so that it isn't compiled with `-O5'.
+
+*** AIX 4.3.x or 4.4: Compiling fails.
+
+This could happen if you use /bin/c89 as your compiler, instead of
+the default `cc'.  /bin/c89 treats certain warnings, such as benign
+redefinitions of macros, as errors, and fails the build.  A solution
+is to use the default compiler `cc'.
+
+*** AIX 4: Some programs fail when run in a Shell buffer
+with an error message like   No terminfo entry for "unknown".
+
+On AIX, many terminal type definitions are not installed by default.
+`unknown' is one of them.  Install the "Special Generic Terminal
+Definitions" to make them defined.
+
+** Solaris
+
+We list bugs in current versions here.  Solaris 2.x and 4.x are covered in the
+section on legacy systems.
+
+*** On Solaris, C-x doesn't get through to Emacs when you use the console.
+
+This is a Solaris feature (at least on Intel x86 cpus).  Type C-r
+C-r C-t, to toggle whether C-x gets through to Emacs.
+
+*** Problem with remote X server on Suns.
+
+On a Sun, running Emacs on one machine with the X server on another
+may not work if you have used the unshared system libraries.  This
+is because the unshared libraries fail to use YP for host name lookup.
+As a result, the host name you specify may not be recognized.
+
+*** Emacs reports a BadAtom error (from X) running on Solaris 7 or 8.
+
+This happens when Emacs was built on some other version of Solaris.
+Rebuild it on Solaris 8.
+
+*** On Solaris, CTRL-t is ignored by Emacs when you use
+the fr.ISO-8859-15 locale (and maybe other related locales).
+
+You can fix this by editing the file:
+
+	/usr/openwin/lib/locale/iso8859-15/Compose
+
+Near the bottom there is a line that reads:
+
+	Ctrl<t> <quotedbl> <Y>                  : "\276"        threequarters
+
+that should read:
+
+	Ctrl<T> <quotedbl> <Y>                  : "\276"        threequarters
+
+Note the lower case <t>.  Changing this line should make C-t work.
+
+*** When using M-x dbx with the SparcWorks debugger, the `up' and `down'
+commands do not move the arrow in Emacs.
+
+You can fix this by adding the following line to `~/.dbxinit':
+
+ dbxenv output_short_file_name off
+
+** Irix
+
+*** Irix 5.2: unexelfsgi.c can't find cmplrs/stsupport.h.
+
+The file cmplrs/stsupport.h was included in the wrong file set in the
+Irix 5.2 distribution.  You can find it in the optional fileset
+compiler_dev, or copy it from some other Irix 5.2 system.  A kludgy
+workaround is to change unexelfsgi.c to include sym.h instead of
+syms.h.
+
+*** Irix 5.3: "out of virtual swap space".
+
+This message occurs when the system runs out of swap space due to too
+many large programs running.  The solution is either to provide more
+swap space or to reduce the number of large programs being run.  You
+can check the current status of the swap space by executing the
+command `swap -l'.
+
+You can increase swap space by changing the file /etc/fstab.  Adding a
+line like this:
+
+/usr/swap/swap.more     swap    swap    pri=3 0 0
+
+where /usr/swap/swap.more is a file previously created (for instance
+by using /etc/mkfile), will increase the swap space by the size of
+that file.  Execute `swap -m' or reboot the machine to activate the
+new swap area.  See the manpages for `swap' and `fstab' for further
+information.
+
+The objectserver daemon can use up lots of memory because it can be
+swamped with NIS information.  It collects information about all users
+on the network that can log on to the host.
+
+If you want to disable the objectserver completely, you can execute
+the command `chkconfig objectserver off' and reboot.  That may disable
+some of the window system functionality, such as responding CDROM
+icons.
+
+You can also remove NIS support from the objectserver.  The SGI `admin'
+FAQ has a detailed description on how to do that; see question 35
+("Why isn't the objectserver working?").  The admin FAQ can be found at
+ftp://viz.tamu.edu/pub/sgi/faq/.
+
+*** Irix 5.3: Emacs crashes in utmpname.
+
+This problem is fixed in Patch 3175 for Irix 5.3.
+It is also fixed in Irix versions 6.2 and up.
+
+*** Irix 6.0: Make tries (and fails) to build a program named unexelfsgi.
+
+A compiler bug inserts spaces into the string "unexelfsgi . o"
+in src/Makefile.  Edit src/Makefile, after configure is run,
+find that string, and take out the spaces.
+
+Compiler fixes in Irix 6.0.1 should eliminate this problem.
+
+*** Irix 6.5: Emacs crashes on the SGI R10K, when compiled with GCC.
+
+This seems to be fixed in GCC 2.95.
+
+*** Trouble using ptys on IRIX, or running out of ptys.
+
+The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
+be set-UID to root, or non-root programs like Emacs will not be able
+to allocate ptys reliably.
+
+** SCO Unix and UnixWare
+
+*** SCO 3.2v4: Unusable default font.
+
+The Open Desktop environment comes with default X resource settings
+that tell Emacs to use a variable-width font.  Emacs cannot use such
+fonts, so it does not work.
+
+This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
+the application-specific resource file for the `scoterm' terminal
+emulator program.  It contains several extremely general X resources
+that affect other programs besides `scoterm'.  In particular, these
+resources affect Emacs also:
+
+	*Font: -*-helvetica-medium-r-*--12-*-p-*
+	*Background:			scoBackground
+	*Foreground:			scoForeground
+
+The best solution is to create an application-specific resource file for
+Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents:
+
+	Emacs*Font:	-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
+	Emacs*Background:	white
+	Emacs*Foreground:	black
+
+(These settings mimic the Emacs defaults, but you can change them to
+suit your needs.)  This resource file is only read when the X server
+starts up, so you should restart it by logging out of the Open Desktop
+environment or by running `scologin stop; scologin start` from the shell
+as root.  Alternatively, you can put these settings in the
+/usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs,
+but then they will not affect remote invocations of Emacs that use the
+Open Desktop display.
+
+These resource files are not normally shared across a network of SCO
+machines; you must create the file on each machine individually.
+
+*** Regular expressions matching bugs on SCO systems.
+
+On SCO, there are problems in regexp matching when Emacs is compiled
+with the system compiler.  The compiler version is "Microsoft C
+version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
+C Compiler Version 1.00.46 (Beta).  The solution is to compile with
+GCC.
+
+*** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
+
+Paul Abrahams (abrahams@acm.org) reports that with the installed
+virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
+the "make" that builds Emacs, when running temacs to dump emacs.  That
+error indicates that the per-process virtual memory limit has been
+exceeded.  The default limit is probably 32MB.  Raising the virtual
+memory limit to 40MB should make it possible to finish building Emacs.
+
+You can do this with the command `ulimit' (sh) or `limit' (csh).
+But you have to be root to do it.
+
+According to Martin Sohnius, you can also retune this in the kernel:
+
+    # /etc/conf/bin/idtune SDATLIM 33554432         ## soft data size limit
+    # /etc/conf/bin/idtune HDATLIM 33554432         ## hard "
+    # /etc/conf/bin/idtune SVMMSIZE unlimited       ## soft process size limit
+    # /etc/conf/bin/idtune HVMMSIZE unlimited       ## hard "
+    # /etc/conf/bin/idbuild -B
+
+(He recommends you not change the stack limit, though.)
+These changes take effect when you reboot.
+
+* Runtime problems specific to MS-Windows
+
+** Emacs exits with "X protocol error" when run with an X server for MS-Windows.
+
+A certain X server for Windows had a bug which caused this.
+Supposedly the newer 32-bit version of this server doesn't have the
+problem.
+
+** Known problems with the MS-Windows port of Emacs 21.2.
+
+Frames are not refreshed while the File or Font dialog or a pop-up menu
+is displayed. This also means help text for pop-up menus is not
+displayed at all.  This is because message handling under Windows is
+synchronous, so we cannot handle repaint (or any other) messages while
+waiting for a system function to return the result of the dialog or
+pop-up menu interaction.
+
+Windows 95 and Windows NT up to version 4.0 do not support help text
+for menus.  Help text is only available in later versions of Windows.
+
+There are problems with display if mouse-tracking is enabled and the
+mouse is moved off a frame, over another frame then back over the first
+frame.  A workaround is to click the left mouse button inside the frame
+after moving back into it.
+
+Some minor flickering still persists during mouse-tracking, although
+not as severely as in 21.1.
+
+Emacs can sometimes abort when non-ASCII text, possibly with null
+characters, is copied and pasted into a buffer.
+
+An inactive cursor remains in an active window after the Windows
+Manager driven switch of the focus, until a key is pressed.
+
+Windows input methods are not recognized by Emacs (as of v21.2).  Some
+of these input methods cause the keyboard to send characters encoded
+in the appropriate coding system (e.g., ISO 8859-1 for Latin-1
+characters, ISO 8859-8 for Hebrew characters, etc.).  To make this
+work, set the keyboard coding system to the appropriate value after
+you activate the Windows input method.  For example, if you activate
+the Hebrew input method, type "C-x RET k iso-8859-8 RET".  (Emacs
+ought to recognize the Windows language-change event and set up the
+appropriate keyboard encoding automatically, but it doesn't do that
+yet.)
+
+The %b specifier for format-time-string does not produce abbreviated
+month names with consistent widths for some locales on some versions
+of Windows. This is caused by a deficiency in the underlying system
+library function.
+
+** Problems running Perl under Emacs on MS-Windows NT/95.
+
+`perl -de 0' just hangs when executed in an Emacs subshell.
+The fault lies with Perl (indirectly with Windows NT/95).
+
+The problem is that the Perl debugger explicitly opens a connection to
+"CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
+with the user.
+
+On Unix, this is okay, because Emacs (or the shell?) creates a
+pseudo-tty so that /dev/tty is really the pipe Emacs is using to
+communicate with the subprocess.
+
+On NT, this fails because CON always refers to the handle for the
+relevant console (approximately equivalent to a tty), and cannot be
+redirected to refer to the pipe Emacs assigned to the subprocess as
+stdin.
+
+A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
+
+For Perl 4:
+
+    *** PERL/LIB/PERLDB.PL.orig	Wed May 26 08:24:18 1993
+    --- PERL/LIB/PERLDB.PL	Mon Jul 01 15:28:16 1996
+    ***************
+    *** 68,74 ****
+	  $rcfile=".perldb";
+      }
+      else {
+    !     $console = "con";
+	  $rcfile="perldb.ini";
+      }
+
+    --- 68,74 ----
+	  $rcfile=".perldb";
+      }
+      else {
+    !     $console = "";
+	  $rcfile="perldb.ini";
+      }
+
+
+    For Perl 5:
+    *** perl/5.001/lib/perl5db.pl.orig	Sun Jun 04 21:13:40 1995
+    --- perl/5.001/lib/perl5db.pl	Mon Jul 01 17:00:08 1996
     ***************
-    *** 163,169 ****
-	    /*
-	     * No return sent for close or fsync!
-	     */
-    !       if (syscall == RSYS_close || syscall == RSYS_fsync)
-		    proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
-	    else
-	    {
-    --- 166,172 ----
-	    /*
-	     * No return sent for close or fsync!
-	     */
-    !       if (syscall == RSYS_close)
-		    proc->p_returnval = deallocate_fd(proc, msg->m_args[0]);
-	    else
-	    {
-
-* Vax C compiler bugs affecting Emacs.
+    *** 22,28 ****
+	  $rcfile=".perldb";
+      }
+      elsif (-e "con") {
+    !     $console = "con";
+	  $rcfile="perldb.ini";
+      }
+      else {
+    --- 22,28 ----
+	  $rcfile=".perldb";
+      }
+      elsif (-e "con") {
+    !     $console = "";
+	  $rcfile="perldb.ini";
+      }
+      else {
+
+** On MS-Windows 95, Alt-f6 does not get through to Emacs.
+
+This character seems to be trapped by the kernel in Windows 95.
+You can enter M-f6 by typing ESC f6.
+
+** Typing Alt-Shift has strange effects on MS-Windows.
+
+This combination of keys is a command to change keyboard layout.  If
+you proceed to type another non-modifier key before you let go of Alt
+and Shift, the Alt and Shift act as modifiers in the usual way.  A
+more permanent work around is to change it to another key combination,
+or disable it in the keyboard control panel.
+
+** Interrupting Cygwin port of Bash from Emacs doesn't work.
+
+Cygwin 1.x builds of the ported Bash cannot be interrupted from the
+MS-Windows version of Emacs.  This is due to some change in the Bash
+port or in the Cygwin library which apparently make Bash ignore the
+keyboard interrupt event sent by Emacs to Bash.  (Older Cygwin ports
+of Bash, up to b20.1, did receive SIGINT from Emacs.)
+
+** Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
+
+If the FTP client is the Cygwin port of GNU `ftp', this appears to be
+due to some bug in the Cygwin DLL or some incompatibility between it
+and the implementation of asynchronous subprocesses in the Windows
+port of Emacs.  Specifically, some parts of the FTP server responses
+are not flushed out, apparently due to buffering issues, which
+confuses ange-ftp.
+
+The solution is to downgrade to an older version of the Cygwin DLL
+(version 1.3.2 was reported to solve the problem), or use the stock
+Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
+directory.  To force ange-ftp use the stock Windows client, set the
+variable `ange-ftp-ftp-program-name' to the absolute file name of the
+client's executable.  For example:
+
+ (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
+
+If you want to stick with the Cygwin FTP client, you can work around
+this problem by putting this in your `.emacs' file:
+
+ (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
+
+** lpr commands don't work on MS-Windows with some cheap printers.
+
+This problem may also strike other platforms, but the solution is
+likely to be a global one, and not Emacs specific.
+
+Many cheap inkjet, and even some cheap laser printers, do not
+print plain text anymore, they will only print through graphical
+printer drivers. A workaround on MS-Windows is to use Windows' basic
+built in editor to print (this is possibly the only useful purpose it
+has):
+
+(setq printer-name "")         ;; notepad takes the default
+(setq lpr-command "notepad")   ;; notepad
+(setq lpr-switches nil)        ;; not needed
+(setq lpr-printer-switch "/P") ;; run notepad as batch printer
+
+** Antivirus software interacts badly with the MS-Windows version of Emacs.
+
+The usual manifestation of these problems is that subprocesses don't
+work or even wedge the entire system.  In particular, "M-x shell RET"
+was reported to fail to work.  But other commands also sometimes don't
+work when an antivirus package is installed.
+
+The solution is to switch the antivirus software to a less aggressive
+mode (e.g., disable the ``auto-protect'' feature), or even uninstall
+or disable it entirely.
+
+** On MS-Windows 95/98/ME, subprocesses do not terminate properly.
+
+This is a limitation of the Operating System, and can cause problems
+when shutting down Windows. Ensure that all subprocesses are exited
+cleanly before exiting Emacs. For more details, see the FAQ at
+http://www.gnu.org/software/emacs/windows/.
+
+** MS-Windows 95/98/ME crashes when Emacs invokes non-existent programs.
+
+When a program you are trying to run is not found on the PATH,
+Windows might respond by crashing or locking up your system.  In
+particular, this has been reported when trying to compile a Java
+program in JDEE when javac.exe is installed, but not on the system
+PATH.
+
+** Pressing the mouse button on MS-Windows does not give a mouse-2 event.
+
+This is usually a problem with the mouse driver. Because most Windows
+programs do not do anything useful with the middle mouse button, many
+mouse drivers allow you to define the wheel press to do something
+different. Some drivers do not even have the option to generate a
+middle button press. In such cases, setting the wheel press to
+"scroll" sometimes works if you press the button twice. Trying a
+generic mouse driver might help.
+
+** Scrolling the mouse wheel on MS-Windows always scrolls the top window.
+
+This is another common problem with mouse drivers. Instead of
+generating scroll events, some mouse drivers try to fake scroll bar
+movement. But they are not intelligent enough to handle multiple
+scroll bars within a frame. Trying a generic mouse driver might help.
+
+** Mail sent through Microsoft Exchange in some encodings appears to be
+mangled and is not seen correctly in Rmail or Gnus.  We don't know
+exactly what happens, but it isn't an Emacs problem in cases we've
+seen.
+
+** On MS-Windows, you cannot use the right-hand ALT key and the left-hand
+CTRL key together to type a Control-Meta character.
+
+This is a consequence of a misfeature beyond Emacs's control.
+
+Under Windows, the AltGr key on international keyboards generates key
+events with the modifiers Right-Alt and Left-Ctrl.  Since Emacs cannot
+distinguish AltGr from an explicit Right-Alt and Left-Ctrl
+combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
+AltGr has been pressed.  The variable `w32-recognize-altgr' can be set
+to nil to tell Emacs that AltGr is really Ctrl and Alt.
+
+** Under some X-servers running on MS-Windows, Emacs' display is incorrect.
+
+The symptoms are that Emacs does not completely erase blank areas of the
+screen during scrolling or some other screen operations (e.g., selective
+display or when killing a region).  M-x recenter will cause the screen
+to be completely redisplayed and the "extra" characters will disappear.
+
+This is known to occur under Exceed 6, and possibly earlier versions
+as well; it is reportedly solved in version 6.2.0.16 and later.  The
+problem lies in the X-server settings.
+
+There are reports that you can solve the problem with Exceed by
+running `Xconfig' from within NT, choosing "X selection", then
+un-checking the boxes "auto-copy X selection" and "auto-paste to X
+selection".
+
+Of this does not work, please inform bug-gnu-emacs@gnu.org.  Then
+please call support for your X-server and see if you can get a fix.
+If you do, please send it to bug-gnu-emacs@gnu.org so we can list it
+here.
+
+* Build-time problems
+
+** Configuration
+
+*** The `configure' script doesn't find the jpeg library.
+
+There are reports that this happens on some systems because the linker
+by default only looks for shared libraries, but jpeg distribution by
+default only installs a nonshared version of the library, `libjpeg.a'.
+
+If this is the problem, you can configure the jpeg library with the
+`--enable-shared' option and then rebuild libjpeg.  This produces a
+shared version of libjpeg, which you need to install.  Finally, rerun
+the Emacs configure script, which should now find the jpeg library.
+Alternatively, modify the generated src/Makefile to link the .a file
+explicitly, and edit src/config.h to define HAVE_JPEG.
+
+*** AIX: You get this compiler error message:
+
+    Processing include file ./XMenuInt.h
+        1501-106: (S) Include file X11/Xlib.h not found.
+
+This means your system was installed with only the X11 runtime i.d
+libraries.  You have to find your sipo (bootable tape) and install
+X11Dev... with smit.
+
+** Compilation
+
+*** Building Emacs over NFS fails with ``Text file busy''.
+
+This was reported to happen when building Emacs on a GNU/Linux system
+(RedHat Linux 6.2) using a build directory automounted from Solaris
+(SunOS 5.6) file server, but it might not be limited to that
+configuration alone.  Presumably, the NFS server doesn't commit the
+files' data to disk quickly enough, and the Emacs executable file is
+left ``busy'' for several seconds after Emacs has finished dumping
+itself.  This causes the subsequent commands which invoke the dumped
+Emacs executable to fail with the above message.
+
+In some of these cases, a time skew between the NFS server and the
+machine where Emacs is built is detected and reported by GNU Make
+(it says that some of the files have modification time in the future).
+This might be a symptom of NFS-related problems.
+
+If the NFS server runs on Solaris, apply the Solaris patch 105379-05
+(Sunos 5.6: /kernel/misc/nfssrv patch).  If that doesn't work, or if
+you have a different version of the OS or the NFS server, you can
+force the NFS server to use 1KB blocks, which was reported to fix the
+problem albeit at a price of slowing down file I/O.  You can force 1KB
+blocks by specifying the "-o  rsize=1024,wsize=1024" options to the
+`mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
+options in the appropriate system configuration file, such as
+`/etc/auto.home'.
+
+Alternatively, when Make fails due to this problem, you could wait for
+a few seconds and then invoke Make again.  In one particular case,
+waiting for 10 or more seconds between the two Make invocations seemed
+to work around the problem.
+
+Similar problems can happen if your machine NFS-mounts a directory
+onto itself.  Suppose the Emacs sources live in `/usr/local/src' and
+you are working on the host called `marvin'.  Then an entry in the
+`/etc/fstab' file like the following is asking for trouble:
+
+    marvin:/usr/local/src /usr/local/src ...options.omitted...
+
+The solution is to remove this line from `etc/fstab'.
+
+*** Building Emacs with GCC 2.9x fails in the `src' directory.
+
+This may happen if you use a development version of GNU `cpp' from one
+of the GCC snapshots between Oct 2000 and Feb 2001, or from a released
+version of GCC newer than 2.95.2 which was prepared around those
+dates; similar problems were reported with some snapshots of GCC 3.1
+around Sep 30 2001.  The preprocessor in those versions is
+incompatible with a traditional Unix cpp (e.g., it expands ".." into
+". .", which breaks relative file names that reference the parent
+directory; or inserts TAB characters before lines that set Make
+variables).
+
+The solution is to make sure the preprocessor is run with the
+`-traditional' option.  The `configure' script does that automatically
+when it detects the known problems in your cpp, but you might hit some
+unknown ones.  To force the `configure' script to use `-traditional',
+run the script like this:
+
+  CPP='gcc -E -traditional' ./configure ...
+
+(replace the ellipsis "..." with any additional arguments you pass to
+the script).
+
+Note that this problem does not pertain to the MS-Windows port of
+Emacs, since it doesn't use the preprocessor to generate Makefiles.
+
+*** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
+*** Compiling wakeup, in lib-src, says it can't make wakeup.c.
+
+This can happen if configure uses GNU sed version 2.03.  That version
+had a bug.  GNU sed version 2.05 works properly.To solve the
+problem, install the current version of GNU Sed, then rerun Emacs's
+configure script.
+
+*** Compiling lib-src says there is no rule to make test-distrib.c.
+
+This results from a bug in a VERY old version of GNU Sed.  To solve
+the problem, install the current version of GNU Sed, then rerun
+Emacs's configure script.
+
+*** Building the MS-Windows port with Cygwin GCC can fail.
+
+Emacs may not build using recent Cygwin builds of GCC, such as Cygwin
+version 1.1.8, using the default configure settings.  It appears to be
+necessary to specify the -mwin32 flag when compiling, and define
+__MSVCRT__, like so:
+
+  configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__
+
+*** Building the MS-Windows port fails with a CreateProcess failure.
+
+Some versions of mingw32 make on some versions of Windows do not seem
+to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
+fails, try running make from Cygwin bash instead.
+
+*** Building the MS-Windows port with Leim fails in the `leim' directory.
+
+The error message might be something like this:
+
+ Converting d:/emacs-21.3/leim/CXTERM-DIC/4Corner.tit to quail-package...
+ Invalid ENCODE: value in TIT dictionary
+ NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
+       '0xffffffff'
+ Stop.
+
+This can happen if the Leim distribution is unpacked with a program
+which converts the `*.tit' files to DOS-style CR-LF text format.  The
+`*.tit' files in the leim/CXTERM-DIC directory require Unix-style line
+endings to compile properly, because Emacs reads them without any code
+or EOL conversions.
+
+The solution is to make sure the program used to unpack Leim does not
+change the files' line endings behind your back.  The GNU FTP site has
+in the `/gnu/emacs/windows' directory a program called `djtarnt.exe'
+which can be used to unpack `.tar.gz' and `.zip' archives without
+mangling them.
+
+*** Building `ctags' for MS-Windows with the MinGW port of GCC fails.
+
+This might happen due to a bug in the MinGW header assert.h, which
+defines the `assert' macro with a trailing semi-colon.  The following
+patch to assert.h should solve this:
+
+*** include/assert.h.orig	Sun Nov  7 02:41:36 1999
+--- include/assert.h	Mon Jan 29 11:49:10 2001
+***************
+*** 41,47 ****
+  /*
+   * If not debugging, assert does nothing.
+   */
+! #define assert(x)	((void)0);
+
+  #else /* debugging enabled */
+
+--- 41,47 ----
+  /*
+   * If not debugging, assert does nothing.
+   */
+! #define assert(x)	((void)0)
+
+  #else /* debugging enabled */
+
+
+** Linking
+
+*** Building Emacs with a system compiler fails to link because of an
+undefined symbol such as __eprintf which does not appear in Emacs.
+
+This can happen if some of the libraries linked into Emacs were built
+with GCC, but Emacs itself is being linked with a compiler other than
+GCC.  Object files compiled with GCC might need some helper functions
+from libgcc.a, the library which comes with GCC, but the system
+compiler does not instruct the linker to search libgcc.a during the
+link stage.
+
+A solution is to link with GCC, like this:
+
+  	make CC=gcc
+
+Since the .o object files already exist, this will not recompile Emacs
+with GCC, but just restart by trying again to link temacs.
+
+*** AIX 1.3 ptf 0013: Link failure.
+
+There is a real duplicate definition of the function `_slibc_free' in
+the library /lib/libc_s.a (just do nm on it to verify).  The
+workaround/fix is:
+
+    cd /lib
+    ar xv libc_s.a NLtmtime.o
+    ar dv libc_s.a NLtmtime.o
+
+*** AIX 4.1.2: Linker error messages such as
+  ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
+	of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
+
+This is a problem in libIM.a.  You can work around it by executing
+these shell commands in the src subdirectory of the directory where
+you build Emacs:
+
+    cp /usr/lib/libIM.a .
+    chmod 664 libIM.a
+    ranlib libIM.a
+
+Then change -lIM to ./libIM.a in the command to link temacs (in
+Makefile).
+
+*** Sun with acc: Link failure when using acc on a Sun.
+
+To use acc, you need additional options just before the libraries, such as
+
+   /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
+
+and you need to add -lansi just before -lc.
+
+The precise file names depend on the compiler version, so we
+cannot easily arrange to supply them.
+
+*** Linking says that the functions insque and remque are undefined.
+
+Change oldXMenu/Makefile by adding insque.o to the variable OBJS.
+
+*** `tparam' reported as a multiply-defined symbol when linking with ncurses.
+
+This problem results from an incompatible change in ncurses, in
+version 1.9.9e approximately.  This version is unable to provide a
+definition of tparm without also defining tparam.  This is also
+incompatible with Terminfo; as a result, the Emacs Terminfo support
+does not work with this version of ncurses.
+
+The fix is to install a newer version of ncurses, such as version 4.2.
+
+** Dumping
+
+*** Linux: Segfault during `make bootstrap' under certain recent versions of the Linux kernel.
+
+With certain recent Linux kernels (like the one of Redhat Fedora Core
+1), the new "Exec-shield" functionality is enabled by default, which
+creates a different memory layout that breaks the emacs dumper.
+
+You can check the Exec-shield state like this:
+
+    cat /proc/sys/kernel/exec-shield
+
+It returns 1 or 2 when Exec-shield is enabled, 0 otherwise.  Please
+read your system documentation for more details on Exec-shield and
+associated commands.
+
+When Exec-shield is enabled, building Emacs will segfault during the
+execution of this command:
+
+temacs --batch --load loadup [dump|bootstrap]
+
+To work around this problem, it is necessary to temporarily disable
+Exec-shield while building Emacs, using the `setarch' command like
+this:
+
+    setarch i386 ./configure <configure parameters>
+    setarch i386 make <make parameters>
+
+*** Fatal signal in the command  temacs -l loadup inc dump.
+
+This command is the final stage of building Emacs.  It is run by the
+Makefile in the src subdirectory, or by build.com on VMS.
+
+It has been known to get fatal errors due to insufficient swapping
+space available on the machine.
+
+On 68000s, it has also happened because of bugs in the
+subroutine `alloca'.  Verify that `alloca' works right, even
+for large blocks (many pages).
+
+*** test-distrib says that the distribution has been clobbered.
+*** or, temacs prints "Command key out of range 0-127".
+*** or, temacs runs and dumps emacs, but emacs totally fails to work.
+*** or, temacs gets errors dumping emacs.
+
+This can be because the .elc files have been garbled.  Do not be
+fooled by the fact that most of a .elc file is text: these are
+binary files and can contain all 256 byte values.
+
+In particular `shar' cannot be used for transmitting GNU Emacs.
+It typically truncates "lines".  What appear to be "lines" in
+a binary file can of course be of any length.  Even once `shar'
+itself is made to work correctly, `sh' discards null characters
+when unpacking the shell archive.
+
+I have also seen character \177 changed into \377.  I do not know
+what transfer means caused this problem.  Various network
+file transfer programs are suspected of clobbering the high bit.
+
+If you have a copy of Emacs that has been damaged in its
+nonprinting characters, you can fix them:
+
+ 1) Record the names of all the .elc files.
+ 2) Delete all the .elc files.
+ 3) Recompile alloc.c with a value of PURESIZE twice as large.
+     (See puresize.h.)  You might as well save the old alloc.o.
+ 4) Remake emacs.  It should work now.
+ 5) Running emacs, do Meta-x byte-compile-file repeatedly
+  to recreate all the .elc files that used to exist.
+  You may need to increase the value of the variable
+  max-lisp-eval-depth to succeed in running the compiler interpreted
+  on certain .el files.  400 was sufficient as of last report.
+ 6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
+  and remake temacs.
+ 7) Remake emacs.  It should work now, with valid .elc files.
+
+*** temacs prints "Pure Lisp storage exhausted".
+
+This means that the Lisp code loaded from the .elc and .el
+files during  temacs -l loadup inc dump  took up more
+space than was allocated.
+
+This could be caused by
+ 1) adding code to the preloaded Lisp files
+ 2) adding more preloaded files in loadup.el
+ 3) having a site-init.el or site-load.el which loads files.
+   Note that ANY site-init.el or site-load.el is nonstandard;
+   if you have received Emacs from some other site
+   and it contains a site-init.el or site-load.el file, consider
+   deleting that file.
+ 4) getting the wrong .el or .elc files
+   (not from the directory you expected).
+ 5) deleting some .elc files that are supposed to exist.
+   This would cause the source files (.el files) to be
+   loaded instead.  They take up more room, so you lose.
+ 6) a bug in the Emacs distribution which underestimates
+   the space required.
+
+If the need for more space is legitimate, change the definition
+of PURESIZE in puresize.h.
+
+But in some of the cases listed above, this problem is a consequence
+of something else that is wrong.  Be sure to check and fix the real
+problem.
+
+*** Linux: Emacs crashes when dumping itself on Mac PPC running Yellow Dog GNU/Linux.
+
+The crashes happen inside the function Fmake_symbol; here's a typical
+C backtrace printed by GDB:
+
+  0x190c0c0 in Fmake_symbol ()
+  (gdb) where
+  #0  0x190c0c0 in Fmake_symbol ()
+  #1  0x1942ca4 in init_obarray ()
+  #2  0x18b3500 in main ()
+  #3  0x114371c in __libc_start_main (argc=5, argv=0x7ffff5b4, envp=0x7ffff5cc,
+
+This could happen because GCC version 2.95 and later changed the base
+of the load address to 0x10000000.  Emacs needs to be told about this,
+but we currently cannot do that automatically, because that breaks
+other versions of GNU/Linux on the MacPPC.  Until we find a way to
+distinguish between the Yellow Dog and the other varieties of
+GNU/Linux systems on the PPC, you will have to manually uncomment the
+following section near the end of the file src/m/macppc.h in the Emacs
+distribution:
+
+  #if 0  /* This breaks things on PPC GNU/Linux except for Yellowdog,
+	    even with identical GCC, as, ld.  Let's take it out until we
+	    know what's really going on here.  */
+  /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to
+     0x10000000.  */
+  #if defined __linux__
+  #if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95)
+  #define DATA_SEG_BITS  0x10000000
+  #endif
+  #endif
+  #endif /* 0 */
+
+Remove the "#if 0" and "#endif" directives which surround this, save
+the file, and then reconfigure and rebuild Emacs.  The dumping process
+should now succeed.
+
+*** HPUX 10.20: Emacs crashes during dumping on the HPPA machine.
+
+This seems to be due to a GCC bug; it is fixed in GCC 2.8.1.
+
+** Installation
+
+*** Installing Emacs gets an error running `install-info'.
+
+You need to install a recent version of Texinfo; that package
+supplies the `install-info' command.
+
+** First execution
+
+*** Emacs binary is not in executable format, and cannot be run.
+
+This was reported to happen when Emacs is built in a directory mounted
+via NFS, for some combinations of NFS client and NFS server.
+Usually, the file `emacs' produced in these cases is full of
+binary null characters, and the `file' utility says:
+
+    emacs: ASCII text, with no line terminators
+
+We don't know what exactly causes this failure.  A work-around is to
+build Emacs in a directory on a local disk.
+
+*** The dumped Emacs crashes when run, trying to write pure data.
+
+Two causes have been seen for such problems.
+
+1) On a system where getpagesize is not a system call, it is defined
+as a macro.  If the definition (in both unexec.c and malloc.c) is wrong,
+it can cause problems like this.  You might be able to find the correct
+value in the man page for a.out (5).
+
+2) Some systems allocate variables declared static among the
+initialized variables.  Emacs makes all initialized variables in most
+of its files pure after dumping, but the variables declared static and
+not initialized are not supposed to be pure.  On these systems you
+may need to add "#define static" to the m- or the s- file.
+
+* Emacs 19 problems
+
+** Error messages `Wrong number of arguments: #<subr where-is-internal>, 5'.
+
+This typically results from having the powerkey library loaded.
+Powerkey was designed for Emacs 19.22.  It is obsolete now because
+Emacs 19 now has this feature built in; and powerkey also calls
+where-is-internal in an obsolete way.
+
+So the fix is to arrange not to load powerkey.
+
+* Runtime problems on legacy systems
+
+This section covers bugs reported on very old hardware or software.
+If you are using hardware and an operating system shipped after 2000,
+it is unlikely you will see any of these.
+
+** Ancient operating systems
+
+*** ISC Unix
+
+**** ISC: display-time causes kernel problems on ISC systems.
+
+Under Interactive Unix versions 3.0.1 and 4.0 (and probably other
+versions), display-time causes the loss of large numbers of STREVENT
+cells.  Eventually the kernel's supply of these cells is exhausted.
+This makes emacs and the whole system run slow, and can make other
+processes die, in particular pcnfsd.
+
+Other emacs functions that communicate with remote processes may have
+the same problem.  Display-time seems to be far the worst.
+
+The only known fix: Don't run display-time.
+
+*** SunOS
+
+**** Sun 4.0.x: M-x shell persistently reports "Process shell exited abnormally with code 1".
+
+This happened on Suns as a result of what is said to be a bug in Sunos
+version 4.0.x.  The only fix was to reboot the machine.
+
+**** SunOS4.1.1 and SunOS4.1.3: Mail is lost when sent to local aliases.
+
+Many emacs mail user agents (VM and rmail, for instance) use the
+sendmail.el library.  This library can arrange for mail to be
+delivered by passing messages to the /usr/lib/sendmail (usually)
+program .  In doing so, it passes the '-t' flag to sendmail, which
+means that the name of the recipient of the message is not on the
+command line and, therefore, that sendmail must parse the message to
+obtain the destination address.
+
+There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
+In short, when given the -t flag, the SunOS sendmail won't recognize
+non-local (i.e. NIS) aliases.  It has been reported that the Solaris
+2.x versions of sendmail do not have this bug.  For those using SunOS
+4.1, the best fix is to install sendmail V8 or IDA sendmail (which
+have other advantages over the regular sendmail as well).  At the time
+of this writing, these official versions are available:
+
+ Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
+   sendmail.8.6.9.base.tar.Z (the base system source & documentation)
+   sendmail.8.6.9.cf.tar.Z   (configuration files)
+   sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
+   sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
+
+ IDA sendmail on vixen.cso.uiuc.edu in /pub:
+   sendmail-5.67b+IDA-1.5.tar.gz
+
+**** Sunos 5.3: Subprocesses remain, hanging but not zombies.
+
+A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
+exits.  Sun patch # 101415-02 is part of the fix for this, but it only
+applies to ptys, and doesn't fix the problem with subprocesses
+communicating through pipes.
+
+**** Sunos 4: You get the error ld: Undefined symbol __lib_version.
+
+This is the result of using cc or gcc with the shared library meant
+for acc (the Sunpro compiler).  Check your LD_LIBRARY_PATH and delete
+/usr/lang/SC2.0.1 or some similar directory.
+
+**** SunOS 4.1.3: Emacs unpredictably crashes in _yp_dobind_soft.
+
+This happens if you configure Emacs specifying just `sparc-sun-sunos4'
+on a system that is version 4.1.3.  You must specify the precise
+version number (or let configure figure out the configuration, which
+it can do perfectly well for SunOS).
+
+**** Sunos 4.1.3: Emacs gets hung shortly after startup.
+
+We think this is due to a bug in Sunos.  The word is that
+one of these Sunos patches fixes the bug:
+
+100075-11  100224-06  100347-03  100482-05  100557-02  100623-03  100804-03  101080-01
+100103-12  100249-09             100496-02  100564-07  100630-02  100891-10  101134-01
+100170-09  100296-04  100377-09  100507-04  100567-04  100650-02  101070-01  101145-01
+100173-10  100305-15  100383-06  100513-04  100570-05  100689-01  101071-03  101200-02
+100178-09  100338-05  100421-03  100536-02  100584-05  100784-01  101072-01  101207-01
+
+We don't know which of these patches really matter.  If you find out
+which ones, please inform bug-gnu-emacs@gnu.org.
+
+**** SunOS 4: Emacs processes keep going after you kill the X server
+(or log out, if you logged in using X).
+
+Someone reported that recompiling with GCC 2.7.0 fixed this problem.
+
+**** SunOS: You get linker errors
+   ld: Undefined symbol
+      _get_wmShellWidgetClass
+      _get_applicationShellWidgetClass
+
+The fix to this is to install patch 100573 for OpenWindows 3.0
+or link libXmu statically.
+
+*** Apollo Domain
+
+**** Shell mode ignores interrupts on Apollo Domain.
+
+You may find that M-x shell prints the following message:
+
+   Warning: no access to tty; thus no job control in this shell...
+
+This can happen if there are not enough ptys on your system.
+Here is how to make more of them.
+
+    % cd /dev
+    % ls pty*
+    # shows how many pty's you have. I had 8, named pty0 to pty7)
+    % /etc/crpty 8
+    # creates eight new pty's
+
+*** Irix
+
+*** Irix 6.2: No visible display on mips-sgi-irix6.2 when compiling with GCC 2.8.1.
+
+This problem went away after installing the latest IRIX patches
+as of 8 Dec 1998.
+
+The same problem has been reported on Irix 6.3.
+
+*** Irix 6.3: substituting environment variables in file names
+in the minibuffer gives peculiar error messages such as
+
+   Substituting nonexistent environment variable ""
+
+This is not an Emacs bug; it is caused by something in SGI patch
+003082 August 11, 1998.
+
+*** OPENSTEP
+
+**** OPENSTEP 4.2: Compiling syntax.c with gcc 2.7.2.1 fails.
+
+The compiler was reported to crash while compiling syntax.c with the
+following message:
+
+   cc: Internal compiler error: program cc1obj got fatal signal 11
+
+To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD,
+INC_BOTH, and INC_FROM with functions.  To this end, first define 3
+functions, one each for every macro.  Here's an example:
+
+    static int update_syntax_table_forward(int from)
+    {
+        return(UPDATE_SYNTAX_TABLE_FORWARD(from));
+    }/*update_syntax_table_forward*/
+
+Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c
+with a call to the function update_syntax_table_forward.
+
+*** Solaris 2.x
+
+**** Strange results from format %d in a few cases, on a Sun.
+
+Sun compiler version SC3.0 has been found to miscompile part of
+editfns.c.  The workaround is to compile with some other compiler such
+as GCC.
+
+**** On Solaris, Emacs dumps core if lisp-complete-symbol is called.
+
+If you compile Emacs with the -fast or -xO4 option with version 3.0.2
+of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is
+called.  The problem does not happen if you compile with GCC.
+
+**** On Solaris, Emacs crashes if you use (display-time).
+
+This can happen if you configure Emacs without specifying the precise
+version of Solaris that you are using.
+
+**** Solaris 2.3 and 2.4: Unpredictable segmentation faults.
+
+A user reported that this happened in 19.29 when it was compiled with
+the Sun compiler, but not when he recompiled with GCC 2.7.0.
+
+We do not know whether something in Emacs is partly to blame for this.
+
+**** Solaris 2.4: Emacs dumps core on startup.
+
+Bill Sebok says that the cause of this is Solaris 2.4 vendor patch
+102303-05, which extends the Solaris linker to deal with the Solaris
+Common Desktop Environment's linking needs.  You can fix the problem
+by removing this patch and installing patch 102049-02 instead.
+However, that linker version won't work with CDE.
+
+Solaris 2.5 comes with a linker that has this bug.  It is reported that if
+you install all the latest patches (as of June 1996), the bug is fixed.
+We suspect the crucial patch is one of these, but we don't know
+for certain.
+
+        103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes)
+        102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes)
+	103242-04: [README] SunOS 5.5: linker patch (595363 bytes)
+
+(One user reports that the bug was fixed by those patches together
+with patches 102980-04, 103279-01, 103300-02, and 103468-01.)
+
+If you can determine which patch does fix the bug, please tell
+bug-gnu-emacs@gnu.org.
+
+Meanwhile, the GNU linker links Emacs properly on both Solaris 2.4 and
+Solaris 2.5.
+
+**** Solaris 2.4: Dired hangs and C-g does not work.  Or Emacs hangs
+forever waiting for termination of a subprocess that is a zombie.
+
+casper@fwi.uva.nl says the problem is in X11R6.  Rebuild libX11.so
+after changing the file xc/config/cf/sunLib.tmpl.  Change the lines
+
+    #if ThreadedX
+    #define SharedX11Reqs -lthread
+    #endif
+
+to:
+
+    #if OSMinorVersion < 4
+    #if ThreadedX
+    #define SharedX11Reqs -lthread
+    #endif
+    #endif
+
+Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
+(as it should be for Solaris 2.4).  The file has three definitions for
+OSMinorVersion: the first is for x86, the second for SPARC under
+Solaris, and the third for SunOS 4.  Make sure to update the
+definition for your type of machine and system.
+
+Then do `make Everything' in the top directory of X11R6, to rebuild
+the makefiles and rebuild X.  The X built this way work only on
+Solaris 2.4, not on 2.3.
+
+For multithreaded X to work it is necessary to install patch
+101925-02 to fix problems in header files [2.4].  You need
+to reinstall gcc or re-run just-fixinc after installing that
+patch.
+
+However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
+he changed
+    #define ThreadedX          YES
+to
+    #define ThreadedX          NO
+in sun.cf and did `make World' to rebuild X11R6.  Removing all
+`-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
+typing 'make install' in that directory also seemed to work.
+
+**** Solaris 2.x: GCC complains "64 bit integer types not supported".
+
+This suggests that GCC is not installed correctly.  Most likely you
+are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this
+does not work without patching.  To run GCC 2.7.2.3 on Solaris 2.6 or
+later, you must patch fixinc.svr4 and reinstall GCC from scratch as
+described in the Solaris FAQ
+<http://www.wins.uva.nl/pub/solaris/solaris2.html>.  A better fix is
+to upgrade to GCC 2.8.1 or later.
+
+**** Solaris 2.7: Building Emacs with WorkShop Compilers 5.0 98/12/15
+C 5.0 failed, apparently with non-default CFLAGS, most probably due to
+compiler bugs.  Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C
+release was reported to work without problems.  It worked OK on
+another system with Solaris 8 using apparently the same 5.0 compiler
+and the default CFLAGS.
+
+**** Solaris 2.x: Emacs dumps core when built with Motif.
+
+The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1.
+Install the current Motif runtime library patch appropriate for your host.
+(Make sure the patch is current; some older patch versions still have the bug.)
+You should install the other patches recommended by Sun for your host, too.
+You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/;
+look for files with names ending in `.PatchReport' to see which patches
+are currently recommended for your host.
+
+On Solaris 2.6, Emacs is said to work with Motif when Solaris patch
+105284-12 is installed, but fail when 105284-15 is installed.
+105284-18 might fix it again.
+
+*** Solaris 2.6 and 7: the Compose key does not work.
+
+This is a bug in Motif in Solaris.  Supposedly it has been fixed for
+the next major release of Solaris.  However, if someone with Sun
+support complains to Sun about the bug, they may release a patch.
+If you do this, mention Sun bug #4188711.
+
+One workaround is to use a locale that allows non-ASCII characters.
+For example, before invoking emacs, set the LC_ALL environment
+variable to "en_US" (American English).  The directory /usr/lib/locale
+lists the supported locales; any locale other than "C" or "POSIX"
+should do.
+
+pen@lysator.liu.se says (Feb 1998) that the Compose key does work
+if you link with the MIT X11 libraries instead of the Solaris X11
+libraries.
+
+*** Ultrix and Digital Unix
+
+**** Ultrix 4.2: `make install' fails on install-doc with `Error 141'.
+
+This happens on Ultrix 4.2 due to failure of a pipeline of tar
+commands.  We don't know why they fail, but the bug seems not to be in
+Emacs.  The workaround is to run the shell command in install-doc by
+hand.
+
+**** Digital Unix 4.0: Garbled display on non-X terminals when Emacs runs.
+
+So far it appears that running `tset' triggers this problem (when TERM
+is vt100, at least).  If you do not run `tset', then Emacs displays
+properly.  If someone can tell us precisely which effect of running
+`tset' actually causes the problem, we may be able to implement a fix
+in Emacs.
+
+**** Ultrix: `expand-file-name' fails to work on any but the machine you dumped Emacs on.
+
+On Ultrix, if you use any of the functions which look up information
+in the passwd database before dumping Emacs (say, by using
+expand-file-name in site-init.el), then those functions will not work
+in the dumped Emacs on any host but the one Emacs was dumped on.
+
+The solution?  Don't use expand-file-name in site-init.el, or in
+anything it loads.  Yuck - some solution.
+
+I'm not sure why this happens; if you can find out exactly what is
+going on, and perhaps find a fix or a workaround, please let us know.
+Perhaps the YP functions cache some information, the cache is included
+in the dumped Emacs, and is then inaccurate on any other host.
+
+*** SVr4
+
+**** SVr4: On some variants of SVR4, Emacs does not work at all with X.
+
+Try defining BROKEN_FIONREAD in your config.h file.  If this solves
+the problem, please send a bug report to tell us this is needed; be
+sure to say exactly what type of machine and system you are using.
+
+**** SVr4: After running emacs once, subsequent invocations crash.
+
+Some versions of SVR4 have a serious bug in the implementation of the
+mmap () system call in the kernel; this causes emacs to run correctly
+the first time, and then crash when run a second time.
+
+Contact your vendor and ask for the mmap bug fix; in the mean time,
+you may be able to work around the problem by adding a line to your
+operating system description file (whose name is reported by the
+configure script) that reads:
+#define SYSTEM_MALLOC
+This makes Emacs use memory less efficiently, but seems to work around
+the kernel bug.
+
+*** Linux 1.x
+
+**** Linux 1.0-1.04: Typing C-c C-c in Shell mode kills your X server.
+
+This happens with Linux kernel 1.0 thru 1.04, approximately.  The workaround is
+to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs.
+Newer Linux kernel versions don't have this problem.
+
+**** Linux 1.3: Output from subprocess (such as man or diff) is randomly
+truncated on GNU/Linux systems.
+
+This is due to a kernel bug which seems to be fixed in Linux version
+1.3.75.
+
+** MS-DOS
+
+*** When compiling with DJGPP on MS-Windows NT, "config msdos" fails.
+
+If the error message is "VDM has been already loaded", this is because
+Windows has a program called `redir.exe' that is incompatible with a
+program by the same name supplied with DJGPP, which is used by
+config.bat.  To resolve this, move the DJGPP's `bin' subdirectory to
+the front of your PATH environment variable.
+
+*** When compiling with DJGPP on MS-Windows 95, Make fails for some targets
+like make-docfile.
+
+This can happen if long file name support (the setting of environment
+variable LFN) when Emacs distribution was unpacked and during
+compilation are not the same.  See the MSDOG section of INSTALL for
+the explanation of how to avoid this problem.
+
+*** Emacs compiled with DJGPP complains at startup:
+
+  "Wrong type of argument: internal-facep, msdos-menu-active-face"
+
+This can happen if you define an environment variable `TERM'.  Emacs
+on MSDOS uses an internal terminal emulator which is disabled if the
+value of `TERM' is anything but the string "internal".  Emacs then
+works as if its terminal were a dumb glass teletype that doesn't
+support faces.  To work around this, arrange for `TERM' to be
+undefined when Emacs runs.  The best way to do that is to add an
+[emacs] section to the DJGPP.ENV file which defines an empty value for
+`TERM'; this way, only Emacs gets the empty value, while the rest of
+your system works as before.
+
+*** MS-DOS: Emacs crashes at startup.
+
+Some users report that Emacs 19.29 requires dpmi memory management,
+and crashes on startup if the system does not have it.  We don't yet
+know why this happens--perhaps these machines don't have enough real
+memory, or perhaps something is wrong in Emacs or the compiler.
+However, arranging to use dpmi support is a workaround.
+
+You can find out if you have a dpmi host by running go32 without
+arguments; it will tell you if it uses dpmi memory.  For more
+information about dpmi memory, consult the djgpp FAQ.  (djgpp
+is the GNU C compiler as packaged for MSDOS.)
+
+Compiling Emacs under MSDOS is extremely sensitive for proper memory
+configuration.  If you experience problems during compilation, consider
+removing some or all memory resident programs (notably disk caches)
+and make sure that your memory managers are properly configured.  See
+the djgpp faq for configuration hints.
+
+*** Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files
+in the directory with the special name `dev' under the root of any
+drive, e.g. `c:/dev'.
+
+This is an unfortunate side-effect of the support for Unix-style
+device names such as /dev/null in the DJGPP runtime library.  A
+work-around is to rename the problem directory to another name.
+
+*** MS-DOS+DJGPP: Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs.
+
+There are two DJGPP library bugs which cause problems:
+
+  * Running `shell-command' (or `compile', or `grep') you get
+    `Searching for program: permission denied (EACCES), c:/command.com';
+  * After you shell to DOS, Ctrl-Break kills Emacs.
+
+To work around these bugs, you can use two files in the msdos
+subdirectory: `is_exec.c' and `sigaction.c'.  Compile them and link
+them into the Emacs executable `temacs'; then they will replace the
+incorrect library functions.
+
+*** MS-DOS: Emacs compiled for MSDOS cannot find some Lisp files, or other
+run-time support files, when long filename support is enabled.
+
+Usually, this problem will manifest itself when Emacs exits
+immediately after flashing the startup screen, because it cannot find
+the Lisp files it needs to load at startup.  Redirect Emacs stdout
+and stderr to a file to see the error message printed by Emacs.
+
+Another manifestation of this problem is that Emacs is unable to load
+the support for editing program sources in languages such as C and
+Lisp.
+
+This can happen if the Emacs distribution was unzipped without LFN
+support, thus causing long filenames to be truncated to the first 6
+characters and a numeric tail that Windows 95 normally attaches to it.
+You should unzip the files again with a utility that supports long
+filenames (such as djtar from DJGPP or InfoZip's UnZip program
+compiled with DJGPP v2).  The MSDOG section of the file INSTALL
+explains this issue in more detail.
+
+Another possible reason for such failures is that Emacs compiled for
+MSDOS is used on Windows NT, where long file names are not supported
+by this version of Emacs, but the distribution was unpacked by an
+unzip program that preserved the long file names instead of truncating
+them to DOS 8+3 limits.  To be useful on NT, the MSDOS port of Emacs
+must be unzipped by a DOS utility, so that long file names are
+properly truncated.
+
+** Archaic window managers and toolkits
+
+*** OpenLook: Under OpenLook, the Emacs window disappears when you type M-q.
+
+Some versions of the Open Look window manager interpret M-q as a quit
+command for whatever window you are typing at.  If you want to use
+Emacs with that window manager, you should try to configure the window
+manager to use some other command.   You can disable the
+shortcut keys entirely by adding this line to ~/.OWdefaults:
+
+    OpenWindows.WindowMenuAccelerators: False
+
+**** twm: A position you specified in .Xdefaults is ignored, using twm.
+
+twm normally ignores "program-specified" positions.
+You can tell it to obey them with this command in your `.twmrc' file:
+
+  UsePPosition	"on"		#allow clients to request a position
+
+** Bugs related to old DEC hardware
+
+*** The Compose key on a DEC keyboard does not work as Meta key.
+
+This shell command should fix it:
+
+  xmodmap -e 'keycode 0xb1 = Meta_L'
+
+*** Keyboard input gets confused after a beep when using a DECserver
+as a concentrator.
+
+This problem seems to be a matter of configuring the DECserver to use
+7 bit characters rather than 8 bit characters.
+
+* Build problems on legacy systems
+
+** BSD/386 1.0: --with-x-toolkit option configures wrong.
+
+This problem is due to bugs in the shell in version 1.0 of BSD/386.
+The workaround is to edit the configure file to use some other shell,
+such as bash.
+
+** Digital Unix 4.0: Emacs fails to build, giving error message
+     Invalid dimension for the charset-ID 160
+
+This is due to a bug or an installation problem in GCC 2.8.0.
+Installing a more recent version of GCC fixes the problem.
+
+** Digital Unix 4.0: Failure in unexec while dumping emacs.
+
+This problem manifests itself as an error message
+
+    unexec: Bad address, writing data section to ...
+
+The user suspects that this happened because his X libraries
+were built for an older system version,
+
+    ./configure --x-includes=/usr/include --x-libraries=/usr/shlib
+
+made the problem go away.
+
+** Sunos 4.1.1: there are errors compiling sysdep.c.
+
+If you get errors such as
+
+    "sysdep.c", line 2017: undefined structure or union
+    "sysdep.c", line 2017: undefined structure or union
+    "sysdep.c", line 2019: nodename undefined
+
+This can result from defining LD_LIBRARY_PATH.  It is very tricky
+to use that environment variable with Emacs.  The Emacs configure
+script links many test programs with the system libraries; you must
+make sure that the libraries available to configure are the same
+ones available when you build Emacs.
+
+** SunOS 4.1.1: You get this error message from GNU ld:
+
+    /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
+
+The problem is in the Sun shared C library, not in GNU ld.
+
+The solution is to install Patch-ID# 100267-03 from Sun.
+
+** Sunos 4.1: Undefined symbols when linking using --with-x-toolkit.
+
+If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
+_iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
+-lXaw in the command that links temacs.
+
+This problem seems to arise only when the international language
+extensions to X11R5 are installed.
+
+** SunOS: Emacs gets error message from linker on Sun.
+
+If the error message says that a symbol such as `f68881_used' or
+`ffpa_used' or `start_float' is undefined, this probably indicates
+that you have compiled some libraries, such as the X libraries,
+with a floating point option other than the default.
+
+It's not terribly hard to make this work with small changes in
+crt0.c together with linking with Fcrt1.o, Wcrt1.o or Mcrt1.o.
+However, the easiest approach is to build Xlib with the default
+floating point option: -fsoft.
+
+** SunOS: Undefined symbols _dlopen, _dlsym and/or _dlclose.
+
+If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking
+with -lX11, compile and link against the file mit/util/misc/dlsym.c in
+the MIT X11R5 distribution.  Alternatively, link temacs using shared
+libraries with s/sunos4shr.h.  (This doesn't work if you use the X
+toolkit.)
+
+If you get the additional error that the linker could not find
+lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in
+X11R4, then use it in the link.
+
+** VMS: Compilation errors on VMS.
+
+You will get warnings when compiling on VMS because there are
+variable names longer than 32 (or whatever it is) characters.
+This is not an error.  Ignore it.
+
+VAX C does not support #if defined(foo).  Uses of this construct
+were removed, but some may have crept back in.  They must be rewritten.
+
+There is a bug in the C compiler which fails to sign extend characters
+in conditional expressions.  The bug is:
+	char c = -1, d = 1;
+	int i;
+
+	i = d ? c : d;
+The result is i == 255;  the fix is to typecast the char in the
+conditional expression as an (int).  Known occurrences of such
+constructs in Emacs have been fixed.
+
+** Vax C compiler bugs affecting Emacs.

 You may get one of these problems compiling Emacs:

@@ -3392,22 +3426,22 @@
 The `contents' field of a Lisp vector is an array of Lisp_Objects,
 so you may see the problem happening with indexed references to that.

-* 68000 C compiler problems
+** 68000 C compiler problems

 Various 68000 compilers have different problems.
 These are some that have been observed.

-** Using value of assignment expression on union type loses.
+*** Using value of assignment expression on union type loses.
 This means that  x = y = z;  or  foo (x = z);  does not work
 if x is of type Lisp_Object.

-** "cannot reclaim" error.
+*** "cannot reclaim" error.

 This means that an expression is too complicated.  You get the correct
 line number in the error message.  The code must be rewritten with
 simpler expressions.

-** XCONS, XSTRING, etc macros produce incorrect code.
+*** XCONS, XSTRING, etc macros produce incorrect code.

 If temacs fails to run at all, this may be the cause.
 Compile this test program and look at the assembler code:
@@ -3427,7 +3461,7 @@
 This problem will not happen if the m-...h file for your type
 of machine defines NO_UNION_TYPE.  That is the recommended setting now.

-* C compilers lose on returning unions
+*** C compilers lose on returning unions.

 I hear that some C compilers cannot handle returning a union type.
 Most of the functions in GNU Emacs return type Lisp_Object, which is
@@ -3437,7 +3471,7 @@
 of machine defines NO_UNION_TYPE.


-Copyright 1987,88,89,93,94,95,96,97,98,1999,2001,2002
+Copyright 1987,88,89,93,94,95,96,97,98,1999,2001,2002,2004
   Free Software Foundation, Inc.

 Copying and redistribution of this file with or without modification
--- a/etc/TODO	Mon Aug 23 08:50:01 2004 +0000
+++ b/etc/TODO	Mon Aug 23 10:12:04 2004 +0000
@@ -62,6 +62,11 @@

 * Other features we would like:

+** ange-ftp
+*** understand sftp
+*** ignore some irrelevant errors (like IPv6 and kerberos thingies).
+*** Use MLS for ange-ftp-insert-directory if a list of files is specified.
+
 ** Ability to map a key, including all modified-combinations.
    E.g map mouse-4 to wheel-up as well as M-mouse-4 -> M-wheel-up
    M-C-mouse-4 -> M-C-wheel-up, H-S-C-M-s-double-mouse-4 ->
--- a/leim/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/leim/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,13 @@
+2004-08-21  David Kastrup  <dak@gnu.org>
+
+	* quail/greek.el ("greek-babel"): Add accent/breathing/uppercase
+	combinations.
+
+2004-08-16  Kenichi Handa  <handa@m17n.org>
+
+	* quail/georgian.el ("georgian"): Call quail-define-package with
+	the show-layout arg t.
+
 2004-08-06  Andreas Schwab  <schwab@suse.de>

 	* Makefile.in (install): Remove .arch-inventory files.
@@ -99,7 +109,7 @@
 	(clean, mostlyclean): Don't delete *.elc distributed with tarball.
 	(maintainer-clean): Delete files that are not in CVS repository.

-2004-02-16  J,bi(Br,bt(Bme Marant  <jmarant@nerim.net>  (tiny change)
+2004-02-16  J,Ai(Br,At(Bme Marant  <jmarant@nerim.net>  (tiny change)

 	* Makefile.in (distclean maintainer-clean): Depend on clean.

@@ -237,7 +247,7 @@
 	("cyrillic-ukrainian"): Fix `q', `Q', `W', `w' bindings.
 	("ukrainian-computer", "belarusian", "bulgarian-bds")
 	("russian-computer"): New.
-	("bulgarian-phonetic"): Rename from bulgarian-pho.  Add ,A'(B, $,1uV(B, ,LN(B.
+	("bulgarian-phonetic"): Rename from bulgarian-pho.  Add ,A'(B, $,1uV(B, $,1(N(B.
 	("russian-typewriter"): Rename from cyrillic-jcuken.

 2002-06-20  Dave Love  <fx@gnu.org>
--- a/leim/quail/greek.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/leim/quail/greek.el	Mon Aug 23 10:12:04 2004 +0000
@@ -489,12 +489,14 @@
  ("))" ?,A;(B) ; #x00bb

  ("A" ?$,1&q(B)
+ ("A|" ?$,1q|(B)
  ("B" ?$,1&r(B)
  ("D" ?$,1&t(B)
  ("E" ?$,1&u(B)
  ("F" ?$,1'&(B)
  ("G" ?$,1&s(B)
  ("H" ?$,1&w(B)
+ ("H|" ?$,1r,(B)
  ("I" ?$,1&y(B)
  ("J" ?$,1&x(B)
  ("K" ?$,1&z(B)
@@ -509,6 +511,7 @@
  ("T" ?$,1'$(B)
  ("U" ?$,1'%(B)
  ("W" ?$,1')(B)
+ ("W|" ?$,1r\(B)
  ("X" ?$,1&~(B)
  ("Y" ?$,1'((B)
  ("Z" ?$,1&v(B)
@@ -560,6 +563,18 @@
  ("\"'i" ?$,1r3(B)
  ("\"`i" ?$,1r2(B)

+ ("<I" ?$,1pY(B)
+ (">I" ?$,1pX(B)
+ ("'I" ?$,1r;(B)
+ ("<'I" ?$,1p](B)
+ (">'I" ?$,1p\(B)
+ ("`I" ?$,1r:(B)
+ ("<`I" ?$,1p[(B)
+ (">`I" ?$,1pZ(B)
+ ("<~I"  ?$,1p_(B)
+ (">~I"  ?$,1p^(B)
+ ("\"I" ?$,1'*(B)
+
  ("<~"  ?$,1r?(B)
  (">~"  ?$,1r/(B)
  ("<'" ?$,1r>(B)
@@ -578,6 +593,15 @@
  ("<`e" ?$,1p3(B)
  (">`e" ?$,1p2(B)

+ ("<E" ?$,1p9(B)
+ (">E" ?$,1p8(B)
+ ("'E" ?$,1r)(B)
+ ("<'E" ?$,1p=(B)
+ (">'E" ?$,1p<(B)
+ ("`E" ?$,1r((B)
+ ("<`E" ?$,1p;(B)
+ (">`E" ?$,1p:(B)
+
  ("<a" ?$,1p!(B)
  (">a" ?$,1p (B)
  ("'a" ?$,1q1(B)
@@ -590,6 +614,17 @@
  ("<~a"  ?$,1p'(B)
  (">~a"  ?$,1p&(B)

+ ("<A" ?$,1p)(B)
+ (">A" ?$,1p((B)
+ ("'A" ?$,1q{(B)
+ ("<'A" ?$,1p-(B)
+ (">'A" ?$,1p,(B)
+ ("`A" ?$,1qz(B)
+ ("<`A" ?$,1p+(B)
+ (">`A" ?$,1p*(B)
+ ("<~A"  ?$,1p/(B)
+ (">~A"  ?$,1p.(B)
+
  ("<a|" ?$,1qA(B)
  (">a|" ?$,1q@(B)
  ("'a|" ?$,1qt(B)
@@ -602,9 +637,20 @@
  ("<~a|"  ?$,1qG(B)
  (">~a|"  ?$,1qF(B)

+ ("<A|" ?$,1qI(B)
+ (">A|" ?$,1qH(B)
+ ("<'A|" ?$,1qM(B)
+ (">'A|" ?$,1qL(B)
+ ("<`A|" ?$,1qK(B)
+ (">`A|" ?$,1qJ(B)
+ ("<~A|"  ?$,1qO(B)
+ (">~A|"  ?$,1qN(B)
+
  ("<r" ?$,1rE(B)
  (">r" ?$,1rD(B)

+ ("<R" ?$,1rL(B)
+
  ("<h" ?$,1pA(B)
  (">h" ?$,1p@(B)
  ("'h" ?$,1q5(B)
@@ -617,6 +663,17 @@
  ("<~h"  ?$,1pG(B)
  (">~h"  ?$,1pF(B)

+ ("<H" ?$,1pI(B)
+ (">H" ?$,1pH(B)
+ ("'H" ?$,1r+(B)
+ ("<'H" ?$,1pM(B)
+ (">'H" ?$,1pL(B)
+ ("`H" ?$,1r*(B)
+ ("<`H" ?$,1pK(B)
+ (">`H" ?$,1pJ(B)
+ ("<~H"  ?$,1pO(B)
+ (">~H"  ?$,1pN(B)
+
  ("|" ?$,1&Z(B) ; ypogegrammeni

  ("<h|" ?$,1qQ(B)
@@ -631,6 +688,15 @@
  ("<~h|"  ?$,1qW(B)
  (">~h|"  ?$,1qV(B)

+ ("<H|" ?$,1qY(B)
+ (">H|" ?$,1qX(B)
+ ("<'H|" ?$,1q](B)
+ (">'H|" ?$,1q\(B)
+ ("<`H|" ?$,1q[(B)
+ (">`H|" ?$,1qZ(B)
+ ("<~H|"  ?$,1q_(B)
+ (">~H|"  ?$,1q^(B)
+
  ("<o" ?$,1pa(B)
  (">o" ?$,1p`(B)
  ("'o" ?$,1q9(B)
@@ -640,6 +706,15 @@
  ("<`o" ?$,1pc(B)
  (">`o" ?$,1pb(B)

+ ("<O" ?$,1pi(B)
+ (">O" ?$,1ph(B)
+ ("'O" ?$,1rY(B)
+ ("<'O" ?$,1pm(B)
+ (">'O" ?$,1pl(B)
+ ("`O" ?$,1rX(B)
+ ("<`O" ?$,1pk(B)
+ (">`O" ?$,1pj(B)
+
  ("<u"   ?$,1pq(B)
  (">u"   ?$,1pp(B)
  ("'u"   ?$,1q;(B)
@@ -655,6 +730,14 @@
  ("\"'u" ?$,1rC(B)
  ("`\"u" ?$,1rB(B)

+ ("<U"   ?$,1py(B)
+ ("'U"   ?$,1rK(B)
+ ("<'U"  ?$,1p}(B)
+ ("`U"   ?$,1rJ(B)
+ ("<`U"  ?$,1p{(B)
+ ("<~U"  ?$,1p(B)
+ ("\"U"  ?$,1'+(B)
+
  ("<w"  ?$,1q!(B)
  (">w"  ?$,1q (B)
  ("'w"  ?$,1q=(B)
@@ -667,6 +750,17 @@
  ("<~w" ?$,1q'(B)
  (">~w" ?$,1q&(B)

+ ("<W"  ?$,1q)(B)
+ (">W"  ?$,1q((B)
+ ("'W"  ?$,1r[(B)
+ ("<'W" ?$,1q-(B)
+ (">'W" ?$,1q,(B)
+ ("`W"  ?$,1rZ(B)
+ ("<`W" ?$,1q+(B)
+ (">`W" ?$,1q*(B)
+ ("<~W" ?$,1q/(B)
+ (">~W" ?$,1q.(B)
+
  ("<w|"	 ?$,1qa(B)
  (">w|"	 ?$,1q`(B)
  ("'w|"	 ?$,1rT(B)
@@ -678,6 +772,16 @@
  ("~w|"	 ?$,1rW(B)
  ("<~w|" ?$,1qg(B)
  (">~w|" ?$,1qf(B)
+
+ ("<W|"	 ?$,1qi(B)
+ (">W|"	 ?$,1qh(B)
+ ("'W|"	 ?$,1rT(B)
+ ("<'W|" ?$,1qm(B)
+ (">'W|" ?$,1ql(B)
+ ("<`W|" ?$,1qk(B)
+ (">`W|" ?$,1qj(B)
+ ("<~W|" ?$,1qo(B)
+ (">~W|" ?$,1qn(B)
  )

 ;;
--- a/lisp/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,125 @@
+2004-08-22  Luc Teirlinck  <teirllm@auburn.edu>
+
+	* speedbar.el (speedbar-file-regexp): Give it a phony defvar
+	before and a real defvar after
+	`speedbar-supported-extension-expressions'.  This is to silence
+	the compiler without breaking bootstrapping.
+
+2004-08-22  Richard M. Stallman  <rms@gnu.org>
+
+	* textmodes/flyspell.el (flyspell-word): Use
+	set-process-query-on-exit-flag.
+	(flyspell-highlight-duplicate-region): Take POSS as arg.
+	(flyspell-word): Pass POSS as arg.
+
+	* progmodes/ada-xref.el: Many doc and style fixes.
+	(ada-find-any-references): Use compilation-start.
+	(ada-get-ali-file-name): Improve error msg.
+	(ada-get-ada-file-name): Likewise.
+
+	* net/ange-ftp.el (ange-ftp-gwp-start, ange-ftp-nslookup-host)
+	(ange-ftp-start-process): Use set-process-query-on-exit-flag.
+
+	* mail/mail-extr.el (mail-extr-all-top-level-domains):
+	Add forward defvar.
+
+	* whitespace.el (global-whitespace-mode): New alias
+	for whitespace-global-mode.
+
+	* speedbar.el (speedbar-file-regexp): Definition moved up.
+	(speedbar-mode, speedbar-set-mode-line-format):
+	Use with-no-warnings.
+	(speedbar-emacs-popup-kludge): Delete Emacs 19 alternative.
+
+	* simple.el (shell-command-on-region): New arg DISPLAY-ERROR-BUFFER
+	controls whether to display the error buffer.
+
+	* ps-mule.el: Delete compatibility code for old Emacses.
+	(ps-mule-find-wrappoint): Don't use chars-in-region.
+
+	* frame.el (display-mouse-p, display-selections-p):
+	Use with-no-warnings.
+
+	* font-lock.el (font-lock-set-defaults): Use with-no-warnings.
+
+2004-08-22  David Kastrup  <dak@gnu.org>
+
+	* textmodes/reftex-auc.el, progmodes/meta-mode.el: Update AUCTeX
+	information.
+
+	* speedbar.el, iswitchb.el, ido.el: Update AUCTeX information.
+
+2004-08-22  Andreas Schwab  <schwab@suse.de>
+
+	* cvs-status.el: Require pcvs during byte-compiling for
+	defun-cvs-mode.
+
+2004-08-22  Masatake YAMATO  <jet@gyve.org>
+
+	* cvs-status.el (cvs-status-checkout): New function.
+	(cvs-status-mode-map): Add a key definition for `cvs-status-checkout'.
+
+2004-08-21  David Kastrup  <dak@gnu.org>
+
+	* net/ange-ftp.el (ange-ftp-hash-entry-exists-p)
+	(ange-ftp-file-entry-p, ange-ftp-file-symlink-p): Since the code
+	has been converted to use hashtables, the relation `nil=none' is
+	no longer valid, as `nil' is not a hashtable.  This patch tries to
+	reduce the number of resulting errors.
+
+2004-08-21  John Paul Wallington  <jpw@gnu.org>
+
+	* subr.el (process-kill-without-query): Made obsolete in
+	version	21.4, not 21.5.
+
+	* log-edit.el (vc-comment-ring, vc-comment-ring-index)
+	(vc-previous-comment, vc-next-comment)
+	(vc-comment-search-reverse, vc-comment-search-forward)
+	(vc-comment-to-change-log): Likewise.
+
+	* international/latin1-disp.el (latin1-char-displayable-p): Likewise.
+
+2004-08-21  Peter Seibel  <peter@javamonkey.com>  (tiny patch)
+
+	* emacs-lisp/cl-indent.el (lisp-indent-defmethod):
+	Correct indentation of DEFMETHODS with non-standard method
+	combinations (e.g., PROGN, MIN, MAX).
+
+2004-08-20  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+	* startup.el (normal-top-level-add-subdirs-to-load-path):
+	Avoid unnecessarily checking system-type.
+	(normal-top-level): Set TERM to "dumb".  Simplify.
+
+	* avoid.el (mouse-avoidance-ignore-p): New fun.
+	Also ignore switch-frame, select-window, double, and triple clicks.
+	(mouse-avoidance-banish-hook, mouse-avoidance-exile-hook)
+	(mouse-avoidance-fancy-hook): Use it.
+
+2004-08-20  Zoran Milojevic  <zoran@sipquest.com>  (tiny change)
+
+	* avoid.el (mouse-avoidance-nudge-mouse)
+	(mouse-avoidance-banish-destination): Stay within the current window
+	to avoid problems with mouse-autoselect-window.
+
+2004-08-19  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+	* pcvs-parse.el (cvs-parse-table, cvs-parse-commit): Try to adapt to
+	the newer format of some messages in cvs-1.12.1.
+
+2004-08-19  Masatake YAMATO  <jet@gyve.org>
+
+	* emacs-lisp/elp.el (elp-results-symname-map): New keymap.
+	(elp-results-jump-to-definition-by-mouse)
+	(elp-results-jump-to-definition, elp-output-insert-symname): New funs.
+	(elp-output-result): Use elp-output-insert-symname.
+
+2004-08-18  Kenichi Handa  <handa@m17n.org>
+
+	* language/cyrillic.el: Register koi8-r in
+	ctext-non-standard-encodings-alist.
+	("Cyrillic-KOI8"): Add ctext-non-standard-encoding.
+
 2004-08-17  Luc Teirlinck  <teirllm@auburn.edu>

 	* emacs-lisp/copyright.el (copyright-update-year): Delete code
@@ -97,35 +219,35 @@
 	CC Mode update to 5.30.9:

 	* progmodes/cc-defs.el, progmodes/cc-vars.el (c-emacs-features):
-	Moved from cc-vars to cc-defs for dependency reasons.  Fixed the
+	Move from cc-vars to cc-defs for dependency reasons.  Fix the
 	POSIX char class test to check that it works in
 	`skip-chars-(forward|backward)' too.

-	* progmodes/cc-align.el (c-lineup-arglist): Fixed bug when the
+	* progmodes/cc-align.el (c-lineup-arglist): Fix bug when the
 	first argument starts with a special brace list.

-	* progmodes/cc-engine.el (c-forward-type): Fixed promotion bug
+	* progmodes/cc-engine.el (c-forward-type): Fix promotion bug
 	when `c-opt-type-concat-key' is used (i.e. in Pike).

-	* progmodes/cc-engine.el (c-looking-at-special-brace-list): Fixed
-	bug when the inner char pair doesn't have paren syntax, i.e. "(<
+	* progmodes/cc-engine.el (c-looking-at-special-brace-list):
+	Fix bug when the inner char pair doesn't have paren syntax, i.e. "(<
 	>)".

 	* progmodes/cc-align.el (c-lineup-multi-inher): Made it syntactic
 	whitespace safe.

-	* progmodes/cc-engine.el (c-guess-basic-syntax): Fixed anchor
+	* progmodes/cc-engine.el (c-guess-basic-syntax): Fix anchor
 	position for `arglist-intro', `arglist-cont-nonempty' and
 	`arglist-close' when there are two arglist open parens on the same
 	line and there's nothing in front of the first.

-	* progmodes/cc-fonts.el (c-basic-matchers-before): Fixed font
+	* progmodes/cc-fonts.el (c-basic-matchers-before): Fix font
 	locking of qualified names in Java, which previously could fontify
 	common indexing expressions in many cases.  The standard Java
 	naming conventions are used to tell them apart.

-	* progmodes/cc-align.el (c-lineup-whitesmith-in-block): Fixed
-	inconsistency wrt opening parens on the first line inside a paren
+	* progmodes/cc-align.el (c-lineup-whitesmith-in-block):
+	Fix inconsistency wrt opening parens on the first line inside a paren
 	block.

 	* progmodes/cc-defs.el (c-langs-are-parametric): Must be known at
@@ -135,29 +257,29 @@
 	`c-major-mode-is' in the event that this is used inside a
 	`c-lang-defconst'.

-	* progmodes/cc-defs.el (c-major-mode-is): Fixed expansion inside
+	* progmodes/cc-defs.el (c-major-mode-is): Fix expansion inside
 	`c-lang-defconst' so that it works better with fallback languages.

-	* progmodes/cc-defs.el (c-add-language): Fixed a typo that caused
+	* progmodes/cc-defs.el (c-add-language): Fix a typo that caused
 	it to fail to record the base mode.

-	* progmodes/cc-engine.el (c-syntactic-re-search-forward): Fixed
-	bug so that it doesn't go past the closing paren when PAREN-LEVEL
+	* progmodes/cc-engine.el (c-syntactic-re-search-forward):
+	Fix bug so that it doesn't go past the closing paren when PAREN-LEVEL
 	is used.  Reordered the syntax checks to get more efficient
 	skipping in some situations.

 	* progmodes/cc-cmds.el (c-electric-brace): Don't trip up on a line
 	continuation which might precede the newly inserted '{'.

-	* progmodes/cc-engine.el (c-syntactic-re-search-forward): Fixed
-	cases where it could loop indefinitely.
+	* progmodes/cc-engine.el (c-syntactic-re-search-forward):
+	Fix cases where it could loop indefinitely.

 	* progmodes/cc-fonts.el (c-font-lock-declarators): Handle array
 	size specs correctly.  Only fontify identifiers in front of '('
 	with as functions - don't accept any paren char.  Tightened up
 	initializer skipping to stop before function and class blocks.

-	* progmodes/cc-engine.el (c-beginning-of-decl-1): Fixed bug where
+	* progmodes/cc-engine.el (c-beginning-of-decl-1): Fix bug where
 	the point could be left directly after an open paren when finding
 	the beginning of the first decl in the block.

@@ -166,13 +288,13 @@
 	This could cause cache inconsistencies when e.g.
 	`c++-template-syntax-table' was temporarily in use.

-	* progmodes/cc-engine.el (c-on-identifier,
-	c-simple-skip-symbol-backward): Small fix for handling "-"
+	* progmodes/cc-engine.el (c-on-identifier)
+	(c-simple-skip-symbol-backward): Small fix for handling "-"
 	correctly in `skip-chars-backward'.  Affected the operator lfun
 	syntax in Pike.

-	* progmodes/cc-engine.el (c-invalidate-sws-region-after): Fixed
-	bug that could cause an error from `after-change-functions' when
+	* progmodes/cc-engine.el (c-invalidate-sws-region-after):
+	Fix bug that could cause an error from `after-change-functions' when
 	the changed region is at bob.

 2004-08-11  Alan Mackenzie  <bug-cc-mode@gnu.org>
@@ -189,7 +311,7 @@
 	string.  (2) Check that settings to `c-offsets-alist' are not
 	spuriously quoted.

-	* progmodes/cc-cmds.el: (c-electric-brace): don't delete a comment
+	* progmodes/cc-cmds.el: (c-electric-brace): Don't delete a comment
 	which precedes the newly inserted `{'.

 2004-08-10  Michael Albinus  <michael.albinus@gmx.de>
@@ -233,8 +355,7 @@

 2004-08-08  Lars Hansen  <larsh@math.ku.dk>

-	* wid-edit.el (widget-sexp-validate): Allow whitespace after
-	expression.
+	* wid-edit.el (widget-sexp-validate): Allow whitespace after expression.

 2004-08-08  Luc Teirlinck  <teirllm@auburn.edu>

@@ -266,8 +387,8 @@

 2004-08-04  Kenichi Handa  <handa@m17n.org>

-	* international/encoded-kb.el (encoded-kbd-setup-keymap): Fix
-	previous change.
+	* international/encoded-kb.el (encoded-kbd-setup-keymap):
+	Fix previous change.

 2004-08-03  Kenichi Handa  <handa@m17n.org>

@@ -301,8 +422,8 @@

 2004-08-01  David Kastrup  <dak@gnu.org>

-	* replace.el (query-replace-read-from): Use
-	`query-replace-compile-replacement'.
+	* replace.el (query-replace-read-from):
+	Use `query-replace-compile-replacement'.
 	(query-replace-compile-replacement): New function.
 	(query-replace-read-to): Use `query-replace-compile-replacement'
 	for repeating the last command.
--- a/lisp/avoid.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/avoid.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1,6 +1,6 @@
 ;;; avoid.el --- make mouse pointer stay out of the way of editing

-;;; Copyright (C) 1993, 1994, 2000 Free Software Foundation, Inc.
+;; Copyright (C) 1993, 1994, 2000, 2004 Free  Software Foundation, Inc.

 ;; Author: Boris Goldowsky <boris@gnu.org>
 ;; Keywords: mouse
@@ -52,7 +52,7 @@
 ;;
 ;; Bugs / Warnings / To-Do:
 ;;
-;; - Using this code does slow emacs down.  "banish" mode shouldn't
+;; - Using this code does slow Emacs down.  "banish" mode shouldn't
 ;;   be too bad, and on my workstation even "animate" is reasonable.
 ;;
 ;; - It ought to find out where any overlapping frames are and avoid them,
@@ -96,7 +96,7 @@

 (defcustom mouse-avoidance-nudge-dist 15
   "*Average distance that mouse will be moved when approached by cursor.
-Only applies in mouse-avoidance-mode `jump' and its derivatives.
+Only applies in Mouse-Avoidance mode `jump' and its derivatives.
 For best results make this larger than `mouse-avoidance-threshold'."
   :type 'integer
   :group 'avoid)
@@ -137,7 +137,7 @@

 (defun mouse-avoidance-point-position ()
   "Return the position of point as (FRAME X . Y).
-Analogous to mouse-position."
+Analogous to `mouse-position'."
   (let* ((w (selected-window))
 	 (edges (window-inside-edges w))
 	 (list
@@ -194,10 +194,11 @@
 		mouse-avoidance-threshold))))))

 (defun mouse-avoidance-banish-destination ()
-  "The position to which mouse-avoidance-mode `banish' moves the mouse.
+  "The position to which Mouse-Avoidance mode `banish' moves the mouse.
 You can redefine this if you want the mouse banished to a different corner."
- (cons (1- (frame-width))
-       0))
+  (let* ((pos (window-edges)))
+    (cons (- (nth 2 pos) 2)
+	  (nth 1 pos))))

 (defun mouse-avoidance-banish-mouse ()
   ;; Put the mouse pointer in the upper-right corner of the current frame.
@@ -225,22 +226,27 @@
 	  (t 0))))

 (defun mouse-avoidance-nudge-mouse ()
-  ;; Push the mouse a little way away, possibly animating the move
+  ;; Push the mouse a little way away, possibly animating the move.
   ;; For these modes, state keeps track of the total offset that we've
   ;; accumulated, and tries to keep it close to zero.
   (let* ((cur (mouse-position))
 	 (cur-frame (car cur))
 	 (cur-pos (cdr cur))
+ 	 (pos (window-edges))
+ 	 (wleft (pop pos))
+ 	 (wtop (pop pos))
+ 	 (wright (pop pos))
+ 	 (wbot (pop pos))
 	 (deltax (mouse-avoidance-delta
 		  (car cur-pos) (- (random mouse-avoidance-nudge-var)
 				   (car mouse-avoidance-state))
 		  mouse-avoidance-nudge-dist mouse-avoidance-nudge-var
-		  0 (frame-width)))
+		  wleft (1- wright)))
 	 (deltay (mouse-avoidance-delta
 		  (cdr cur-pos) (- (random mouse-avoidance-nudge-var)
 				   (cdr mouse-avoidance-state))
 		  mouse-avoidance-nudge-dist mouse-avoidance-nudge-var
-		  0 (frame-height))))
+		  wtop (1- wbot))))
     (setq mouse-avoidance-state
 	  (cons (+ (car mouse-avoidance-state) deltax)
 		(+ (cdr mouse-avoidance-state) deltay)))
@@ -277,33 +283,34 @@
   (nth (random mouse-avoidance-n-pointer-shapes)
        mouse-avoidance-pointer-shapes))

+(defun mouse-avoidance-ignore-p ()
+  (let ((mp (mouse-position)))
+    (or executing-kbd-macro	       ; don't check inside macro
+	(null (cadr mp))	       ; don't move unless in an Emacs frame
+	(not (eq (car mp) (selected-frame)))
+	;; Don't do anything if last event was a mouse event.
+	;; FIXME: this code fails in the case where the mouse was moved
+	;; since the last key-press but without generating any event.
+	(and (consp last-input-event)
+	     (symbolp (car last-input-event))
+	     (let ((modifiers (event-modifiers (car last-input-event))))
+	       (or (memq (car last-input-event)
+			 '(mouse-movement scroll-bar-movement
+			   select-window switch-frame))
+		   (memq 'click modifiers)
+		   (memq 'double modifiers)
+		   (memq 'triple modifiers)
+		   (memq 'drag modifiers)
+		   (memq 'down modifiers)))))))
+
 (defun mouse-avoidance-banish-hook ()
-  (if (and (not executing-kbd-macro)	; don't check inside macro
-	   (cadr (mouse-position))      ; don't move unless in an Emacs frame
-	   ;; Don't do anything if last event was a mouse event.
-	   (not (and (consp last-input-event)
-		     (symbolp (car last-input-event))
-		     (let ((modifiers (event-modifiers (car last-input-event))))
-		       (or (memq (car last-input-event)
-				 '(mouse-movement scroll-bar-movement))
-			   (memq 'click modifiers)
-			   (memq 'drag modifiers)
-			   (memq 'down modifiers))))))
+  (if (not (mouse-avoidance-ignore-p))
       (mouse-avoidance-banish-mouse)))

 (defun mouse-avoidance-exile-hook ()
   ;; For exile mode, the state is nil when the mouse is in its normal
   ;; position, and set to the old mouse-position when the mouse is in exile.
-  (if (and (not executing-kbd-macro)
-	   ;; Don't do anything if last event was a mouse event.
-	   (not (and (consp last-input-event)
-		     (symbolp (car last-input-event))
-		     (let ((modifiers (event-modifiers (car last-input-event))))
-		       (or (memq (car last-input-event)
-				 '(mouse-movement scroll-bar-movement))
-			   (memq 'click modifiers)
-			   (memq 'drag modifiers)
-			   (memq 'down modifiers))))))
+  (if (not (mouse-avoidance-ignore-p))
       (let ((mp (mouse-position)))
 	(cond ((and (not mouse-avoidance-state)
 		    (mouse-avoidance-too-close-p mp))
@@ -321,16 +328,7 @@

 (defun mouse-avoidance-fancy-hook ()
   ;; Used for the "fancy" modes, ie jump et al.
-  (if (and (not executing-kbd-macro)	; don't check inside macro
-	   ;; Don't do anything if last event was a mouse event.
-	   (not (and (consp last-input-event)
-		     (symbolp (car last-input-event))
-		     (let ((modifiers (event-modifiers (car last-input-event))))
-		       (or (memq (car last-input-event)
-				 '(mouse-movement scroll-bar-movement))
-			   (memq 'click modifiers)
-			   (memq 'drag modifiers)
-			   (memq 'down modifiers)))))
+  (if (and (not (mouse-avoidance-ignore-p))
 	   (mouse-avoidance-too-close-p (mouse-position)))
       (let ((old-pos (mouse-position)))
 	(mouse-avoidance-nudge-mouse)
@@ -416,5 +414,5 @@
 (if mouse-avoidance-mode
     (mouse-avoidance-mode mouse-avoidance-mode))

-;;; arch-tag: 64ad4ef8-a870-4183-8d96-3aa93b7a6800
+;; arch-tag: 64ad4ef8-a870-4183-8d96-3aa93b7a6800
 ;;; avoid.el ends here
--- a/lisp/cvs-status.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/cvs-status.el	Mon Aug 23 10:12:04 2004 +0000
@@ -31,6 +31,7 @@
 ;;; Code:

 (eval-when-compile (require 'cl))
+(eval-when-compile (require 'pcvs))
 (require 'pcvs-util)

 ;;;
@@ -48,7 +49,8 @@
     ("\M-n"	. cvs-status-next)
     ("\M-p"	. cvs-status-prev)
     ("t"	. cvs-status-cvstrees)
-    ("T"	. cvs-status-trees))
+    ("T"	. cvs-status-trees)
+    (">"        . cvs-status-checkout))
   "CVS-Status' keymap."
   :group 'cvs-status
   :inherit 'cvs-mode-map)
@@ -464,6 +466,25 @@
 	    ;;(sit-for 0)
 	    ))))))

+(defun-cvs-mode (cvs-status-checkout . NOARGS) (dir)
+  "Run cvs-checkout against the tag under the point.
+The files are stored to DIR."
+  (interactive
+   (let* ((module (cvs-get-module))
+	  (branch (cvs-prefix-get 'cvs-branch-prefix))
+	  (prompt (format "CVS Checkout Directory for `%s%s': "
+			 module
+			 (if branch (format "(branch: %s)" branch)
+			   ""))))
+     (list
+      (read-directory-name prompt
+			   nil default-directory nil))))
+  (let ((modules (cvs-string->strings (cvs-get-module)))
+	(flags (cvs-add-branch-prefix
+		(cvs-flags-query 'cvs-checkout-flags "cvs checkout flags")))
+	(cvs-cvsroot (cvs-get-cvsroot)))
+    (cvs-checkout modules dir flags)))
+
 (defun cvs-tree-tags-insert (tags prev)
   (when tags
     (let* ((tag (car tags))
--- a/lisp/emacs-lisp/cl-indent.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/emacs-lisp/cl-indent.el	Mon Aug 23 10:12:04 2004 +0000
@@ -458,7 +458,7 @@
 					    (forward-char 1)
                                             (forward-sexp 3)
                                             (backward-sexp)
-					    (looking-at ":")))
+					    (looking-at ":\\|\\sw+")))
 		       '(4 4 (&whole 4 &rest 4) &body)
 		     (get 'defun 'common-lisp-indent-function))
 		   path state indent-point sexp-column normal-indent))
--- a/lisp/emacs-lisp/elp.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/emacs-lisp/elp.el	Mon Aug 23 10:12:04 2004 +0000
@@ -513,7 +513,7 @@
 	     (numberp elp-report-limit)
 	     (< cc elp-report-limit))
 	nil
-      (insert symname)
+      (elp-output-insert-symname symname)
       (insert-char 32 (+ elp-field-len (- (length symname)) 2))
       ;; print stuff out, formatting it nicely
       (insert callcnt)
@@ -525,6 +525,32 @@
 	(insert atstr))
       (insert "\n"))))

+(defvar elp-results-symname-map
+  (let ((map (make-sparse-keymap)))
+    (define-key map [mouse-2] 'elp-results-jump-to-definition-by-mouse)
+    (define-key map "\C-m" 'elp-results-jump-to-definition)
+    map)
+  "Keymap used on the function name column." )
+
+(defun elp-results-jump-to-definition-by-mouse (event)
+  "Jump to the definition of the function under the place specified by EVENT."
+  (interactive "e")
+  (posn-set-point (event-end event))
+  (elp-results-jump-to-definition))
+
+(defun elp-results-jump-to-definition ()
+  "Jump to the definition of the function under the point."
+  (interactive)
+  (find-function (get-text-property (point) 'elp-symname)))
+
+(defun elp-output-insert-symname (symname)
+  ;; Insert SYMNAME with text properties.
+  (insert (propertize symname
+		      'elp-symname (intern symname)
+		      'keymap elp-results-symname-map
+		      'mouse-face 'highlight
+		      'help-echo (substitute-command-keys "\\{elp-results-symname-map}"))))
+
 ;;;###autoload
 (defun elp-results ()
   "Display current profiling results.
--- a/lisp/font-lock.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/font-lock.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1516,7 +1516,9 @@
     (make-local-variable 'font-lock-fontified)
     (make-local-variable 'font-lock-multiline)
     (let* ((defaults (or font-lock-defaults
-			 (cdr (assq major-mode font-lock-defaults-alist))))
+			 (cdr (assq major-mode
+				    (with-no-warnings
+				     font-lock-defaults-alist)))))
 	   (keywords
 	    (font-lock-choose-keywords (nth 0 defaults)
 				       (font-lock-value-in-major-mode font-lock-maximum-decoration)))
--- a/lisp/frame.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/frame.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1058,7 +1058,8 @@
      ((eq frame-type 'pc)
       (msdos-mouse-p))
      ((eq system-type 'windows-nt)
-      (> w32-num-mouse-buttons 0))
+      (with-no-warnings
+       (> w32-num-mouse-buttons 0)))
      ((memq frame-type '(x mac))
       t)    ;; We assume X and Mac *always* have a pointing device
      (t
@@ -1111,7 +1112,8 @@
      ((eq frame-type 'pc)
       ;; MS-DOG frames support selections when Emacs runs inside
       ;; the Windows' DOS Box.
-      (not (null dos-windows-version)))
+      (with-no-warnings
+       (not (null dos-windows-version))))
      ((memq frame-type '(x w32 mac))
       t)    ;; FIXME?
      (t
--- a/lisp/ido.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/ido.el	Mon Aug 23 10:12:04 2004 +0000
@@ -291,7 +291,7 @@
 ;; then all files matching "Summary" are moved to the end of the
 ;; list.  (I find this handy for keeping the INBOX Summary and so on
 ;; out of the way.)  It also moves files matching "output\*$" to the
-;; end of the list (these are created by AUC TeX when compiling.)
+;; end of the list (these are created by AUCTeX when compiling.)
 ;; Other functions could be made available which alter the list of
 ;; matching files (either deleting or rearranging elements.)
--- a/lisp/international/latin1-disp.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/international/latin1-disp.el	Mon Aug 23 10:12:04 2004 +0000
@@ -225,7 +225,7 @@

 ;; Backwards compatibility.
 (defalias 'latin1-char-displayable-p 'char-displayable-p)
-(make-obsolete 'latin1-char-displayable-p 'char-displayable-p "21.5")
+(make-obsolete 'latin1-char-displayable-p 'char-displayable-p "21.4")

 (defun latin1-display-setup (set &optional force)
   "Set up Latin-1 display for characters in the given SET.
--- a/lisp/iswitchb.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/iswitchb.el	Mon Aug 23 10:12:04 2004 +0000
@@ -159,7 +159,7 @@
 ;; then all buffers matching "Summary" are moved to the end of the
 ;; list.  (I find this handy for keeping the INBOX Summary and so on
 ;; out of the way.)  It also moves buffers matching "output\*$" to the
-;; end of the list (these are created by AUC TeX when compiling.)
+;; end of the list (these are created by AUCTeX when compiling.)
 ;; Other functions could be made available which alter the list of
 ;; matching buffers (either deleting or rearranging elements.)
--- a/lisp/language/cyrillic.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/language/cyrillic.el	Mon Aug 23 10:12:04 2004 +0000
@@ -186,6 +186,13 @@
 (define-coding-system-alias 'koi8 'cyrillic-koi8)
 (define-coding-system-alias 'cp878 'cyrillic-koi8)

+(let ((elt `("koi8-r" koi8-r 1
+	     ,(get 'cyrillic-koi8-r-encode-table 'translation-table)))
+      (slot (assoc "koi8-r" ctext-non-standard-encodings-alist)))
+  (if slot
+      (setcdr slot (cdr elt))
+    (push elt ctext-non-standard-encodings-alist)))
+
 ;; Allow displaying some of KOI & al with an 8859-5-encoded font.  We
 ;; won't bother about the exceptions when encoding the font, since
 ;; NBSP will fall through below and work anyhow, and we'll have
@@ -219,6 +226,7 @@
 			    'translation-table))
 		   (coding-system cyrillic-koi8)
 		   (coding-priority cyrillic-koi8 cyrillic-iso-8bit)
+		   (ctext-non-standard-encodings "koi8-r")
 		   (input-method . "russian-typewriter")
 		   (features cyril-util)
 		   (unibyte-display . cyrillic-koi8)
--- a/lisp/log-edit.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/log-edit.el	Mon Aug 23 10:12:04 2004 +0000
@@ -281,19 +281,19 @@

 ;; Compatibility with old names.
 (defvaralias 'vc-comment-ring 'log-edit-comment-ring)
-(make-obsolete-variable 'vc-comment-ring 'log-edit-comment-ring "21.5")
+(make-obsolete-variable 'vc-comment-ring 'log-edit-comment-ring "21.4")
 (defvaralias 'vc-comment-ring-index 'log-edit-comment-ring-index)
-(make-obsolete-variable 'vc-comment-ring-index 'log-edit-comment-ring-index "21.5")
+(make-obsolete-variable 'vc-comment-ring-index 'log-edit-comment-ring-index "21.4")
 (defalias 'vc-previous-comment 'log-edit-previous-comment)
-(make-obsolete 'vc-previous-comment 'log-edit-previous-comment "21.5")
+(make-obsolete 'vc-previous-comment 'log-edit-previous-comment "21.4")
 (defalias 'vc-next-comment 'log-edit-next-comment)
-(make-obsolete 'vc-next-comment 'log-edit-next-comment "21.5")
+(make-obsolete 'vc-next-comment 'log-edit-next-comment "21.4")
 (defalias 'vc-comment-search-reverse 'log-edit-comment-search-backward)
-(make-obsolete 'vc-comment-search-reverse 'log-edit-comment-search-backward "21.5")
+(make-obsolete 'vc-comment-search-reverse 'log-edit-comment-search-backward "21.4")
 (defalias 'vc-comment-search-forward 'log-edit-comment-search-forward)
-(make-obsolete 'vc-comment-search-forward 'log-edit-comment-search-forward "21.5")
+(make-obsolete 'vc-comment-search-forward 'log-edit-comment-search-forward "21.4")
 (defalias 'vc-comment-to-change-log 'log-edit-comment-to-change-log)
-(make-obsolete 'vc-comment-to-change-log 'log-edit-comment-to-change-log "21.5")
+(make-obsolete 'vc-comment-to-change-log 'log-edit-comment-to-change-log "21.4")

 ;;;
 ;;; Actual code
--- a/lisp/mail/mail-extr.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mail/mail-extr.el	Mon Aug 23 10:12:04 2004 +0000
@@ -687,6 +687,7 @@
 (defvar disable-initial-guessing-flag)	; dynamic assignment
 (defvar cbeg)				; dynamic assignment
 (defvar cend)				; dynamic assignment
+(defvar mail-extr-all-top-level-domains) ; Defined below.

 ;;;###autoload
 (defun mail-extract-address-components (address &optional all)
--- a/lisp/mh-e/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,40 @@
+2004-08-21  Bill Wohler  <wohler@newt.com>
+
+	* Released MH-E version 7.81.
+
+	* MH-E-NEWS, README: Updated for release 7.81.
+
+	* mh-e.el (Version, mh-version): Updated for release 7.81.
+
+2004-08-21  Bill Wohler  <wohler@newt.com>
+
+	* release-utils (variable_changes): Check for checked-out
+	directory before proceeding. Remove temporary files. Renamed
+	--variable-update flag to --variable-changes.
+
+2004-08-16  Mark D. Baushke  <mdb@gnu.org>
+
+	* mh-mime.el (mh-toggle-mh-decode-mime-flag: New function.
+	* mh-e.el (mh-help-messages): Add [;] help string for it.
+	(mh-folder-mode-map): Add ";" key binding for it.
+
+2004-08-15  Satyaki Das  <satyaki@theforce.stanford.edu>
+
+	* mh-acros.el (mh-defstruct): Distinguishing structures created
+	by mh-defstruct just based on the number of fields is not
+	sufficient, since both the mh-thread-message and
+	mh-thread-container structures have the same length.
+
+2004-08-15  Mark D. Baushke  <mdb@gnu.org>
+
+	* mh-customize.el (mh-identity-handlers): Use ":default" instead of
+	"default" to avoid problems with "Default:" as a user defined field.
+	* mh-identity.el (mh-identity-field-handler): Ditto.
+
+2004-08-15  Bill Wohler  <wohler@newt.com>
+
+	* mh-e.el (Version, mh-version): Added +cvs to release number.
+
 2004-08-15  Bill Wohler  <wohler@newt.com>

 	* Released MH-E version 7.4.80.
--- a/lisp/mh-e/mh-acros.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-acros.el	Mon Aug 23 10:12:04 2004 +0000
@@ -121,10 +121,10 @@
     `(progn
        (defun* ,constructor (&key ,@(mapcar* #'(lambda (x y) (list x y))
                                              field-names field-init-forms))
-         (list ,@field-names))
+         (list (quote ,struct-name) ,@field-names))
        (defun ,predicate (arg)
-         (and (consp arg) (eql (length arg) ,(length fields))))
-       ,@(loop for x from 0
+         (and (consp arg) (eq (car arg) (quote ,struct-name))))
+       ,@(loop for x from 1
                for y in field-names
                collect `(defmacro ,(intern (format "%s%s" conc-name y)) (z)
                           (list 'nth ,x z)))
--- a/lisp/mh-e/mh-customize.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-customize.el	Mon Aug 23 10:12:04 2004 +0000
@@ -527,7 +527,7 @@
   :group 'mh-identity)

 (defcustom mh-identity-handlers
-  '(("default" . mh-identity-handler-bottom)
+  '((":default" . mh-identity-handler-bottom)
     ("from" . mh-identity-handler-top)
     (":attribution-verb" . mh-identity-handler-attribution-verb)
     (":signature" . mh-identity-handler-signature)
@@ -535,9 +535,8 @@
   "Handler functions for fields in `mh-identity-list'.
 This is an alist of fields (strings) and handlers (functions). Strings are
 lowercase. Use \":signature\" for Signature and \":pgg-default-user-id\" for
-GPG Key ID. The function associated with the string \"default\" is used if no
-other functions are appropriate. For this reason, don't name a header field
-\"Default\"."
+GPG Key ID. The function associated with the string \":default\" is used if no
+other functions are appropriate."
   :type '(repeat (cons (string :tag "Field") function))
   :group 'mh-identity)
--- a/lisp/mh-e/mh-e.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-e.el	Mon Aug 23 10:12:04 2004 +0000
@@ -5,7 +5,7 @@

 ;; Author: Bill Wohler <wohler@newt.com>
 ;; Maintainer: Bill Wohler <wohler@newt.com>
-;; Version: 7.4.80
+;; Version: 7.81
 ;; Keywords: mail

 ;; This file is part of GNU Emacs.
@@ -96,7 +96,7 @@
 (defvar font-lock-auto-fontify)
 (defvar font-lock-defaults)

-(defconst mh-version "7.4.80" "Version number of MH-E.")
+(defconst mh-version "7.81" "Version number of MH-E.")

 ;;; Autoloads
 (autoload 'Info-goto-node "info")
@@ -2347,6 +2347,7 @@
   "'"           mh-toggle-tick
   ","           mh-header-display
   "."           mh-alt-show
+  ";"           mh-toggle-mh-decode-mime-flag
   ">"           mh-write-msg-to-file
   "?"           mh-help
   "E"           mh-extract-rejected-mail
@@ -2496,7 +2497,8 @@
 (defvar mh-help-messages
   '((nil "[i]nc, [.]show, [,]show all, [n]ext, [p]revious,\n"
          "[d]elete, [o]refile, e[x]ecute,\n"
-         "[s]end, [r]eply.\n"
+         "[s]end, [r]eply,\n"
+         "[;]toggle MIME decoding.\n"
          "Prefix characters:\n [F]older, [S]equence, [J]unk, MIME [K]eys,"
          "\n [T]hread, [/]limit, e[X]tract, [D]igest, [I]nc spools.")
--- a/lisp/mh-e/mh-identity.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-identity.el	Mon Aug 23 10:12:04 2004 +0000
@@ -127,7 +127,7 @@
   (or (cdr (assoc (downcase field) mh-identity-handlers))
       (and (eq (aref field 0) ?:)
            (error (format "Field %s - unknown mh-identity-handler" field)))
-      (cdr (assoc "default" mh-identity-handlers))
+      (cdr (assoc ":default" mh-identity-handlers))
       'mh-identity-handler-default))

 ;;;###mh-autoload
--- a/lisp/mh-e/mh-loaddefs.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-loaddefs.el	Mon Aug 23 10:12:04 2004 +0000
@@ -261,7 +261,7 @@
 ;;;;;;  mh-identity-insert-attribution-verb mh-identity-handler-attribution-verb
 ;;;;;;  mh-identity-handler-signature mh-identity-handler-gpg-identity
 ;;;;;;  mh-insert-identity mh-identity-list-set mh-identity-make-menu)
-;;;;;;  "mh-identity" "mh-identity.el" (16665 55172))
+;;;;;;  "mh-identity" "mh-identity.el" (16680 7172))
 ;;; Generated autoloads from mh-identity.el

 (autoload (quote mh-identity-make-menu) "mh-identity" "\
@@ -582,7 +582,7 @@
 ;;;***

 ;;;### (autoloads (mh-variants mh-variant-p mh-variant-set) "mh-init"
-;;;;;;  "mh-init.el" (16671 49652))
+;;;;;;  "mh-init.el" (16680 9361))
 ;;; Generated autoloads from mh-init.el

 (autoload (quote mh-variant-set) "mh-init" "\
@@ -633,17 +633,18 @@

 ;;;### (autoloads (mh-display-with-external-viewer mh-mime-inline-part
 ;;;;;;  mh-mime-save-part mh-push-button mh-press-button mh-mime-display
-;;;;;;  mh-decode-message-header mh-mime-save-parts mh-display-emphasis
-;;;;;;  mh-display-smileys mh-add-missing-mime-version-header mh-destroy-postponed-handles
-;;;;;;  mh-mime-cleanup mh-mml-directive-present-p mh-mml-secure-message-signencrypt
-;;;;;;  mh-mml-secure-message-encrypt mh-mml-secure-message-sign
-;;;;;;  mh-mml-unsecure-message mh-mml-attach-file mh-mml-query-cryptographic-method
-;;;;;;  mh-mml-forward-message mh-mml-to-mime mh-mhn-directive-present-p
-;;;;;;  mh-revert-mhn-edit mh-edit-mhn mh-mhn-compose-forw mh-mhn-compose-external-type
+;;;;;;  mh-decode-message-header mh-toggle-mh-decode-mime-flag mh-mime-save-parts
+;;;;;;  mh-display-emphasis mh-display-smileys mh-add-missing-mime-version-header
+;;;;;;  mh-destroy-postponed-handles mh-mime-cleanup mh-mml-directive-present-p
+;;;;;;  mh-mml-secure-message-signencrypt mh-mml-secure-message-encrypt
+;;;;;;  mh-mml-secure-message-sign mh-mml-unsecure-message mh-mml-attach-file
+;;;;;;  mh-mml-query-cryptographic-method mh-mml-forward-message
+;;;;;;  mh-mml-to-mime mh-mhn-directive-present-p mh-revert-mhn-edit
+;;;;;;  mh-edit-mhn mh-mhn-compose-forw mh-mhn-compose-external-type
 ;;;;;;  mh-mhn-compose-external-compressed-tar mh-mhn-compose-anon-ftp
 ;;;;;;  mh-mhn-compose-insertion mh-file-mime-type mh-have-file-command
 ;;;;;;  mh-compose-forward mh-compose-insertion) "mh-mime" "mh-mime.el"
-;;;;;;  (16665 55171))
+;;;;;;  (16680 7172))
 ;;; Generated autoloads from mh-mime.el

 (autoload (quote mh-compose-insertion) "mh-mime" "\
@@ -821,6 +822,9 @@
 mh_profile directives, since this function calls on mhstore or mhn to do the
 actual storing." t nil)

+(autoload (quote mh-toggle-mh-decode-mime-flag) "mh-mime" "\
+Toggle whether MH-E should decode MIME or not." t nil)
+
 (autoload (quote mh-decode-message-header) "mh-mime" "\
 Decode RFC2047 encoded message header fields." nil nil)

@@ -878,7 +882,7 @@

 ;;;### (autoloads (mh-print-msg mh-ps-print-toggle-mime mh-ps-print-toggle-color
 ;;;;;;  mh-ps-print-toggle-faces mh-ps-print-msg-show mh-ps-print-msg-file
-;;;;;;  mh-ps-print-msg) "mh-print" "mh-print.el" (16671 49652))
+;;;;;;  mh-ps-print-msg) "mh-print" "mh-print.el" (16680 9361))
 ;;; Generated autoloads from mh-print.el

 (autoload (quote mh-ps-print-msg) "mh-print" "\
--- a/lisp/mh-e/mh-mime.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/mh-e/mh-mime.el	Mon Aug 23 10:12:04 2004 +0000
@@ -850,6 +850,14 @@
                         (car ct))))))

 ;;;###mh-autoload
+(defun mh-toggle-mh-decode-mime-flag ()
+  "Toggle whether MH-E should decode MIME or not."
+  (interactive)
+  (setq mh-decode-mime-flag (not mh-decode-mime-flag))
+  (mh-show nil t)
+  (message (format "(setq mh-decode-mime-flag %s)" mh-decode-mime-flag)))
+
+;;;###mh-autoload
 (defun mh-decode-message-header ()
   "Decode RFC2047 encoded message header fields."
   (when mh-decode-mime-flag
--- a/lisp/net/ange-ftp.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/net/ange-ftp.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1014,7 +1014,7 @@

 (defun ange-ftp-hash-entry-exists-p (key tbl)
   "Return whether there is an association for KEY in TABLE."
-  (not (eq (gethash key tbl 'unknown) 'unknown)))
+  (and tbl (not (eq (gethash key tbl 'unknown) 'unknown))))

 (defun ange-ftp-hash-table-keys (tbl)
   "Return a sorted list of all the active keys in TABLE, as strings."
@@ -1771,7 +1771,7 @@
 				ange-ftp-gateway-program
 				ange-ftp-gateway-host)))
 	 (ftp (mapconcat 'identity args " ")))
-    (process-kill-without-query proc)
+    (set-process-query-on-exit-flag proc nil)
     (set-process-sentinel proc 'ange-ftp-gwp-sentinel)
     (set-process-filter proc 'ange-ftp-gwp-filter)
     (save-excursion
@@ -1880,7 +1880,7 @@
 		    (start-process " *nslookup*" " *nslookup*"
 				   ange-ftp-nslookup-program host)))
 	    (res host))
-	(process-kill-without-query proc)
+	(set-process-query-on-exit-flag proc nil)
 	(save-excursion
 	  (set-buffer (process-buffer proc))
 	  (while (memq (process-status proc) '(run open))
@@ -1938,7 +1938,7 @@
       (set-buffer (process-buffer proc))
       (goto-char (point-max))
       (set-marker (process-mark proc) (point)))
-    (process-kill-without-query proc)
+    (set-process-query-on-exit-flag proc nil)
     (set-process-sentinel proc 'ange-ftp-process-sentinel)
     (set-process-filter proc 'ange-ftp-process-filter)
     ;; On Windows, the standard ftp client buffers its output (because
@@ -2919,11 +2919,8 @@
 	       ;; error message.
 	       (gethash "." ent))
 	  ;; Child lookup failed, so try the parent.
-	  (let ((table (ange-ftp-get-files dir 'no-error)))
-	    ;; If the dir doesn't exist, don't use it as a hash table.
-	    (and table
-		 (ange-ftp-hash-entry-exists-p file
-					       table)))))))
+	  (ange-ftp-hash-entry-exists-p
+	   file (ange-ftp-get-files dir 'no-error))))))

 (defun ange-ftp-get-file-entry (name)
   "Given NAME, return the given file entry.
@@ -3374,11 +3371,11 @@
   (setq file (ange-ftp-expand-file-name file))
   (if (ange-ftp-ftp-name file)
       (condition-case nil
-	  (let ((file-ent
-		 (gethash
-		  (ange-ftp-get-file-part file)
-		  (ange-ftp-get-files (file-name-directory file)))))
-	    (and (stringp file-ent) file-ent))
+	  (let ((ent (ange-ftp-get-files (file-name-directory file))))
+	    (and ent
+		 (stringp (setq ent
+				(gethash (ange-ftp-get-file-part file) ent)))
+		 ent))
 	;; If we can't read the parent directory, just assume
 	;; this file is not a symlink.
 	;; This makes it possible to access a directory that
--- a/lisp/pcvs-parse.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/pcvs-parse.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1,7 +1,7 @@
 ;;; pcvs-parse.el --- the CVS output parser

-;; Copyright (C) 1991,92,93,94,95,96,97,98,99,2000,02,2003
-;; 		 Free Software Foundation, Inc.
+;; Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+;;   2000, 2002, 2003, 2004  Free Software Foundation, Inc.

 ;; Author: Stefan Monnier <monnier@cs.yale.edu>
 ;; Keywords: pcl-cvs
@@ -370,7 +370,7 @@
        ;; File you removed still exists.  Ignore (will be noted as removed).
        (cvs-match ".* should be removed and is still there$")
        ;; just a note
-       (cvs-match "use '.+ commit' to \\sw+ th\\sw+ files? permanently$")
+       (cvs-match "use ['`].+ commit' to \\sw+ th\\sw+ files? permanently$")
        ;; [add,status] followed by a more complete status description anyway
        (and (cvs-match "nothing known about \\(.*\\)$" (path 1))
 	    (cvs-parsed-fileinfo 'DEAD path 'trust))
@@ -492,12 +492,14 @@
 			  :head-rev head-rev))))

 (defun cvs-parse-commit ()
-  (let (path base-rev subtype)
+  (let (path file base-rev subtype)
     (cvs-or

      (and
-      (cvs-match "\\(Checking in\\|Removing\\) \\(.*\\);$" (path 2))
-      (cvs-match ".*,v  <--  .*$")
+      (cvs-or
+       (cvs-match "\\(Checking in\\|Removing\\) \\(.*\\);$" (path 2))
+       t)
+      (cvs-match ".*,v  <--  \\(.*\\)$" (file 1))
       (cvs-or
        ;; deletion
        (cvs-match "new revision: delete; previous revision: \\([0-9.]*\\)$"
@@ -508,7 +510,7 @@
        ;; update
        (cvs-match "new revision: \\([0-9.]*\\); previous revision: .*$"
 		  (subtype 'COMMITTED) (base-rev 1)))
-      (cvs-match "done$")
+      (cvs-or (cvs-match "done$") t)
       (progn
 	;; Try to remove the temp files used by VC.
 	(vc-delete-automatic-version-backups (expand-file-name path))
@@ -516,7 +518,8 @@
 	;; because `cvs commit' might begin by a series of Examining messages
 	;; so the processing of the actual checkin messages might begin with
 	;; a `current-dir' set to something different from ""
-	(cvs-parsed-fileinfo (cons 'UP-TO-DATE subtype) path 'trust
+	(cvs-parsed-fileinfo (cons 'UP-TO-DATE subtype)
+			     (or path file) (if path 'trust)
 			     :base-rev base-rev)))

      ;; useless message added before the actual addition: ignored
@@ -525,5 +528,5 @@

 (provide 'pcvs-parse)

-;;; arch-tag: 35418375-1a23-40a0-957d-96b0262f91d6
+;; arch-tag: 35418375-1a23-40a0-957d-96b0262f91d6
 ;;; pcvs-parse.el ends here
--- a/lisp/progmodes/ada-xref.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/progmodes/ada-xref.el	Mon Aug 23 10:12:04 2004 +0000
@@ -33,7 +33,7 @@
 ;;; for lookup and completion in Ada mode.
 ;;;
 ;;; If a file *.`adp' exists in the ada-file directory, then it is
-;;; read for configuration informations. It is read only the first
+;;; read for configuration informations.  It is read only the first
 ;;; time a cross-reference is asked for, and is not read later.

 ;;; You need Emacs >= 20.2 to run this package
@@ -55,26 +55,25 @@

 (defcustom ada-xref-create-ali nil
   "*If non-nil, run gcc whenever the cross-references are not up-to-date.
-If nil, the cross-reference mode will never run gcc."
+If nil, the cross-reference mode never runs gcc."
   :type 'boolean :group 'ada)

 (defcustom ada-xref-confirm-compile nil
-  "*If non-nil, always ask for user confirmation before compiling or running
-the application."
+  "*If non-nil, ask for confirmation before compiling or running the application."
   :type 'boolean :group 'ada)

 (defcustom ada-krunch-args "0"
-  "*Maximum number of characters for filenames created by gnatkr.
-Set to 0, if you don't use crunched filenames. This should be a string."
+  "*Maximum number of characters for filenames created by `gnatkr'.
+Set to 0, if you don't use crunched filenames.  This should be a string."
   :type 'string :group 'ada)

 (defcustom ada-gnatls-args '("-v")
-  "*Arguments to pass to gnatfind when the location of the runtime is searched.
-Typical use is to pass --RTS=soft-floats on some systems that support it.
+  "*Arguments to pass to `gnatfind' to find location of the runtime.
+Typical use is to pass `--RTS=soft-floats' on some systems that support it.

-You can also add -I- if you do not want the current directory to be included.
+You can also add `-I-' if you do not want the current directory to be included.
 Otherwise, going from specs to bodies and back will first look for files in the
-current directory. This only has an impact if you are not using project files,
+current directory.  This only has an impact if you are not using project files,
 but only ADA_INCLUDE_PATH."
   :type '(repeat string) :group 'ada)

@@ -91,14 +90,14 @@
   :type 'string :group 'ada)

 (defcustom ada-prj-default-gnatmake-opt "-g"
-  "Default options for gnatmake."
+  "Default options for `gnatmake'."
   :type 'string :group 'ada)

 (defcustom ada-prj-gnatfind-switches "-rf"
-  "Default switches to use for gnatfind.
-You should modify this variable, for instance to add -a, if you are working
+  "Default switches to use for `gnatfind'.
+You should modify this variable, for instance to add `-a', if you are working
 in an environment where most ALI files are write-protected.
-The command gnatfind is used every time you choose the menu
+The command `gnatfind' is used every time you choose the menu
 \"Show all references\"."
   :type 'string :group 'ada)

@@ -106,12 +105,12 @@
   (concat "${cross_prefix}gnatmake -u -c ${gnatmake_opt} ${full_current} -cargs"
 	  " ${comp_opt}")
   "*Default command to be used to compile a single file.
-Emacs will add the filename at the end of this command. This is the same
+Emacs will add the filename at the end of this command.  This is the same
 syntax as in the project file."
   :type 'string :group 'ada)

 (defcustom ada-prj-default-debugger "${cross_prefix}gdb"
-  "*Default name of the debugger. We recommend either `gdb',
+  "*Default name of the debugger.  We recommend either `gdb',
 `gdb --emacs_gdbtk' or `ddd --tty -fullname'."
   :type 'string :group 'ada)

@@ -129,7 +128,7 @@
   :type '(file :must-match t) :group 'ada)

 (defcustom ada-gnatstub-opts "-q -I${src_dir}"
-  "*List of the options to pass to gnatsub to generate the body of a package.
+  "*List of the options to pass to `gnatsub' to generate the body of a package.
 This has the same syntax as in the project file (with variable substitution)."
   :type 'string :group 'ada)

@@ -139,7 +138,7 @@
   :type 'boolean :group 'ada)

 (defconst is-windows (memq system-type (quote (windows-nt)))
-  "True if we are running on windows NT or windows 95.")
+  "True if we are running on Windows NT or Windows 95.")

 (defcustom ada-tight-gvd-integration nil
   "*If non-nil, a new Emacs frame will be swallowed in GVD when debugging.
@@ -149,7 +148,7 @@
 (defcustom ada-xref-search-with-egrep t
   "*If non-nil, use egrep to find the possible declarations for an entity.
 This alternate method is used when the exact location was not found in the
-information provided by GNAT. However, it might be expensive if you have a lot
+information provided by GNAT.  However, it might be expensive if you have a lot
 of sources, since it will search in all the files in your project."
   :type 'boolean :group 'ada)

@@ -161,8 +160,8 @@

 If the function can load the file with the given filename, it should create a
 buffer that contains a conversion of the file to the standard format of the
-project files, and return that buffer. (the usual \"src_dir=\" or \"obj_dir=\"
-lines).  It should return nil if it doesn't know how to convert that project
+project files, and return that buffer.  (The usual \"src_dir=\" or \"obj_dir=\"
+lines.)  It should return nil if it doesn't know how to convert that project
 file.")


@@ -192,14 +191,13 @@
   (if (string-match "cmdproxy.exe" shell-file-name)
       "cd /d"
     "cd")
-  "Command to use to change to a specific directory. On windows systems
-using cmdproxy.exe as the shell, we need to use /d or the drive is never
-changed.")
+  "Command to use to change to a specific directory.
+On Windows systems using `cmdproxy.exe' as the shell,
+we need to use `/d' or the drive is never changed.")

 (defvar ada-command-separator (if is-windows " && " "\n")
-  "Separator to use when sending multiple commands to `compile' or
-`start-process'.
-cmdproxy.exe doesn't recognize multiple-line commands, so we have to use
+  "Separator to use between multiple commands to `compile' or `start-process'.
+`cmdproxy.exe' doesn't recognize multiple-line commands, so we have to use
 \"&&\" for now.")

 (defconst ada-xref-pos-ring-max 16
@@ -247,12 +245,12 @@
 ;; -----------------------------------------------------------------------

 (defun ada-quote-cmd (cmd)
-  "Duplicates all \\ characters in CMD so that it can be passed to `compile'"
+  "Duplicate all \\ characters in CMD so that it can be passed to `compile'."
   (mapconcat 'identity (split-string cmd "\\\\") "\\\\"))

 (defun ada-initialize-runtime-library (cross-prefix)
-  "Initializes the variables for the runtime library location.
-CROSS-PREFIX is the prefix to use for the gnatls command"
+  "Initialize the variables for the runtime library location.
+CROSS-PREFIX is the prefix to use for the gnatls command."
   (save-excursion
     (setq ada-xref-runtime-library-specs-path '()
 	  ada-xref-runtime-library-ali-path   '())
@@ -591,7 +589,7 @@
 (defun ada-set-default-project-file (name &optional keep-existing)
   "Set the file whose name is NAME as the default project file.
 If KEEP-EXISTING is true and a project file has already been loaded, nothing
-is done. This is meant to be used from ada-mode-hook, for instance to force
+is done.  This is meant to be used from `ada-mode-hook', for instance, to force
 a project file unless the user has already loaded one."
   (interactive "fProject file:")
   (if (or (not keep-existing)
@@ -608,7 +606,7 @@
 If NO-USER-QUESTION is non-nil, use a default file if not project file was
 found, and do not ask the user.
 If the buffer is not an Ada buffer, associate it with the default project
-file. If none is set, return nil."
+file.  If none is set, return nil."

   (let (selected)

@@ -711,7 +709,7 @@
 	(ada-xref-set-default-prj-values 'project (current-buffer))

 	;;  Do not use find-file below, since we don't want to show this
-	;;  buffer. If the file is open through speedbar, we can't use
+	;;  buffer.  If the file is open through speedbar, we can't use
 	;;  find-file anyway, since the speedbar frame is special and does not
 	;;  allow the selection of a file in it.

@@ -786,7 +784,7 @@
 	  ;;  Else the file wasn't readable (probably the default project).
 	  ;;  We initialize it with the current environment variables.
           ;;  We need to add the startup directory in front so that
-          ;;  files locally redefined are properly found. We cannot
+          ;;  files locally redefined are properly found.  We cannot
           ;;  add ".", which varies too much depending on what the
           ;;  current buffer is.
 	  (set 'project
@@ -836,7 +834,7 @@

     ;;  No prj file ? => Setup default values
     ;;  Note that nil means that all compilation modes will first look in the
-    ;;  current directory, and only then in the current file's directory. This
+    ;;  current directory, and only then in the current file's directory.  This
     ;;  current file is assumed at this point to be in the common source
     ;;  directory.
     (setq compilation-search-path (list nil default-directory))
@@ -846,10 +844,9 @@
 (defun ada-find-references (&optional pos arg local-only)
   "Find all references to the entity under POS.
 Calls gnatfind to find the references.
-if ARG is t, the contents of the old *gnatfind* buffer is preserved.
-if LOCAL-ONLY is t, only the declarations in the current file are returned."
-  (interactive "d
-P")
+If ARG is t, the contents of the old *gnatfind* buffer is preserved.
+If LOCAL-ONLY is t, only the declarations in the current file are returned."
+  (interactive "d\nP")
   (ada-require-project-file)

   (let* ((identlist (ada-read-identifier pos))
@@ -872,24 +869,23 @@

 (defun ada-find-local-references (&optional pos arg)
   "Find all references to the entity under POS.
-Calls gnatfind to find the references.
-if ARG is t, the contents of the old *gnatfind* buffer is preserved."
-  (interactive "d
-P")
+Calls `gnatfind' to find the references.
+If ARG is t, the contents of the old *gnatfind* buffer is preserved."
+  (interactive "d\nP")
   (ada-find-references pos arg t))

 (defun ada-find-any-references
   (entity &optional file line column local-only append)
   "Search for references to any entity whose name is ENTITY.
 ENTITY was first found the location given by FILE, LINE and COLUMN.
-If LOCAL-ONLY is t, then only the references in file will be listed, which
+If LOCAL-ONLY is t, then list only the references in FILE, which
 is much faster.
-If APPEND is t, then the output of the command will be append to the existing
-buffer *gnatfind* if it exists."
+If APPEND is t, then append the output of the command to the existing
+buffer `*gnatfind*', if there is one."
   (interactive "sEntity name: ")
   (ada-require-project-file)

-  ;;  Prepare the gnatfind command. Note that we must protect the quotes
+  ;;  Prepare the gnatfind command.  Note that we must protect the quotes
   ;;  around operators, so that they are correctly handled and can be
   ;;  processed (gnatfind \"+\":...).
   (let* ((quote-entity
@@ -921,7 +917,8 @@
 	  (set-buffer "*gnatfind*")
 	  (setq old-contents (buffer-string))))

-    (compile-internal command "No more references" "gnatfind")
+    (let ((compilation-error "reference"))
+      (compilation-start command))

     ;;  Hide the "Compilation" menu
     (save-excursion
@@ -941,8 +938,8 @@
 ;; ----- Identifier Completion --------------------------------------------
 (defun ada-complete-identifier (pos)
   "Tries to complete the identifier around POS.
-The feature is only available if the files where compiled not using the -gnatx
-option."
+The feature is only available if the files where compiled without
+the option `-gnatx'."
   (interactive "d")
   (ada-require-project-file)

@@ -1026,12 +1023,12 @@
 	 ;; entity, whose references are not given by GNAT
 	 (if (and (file-exists-p ali-file)
 		  (file-newer-than-file-p ali-file (ada-file-of identlist)))
-	     (message "No cross-reference found. It might be a predefined entity.")
+	     (message "No cross-reference found--may be a predefined entity.")

 	   ;; Else, look in every ALI file, except if the user doesn't want that
 	   (if ada-xref-search-with-egrep
 	       (ada-find-in-src-path identlist other-frame)
-	     (message "Cross-referencing information is not up-to-date. Please recompile.")
+	     (message "Cross-referencing information is not up-to-date; please recompile.")
 	     )))))))

 (defun ada-goto-declaration-other-frame (pos)
@@ -1052,12 +1049,13 @@

 (defun ada-get-absolute-dir-list (dir-list root-dir)
   "Returns the list of absolute directories found in dir-list.
-If a directory is a relative directory, the value of ROOT-DIR is added in
-front."
+If a directory is a relative directory, add the value of ROOT-DIR in front."
   (mapcar (lambda (x) (expand-file-name x root-dir)) dir-list))

 (defun ada-set-environment ()
-  "Return the new value for process-environment.
+  "Prepare an environment for Ada compilation.
+This returns a new value to use for `process-environment',
+but does not actually put it into use.
 It modifies the source path and object path with the values found in the
 project file."
   (let ((include   (getenv "ADA_INCLUDE_PATH"))
@@ -1082,7 +1080,7 @@
       process-environment))))

 (defun ada-compile-application (&optional arg)
-  "Compiles the application, using the command found in the project file.
+  "Compile the application, using the command found in the project file.
 If ARG is not nil, ask for user confirmation."
   (interactive "P")
   (ada-require-project-file)
@@ -1104,7 +1102,7 @@
 	(setq cmd (read-from-minibuffer "enter command to compile: " cmd)))

     ;;  Insert newlines so as to separate the name of the commands to run
-    ;;  and the output of the commands. this doesn't work with cmdproxy.exe,
+    ;;  and the output of the commands.  This doesn't work with cmdproxy.exe,
     ;;  which gets confused by newline characters.
     (if (not (string-match ".exe" shell-file-name))
 	(setq cmd (concat cmd "\n\n")))
@@ -1137,7 +1135,7 @@
 	(setq cmd (read-from-minibuffer "enter command to compile: " cmd)))

     ;;  Insert newlines so as to separate the name of the commands to run
-    ;;  and the output of the commands. this doesn't work with cmdproxy.exe,
+    ;;  and the output of the commands.  This doesn't work with cmdproxy.exe,
     ;;  which gets confused by newline characters.
     (if (not (string-match ".exe" shell-file-name))
 	(setq cmd (concat cmd "\n\n")))
@@ -1152,7 +1150,7 @@

 (defun ada-run-application (&optional arg)
   "Run the application.
-if ARG is not-nil, asks for user confirmation."
+if ARG is not-nil, ask for user confirmation."
   (interactive)
   (ada-require-project-file)

@@ -1227,7 +1225,7 @@
 	;;  We make sure that gvd swallows the new frame, not the one the
 	;;  user has been using until now
 	;;  The frame is made invisible initially, so that GtkPlug gets a
-	;;  chance to fully manage it. Then it works fine with Enlightenment
+	;;  chance to fully manage it.  Then it works fine with Enlightenment
 	;;  as well
 	(let ((frame (make-frame '((visibility . nil)))))
 	  (set 'cmd (concat
@@ -1297,7 +1295,7 @@
       (end-of-buffer)

       ;;  Display both the source window and the debugger window (the former
-      ;;  above the latter). No need to show the debugger window unless it
+      ;;  above the latter).  No need to show the debugger window unless it
       ;;  is going to have some relevant information.
       (if (or (not (string-match "gvd" (comint-arguments cmd 0 0)))
 	      (string-match "--tty" cmd))
@@ -1328,8 +1326,8 @@
   "Update the cross-references for FILE.
 This in fact recompiles FILE to create ALI-FILE-NAME.
 This function returns the name of the file that was recompiled to generate
-the cross-reference information. Note that the ali file can then be deduced by
-replacing the file extension with .ali"
+the cross-reference information.  Note that the ali file can then be deduced by
+replacing the file extension with `.ali'."
   ;; kill old buffer
   (if (and ali-file-name
            (get-file-buffer ali-file-name))
@@ -1338,7 +1336,7 @@
   (let* ((name      (ada-convert-file-name file))
 	 (body-name (or (ada-get-body-name name) name)))

-    ;; Always recompile the body when we can. We thus temporarily switch to a
+    ;; Always recompile the body when we can.  We thus temporarily switch to a
     ;; buffer than contains the body of the unit
     (save-excursion
       (let ((body-visible (find-buffer-visiting body-name))
@@ -1347,7 +1345,7 @@
 	    (set-buffer body-visible)
 	  (find-file body-name))

-	;; Execute the compilation. Note that we must wait for the end of the
+	;; Execute the compilation.  Note that we must wait for the end of the
 	;; process, or the ALI file would still not be available.
 	;; Unfortunately, the underlying `compile' command that we use is
 	;; asynchronous.
@@ -1377,13 +1375,13 @@
     found))

 (defun ada-find-ali-file-in-dir (file)
-  "Find an .ali file in obj_dir. The current buffer must be the Ada file.
+  "Find an .ali file in obj_dir.  The current buffer must be the Ada file.
 Adds build_dir in front of the search path to conform to gnatmake's behavior,
 and the standard runtime location at the end."
   (ada-find-file-in-dir file (ada-xref-get-obj-dir-field)))

 (defun ada-find-src-file-in-dir (file)
-  "Find a source file in src_dir. The current buffer must be the Ada file.
+  "Find a source file in src_dir.  The current buffer must be the Ada file.
 Adds src_dir in front of the search path to conform to gnatmake's behavior,
 and the standard runtime location at the end."
   (ada-find-file-in-dir file (ada-xref-get-src-dir-field)))
@@ -1400,7 +1398,7 @@
   ;;      and look for this file
   ;;   2- If this file is found:
   ;;      grep the "^U" lines, and make sure we are not reading the
-  ;;      .ali file for a spec file. If we are, go to step 3.
+  ;;      .ali file for a spec file.  If we are, go to step 3.
   ;;   3- If the file is not found or step 2 failed:
   ;;      find the name of the "other file", ie the body, and look
   ;;      for its associated .ali file by subtituing the extension
@@ -1408,9 +1406,9 @@
   ;; We must also handle the case of separate packages and subprograms:
   ;;   4- If no ali file was found, we try to modify the file name by removing
   ;;      everything after the last '-' or '.' character, so as to get the
-  ;;      ali file for the parent unit. If we found an ali file, we check that
+  ;;      ali file for the parent unit.  If we found an ali file, we check that
   ;;      it indeed contains the definition for the separate entity by checking
-  ;;      the 'D' lines. This is done repeatedly, in case the direct parent is
+  ;;      the 'D' lines.  This is done repeatedly, in case the direct parent is
   ;;      also a separate.

   (save-excursion
@@ -1423,7 +1421,7 @@

       ;; If we have a non-standard file name, and this is a spec, we first
       ;; look for the .ali file of the body, since this is the one that
-      ;; contains the most complete information. If not found, we will do what
+      ;; contains the most complete information.  If not found, we will do what
       ;; we can with the .ali file for the spec...

       (if (not (string= (file-name-extension file) "ads"))
@@ -1476,8 +1474,8 @@

       ;; If still not found, try to recompile the file
       (if (not ali-file-name)
-	  ;; recompile only if the user asked for this. and search the ali
-	  ;; filename again. We avoid a possible infinite recursion by
+	  ;; Recompile only if the user asked for this, and search the ali
+	  ;; filename again.  We avoid a possible infinite recursion by
 	  ;; temporarily disabling the automatic compilation.

 	  (if ada-xref-create-ali
@@ -1485,7 +1483,7 @@
 		    (concat (file-name-sans-extension (ada-xref-current file))
 			    ".ali"))

-	    (error "Ali file not found. Recompile your file"))
+	    (error "`.ali' file not found; recompile your source file"))


 	;; same if the .ali file is too old and we must recompile it
@@ -1499,7 +1497,7 @@

 (defun ada-get-ada-file-name (file original-file)
   "Create the complete file name (+directory) for FILE.
-The original file (where the user was) is ORIGINAL-FILE. Search in project
+The original file (where the user was) is ORIGINAL-FILE.  Search in project
 file for possible paths."

   (save-excursion
@@ -1519,7 +1517,7 @@
           (expand-file-name filename)
         (error (concat
                 (file-name-nondirectory file)
-                " not found in src_dir. Please check your project file")))
+                " not found in src_dir; please check your project file")))

       )))

@@ -1671,13 +1669,13 @@
 	      (set 'declaration-found nil))))

       ;; Still no success ! The ali file must be too old, and we need to
-      ;; use a basic algorithm based on guesses. Note that this only happens
+      ;; use a basic algorithm based on guesses.  Note that this only happens
       ;; if the user does not want us to automatically recompile files
       ;; automatically
       (unless declaration-found
 	(if (ada-xref-find-in-modified-ali identlist)
 	    (set 'declaration-found t)
-	  ;; no more idea to find the declaration. Give up
+	  ;; No more idea to find the declaration.  Give up
 	  (progn
 	    (kill-buffer ali-buffer)
 	    (error (concat "No declaration of " (ada-name-of identlist)
@@ -1911,7 +1909,7 @@

     (save-excursion

-      ;;  Do the grep in all the directories. We do multiple shell
+      ;;  Do the grep in all the directories.  We do multiple shell
       ;;  commands instead of one in case there is no .ali file in one
       ;;  of the directory and the shell stops because of that.

@@ -2011,7 +2009,7 @@
   (file line column identlist &optional other-frame)
   "Select and display FILE, at LINE and COLUMN.
 If we do not end on the same identifier as IDENTLIST, find the closest
-match. Kills the .ali buffer at the end.
+match.  Kills the .ali buffer at the end.
 If OTHER-FRAME is non-nil, creates a new frame to show the file."

   (let (declaration-buffer)
@@ -2178,7 +2176,7 @@
   (unless (buffer-file-name (car (buffer-list)))
     (set-buffer (cadr (buffer-list))))

-  ;;  Make sure we have a project file (for parameters to gnatstub). Note that
+  ;;  Make sure we have a project file (for parameters to gnatstub).  Note that
   ;;  this might have already been done if we have been called from the hook,
   ;;  but this is not an expensive call)
   (ada-require-project-file)
@@ -2240,9 +2238,9 @@

 ;;  Use gvd or ddd as the default debugger if it was found
 ;;  On windows, do not use the --tty switch for GVD, since this is
-;;  not supported. Actually, we do not use this on Unix either, since otherwise
-;;  there is no console window left in GVD, and people have to use the
-;;  Emacs one.
+;;  not supported.  Actually, we do not use this on Unix either,
+;;  since otherwise there is no console window left in GVD,
+;;  and people have to use the Emacs one.
 ;;  This must be done before initializing the Ada menu.
 (if (ada-find-file-in-dir "gvd" exec-path)
     (set 'ada-prj-default-debugger "gvd ")
--- a/lisp/progmodes/meta-mode.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/progmodes/meta-mode.el	Mon Aug 23 10:12:04 2004 +0000
@@ -32,7 +32,7 @@
 ;; a major mode including an approriate syntax table, keymap, and a
 ;; mode-specific pull-down menu.  It also provides a sophisticated set
 ;; of font-lock patterns, a fancy indentation function adapted from
-;; AUC-TeX's latex.el, and some basic mode-specific editing functions
+;; AUCTeX's latex.el, and some basic mode-specific editing functions
 ;; such as functions to move to the beginning or end of the enclosing
 ;; environment, or to mark, re-indent, or comment-out environments.
 ;; On the other hand, it doesn't yet provide any functionality for
--- a/lisp/ps-mule.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/ps-mule.el	Mon Aug 23 10:12:04 2004 +0000
@@ -213,53 +213,6 @@
 		 (const bdf-font-except-latin) (const :tag "nil" nil))
   :group 'ps-print-font)

-
-(eval-and-compile
-  ;; For Emacs 20.2 and the earlier version.
-  (if (and (boundp 'mule-version)
-	   (not (string< (symbol-value 'mule-version) "4.0")))
-      ;; mule package is loaded
-      (progn
-	(defalias 'ps-mule-next-point '1+)
-	(defalias 'ps-mule-chars-in-string 'length)
-	(defalias 'ps-mule-string-char 'aref)
-	(defsubst ps-mule-next-index (str i) (1+ i)))
-    ;; mule package isn't loaded or mule version lesser than 4.0
-    (defun ps-mule-next-point (arg)
-      (save-excursion (goto-char arg) (forward-char 1) (point)))
-    (defun ps-mule-chars-in-string (string)
-      (/ (length string)
-	 (charset-bytes (char-charset (string-to-char string)))))
-    (defun ps-mule-string-char (string idx)
-      (string-to-char (substring string idx)))
-    (defun ps-mule-next-index (string i)
-      (+ i (charset-bytes (char-charset (string-to-char string)))))
-    )
-  ;; For Emacs 20.4 and the earlier version.
-  (if (and (boundp 'mule-version)
-	   (string< (symbol-value 'mule-version) "5.0"))
-      ;; mule package is loaded and mule version is lesser than 5.0
-      (progn
-	(defun encode-composition-rule (rule)
-	  (if (= (car rule) 4) (setcar rule 10))
-	  (if (= (cdr rule) 4) (setcdr rule 10))
-	  (+ (* (car rule) 12) (cdr rule)))
-	(defun find-composition (pos &rest ignore)
-	  (let ((ch (char-after pos)))
-	    (and ch (eq (char-charset ch) 'composition)
-		 (let ((components (decompose-composite-char ch 'vector t)))
-		   (list pos (ps-mule-next-point pos) components
-			 (integerp (aref components 1)) nil
-			 (char-width ch)))))))
-    ;; mule package isn't loaded
-    (or (fboundp 'encode-composition-rule)
-	(defun encode-composition-rule (rule)
-	  130))
-    (or (fboundp 'find-composition)
-	(defun find-composition (pos &rest ignore)
-	  nil))
-    ))
-
 (defvar ps-mule-font-info-database
   nil
   "Alist of charsets with the corresponding font information.
@@ -847,7 +800,7 @@
 		run-width)))
     ;; We assume that all characters in this range have the same width.
     (setq char-width (* char-width (charset-width ps-mule-current-charset)))
-    (let ((run-width (* (chars-in-region from to) char-width)))
+    (let ((run-width (* (abs (- from to)) char-width)))
       (if (> run-width ps-width-remaining)
 	  (cons (min to
 		     (save-excursion
--- a/lisp/simple.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/simple.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1628,7 +1628,7 @@

 (defun shell-command-on-region (start end command
 				      &optional output-buffer replace
-				      error-buffer)
+				      error-buffer display-error-buffer)
   "Execute string COMMAND in inferior shell with region as input.
 Normally display output (if any) in temp buffer `*Shell Command Output*';
 Prefix arg means replace the region with it.  Return the exit code of
@@ -1641,10 +1641,10 @@
 `buffer-file-coding-system'.  If the output is going to replace the region,
 then it is decoded from that same coding system.

-The noninteractive arguments are START, END, COMMAND, OUTPUT-BUFFER,
-REPLACE, ERROR-BUFFER.  Noninteractive callers can specify coding
-systems by binding `coding-system-for-read' and
-`coding-system-for-write'.
+The noninteractive arguments are START, END, COMMAND,
+OUTPUT-BUFFER, REPLACE, ERROR-BUFFER, and DISPLAY-ERROR-BUFFER.
+Noninteractive callers can specify coding systems by binding
+`coding-system-for-read' and `coding-system-for-write'.

 If the command generates output, the output may be displayed
 in the echo area or in a buffer.
@@ -1674,6 +1674,8 @@
 If optional sixth argument ERROR-BUFFER is non-nil, it is a buffer
 or buffer name to which to direct the command's standard error output.
 If it is nil, error output is mingled with regular output.
+If DISPLAY-ERROR-BUFFER is non-nil, display the error buffer if there
+were any errors.  (This is always t, interactively.)
 In an interactive call, the variable `shell-command-default-error-buffer'
 specifies the value of ERROR-BUFFER."
   (interactive (let (string)
@@ -1691,7 +1693,8 @@
 		       string
 		       current-prefix-arg
 		       current-prefix-arg
-		       shell-command-default-error-buffer)))
+		       shell-command-default-error-buffer
+		       t)))
   (let ((error-file
 	 (if error-buffer
 	     (make-temp-file
@@ -1800,7 +1803,8 @@
 	      (format-insert-file error-file nil)
 	      ;; Put point after the inserted errors.
 	      (goto-char (- (point-max) pos-from-end)))
-	    (display-buffer (current-buffer))))
+	    (and display-error-buffer
+		 (display-buffer (current-buffer)))))
       (delete-file error-file))
     exit-status))
--- a/lisp/speedbar.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/speedbar.el	Mon Aug 23 10:12:04 2004 +0000
@@ -92,7 +92,7 @@
 ;; into sub-lists.  A long flat list can be used instead if needed.
 ;; Other filters can be easily added.
 ;;
-;;    AUC-TEX users: The imenu tags for AUC-TEX mode doesn't work very
+;;    AUCTEX users: The imenu tags for AUCTEX mode doesn't work very
 ;; well.  Use the imenu keywords from tex-mode.el for better results.
 ;;
 ;; This file requires the library package assoc (association lists)
@@ -665,6 +665,9 @@
   "*Regexp matching files we don't want displayed in a speedbar buffer.
 It is generated from the variable `completion-ignored-extensions'")

+;; Ugly compiler silencing trick.  The real defvar comes later in this file.
+(defvar speedbar-file-regexp)
+
 ;; this is dangerous to customize, because the defaults will probably
 ;; change in the future.
 (defcustom speedbar-supported-extension-expressions
@@ -691,6 +694,12 @@
 	 (setq speedbar-supported-extension-expressions val
 	       speedbar-file-regexp (speedbar-extension-list-to-regex val))))

+(defvar speedbar-file-regexp
+  (speedbar-extension-list-to-regex speedbar-supported-extension-expressions)
+  "Regular expression matching files we know how to expand.
+Created from `speedbar-supported-extension-expression' with the
+function `speedbar-extension-list-to-regex'")
+
 (defcustom speedbar-scan-subdirs nil
   "*Non-nil means speedbar will check if subdirs are empty.
 That way you don't have to click on them to find out.  But this
@@ -700,12 +709,6 @@
   :type 'boolean
   :version 21.4)

-(defvar speedbar-file-regexp
-  (speedbar-extension-list-to-regex speedbar-supported-extension-expressions)
-  "Regular expression matching files we know how to expand.
-Created from `speedbar-supported-extension-expression' with the
-function `speedbar-extension-list-to-regex'")
-
 (defun speedbar-add-supported-extension (extension)
   "Add EXTENSION as a new supported extension for speedbar tagging.
 This should start with a `.' if it is not a complete file name, and
@@ -1295,8 +1298,9 @@
     (toggle-read-only 1)
     (speedbar-set-mode-line-format)
     (if speedbar-xemacsp
-	(set (make-local-variable 'mouse-motion-handler)
-	     'speedbar-track-mouse-xemacs)
+	(with-no-warnings
+	 (set (make-local-variable 'mouse-motion-handler)
+	      'speedbar-track-mouse-xemacs))
       (if speedbar-track-mouse-flag
 	  (set (make-local-variable 'track-mouse) t))	;this could be messy.
       (setq auto-show-mode nil))	;no auto-show for Emacs
@@ -1345,7 +1349,8 @@
 frame and window to be the currently active frame and window."
   (if (and (frame-live-p speedbar-frame)
 	   (or (not speedbar-xemacsp)
-	       (specifier-instance has-modeline-p)))
+	       (with-no-warnings
+		(specifier-instance has-modeline-p))))
       (save-excursion
 	(set-buffer speedbar-buffer)
 	(let* ((w (or (speedbar-frame-width) 20))
@@ -1546,9 +1551,7 @@
     ;; This gets the cursor where the user can see it.
     (if (not (bolp)) (forward-char -1))
     (sit-for 0)
-    (if (< emacs-major-version 20)
-	(mouse-major-mode-menu e)
-      (mouse-major-mode-menu e nil))))
+    (mouse-major-mode-menu e nil)))

 (defun speedbar-hack-buffer-menu (e)
   "Control mouse 1 is buffer menu.
--- a/lisp/startup.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/startup.el	Mon Aug 23 10:12:04 2004 +0000
@@ -227,7 +227,7 @@
   "File containing site-wide run-time initializations.
 This file is loaded at run-time before `~/.emacs'.  It contains inits
 that need to be in place for the entire site, but which, due to their
-higher incidence of change, don't make sense to load into emacs'
+higher incidence of change, don't make sense to load into Emacs's
 dumped image.  Thus, the run-time load order is: 1. file described in
 this variable, if non-nil; 2. `~/.emacs'; 3. `default.el'.

@@ -300,8 +300,8 @@
       (let* ((this-dir (car dirs))
 	     (contents (directory-files this-dir))
 	     (default-directory this-dir)
-	     (canonicalized (and (eq system-type 'windows-nt)
-				 (untranslated-canonical-name this-dir))))
+	     (canonicalized (if (fboundp 'untranslated-canonical-name)
+				(untranslated-canonical-name this-dir))))
 	;; The Windows version doesn't report meaningful inode
 	;; numbers, so use the canonicalized absolute file name of the
 	;; directory instead.
@@ -350,12 +350,14 @@
     ;; Give *Messages* the same default-directory as *scratch*,
     ;; just to keep things predictable.
     (let ((dir default-directory))
-      (save-excursion
-	(set-buffer (get-buffer "*Messages*"))
+      (with-current-buffer "*Messages*"
 	(setq default-directory dir)))
     ;; `user-full-name' is now known; reset its standard-value here.
     (put 'user-full-name 'standard-value
 	 (list (default-value 'user-full-name)))
+    ;; Subprocesses of Emacs do not have direct access to the terminal,
+    ;; so unless told otherwise they should only assume a dumb terminal.
+    (setenv "TERM" "dumb")
     ;; For root, preserve owner and group when editing files.
     (if (equal (user-uid) 0)
 	(setq backup-by-copying-when-mismatch t))
@@ -364,32 +366,25 @@
     ;; of that dir into load-path,
     ;; Look for a leim-list.el file too.  Loading it will register
     ;; available input methods.
-    (let ((tail load-path)
-	  new)
-      (while tail
-	(push (car tail) new)
-	(condition-case nil
-	    (let ((default-directory (car tail)))
-	      (load (expand-file-name "subdirs.el" (car tail)) t t t)))
-	(condition-case nil
-	    (let ((default-directory (car tail)))
-	      (load (expand-file-name "leim-list.el" (car tail)) t t t)))
-	(setq tail (cdr tail))))
-    (if (not (eq system-type 'vax-vms))
-	(progn
-	  ;; If the PWD environment variable isn't accurate, delete it.
-	  (let ((pwd (getenv "PWD")))
-	    (and (stringp pwd)
-		 ;; Use FOO/., so that if FOO is a symlink, file-attributes
-		 ;; describes the directory linked to, not FOO itself.
-		 (or (equal (file-attributes
-			     (concat (file-name-as-directory pwd) "."))
-			    (file-attributes
-			     (concat (file-name-as-directory default-directory)
-				     ".")))
-		     (setq process-environment
-			   (delete (concat "PWD=" pwd)
-				   process-environment)))))))
+    (dolist (dir load-path)
+      (let ((default-directory dir))
+	(load (expand-file-name "subdirs.el") t t t))
+      (let ((default-directory dir))
+	(load (expand-file-name "leim-list.el") t t t)))
+    (unless (eq system-type 'vax-vms)
+      ;; If the PWD environment variable isn't accurate, delete it.
+      (let ((pwd (getenv "PWD")))
+	(and (stringp pwd)
+	     ;; Use FOO/., so that if FOO is a symlink, file-attributes
+	     ;; describes the directory linked to, not FOO itself.
+	     (or (equal (file-attributes
+			 (concat (file-name-as-directory pwd) "."))
+			(file-attributes
+			 (concat (file-name-as-directory default-directory)
+				 ".")))
+		 (setq process-environment
+		       (delete (concat "PWD=" pwd)
+			       process-environment))))))
     (setq default-directory (abbreviate-file-name default-directory))
     (let ((menubar-bindings-done nil))
       (unwind-protect
--- a/lisp/subr.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/subr.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1196,7 +1196,7 @@

 (make-obsolete 'process-kill-without-query
                "use `process-query-on-exit-flag' or `set-process-query-on-exit-flag'."
-               "21.5")
+               "21.4")
 (defun process-kill-without-query (process &optional flag)
   "Say no query needed if PROCESS is running when Emacs is exited.
 Optional second argument if non-nil says to require a query.
--- a/lisp/textmodes/flyspell.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/textmodes/flyspell.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1011,8 +1011,7 @@
 				 (concat "^" word "\n"))
 	    ;; we mark the ispell process so it can be killed
 	    ;; when emacs is exited without query
-	    (if (fboundp 'process-kill-without-query)
-		(process-kill-without-query ispell-process))
+	    (set-process-query-on-exit-flag ispell-process nil)
 	    ;; wait until ispell has processed word
 	    (while (progn
 		     (accept-process-output ispell-process)
@@ -1065,7 +1064,7 @@
 				      flyspell-duplicate-distance)
 				   t)))))
 		   (if flyspell-highlight-flag
-		       (flyspell-highlight-duplicate-region start end)
+		       (flyspell-highlight-duplicate-region start end poss)
 		     (message (format "duplicate `%s'" word))))
 		  (t
 		   ;; incorrect highlight the location
@@ -1540,8 +1539,9 @@
 ;*---------------------------------------------------------------------*/
 ;*    flyspell-highlight-duplicate-region ...                          */
 ;*---------------------------------------------------------------------*/
-(defun flyspell-highlight-duplicate-region (beg end)
-  "Set up an overlay on a duplicated word, in the buffer from BEG to END."
+(defun flyspell-highlight-duplicate-region (beg end poss)
+  "Set up an overlay on a duplicated word, in the buffer from BEG to END.
+??? What does POSS mean?"
   (let ((inhibit-read-only t))
     (unless (run-hook-with-args-until-success
 	     'flyspell-incorrect-hook beg end poss)
@@ -1947,7 +1947,6 @@
 			     mouse-pos
 			   (set-mouse-position (car mouse-pos)
 				 	       (/ (frame-width) 2) 2)
-			   (unfocus-frame)
 			   (mouse-position))))
 	(setq event (list (list (car (cdr mouse-pos))
 				(1+ (cdr (cdr mouse-pos))))
--- a/lisp/textmodes/reftex-auc.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/textmodes/reftex-auc.el	Mon Aug 23 10:12:04 2004 +0000
@@ -1,4 +1,4 @@
-;;; reftex-auc.el --- RefTeX's interface to AUC TeX
+;;; reftex-auc.el --- RefTeX's interface to AUCTeX
 ;; Copyright (c) 1997, 1998, 1999, 2000, 2003 Free Software Foundation, Inc.

 ;; Author: Carsten Dominik <dominik@science.uva.nl>
--- a/lisp/whitespace.el	Mon Aug 23 08:50:01 2004 +0000
+++ b/lisp/whitespace.el	Mon Aug 23 10:12:04 2004 +0000
@@ -820,6 +820,9 @@
       (setq whitespace-rescan-timer nil))))

 ;;;###autoload
+(defalias 'global-whitespace-mode 'whitespace-global-mode)
+
+;;;###autoload
 (define-minor-mode whitespace-global-mode
   "Toggle using Whitespace mode in new buffers.
 With ARG, turn the mode on iff ARG is positive.
--- a/lispref/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/lispref/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,8 @@
+2004-08-22  Richard M. Stallman  <rms@gnu.org>
+
+	* modes.texi (Major Mode Conventions): Discuss rebinding of
+	standard key bindings.
+
 2004-08-18  Kim F. Storm  <storm@cua.dk>

 	* processes.texi (Accepting Output): Add `just-this-one' arg to
--- a/lispref/modes.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/lispref/modes.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -188,16 +188,24 @@
 characters are reserved for minor modes, and ordinary letters are
 reserved for users.

-It is reasonable for a major mode to rebind a key sequence with a
-standard meaning, if it implements a command that does ``the same job''
-in a way that fits the major mode better.  For example, a major mode for
-editing a programming language might redefine @kbd{C-M-a} to ``move to
-the beginning of a function'' in a way that works better for that
-language.
-
-Major modes such as Dired or Rmail that do not allow self-insertion of
-text can reasonably redefine letters and other printing characters as
-editing commands.  Dired and Rmail both do this.
+A major mode can also rebind the keys @kbd{M-n}, @kbd{M-p} and
+@kbd{M-s}.  The bindings for @kbd{M-n} and @kbd{M-p} should normally
+be some kind of ``moving forward and backward,'' but this does not
+necessarily mean cursor motion.
+
+It is legitimate for a major mode to rebind a standard key sequence if
+it provides a command that does ``the same job'' in a way better
+suited to the text this mode is used for.  For example, a major mode
+for editing a programming language might redefine @kbd{C-M-a} to
+``move to the beginning of a function'' in a way that works better for
+that language.
+
+It is also legitimate for a major mode to rebind a standard key
+sequence whose standard meaning is rarely useful in that mode.  For
+instance, minibuffer modes rebind @kbd{M-r}, whose standard meaning is
+rarely of any use in the minibuffer.  Major modes such as Dired or
+Rmail that do not allow self-insertion of text can reasonably redefine
+letters and other printing characters as special commands.

 @item
 Major modes must not define @key{RET} to do anything other than insert
--- a/man/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,38 @@
+2004-08-22  David Kastrup  <dak@gnu.org>
+
+	* reftex.texi (AUCTeX): Update links, section name.
+
+	* faq.texi (Calc): Update availability (included in 21.4).
+	(AUCTeX): Update availability, information, versions, description.
+
+2004-08-21  Luc Teirlinck  <teirllm@auburn.edu>
+
+	* kmacro.texi (Keyboard Macro Ring): Rename section.
+	Emacs treats the head of the macro ring as the `last keyboard macro'.
+	(Keyboard Macro Counter): Minor change.
+	(Save Keyboard Macro): Some clarifications.
+	(Edit Keyboard Macro): Rename section.
+
+	* buffers.texi (Buffers): Maximum buffer size is now 256M on
+	32-bit machines.
+	(Several Buffers): Clarify which buffer is selected if `2' is
+	pressed in the Buffer Menu.
+	Auto Revert mode can be used to update the Buffer Menu
+	automatically.
+
+2004-08-21  Eli Zaretskii  <eliz@gnu.org>
+
+	* help.texi (Misc Help): Add an index entry for finding an Info
+	manual by its file name.
+
+2004-08-20  Luc Teirlinck  <teirllm@auburn.edu>
+
+	* files.texi (Backup Deletion): Correct description of
+	`delete-old-versions'.
+	(Time Stamps): `time-stamp' needs to be added to `before-save-hook'.
+	(Auto Save Files): Recommend `auto-save-mode' to reenable
+	auto-saving, rather than the abbreviation `auto-save'.
+
 2004-08-17  Luc Teirlinck  <teirllm@auburn.edu>

 	* emacs.texi (Top): Mention "cutting" and "pasting" as synonyms
--- a/man/buffers.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/buffers.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -1,5 +1,5 @@
 @c This is part of the Emacs manual.
-@c Copyright (C) 1985, 86, 87, 93, 94, 95, 97, 2000, 2001
+@c Copyright (C) 1985, 86, 87, 93, 94, 95, 97, 2000, 2001, 2004
 @c   Free Software Foundation, Inc.
 @c See file emacs.texi for copying conditions.
 @node Buffers, Windows, Files, Top
@@ -44,7 +44,7 @@
   A buffer's size cannot be larger than some maximum, which is defined
 by the largest buffer position representable by the @dfn{Emacs integer}
 data type.  This is because Emacs tracks buffer positions using that
-data type.  For 32-bit machines, the largest buffer size is 128
+data type.  For 32-bit machines, the largest buffer size is 256
 megabytes.

 @menu
@@ -395,9 +395,9 @@
 @item 1
 Immediately select this line's buffer in a full-screen window.
 @item 2
-Immediately set up two windows, with this line's buffer in one, and the
-previously current buffer (aside from the buffer @samp{*Buffer List*})
-in the other.
+Immediately set up two windows, with this line's buffer selected in
+one, and the previously current buffer (aside from the buffer
+@samp{*Buffer List*}) displayed in the other.
 @item b
 Bury the buffer listed on this line.
 @item m
@@ -427,12 +427,19 @@
 and select the buffer list manually, you can use all of the commands
 described here.

-  The buffer @samp{*Buffer List*} is not updated automatically when
+  Normally, the buffer @samp{*Buffer List*} is not updated automatically when
 buffers are created and killed; its contents are just text.  If you have
 created, deleted or renamed buffers, the way to update @samp{*Buffer
 List*} to show what you have done is to type @kbd{g}
 (@code{revert-buffer}) or repeat the @code{buffer-menu} command.

+  The @samp{*Buffer List*} buffer does automatically update every
+@code{auto-revert-interval} seconds if you enable Auto Revert mode in
+it.  (As long as it is not marked modified.)  Global Auto Revert mode
+does not update the @samp{*Buffer List*} buffer by default, but it
+does if @code{global-auto-revert-non-file-buffers} is non-@code{nil}.
+@inforef{Autorevert,, emacs-xtra}, for details.
+
   The command @code{buffer-menu-other-window} works the same as
 @code{buffer-menu}, except that it displays the buffers list in
 another window.
--- a/man/faq.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/faq.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -3953,10 +3953,11 @@
 @email{daveg@@csvax.cs.caltech.edu, Dave Gillespie}

 @item Latest version
-2.02f
+2.02g (part of Emacs since version 21.4)

 @item Distribution
-@uref{ftp://ftp.gnu.org/pub/gnu/calc/calc-2.02f.tar.gz}
+No separate distribution outside of Emacs.  Older versions
+are available at @uref{ftp://ftp.gnu.org/pub/gnu/calc/}.

 @end table

@@ -3996,34 +3997,41 @@
 @end table

 @node AUCTeX, BBDB, VIPER, Major packages and programs
-@section AUCTeX --- enhanced LaTeX mode with debugging facilities
+@section AUC@TeX{} --- enhanced @TeX{} modes with debugging facilities
 @cindex Mode for @TeX{}
 @cindex @TeX{} mode
-@cindex AUCTeX mode for editing @TeX{}
+@cindex AUC@TeX{} mode for editing @TeX{}
 @cindex Writing and debugging @TeX{}

+AUC@TeX{} is a set of sophisticated major modes for @TeX{}, LaTeX,
+ConTeXt, and Texinfo offering context-sensitive syntax highlighting,
+indentation, formatting and folding, macro completion, @TeX{} shell
+functionality, and debugging.  Some important supplemental packages are
+described in @ref{Introduction, RefTeX, Introduction, reftex, Ref@TeX{}
+User Manual}, and
+@uref{http://preview-latex.sourceforge.net,preview-latex}.
+
 @table @b

 @item Authors
-@email{krab@@iesd.auc.dk, Kresten Krab Thorup} and@*
-@email{abraham@@dina.kvl.dk, Per Abrahamsen}
+@email{krab@@iesd.auc.dk, Kresten Krab Thorup}, @*
+@email{abraham@@dina.kvl.dk, Per Abrahamsen}, @* and others.

 @item Maintainer
 @email{dak@@gnu.org, David Kastrup}

 @item Latest version
-11.13
+11.52

 @item Distribution
-@uref{http://savannah.gnu.org/download/auctex/stable.pkg/11.13/auctex-11.13.tar.gz}
+@uref{ftp://ftp.gnu.org/pub/gnu/auctex/}

 @item Web site
 @uref{http://www.gnu.org/software/auctex/}

 @item Mailing list:
 Subscription requests to @email{auc-tex-subscribe@@sunsite.dk}@*
-Submissions to @email{auc-tex@@sunsite.dk}@*
-Development team is at @email{auc-tex_mgr@@sunsite.dk}
+Submissions to @email{auc-tex@@sunsite.dk}

 @end table
--- a/man/files.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/files.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -1,5 +1,5 @@
 @c This is part of the Emacs manual.
-@c Copyright (C) 1985,86,87,93,94,95,97,99, 2000, 2001
+@c Copyright (C) 1985,86,87,93,94,95,97,99, 2000, 2001, 2004
 @c   Free Software Foundation, Inc.
 @c See file emacs.texi for copying conditions.
 @node Files, Buffers, Keyboard Macros, Top
@@ -625,9 +625,10 @@
 default, both variables are 2.

 @vindex delete-old-versions
-  If @code{delete-old-versions} is non-@code{nil}, Emacs deletes the
-excess backup files silently.  If it is @code{nil}, the default, Emacs
-asks you whether it should delete the excess backup versions.
+  If @code{delete-old-versions} is @code{t}, Emacs deletes the excess
+backup files silently.  If it is @code{nil}, the default, Emacs asks
+you whether it should delete the excess backup versions.  If it has
+any other value, then Emacs never automatically deletes backups.

   Dired's @kbd{.} (Period) command can also be used to delete old versions.
 @xref{Dired Deletion}.
@@ -836,7 +837,7 @@
 @end example

   Then add the hook function @code{time-stamp} to the hook
-@code{write-file-functions}; that hook function will automatically update
+@code{before-save-hook}; that hook function will automatically update
 the time stamp, inserting the current date and time when you save the
 file.  You can also use the command @kbd{M-x time-stamp} to update the
 time stamp manually.  For other customizations, see the Custom group
@@ -942,7 +943,7 @@
 @samp{#} to the front and rear of buffer name, then
 adding digits and letters at the end for uniqueness.  For
 example, the @samp{*mail*} buffer in which you compose messages to be
-sent might auto-saved in a file named @file{#*mail*#704juu}.  Auto-save file
+sent might be auto-saved in a file named @file{#*mail*#704juu}.  Auto-save file
 names are made this way unless you reprogram parts of Emacs to do
 something different (the functions @code{make-auto-save-file-name} and
 @code{auto-save-file-name-p}).  The file name to be used for auto-saving
@@ -962,7 +963,7 @@
 deleted the text unintentionally, you might find the auto-save file more
 useful if it contains the deleted text.  To reenable auto-saving after
 this happens, save the buffer with @kbd{C-x C-s}, or use @kbd{C-u 1 M-x
-auto-save}.
+auto-save-mode}.

 @vindex auto-save-visited-file-name
   If you want auto-saving to be done in the visited file rather than
@@ -1567,7 +1568,7 @@

 @item
 Pressing @kbd{L} shows the log of the revision at line.  This is
-useful to see the author's description of the changes that occured
+useful to see the author's description of the changes that occurred
 when the revision denoted on the current line was committed.

 @item
@@ -1585,7 +1586,7 @@
 @menu
 * Registering::         Putting a file under version control.
 * VC Status::           Viewing the VC status of files.
-* VC Undo::             Cancelling changes before or after check-in.
+* VC Undo::             Canceling changes before or after check-in.
 * VC Dired Mode::       Listing files managed by version control.
 * VC Dired Commands::   Commands to use in a VC Dired buffer.
 @end menu
--- a/man/help.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/help.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -455,6 +455,7 @@
 system will be available.  Type @kbd{h} after entering Info to run
 a tutorial on using Info.

+@cindex find Info manual by its file name
   If you specify a numeric argument, @kbd{C-h i} prompts for the name of
 a documentation file.  This way, you can browse a file which doesn't
 have an entry in the top-level Info menu.  It is also handy when you
--- a/man/kmacro.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/kmacro.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -1,5 +1,5 @@
 @c This is part of the Emacs manual.
-@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2002,2003
+@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2002,2003,2004
 @c  Free Software Foundation, Inc.
 @c See file emacs.texi for copying conditions.
 @node Keyboard Macros, Files, Fixit, Top
@@ -179,7 +179,7 @@
 beginning of the line and then executing the macro.

 @node Keyboard Macro Ring
-@section Where previous keyboard macros are saved
+@section The Keyboard Macro Ring

   All defined keyboard macros are recorded in the ``keyboard macro ring'',
 a list of sequences of keys.  There is only one keyboard macro ring,
@@ -220,6 +220,10 @@
 desired macro is at the head of the ring.  To execute the new macro
 ring head immediately, just type @kbd{C-k}.

+  Note that Emacs treats the head of the macro ring as the ``last
+defined keyboard macro''.  For instance, it is the keyboard macro that
+@kbd{C-x e} will execute.
+
 @findex kmacro-view-macro-repeat
 @kindex C-x C-k C-v

@@ -264,8 +268,7 @@
 macro counter is initialized to 0 when you start defining the macro,
 and incremented by 1 after each insertion of the counter value;
 that is, if you insert the macro counter twice while defining the
-macro, it will be incremented by 2 time for each repetition of the
-macro.
+macro, the counter will increase by 2 on each repetition of the macro.

 @findex kmacro-insert-counter
 @kindex C-x C-k C-i
@@ -362,18 +365,21 @@
 @kindex C-x C-k n
   If you wish to save a keyboard macro for later use, you can give it
 a name using @kbd{C-x C-k n} (@code{name-last-kbd-macro}).
-This reads a name as an argument using the minibuffer and defines that name
-to execute the macro.  The macro name is a Lisp symbol, and defining it in
-this way makes it a valid command name for calling with @kbd{M-x} or for
-binding a key to with @code{global-set-key} (@pxref{Keymaps}).  If you
-specify a name that has a prior definition other than another keyboard
-macro, an error message is shown and nothing is changed.
+This reads a name as an argument using the minibuffer and defines that
+name to execute the last keyboard macro, in its current form.  (If you
+later add to the definition of this macro, that does not alter the
+name's definition as a macro.)  The macro name is a Lisp symbol, and
+defining it in this way makes it a valid command name for calling with
+@kbd{M-x} or for binding a key to with @code{global-set-key}
+(@pxref{Keymaps}).  If you specify a name that has a prior definition
+other than a keyboard macro, an error message is shown and nothing is
+changed.

 @cindex binding keyboard macros
 @findex kmacro-bind-to-key
 @kindex C-x C-k b
-  Rather than giving a keyboard macro a name, you can bind it to a
-key using @kbd{C-x C-k b} (@code{kmacro-bind-to-key}) followed by the
+  You can also bind the last keyboard macro to a key, using
+@kbd{C-x C-k b} (@code{kmacro-bind-to-key}) followed by the
 key sequence you want the keyboard macro to be bound to.  You can
 bind to any key sequence in the global keymap, but since most key
 sequences already have other bindings, you should select the key
@@ -414,12 +420,12 @@
 macro will be defined each time you run Emacs.

   If you give @code{insert-kbd-macro} a numeric argument, it makes
-additional Lisp code to record the keys (if any) that you have bound to the
-keyboard macro, so that the macro will be reassigned the same keys when you
-load the file.
+additional Lisp code to record the keys (if any) that you have bound
+to @var{macroname}, so that the macro will be reassigned the same keys
+when you load the file.

 @node Edit Keyboard Macro
-@section Interactively executing and editing a keyboard macro
+@section Editing a Keyboard Macro

 @findex kmacro-edit-macro
 @kindex C-x C-k C-e
--- a/man/reftex.texi	Mon Aug 23 08:50:01 2004 +0000
+++ b/man/reftex.texi	Mon Aug 23 10:12:04 2004 +0000
@@ -2976,7 +2976,7 @@
 @end lisp

 @node AUCTeX, Multifile Documents, Faces, Top
-@section @w{AUC @TeX{}}
+@section AUC@TeX{}
 @cindex @code{AUCTeX}, Emacs package
 @cindex Emacs packages, @code{AUCTeX}

@@ -2985,7 +2985,7 @@
 If AUCTeX is not part of your Emacs distribution, you can get
 it@footnote{XEmacs 21.x users may want to install the corresponding
 XEmacs package.} by ftp from the
-@uref{http://www.sunsite.auc.dk/auctex/,AUCTeX distribution site}.
+@uref{ftp://ftp.gnu.org/pub/gnu/auctex,AUCTeX distribution site}.

 @menu
 * AUCTeX-RefTeX Interface::          How both packages work together
--- a/src/ChangeLog	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/ChangeLog	Mon Aug 23 10:12:04 2004 +0000
@@ -1,3 +1,45 @@
+2004-08-22  Richard M. Stallman  <rms@gnu.org>
+
+	* process.c (process_send_signal) [SIGNALS_VIA_CHARACTERS,
+	HAVE_TERMIOS]: If there's no char for this signal, drop through
+	and use system calls.
+
+	* bytecode.c (Fbyte_code) <unwind-protect>: Cannot GC.
+
+2004-08-20  Kim F. Storm  <storm@cua.dk>
+
+	* process.c (wait_reading_process_output): Rename from
+	wait_reading_process_input.  All uses changed.
+	(wait_reading_process_output_1): Rename from
+	wait_reading_process_input_1.  All uses changed.
+
+	* dispnew.c (Fsleep_for): Remove obsolete code.
+
+2004-08-20  Kenichi Handa  <handa@m17n.org>
+
+	* syntax.c (skip_chars): Fix for unibyte case.
+
+2004-08-19  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+	* syntax.c (char_quoted): Mixup byte/char pos.
+	(back_comment): Fixup globals in all cases.
+
+2004-08-19  Jan Dj,Ad(Brv  <jan.h.d@swipnet.se>
+
+	* xfns.c (x_set_name, x_set_title): Encode title to UTF8 before
+	passing it to gtk_window_set_title.
+
+2004-08-19  Kim F. Storm  <storm@cua.dk>
+
+	* process.c (wait_reading_process_input): Clean up.
+	Add wait_for_cell, wait_proc, and just_wait_proc args
+	to avoid overloading `read_kbd' and `do_display' args.
+	Change read_kbd arg to int.  All callers changed.
+
+	* process.c (process_send_signal): Use CDISABLE.
+
+	* sysdep.c (child_setup_tty, init_sys_modes): Use CDISABLE.
+
 2004-08-18  Kim F. Storm  <storm@cua.dk>

 	* process.c (Faccept_process_output): Add arg JUST-THIS-ONE;
--- a/src/bytecode.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/bytecode.c	Mon Aug 23 10:12:04 2004 +0000
@@ -855,10 +855,7 @@
 	  }

 	case Bunwind_protect:
-	  /* The function record_unwind_protect can GC.  */
-	  BEFORE_POTENTIAL_GC ();
 	  record_unwind_protect (Fprogn, POP);
-	  AFTER_POTENTIAL_GC ();
 	  break;

 	case Bcondition_case:
--- a/src/dispnew.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/dispnew.c	Mon Aug 23 10:12:04 2004 +0000
@@ -6358,52 +6358,13 @@
   if (sec < 0 || (sec == 0 && usec == 0))
     return Qnil;

-  {
-    Lisp_Object zero;
-
-    XSETFASTINT (zero, 0);
-    wait_reading_process_input (sec, usec, zero, 0);
-  }
-
-  /* We should always have wait_reading_process_input; we have a dummy
-     implementation for systems which don't support subprocesses.  */
-#if 0
-  /* No wait_reading_process_input */
-  immediate_quit = 1;
-  QUIT;
-
-#ifdef VMS
-  sys_sleep (sec);
-#else /* not VMS */
-/* The reason this is done this way
-    (rather than defined (H_S) && defined (H_T))
-   is because the VMS preprocessor doesn't grok `defined'.  */
-#ifdef HAVE_SELECT
-  EMACS_GET_TIME (end_time);
-  EMACS_SET_SECS_USECS (timeout, sec, usec);
-  EMACS_ADD_TIME (end_time, end_time, timeout);
-
-  while (1)
-    {
-      EMACS_GET_TIME (timeout);
-      EMACS_SUB_TIME (timeout, end_time, timeout);
-      if (EMACS_TIME_NEG_P (timeout)
-	  || !select (1, 0, 0, 0, &timeout))
-	break;
-    }
-#else /* not HAVE_SELECT */
-  sleep (sec);
-#endif /* HAVE_SELECT */
-#endif /* not VMS */
-
-  immediate_quit = 0;
-#endif /* no subprocesses */
+  wait_reading_process_output (sec, usec, 0, 0, Qnil, NULL, 0);

   return Qnil;
 }


-/* This is just like wait_reading_process_input, except that
+/* This is just like wait_reading_process_output, except that
    it does the redisplay.

    It's also much like Fsit_for, except that it can be used for
@@ -6413,8 +6374,6 @@
 sit_for (sec, usec, reading, display, initial_display)
      int sec, usec, reading, display, initial_display;
 {
-  Lisp_Object read_kbd;
-
   swallow_events (display);

   if (detect_input_pending_run_timers (display) || !NILP (Vexecuting_macro))
@@ -6430,8 +6389,8 @@
   gobble_input (0);
 #endif

-  XSETINT (read_kbd, reading ? -1 : 1);
-  wait_reading_process_input (sec, usec, read_kbd, display);
+  wait_reading_process_output (sec, usec, reading ? -1 : 1, display,
+			       Qnil, NULL, 0);

   return detect_input_pending () ? Qnil : Qt;
 }
--- a/src/keyboard.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/keyboard.c	Mon Aug 23 10:12:04 2004 +0000
@@ -3895,10 +3895,7 @@
 	break;
 #endif
       {
-	Lisp_Object minus_one;
-
-	XSETINT (minus_one, -1);
-	wait_reading_process_input (0, 0, minus_one, 1);
+	wait_reading_process_output (0, 0, -1, 1, Qnil, NULL, 0);

 	if (!interrupt_input && kbd_fetch_ptr == kbd_store_ptr)
 	  /* Pass 1 for EXPECT since we just waited to have input.  */
@@ -9995,7 +9992,7 @@
 }

 /* Return nonzero if there are pending requeued events.
-   This isn't used yet.  The hope is to make wait_reading_process_input
+   This isn't used yet.  The hope is to make wait_reading_process_output
    call it, and return if it runs Lisp code that unreads something.
    The problem is, kbd_buffer_get_event needs to be fixed to know what
    to do in that case.  It isn't trivial.  */
--- a/src/lisp.h	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/lisp.h	Mon Aug 23 10:12:04 2004 +0000
@@ -2964,7 +2964,10 @@
 EXFUN (Fwaiting_for_user_input_p, 0);
 extern Lisp_Object Qprocessp;
 extern void kill_buffer_processes P_ ((Lisp_Object));
-extern int wait_reading_process_input P_ ((int, int, Lisp_Object, int));
+extern int wait_reading_process_output P_ ((int, int, int, int,
+					    Lisp_Object,
+					    struct Lisp_Process *,
+					    int));
 extern void deactivate_process P_ ((Lisp_Object));
 extern void add_keyboard_wait_descriptor P_ ((int));
 extern void delete_keyboard_wait_descriptor P_ ((int));
--- a/src/msdos.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/msdos.c	Mon Aug 23 10:12:04 2004 +0000
@@ -5102,7 +5102,7 @@

 /* Only event queue is checked.  */
 /* We don't have to call timer_check here
-   because wait_reading_process_input takes care of that.  */
+   because wait_reading_process_output takes care of that.  */
 int
 sys_select (nfds, rfds, wfds, efds, timeout)
      int nfds;
--- a/src/process.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/process.c	Mon Aug 23 10:12:04 2004 +0000
@@ -3777,13 +3777,12 @@
   else
     seconds = NILP (process) ? -1 : 0;

-  if (NILP (process))
-    XSETFASTINT (process, 0);
-
   return
-    (wait_reading_process_input (seconds, useconds, process,
-				 NILP (just_this_one) ? 0 :
-				 !INTEGERP (just_this_one) ? -1 : -2)
+    (wait_reading_process_output (seconds, useconds, 0, 0,
+				  Qnil,
+				  !NILP (process) ? XPROCESS (process) : NULL,
+				  NILP (just_this_one) ? 0 :
+				  !INTEGERP (just_this_one) ? 1 : -1)
      ? Qt : Qnil);
 }

@@ -3983,12 +3982,12 @@
    lisp code is being evalled.
    This is also used in record_asynch_buffer_change.
    For that purpose, this must be 0
-   when not inside wait_reading_process_input.  */
+   when not inside wait_reading_process_output.  */
 static int waiting_for_user_input_p;

 /* This is here so breakpoints can be put on it.  */
 static void
-wait_reading_process_input_1 ()
+wait_reading_process_output_1 ()
 {
 }

@@ -4010,28 +4009,32 @@
      1 to return when input is available, or
      -1 meaning caller will actually read the input, so don't throw to
        the quit handler, or
-     a cons cell, meaning wait until its car is non-nil
-       (and gobble terminal input into the buffer if any arrives), or
-     a process object, meaning wait until something arrives from that
-       process.  The return value is true iff we read some input from
-       that process.
-
-   If READ_KBD is a process object, DO_DISPLAY < 0 means handle only
-     output from that process (suspending output from other processes)
-     and DO_DISPLAY == -2 specifically means don't run any timers either.
-   Otherwise, != 0 means redisplay should be done to show subprocess
+
+   DO_DISPLAY != 0 means redisplay should be done to show subprocess
      output that arrives.

-   If READ_KBD is a pointer to a struct Lisp_Process, then the
-     function returns true iff we received input from that process
-     before the timeout elapsed.
+   If WAIT_FOR_CELL is a cons cell, wait until its car is non-nil
+     (and gobble terminal input into the buffer if any arrives).
+
+   If WAIT_PROC is specified, wait until something arrives from that
+     process.  The return value is true iff we read some input from
+     that process.
+
+   If JUST_WAIT_PROC is non-nil, handle only output from WAIT_PROC
+     (suspending output from other processes).  A negative value
+     means don't run any timers either.
+
+   If WAIT_PROC is specified, then the function returns true iff we
+     received input from that process before the timeout elapsed.
    Otherwise, return true iff we received input from any process.  */

 int
-wait_reading_process_input (time_limit, microsecs, read_kbd, do_display)
-     int time_limit, microsecs;
-     Lisp_Object read_kbd;
-     int do_display;
+wait_reading_process_output (time_limit, microsecs, read_kbd, do_display,
+			     wait_for_cell, wait_proc, just_wait_proc)
+     int time_limit, microsecs, read_kbd, do_display;
+     Lisp_Object wait_for_cell;
+     struct Lisp_Process *wait_proc;
+     int just_wait_proc;
 {
   register int channel, nfds;
   SELECT_TYPE Available;
@@ -4041,39 +4044,19 @@
   Lisp_Object proc;
   EMACS_TIME timeout, end_time;
   int wait_channel = -1;
-  struct Lisp_Process *wait_proc = 0;
-  int just_wait_proc = 0;
   int got_some_input = 0;
   /* Either nil or a cons cell, the car of which is of interest and
      may be changed outside of this routine.  */
-  Lisp_Object wait_for_cell = Qnil;
   int saved_waiting_for_user_input_p = waiting_for_user_input_p;

   FD_ZERO (&Available);
   FD_ZERO (&Connecting);

-  /* If read_kbd is a process to watch, set wait_proc and wait_channel
-     accordingly.  */
-  if (PROCESSP (read_kbd))
-    {
-      wait_proc = XPROCESS (read_kbd);
-      wait_channel = XINT (wait_proc->infd);
-      XSETFASTINT (read_kbd, 0);
-      if (do_display < 0)
-	{
-	  just_wait_proc = do_display;
-	  do_display = 0;
-	}
-    }
-
-  /* If waiting for non-nil in a cell, record where.  */
-  if (CONSP (read_kbd))
-    {
-      wait_for_cell = read_kbd;
-      XSETFASTINT (read_kbd, 0);
-    }
-
-  waiting_for_user_input_p = XINT (read_kbd);
+  /* If wait_proc is a process to watch, set wait_channel accordingly.  */
+  if (wait_proc != NULL)
+    wait_channel = XINT (wait_proc->infd);
+
+  waiting_for_user_input_p = read_kbd;

   /* Since we may need to wait several times,
      compute the absolute time to return at.  */
@@ -4101,7 +4084,7 @@
       /* If calling from keyboard input, do not quit
 	 since we want to return C-g as an input character.
 	 Otherwise, do pending quit if requested.  */
-      if (XINT (read_kbd) >= 0)
+      if (read_kbd >= 0)
 	QUIT;
 #ifdef SYNC_INPUT
       else if (interrupt_input_pending)
@@ -4139,7 +4122,7 @@
 	 the wait is supposed to be short,
 	 and those callers cannot handle running arbitrary Lisp code here.  */
       if (NILP (wait_for_cell)
-	  && just_wait_proc != -2)
+	  && just_wait_proc >= 0)
 	{
 	  EMACS_TIME timer_delay;

@@ -4167,7 +4150,7 @@
 	  while (!detect_input_pending ());

 	  /* If there is unread keyboard input, also return.  */
-	  if (XINT (read_kbd) != 0
+	  if (read_kbd != 0
 	      && requeued_events_pending_p ())
 	    break;

@@ -4185,7 +4168,7 @@
 	  else if (time_limit != -1)
 	    {
 	      /* This is so a breakpoint can be put here.  */
-	      wait_reading_process_input_1 ();
+	      wait_reading_process_output_1 ();
 	    }
 	}

@@ -4195,7 +4178,7 @@
 	 It is important that we do this before checking for process
 	 activity.  If we get a SIGCHLD after the explicit checks for
 	 process activity, timeout is the only way we will know.  */
-      if (XINT (read_kbd) < 0)
+      if (read_kbd < 0)
 	set_waiting_for_input (&timeout);

       /* If status of something has changed, and no input is
@@ -4275,8 +4258,10 @@

       /* Wait till there is something to do */

-      if (just_wait_proc)
+      if (wait_proc && just_wait_proc)
 	{
+	  if (XINT (wait_proc->infd) < 0)  /* Terminated */
+	    break;
 	  FD_SET (XINT (wait_proc->infd), &Available);
 	  check_connect = check_delay = 0;
 	}
@@ -4287,7 +4272,7 @@
 	}
       else
 	{
-	  if (! XINT (read_kbd))
+	  if (! read_kbd)
 	    Available = non_keyboard_wait_mask;
 	  else
 	    Available = input_wait_mask;
@@ -4304,12 +4289,12 @@
 	{
 	  clear_waiting_for_input ();
 	  redisplay_preserve_echo_area (11);
-	  if (XINT (read_kbd) < 0)
+	  if (read_kbd < 0)
 	    set_waiting_for_input (&timeout);
 	}

       no_avail = 0;
-      if (XINT (read_kbd) && detect_input_pending ())
+      if (read_kbd && detect_input_pending ())
 	{
 	  nfds = 0;
 	  no_avail = 1;
@@ -4426,10 +4411,10 @@
       /* If we are using polling for input,
 	 and we see input available, make it get read now.
 	 Otherwise it might not actually get read for a second.
-	 And on hpux, since we turn off polling in wait_reading_process_input,
+	 And on hpux, since we turn off polling in wait_reading_process_output,
 	 it might never get read at all if we don't spend much time
-	 outside of wait_reading_process_input.  */
-      if (XINT (read_kbd) && interrupt_input
+	 outside of wait_reading_process_output.  */
+      if (read_kbd && interrupt_input
 	  && keyboard_bit_set (&Available)
 	  && input_polling_used ())
 	kill (getpid (), SIGALRM);
@@ -4439,7 +4424,7 @@
       /* If there is any, return immediately
 	 to give it higher priority than subprocesses */

-      if (XINT (read_kbd) != 0)
+      if (read_kbd != 0)
 	{
 	  int old_timers_run = timers_run;
 	  struct buffer *old_buffer = current_buffer;
@@ -4464,7 +4449,7 @@
 	}

       /* If there is unread keyboard input, also return.  */
-      if (XINT (read_kbd) != 0
+      if (read_kbd != 0
 	  && requeued_events_pending_p ())
 	break;

@@ -4475,7 +4460,7 @@
 	 That would causes delays in pasting selections, for example.

 	 (We used to do this only if wait_for_cell.)  */
-      if (XINT (read_kbd) == 0 && detect_input_pending ())
+      if (read_kbd == 0 && detect_input_pending ())
 	{
 	  swallow_events (do_display);
 #if 0  /* Exiting when read_kbd doesn't request that seems wrong, though.  */
@@ -4494,7 +4479,7 @@
 	 In that case, there really is no input and no SIGIO,
 	 but select says there is input.  */

-      if (XINT (read_kbd) && interrupt_input
+      if (read_kbd && interrupt_input
 	  && keyboard_bit_set (&Available) && ! noninteractive)
 	kill (getpid (), SIGIO);
 #endif
@@ -4504,7 +4489,7 @@

       /* If checking input just got us a size-change event from X,
 	 obey it now if we should.  */
-      if (XINT (read_kbd) || ! NILP (wait_for_cell))
+      if (read_kbd || ! NILP (wait_for_cell))
 	do_pending_window_change (0);

       /* Check for data from a process.  */
@@ -4679,7 +4664,7 @@
   /* If calling from keyboard input, do not quit
      since we want to return C-g as an input character.
      Otherwise, do pending quit if requested.  */
-  if (XINT (read_kbd) >= 0)
+  if (read_kbd >= 0)
     {
       /* Prevent input_pending from remaining set if we quit.  */
       clear_input_pending ();
@@ -5326,7 +5311,6 @@
 		       that may allow the program
 		       to finish doing output and read more.  */
 		    {
-		      Lisp_Object zero;
 		      int offset = 0;

 #ifdef BROKEN_PTY_READ_AFTER_EAGAIN
@@ -5361,11 +5345,10 @@
 		      else if (STRINGP (object))
 			offset = buf - SDATA (object);

-		      XSETFASTINT (zero, 0);
 #ifdef EMACS_HAS_USECS
-		      wait_reading_process_input (0, 20000, zero, 0);
+		      wait_reading_process_output (0, 20000, 0, 0, Qnil, NULL, 0);
 #else
-		      wait_reading_process_input (1, 0, zero, 0);
+		      wait_reading_process_output (1, 0, 0, 0, Qnil, NULL, 0);
 #endif

 		      if (BUFFERP (object))
@@ -5594,17 +5577,13 @@
 	  break;
 	}

-#ifndef _POSIX_VDISABLE
-#ifdef CVDISABLE
-#define _POSIX_VDISABLE CVDISABLE
-#else
-#define _POSIX_VDISABLE '\0'
-#endif
-#endif
-
-      if (sig_char && *sig_char != _POSIX_VDISABLE)
-	send_process (proc, sig_char, 1, Qnil);
-      return;
+      if (sig_char && *sig_char != CDISABLE)
+	{
+	  send_process (proc, sig_char, 1, Qnil);
+	  return;
+	}
+      /* If we can't send the signal with a character,
+	 fall through and send it another way.  */
 #else /* ! HAVE_TERMIOS */

       /* On Berkeley descendants, the following IOCTL's retrieve the
@@ -5661,9 +5640,12 @@
 	 you'd better be using one of the alternatives above!  */
 #endif /* ! defined (TCGETA) */
 #endif /* ! defined (TIOCGLTC) && defined (TIOCGETC) */
-#endif /* ! defined HAVE_TERMIOS */
+	/* In this case, the code above should alway returns.  */
 	abort ();
-      /* The code above always returns from the function.  */
+#endif /* ! defined HAVE_TERMIOS */
+
+      /* The code above may fall through if it can't
+	 handle the signal.  */
 #endif /* defined (SIGNALS_VIA_CHARACTERS) */

 #ifdef TIOCGPGRP
@@ -6235,7 +6217,7 @@
 	      FD_CLR (XINT (p->infd), &non_keyboard_wait_mask);
 	    }

-	  /* Tell wait_reading_process_input that it needs to wake up and
+	  /* Tell wait_reading_process_output that it needs to wake up and
 	     look around.  */
 	  if (input_available_clear_time)
 	    EMACS_SET_SECS_USECS (*input_available_clear_time, 0, 0);
@@ -6253,7 +6235,7 @@
 	  else if (WIFSIGNALED (w))
             synch_process_termsig = WTERMSIG (w);

-	  /* Tell wait_reading_process_input that it needs to wake up and
+	  /* Tell wait_reading_process_output that it needs to wake up and
 	     look around.  */
 	  if (input_available_clear_time)
 	    EMACS_SET_SECS_USECS (*input_available_clear_time, 0, 0);
@@ -6892,10 +6874,9 @@
      1 to return when input is available, or
      -1 means caller will actually read the input, so don't throw to
        the quit handler.
-     a cons cell, meaning wait until its car is non-nil
-       (and gobble terminal input into the buffer if any arrives), or
-     We know that read_kbd will never be a Lisp_Process, since
-     `subprocesses' isn't defined.
+
+   see full version for other parameters. We know that wait_proc will
+     always be NULL, since `subprocesses' isn't defined.

    do_display != 0 means redisplay should be done to show subprocess
    output that arrives.
@@ -6903,27 +6884,17 @@
    Return true iff we received input from any process.  */

 int
-wait_reading_process_input (time_limit, microsecs, read_kbd, do_display)
-     int time_limit, microsecs;
-     Lisp_Object read_kbd;
-     int do_display;
+wait_reading_process_output (time_limit, microsecs, read_kbd, do_display,
+			     wait_for_cell, wait_proc, just_wait_proc)
+     int time_limit, microsecs, read_kbd, do_display;
+     Lisp_Object wait_for_cell;
+     struct Lisp_Process *wait_proc;
+     int just_wait_proc;
 {
   register int nfds;
   EMACS_TIME end_time, timeout;
   SELECT_TYPE waitchannels;
   int xerrno;
-  /* Either nil or a cons cell, the car of which is of interest and
-     may be changed outside of this routine.  */
-  Lisp_Object wait_for_cell;
-
-  wait_for_cell = Qnil;
-
-  /* If waiting for non-nil in a cell, record where.  */
-  if (CONSP (read_kbd))
-    {
-      wait_for_cell = read_kbd;
-      XSETFASTINT (read_kbd, 0);
-    }

   /* What does time_limit really mean?  */
   if (time_limit || microsecs)
@@ -6946,7 +6917,7 @@
       /* If calling from keyboard input, do not quit
 	 since we want to return C-g as an input character.
 	 Otherwise, do pending quit if requested.  */
-      if (XINT (read_kbd) >= 0)
+      if (read_kbd >= 0)
 	QUIT;

       /* Exit now if the cell we're waiting for became non-nil.  */
@@ -6997,7 +6968,7 @@
 	  while (!detect_input_pending ());

 	  /* If there is unread keyboard input, also return.  */
-	  if (XINT (read_kbd) != 0
+	  if (read_kbd != 0
 	      && requeued_events_pending_p ())
 	    break;

@@ -7015,12 +6986,12 @@

       /* Cause C-g and alarm signals to take immediate action,
 	 and cause input available signals to zero out timeout.  */
-      if (XINT (read_kbd) < 0)
+      if (read_kbd < 0)
 	set_waiting_for_input (&timeout);

       /* Wait till there is something to do.  */

-      if (! XINT (read_kbd) && NILP (wait_for_cell))
+      if (! read_kbd && NILP (wait_for_cell))
 	FD_ZERO (&waitchannels);
       else
 	FD_SET (0, &waitchannels);
@@ -7031,11 +7002,11 @@
 	{
 	  clear_waiting_for_input ();
 	  redisplay_preserve_echo_area (15);
-	  if (XINT (read_kbd) < 0)
+	  if (read_kbd < 0)
 	    set_waiting_for_input (&timeout);
 	}

-      if (XINT (read_kbd) && detect_input_pending ())
+      if (read_kbd && detect_input_pending ())
 	{
 	  nfds = 0;
 	  FD_ZERO (&waitchannels);
@@ -7071,13 +7042,13 @@
 	kill (getpid (), SIGIO);
 #endif
 #ifdef SIGIO
-      if (XINT (read_kbd) && interrupt_input && (waitchannels & 1))
+      if (read_kbd && interrupt_input && (waitchannels & 1))
 	kill (getpid (), SIGIO);
 #endif

       /* Check for keyboard input */

-      if ((XINT (read_kbd) != 0)
+      if (read_kbd
 	  && detect_input_pending_run_timers (do_display))
 	{
 	  swallow_events (do_display);
@@ -7086,7 +7057,7 @@
 	}

       /* If there is unread keyboard input, also return.  */
-      if (XINT (read_kbd) != 0
+      if (read_kbd
 	  && requeued_events_pending_p ())
 	break;
--- a/src/syntax.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/syntax.c	Mon Aug 23 10:12:04 2004 +0000
@@ -292,7 +292,7 @@

   DEC_BOTH (charpos, bytepos);

-  while (bytepos >= beg)
+  while (charpos >= beg)
     {
       int c;

@@ -673,7 +673,7 @@
     {
       from = comstart_pos;
       from_byte = comstart_byte;
-      /* Globals are correct now.  */
+      UPDATE_SYNTAX_TABLE_FORWARD (from - 1);
     }
   else
     {
@@ -1728,12 +1728,12 @@
 		      if (negate)
 			break;
 		      else
-			goto fwd_ok;
+			goto fwd_unibyte_ok;
 		    }

 		  if (!fastmap[*p])
 		    break;
-
+		fwd_unibyte_ok:
 		  p++, pos++;
 		}
 	  }
@@ -1801,12 +1801,12 @@
 		      if (negate)
 			break;
 		      else
-			goto fwd_ok;
+			goto back_unibyte_ok;
 		    }

 		  if (!fastmap[p[-1]])
 		    break;
-
+		back_unibyte_ok:
 		  p--, pos--;
 		}
 	  }
--- a/src/sysdep.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/sysdep.c	Mon Aug 23 10:12:04 2004 +0000
@@ -610,9 +610,9 @@
 #ifdef SIGNALS_VIA_CHARACTERS
   /* the QUIT and INTR character are used in process_send_signal
      so set them here to something useful.  */
-  if (s.main.c_cc[VQUIT] == 0377)
+  if (s.main.c_cc[VQUIT] == CDISABLE)
     s.main.c_cc[VQUIT] = '\\'&037;	/* Control-\ */
-  if (s.main.c_cc[VINTR] == 0377)
+  if (s.main.c_cc[VINTR] == CDISABLE)
     s.main.c_cc[VINTR] = 'C'&037;	/* Control-C */
 #endif /* not SIGNALS_VIA_CHARACTERS */

@@ -631,11 +631,11 @@
      would force it to 0377.  That looks like duplicated code.  */
 #ifndef SIGNALS_VIA_CHARACTERS
   /* QUIT and INTR work better as signals, so disable character forms */
-  s.main.c_cc[VQUIT] = 0377;
-  s.main.c_cc[VINTR] = 0377;
+  s.main.c_cc[VQUIT] = CDISABLE;
+  s.main.c_cc[VINTR] = CDISABLE;
   s.main.c_lflag &= ~ISIG;
 #endif /* no TIOCGPGRP or no TIOCGLTC or no TIOCGETC */
-  s.main.c_cc[VEOL] = 0377;
+  s.main.c_cc[VEOL] = CDISABLE;
   s.main.c_cflag = (s.main.c_cflag & ~CBAUD) | B9600; /* baud rate sanity */
 #endif /* AIX */

@@ -1550,10 +1550,10 @@
   tty.main.c_line = 0;
   tty.main.c_iflag &= ~ASCEDIT;
 #else
-  tty.main.c_cc[VSTRT] = 255;
-  tty.main.c_cc[VSTOP] = 255;
-  tty.main.c_cc[VSUSP] = 255;
-  tty.main.c_cc[VDSUSP] = 255;
+  tty.main.c_cc[VSTRT] = CDISABLE;
+  tty.main.c_cc[VSTOP] = CDISABLE;
+  tty.main.c_cc[VSUSP] = CDISABLE;
+  tty.main.c_cc[VDSUSP] = CDISABLE;
 #endif /* IBMR2AIX */
   if (tty_out->flow_control)
     {
--- a/src/w32proc.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/w32proc.c	Mon Aug 23 10:12:04 2004 +0000
@@ -1218,7 +1218,7 @@
     {
       DebPrint (("select.WaitForMultipleObjects (%d, %lu) failed with %lu\n",
 		 nh + nc, timeout_ms, GetLastError ()));
-      /* don't return EBADF - this causes wait_reading_process_input to
+      /* don't return EBADF - this causes wait_reading_process_output to
 	 abort; WAIT_FAILED is returned when single-stepping under
 	 Windows 95 after switching thread focus in debugger, and
 	 possibly at other times. */
--- a/src/w32term.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/w32term.c	Mon Aug 23 10:12:04 2004 +0000
@@ -4570,7 +4570,7 @@
 		  f->async_visible = 1;
 		  f->async_iconified = 0;

-		  /* wait_reading_process_input will notice this and update
+		  /* wait_reading_process_output will notice this and update
 		     the frame's display structures.  */
 		  SET_FRAME_GARBAGED (f);
--- a/src/xdisp.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/xdisp.c	Mon Aug 23 10:12:04 2004 +0000
@@ -10377,7 +10377,7 @@
    This is useful in situations where you need to redisplay but no
    user action has occurred, making it inappropriate for the message
    area to be cleared.  See tracking_off and
-   wait_reading_process_input for examples of these situations.
+   wait_reading_process_output for examples of these situations.

    FROM_WHERE is an integer saying from where this function was
    called.  This is useful for debugging.  */
--- a/src/xfns.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/xfns.c	Mon Aug 23 10:12:04 2004 +0000
@@ -1661,7 +1661,7 @@
 	  }
 #ifdef USE_GTK
         gtk_window_set_title (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
-                              SDATA (name));
+                              SDATA (ENCODE_UTF_8 (name)));
 #else /* not USE_GTK */
 	XSetWMName (FRAME_X_DISPLAY (f), FRAME_OUTER_WINDOW (f), &text);
 #endif /* not USE_GTK */
@@ -1769,7 +1769,7 @@

 #ifdef USE_GTK
         gtk_window_set_title (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
-                              SDATA (name));
+                              SDATA (ENCODE_UTF_8 (name)));
 #else /* not USE_GTK */
 	XSetWMName (FRAME_X_DISPLAY (f), FRAME_OUTER_WINDOW (f), &text);
 #endif /* not USE_GTK */
--- a/src/xselect.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/xselect.c	Mon Aug 23 10:12:04 2004 +0000
@@ -1117,7 +1117,8 @@
       secs = x_selection_timeout / 1000;
       usecs = (x_selection_timeout % 1000) * 1000;
       TRACE2 ("  Waiting %d secs, %d usecs", secs, usecs);
-      wait_reading_process_input (secs, usecs, property_change_reply, 0);
+      wait_reading_process_output (secs, usecs, 0, 0,
+				   property_change_reply, NULL, 0);

       if (NILP (XCAR (property_change_reply)))
 	{
@@ -1305,7 +1306,8 @@
   secs = x_selection_timeout / 1000;
   usecs = (x_selection_timeout % 1000) * 1000;
   TRACE1 ("  Start waiting %d secs for SelectionNotify", secs);
-  wait_reading_process_input (secs, usecs, reading_selection_reply, 0);
+  wait_reading_process_output (secs, usecs, 0, 0,
+			       reading_selection_reply, NULL, 0);
   TRACE1 ("  Got event = %d", !NILP (XCAR (reading_selection_reply)));

   BLOCK_INPUT;
--- a/src/xterm.c	Mon Aug 23 08:50:01 2004 +0000
+++ b/src/xterm.c	Mon Aug 23 10:12:04 2004 +0000
@@ -6178,7 +6178,7 @@
       f = x_top_window_to_frame (dpyinfo, event.xmap.window);
       if (f)
         {
-          /* wait_reading_process_input will notice this and update
+          /* wait_reading_process_output will notice this and update
              the frame's display structures.
              If we where iconified, we should not set garbaged,
              because that stops redrawing on Expose events.  This looks