+Known Problems with GNU Emacs
+
Copyright (C) 1987, 1988, 1989, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
Free Software Foundation, Inc.
in compiling, installing and running GNU Emacs. Try doing Ctl-C Ctl-t
and browsing through the outline headers.
+* Mule-UCS doesn't work in Emacs 23.
+
+It's completely redundant now, as far as we know.
+
* Emacs startup failures
** Emacs fails to start, complaining about missing fonts.
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
This can occur when two different versions of FontConfig are used.
For example, XFree86 4.3.0 has one version and Gnome usually comes
-with a newer version. Emacs compiled with --with-gtk will then use
+with a newer version. Emacs compiled with Gtk+ will then use
the newer version. In most cases the problem can be temporarily
fixed by stopping the application that has the error (it can be
Emacs or any other application), removing ~/.fonts.cache-1,
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'.
+neep font from the Debian xfonts-jmk package prior to version 3.0.17.
+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
** Subscript/superscript text in TeX is hard to read.
-tex-mode displays subscript/superscript text in the faces
-subscript/superscript, which are smaller than the normal font and
-lowered/raised. With some fonts, nested superscripts (say) can be
-hard to read. Switching to a different font, or changing your
-antialiasing setting (on an LCD screen), can both make the problem
-disappear. Alternatively, customize the subscript and superscript
-faces to increase their height.
+If `tex-fontify-script' is non-nil, tex-mode displays
+subscript/superscript text in the faces subscript/superscript, which
+are smaller than the normal font and lowered/raised. With some fonts,
+nested superscripts (say) can be hard to read. Switching to a
+different font, or changing your antialiasing setting (on an LCD
+screen), can both make the problem disappear. Alternatively, customize
+the following variables: tex-font-script-display (how much to
+lower/raise); tex-suscript-height-ratio (how much smaller than
+normal); tex-suscript-height-minimum (minimum height).
* Internationalization problems
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.
-
-*** Mac OS X 10.3.9 (Carbon): QuickTime updater breaks build.
-
-Some QuickTime updaters such as 7.0.4 and 7.2.0 are known to break
-build at the link stage with the message like "Undefined symbols:
-_HICopyAccessibilityActionDescription referenced from QuickTime
-expected to be defined in Carbon". A workaround is to use a QuickTime
-reinstaller. Alternatively, you can link with the frameworks in the
-corresponding SDK by specifying LDFLAGS as
-"-Wl,-F/Developer/SDKs/MacOSX10.3.0.sdk/System/Library/Frameworks".
-
** FreeBSD
*** FreeBSD 2.1.5: useless symbolic links remain in /tmp or other
*** 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.
+Makefile in the src subdirectory.
It has been known to get fatal errors due to insufficient swapping
space available on the machine.
The only known fix: Don't run display-time.
-*** SunOS
-
-SunOS 4.1.4 stopped shipping on Sep 30 1998.
-
-**** SunOS: You get linker errors
- ld: Undefined symbol
- _get_wmShellWidgetClass
- _get_applicationShellWidgetClass
-
-**** 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 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.
-
-The fix to this is to install patch 100573 for OpenWindows 3.0
-or link libXmu statically.
-
**** Sunos 5.3: Subprocesses remain, hanging but not zombies.
A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
applies to ptys, and doesn't fix the problem with subprocesses
communicating through pipes.
-*** 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.
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.
-
-** SunOS4, DGUX 5.4.2: --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.
-
** 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.
-** 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:
In the XCONS, etc., macros in lisp.h you must replace (a).u.val with
((a).u.val + coercedummy) where coercedummy is declared as int.
-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.
+This problem will only happen if USE_LISP_UNION_TYPE is manually
+defined in lisp.h.
*** C compilers lose on returning unions.
Most of the functions in GNU Emacs return type Lisp_Object, which is
defined as a union on some rare architectures.
-This problem will not happen if the m-...h file for your type
-of machine defines NO_UNION_TYPE.
+This problem will only happen if USE_LISP_UNION_TYPE is manually
+defined in lisp.h.
\f
This file is part of GNU Emacs.
-GNU Emacs is free software; you can redistribute it and/or modify
+GNU Emacs is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 3, or (at your option)
-any later version.
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
GNU Emacs is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
-along with GNU Emacs; see the file COPYING. If not, write to the
-Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
-Boston, MA 02110-1301, USA.
+along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
\f
Local variables: