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
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".
* 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 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 ...)'
++ ;; 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
** 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
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
* Runtime problems specific to MS-Windows
+** Windows 95 and networking.
+
+To support server sockets, Emacs 22.1 loads ws2_32.dll. If this file
+is missing, all Emacs networking features are disabled.
+
+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.
A certain X server for Windows had a bug which caused this.
more permanent work around is to change it to another key combination,
or disable it in the keyboard control panel.
+** Cygwin build of Emacs hangs after rebasing Cygwin DLLs
+
+Usually, on Cygwin, one needs to rebase the DLLs if an application
+aborts with a message like this:
+
+ 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.
+
+This was reported to happen for Emacs 21.2 and also for the pretest of
+Emacs 22.1 on Cygwin.
+
+To work around this, build Emacs like this:
+
+ LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base' ./configure
+ make LD='$(CC)'
+ make LD='$(CC)' install
+
+This produces an Emacs binary that is independent of rebasing.
+
+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.
Cygwin 1.x builds of the ported Bash cannot be interrupted from the
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
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
or
- setarch i386 -R make bootstrap
+ setarch i386 -R make bootstrap
*** Fatal signal in the command temacs -l loadup inc dump.
of machine defines NO_UNION_TYPE.
\f
-Copyright 1987, 1988, 1989, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
- 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
+Copyright (C) 1987, 1988, 1989, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+ 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
Copying and redistribution of this file with or without modification
are permitted without royalty provided this notice is preserved.