+Copyright (C) 1987, 1988, 1989, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+ 2001, 2002, 2003, 2004, 2005, 2006, 2007
+ Free Software Foundation, Inc.
+See the end of the file for license conditions.
+
+
This file describes various problems that have been encountered
-in compiling, installing and running GNU Emacs. Try doing Ctl t
+in compiling, installing and running GNU Emacs. Try doing Ctl-C Ctl-t
and browsing through the outline headers.
* Emacs startup failures
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.
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.
+** Emacs compiled with Gtk+ crashes when closing a display (x-close-connection).
+
+This happens because of bugs in Gtk+. Gtk+ 2.10 seems to be OK. See bug
+http://bugzilla.gnome.org/show_bug.cgi?id=85715.
+
* General runtime problems
** Lisp problems
*** 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.
+*** 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
Upgrade to AUC TeX version 10 or later, and make sure it is
byte-compiled with Emacs 21.
+** PCL-CVS
+
+*** Lines are not updated or new lines are added in the buffer upon commit.
+
+When committing files located higher in the hierarchy than the examined
+directory, some versions of the CVS program return an ambiguous message
+from which PCL-CVS cannot extract the full location of the committed
+files. As a result, the corresponding lines in the PCL-CVS buffer are
+not updated with the new revision of these files, and new lines are
+added to the top-level directory.
+
+This can happen with CVS versions 1.12.8 and 1.12.9. Upgrade to CVS
+1.12.10 or newer to fix this problem.
+
** Miscellaneous problems
*** Self-documentation messages are garbled.
problem by adding this to your .cshrc file:
if ($?EMACS) then
- if ($EMACS == "t") then
+ if ("$EMACS" =~ /*) then
unset edit
stty -icrnl -onlcr -echo susp ^Z
endif
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.
+display all the characters Emacs supports. The etl-unicode collection
+of fonts (available from <URL:ftp://ftp.x.org/contrib/fonts/> and
+<URL:ftp://ftp.xfree86.org/pub/mirror/X.Org/contrib/fonts/>) includes
+fonts that can display many Unicode characters; they can also be used
+by ps-print and ps-mule to print Unicode characters.
Another cause of this for specific characters is fonts which have a
missing glyph and no default character. This is known to occur for
** Under X11, some characters appear improperly aligned in their lines.
-You may have bad X11 fonts; try installing the intlfonts distribution.
+You may have bad X11 fonts; try installing the intlfonts distribution
+or the etl-unicode collection (see the previous entry).
** Certain fonts make each line take one pixel more than it "should".
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
+Beginning with version 22.1, 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.
* Internationalization problems
+** M-{ does not work on a Spanish PC keyboard.
+
+Many Spanish keyboards seem to ignore that combination. Emacs can't
+do anything about it.
+
** Characters from the mule-unicode charsets aren't displayed under X.
XFree86 4 contains many fonts in iso10646-1 encoding which have
** 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
-of CJK, Yi and Hangul, as well as everything outside the BMP.
+Emacs directly supports the Unicode BMP whose code points are in the
+ranges 0000-33ff and e000-ffff, and indirectly supports the parts of
+CJK characters belonging to these legacy charsets:
+
+ GB2312, Big5, JISX0208, JISX0212, JISX0213-1, JISX0213-2, KSC5601
+
+The latter support is done in Utf-Translate-Cjk mode (turned on by
+default). Which Unicode CJK characters are decoded into which Emacs
+charset is decided by the current language environment. For instance,
+in Chinese-GB, most of them are decoded into chinese-gb2312.
If you read UTF-8 data with code points outside these ranges, the
characters appear in the buffer as raw bytes of the original UTF-8
substituted with the Unicode `replacement character', and you lose
information.
-To edit such UTF data, turn on Utf-Translate-Cjk mode, which makes
-many common CJK characters available for encoding and decoding and can
-be extended by updating the tables it uses. This also allows you to
-save as UTF buffers containing characters decoded by the chinese-,
-japanese- and korean- coding systems, e.g. cut and pasted from
-elsewhere.
-
** Mule-UCS loads very slowly.
Changes to Emacs internals interact badly with Mule-UCS's `un-define'
Note that Emacs has native support for Unicode, roughly equivalent to
Mule-UCS's, so you may not need it.
+** Mule-UCS compilation problem.
+
+Emacs of old versions and XEmacs byte-compile the form `(progn progn
+...)' the same way as `(progn ...)', but Emacs of version 21.3 and the
+later process that form just as interpreter does, that is, as `progn'
+variable reference. Apply the following patch to Mule-UCS 0.84 to
+make it compiled by the latest Emacs.
+
+--- mucs-ccl.el 2 Sep 2005 00:42:23 -0000 1.1.1.1
++++ mucs-ccl.el 2 Sep 2005 01:31:51 -0000 1.3
+@@ -639,10 +639,14 @@
+ (mucs-notify-embedment 'mucs-ccl-required name)
+ (setq ccl-pgm-list (cdr ccl-pgm-list)))
+ ; (message "MCCLREGFIN:%S" result)
+- `(progn
+- (setq mucs-ccl-facility-alist
+- (quote ,mucs-ccl-facility-alist))
+- ,@result)))
++ ;; The only way the function is used in this package is included
++ ;; in `mucs-package-definition-end-hook' value, where it must
++ ;; return (possibly empty) *list* of forms. Do this. Do not rely
++ ;; on byte compiler to remove extra `progn's in `(progn ...)'
++ ;; form.
++ `((setq mucs-ccl-facility-alist
++ (quote ,mucs-ccl-facility-alist))
++ ,@result)))
+
+ ;;; Add hook for embedding translation informations to a package.
+ (add-hook 'mucs-package-definition-end-hook
+
** Accented ISO-8859-1 characters are displayed as | or _.
Try other font set sizes (S-mouse-1). If the problem persists with
Use the shell command `xset bc' to make the old X Menu package work.
+*** C-SPC fails to work on Fedora GNU/Linux (or with fcitx input method).
+
+Fedora Core 4 steals the C-SPC key by default for the `iiimx' program
+which is the input method for some languages. It blocks Emacs users
+from using the C-SPC key for `set-mark-command'.
+
+One solutions is to remove the `<Ctrl>space' from the `Iiimx' file
+which can be found in the `/usr/lib/X11/app-defaults' directory.
+However, that requires root access.
+
+Another is to specify `Emacs*useXIM: false' in your X resources.
+
+Another is to build Emacs with the `--without-xim' configure option.
+
+The same problem happens on any other system if you are using fcitx
+(Chinese input method) which by default use C-SPC for toggling. If
+you want to use fcitx with Emacs, you have two choices. Toggle fcitx
+by another key (e.g. C-\) by modifying ~/.fcitx/config, or be
+accustomed to use C-@ for `set-mark-command'.
+
*** M-SPC seems to be ignored as input.
See if your X server is set up to use this as a command
** Window-manager and toolkit-related problems
+*** Gnome: Emacs receives input directly from the keyboard, bypassing XIM.
+
+This seems to happen when gnome-settings-daemon version 2.12 or later
+is running. If gnome-settings-daemon is not running, Emacs receives
+input through XIM without any problem. Furthermore, this seems only
+to happen in *.UTF-8 locales; zh_CN.GB2312 and zh_CN.GBK locales, for
+example, work fine. A bug report has been filed in the Gnome
+bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032
+
*** 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
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,
+of klipper don't implement the ICCCM protocol for large selections,
which leads to Emacs being flooded with selection requests. After a
-while, Emacs will print a message:
+while, Emacs may print a message:
Timed out waiting for property-notify event
-A workaround is to not use `klipper'.
+A workaround is to not use `klipper'. An upgrade to the `klipper' that
+comes with KDE 3.3 or later also solves the problem.
*** CDE: Frames may cover dialogs they created when using CDE.
A solution is to exit the offending X programs before starting Emacs.
+"undefined color" messages can also occur if the RgbPath entry in the
+X configuration file is incorrect, or the rgb.txt file is not where
+X expects to find it.
+
*** Improving performance with slow X connections.
There are several ways to improve this performance, any subset of which can
package.
2) If the connection is very slow, you might also want to consider
- switching off scroll bars, menu bar, and tool bar.
+ switching off scroll bars, menu bar, and tool bar. Adding the
+ following forms to your .emacs file will accomplish that, but only
+ after the the initial frame is displayed:
+
+ (scroll-bar-mode -1)
+ (menu-bar-mode -1)
+ (tool-bar-mode -1)
+
+ For still quicker startup, put these X resources in your .Xdefaults
+ file:
+
+ Emacs.verticalScrollBars: off
+ Emacs.menuBar: off
+ Emacs.toolBar: off
3) Use ssh to forward the X connection, and enable compression on this
forwarded X connection (ssh -XC remotehostname emacs ...).
For more about lbxproxy, see:
http://www.xfree86.org/4.3.0/lbxproxy.1.html
+5) If copying and killing is slow, try to disable the interaction with the
+ native system's clipboard by adding these lines to your .emacs file:
+ (setq interprogram-cut-function nil)
+ (setq interprogram-paste-function nil)
+
*** Emacs gives the error, Couldn't find per display information.
This can result if the X server runs out of memory because Emacs uses
-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'.
`xterm-color' might activate the color support on an xterm-compatible
emulator.
-Beginning with version 21.4, Emacs supports the --color command-line
+Beginning with version 22.1, 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.
** GNU/Linux
+*** GNU/Linux: Process output is corrupted.
+
+There is a bug in Linux kernel 2.6.10 PTYs that can cause emacs to
+read corrupted process output.
+
+*** GNU/Linux: Remote access to CVS with SSH causes file corruption.
+
+If you access a remote CVS repository via SSH, files may be corrupted
+due to bad interaction between CVS, SSH, and libc.
+
+To fix the problem, save the following script into a file, make it
+executable, and set CVS_RSH environment variable to the file name of
+the script:
+
+#!/bin/bash
+exec 2> >(exec cat >&2 2>/dev/null)
+exec ssh "$@"
+
*** 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.
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.
+*** GNU/Linux: 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'.
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 7.0.4 updater breaks build.
+
+On the above environment, build fails 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 QuickTime 7.0.1 reinstaller.
+
** FreeBSD
*** FreeBSD 2.1.5: useless symbolic links remain in /tmp or other
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).
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.
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
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:
+*** Solaris 2,6: Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
- /usr/openwin/lib/locale/iso8859-15/Compose
+We suspect that this is a 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:
-Near the bottom there is a line that reads:
+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
- Ctrl<t> <quotedbl> <Y> : "\276" threequarters
+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:
-that should read:
+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
- Ctrl<T> <quotedbl> <Y> : "\276" threequarters
+*** Solaris 7 or 8: Emacs reports a BadAtom error (from X)
-Note the lower case <t>. Changing this line should make C-t work.
+This happens when Emacs was built on some other version of Solaris.
+Rebuild it on Solaris 8.
*** When using M-x dbx with the SparcWorks debugger, the `up' and `down'
commands do not move the arrow in Emacs.
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.
+*** On Solaris, CTRL-t is ignored by Emacs when you use
+the fr.ISO-8859-15 locale (and maybe other related locales).
-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.
+You can fix this by editing the file:
-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.
+ /usr/openwin/lib/locale/iso8859-15/Compose
-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/.
+Near the bottom there is a line that reads:
-*** Irix 5.3: Emacs crashes in utmpname.
+ Ctrl<t> <quotedbl> <Y> : "\276" threequarters
-This problem is fixed in Patch 3175 for Irix 5.3.
-It is also fixed in Irix versions 6.2 and up.
+that should read:
-*** Irix 6.0: Make tries (and fails) to build a program named unexelfsgi.
+ Ctrl<T> <quotedbl> <Y> : "\276" threequarters
-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.
+Note the lower case <t>. Changing this line should make C-t work.
-Compiler fixes in Irix 6.0.1 should eliminate this problem.
+** Irix
*** 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.
+*** Irix: Trouble using ptys, 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:
+* Runtime problems specific to MS-Windows
- # /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
+** Windows 95 and networking.
-(He recommends you not change the stack limit, though.)
-These changes take effect when you reboot.
+To support server sockets, Emacs 22.1 loads ws2_32.dll. If this file
+is missing, all Emacs networking features are disabled.
-* Runtime problems specific to MS-Windows
+Old versions of Windows 95 may not have the required DLL. To use
+Emacs' networking features on Windows 95, you must install the
+"Windows Socket 2" update available from MicroSoft's support Web.
** Emacs exits with "X protocol error" when run with an X server for MS-Windows.
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.
+** Known problems with the MS-Windows port of Emacs 22.1
+
+Using create-fontset-from-ascii-font or the --font startup parameter
+with a Chinese, Japanese or Korean font leads to display problems.
+Use a Latin-only font as your default font. If you want control over
+which font is used to display Chinese, Japanese or Korean character,
+use create-fontset-from-fontset-spec to define a fontset.
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
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
+Windows input methods are not recognized by Emacs. 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
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).
+** Typing Alt-Shift has strange effects on MS-Windows.
-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.
+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.
-For Perl 4:
+** Cygwin build of Emacs hangs after rebasing Cygwin DLLs
- *** 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";
- }
+Usually, on Cygwin, one needs to rebase the DLLs if an application
+aborts with a message like this:
- --- 68,74 ----
- $rcfile=".perldb";
- }
- else {
- ! $console = "";
- $rcfile="perldb.ini";
- }
+ C:\cygwin\bin\python.exe: *** unable to remap C:\cygwin\bin\cygssl.dll to
+ same address as parent(0xDF0000) != 0xE00000
+However, since Cygwin DLL 1.5.17 was released, after such rebasing,
+Emacs hangs.
- 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 {
+This was reported to happen for Emacs 21.2 and also for the pretest of
+Emacs 22.1 on Cygwin.
-** On MS-Windows 95, Alt-f6 does not get through to Emacs.
+To work around this, build Emacs like this:
-This character seems to be trapped by the kernel in Windows 95.
-You can enter M-f6 by typing ESC f6.
+ LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base' ./configure
+ make LD='$(CC)'
+ make LD='$(CC)' install
-** Typing Alt-Shift has strange effects on MS-Windows.
+This produces an Emacs binary that is independent of rebasing.
-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.
+Note that you _must_ use LD='$(CC)' in the last two commands above, to
+prevent GCC from passing the "--image-base 0x20000000" option to the
+linker, which is what it does by default. That option produces an
+Emacs binary with the base address 0x20000000, which will cause Emacs
+to hang after Cygwin DLLs are rebased.
** Interrupting Cygwin port of Bash from Emacs doesn't work.
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
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''.
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.
+*** Building a 32-bit executable on a 64-bit GNU/Linux architecture.
+
+First ensure that the necessary 32-bit system libraries and include
+files are installed. Then use:
+
+ env CC="gcc -m32" ./configure --build=i386-linux-gnu \
+ --x-libraries=/usr/X11R6/lib
+
+(using the location of the 32-bit X libraries on your system).
+
+*** Building the Cygwin port for MS-Windows can fail with some GCC version
+
+Building Emacs 22 with Cygwin builds of GCC 3.4.4-1 and 3.4.4-2 is
+reported to either fail or cause Emacs to segfault at run time. In
+addition, the Cygwin GCC 3.4.4-2 has problems with generating debug
+info. Cygwin users are advised not to use these versions of GCC for
+compiling Emacs. GCC versions 4.0.3 and 4.1.1 reportedly build a
+working Cygwin binary of Emacs, so we recommend these GCC versions.
+
+*** Building the native 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
*** 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.
+1 and newer), the new "Exec-shield" functionality is enabled by default, which
+creates a different memory layout that breaks the emacs dumper. Emacs tries
+to handle this at build time, but if the workaround used fails, these
+instructions can be useful.
+The work-around explained here is not enough on Fedora Core 4 (and possible
+newer). Read the next item.
+
+Configure can overcome the problem of exec-shield if the architecture is
+x86 and the program setarch is present. On other architectures no
+workaround is known.
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
+It returns non-zero when Exec-shield is enabled, 0 otherwise. Please
read your system documentation for more details on Exec-shield and
-associated commands.
+associated commands. Exec-shield can be turned off with this command:
+
+ echo "0" > /proc/sys/kernel/exec-shield
When Exec-shield is enabled, building Emacs will segfault during the
execution of this command:
-temacs --batch --load loadup [dump|bootstrap]
+ ./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:
+Exec-shield while building Emacs, or, on x86, by using the `setarch'
+command when running temacs like this:
+
+ setarch i386 ./temacs --batch --load loadup [dump|bootstrap]
+
+
+*** Fedora Core 4 GNU/Linux: Segfault during dumping.
+
+In addition to exec-shield explained above "Linux: Segfault during
+`make bootstrap' under certain recent versions of the Linux kernel"
+item, Linux kernel shipped with Fedora Core 4 randomizes the virtual
+address space of a process. As the result dumping may fail even if
+you turn off exec-shield. In this case, use the -R option to the setarch
+command:
+
+ setarch i386 -R ./temacs --batch --load loadup [dump|bootstrap]
- setarch i386 ./configure <configure parameters>
- setarch i386 make <make parameters>
+or
+
+ setarch i386 -R make bootstrap
*** Fatal signal in the command temacs -l loadup inc dump.
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'.
** Ancient operating systems
+AIX 4.2 was end-of-lifed on Dec 31st, 1999.
+
+*** 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.
+
+(This report must be ancient. Bootable tapes are long dead.)
+
+*** 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 3.2.5: 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 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.
+
*** ISC Unix
**** ISC: display-time causes kernel problems on ISC systems.
*** 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
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
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.
+**** 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.
+
*** Apollo Domain
**** Shell mode ignores interrupts on Apollo Domain.
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.
+**** 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
if you link with the MIT X11 libraries instead of the Solaris X11
libraries.
+*** HP/UX versions before 11.0
+
+HP/UX 9 was end-of-lifed in December 1998.
+HP/UX 10 was end-of-lifed in May 1999.
+
+**** HP/UX 9: Emacs crashes with SIGBUS or SIGSEGV 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.
+
+*** HP/UX 10: Large file support is disabled.
+
+See the comments in src/s/hpux10.h.
+
+*** 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.
+
*** Ultrix and Digital Unix
**** Ultrix 4.2: `make install' fails on install-doc with `Error 141'.
This makes Emacs use memory less efficiently, but seems to work around
the kernel bug.
+*** Irix 5 and earlier
+
+Exactly when Irix-5 end-of-lifed is obscure. But since Irix 6.0
+shipped in 1994, it has been some years.
+
+**** 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.
+
+*** 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.
+
+**** SCO 4.2.0: 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.
+
*** Linux 1.x
**** Linux 1.0-1.04: Typing C-c C-c in Shell mode kills your X server.
This is due to a kernel bug which seems to be fixed in Linux version
1.3.75.
+** Windows 3.1, 95, 98, and ME
+
+*** MS-Windows NT/95: Problems running Perl under Emacs
+
+`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 {
+
+*** 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.
+
+*** 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.
+
** MS-DOS
*** When compiling with DJGPP on MS-Windows NT, "config msdos" fails.
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
of machine defines NO_UNION_TYPE.
\f
-Copyright 1987,88,89,93,94,95,96,97,98,1999,2001,2002,2004
- Free Software Foundation, Inc.
+This file is part of GNU Emacs.
-Copying and redistribution of this file with or without modification
-are permitted without royalty provided this notice is preserved.
+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 2, 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
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+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.
+
+\f
Local variables:
mode: outline
paragraph-separate: "[ \f]*$"
HCoop / bpt / emacs.git / blobdiff