Changeset 3207 for trunk/etc/PROBLEMS

Timestamp:

2003年12月28日 22時47分28秒 (5 years ago)

Author:

miyoshi

Message:

Sync up with Emacs-21.2.

Files:

• trunk/etc/PROBLEMS (modified) (34 diffs)

trunk/etc/PROBLEMS

@@ -20 +20 @@
-run the script like this:
-
-"
+'
-
-(replace the ellipsis "..." with any additional arguments you pass to
@@ -27 +27 @@
-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 start by trying again to link temacs.
-
-* Building the MS-Windows port with Cygwin GCC can fail.
@@ -41 +58 @@
-The error message might be something like this:
-
-1
+2
- Invalid ENCODE: value in TIT dictionary
- NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
@@ -201 +218 @@
-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.
-
@@ -206 +234 @@
-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.
@@ -245 +301 @@
-`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.
+
-* Problems in Emacs built with LessTif.
-
@@ -263 +342 @@
-developers.
-
-1
-
-1
+2
+
+2
-and tooltips.  Support for these will be added in future versions.
-
-Help text that is displayed in a tooltip on other window systems, on
-Windows is printed in the echo area, since tooltips are not yet
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-Emacs can sometimes abort when non-ASCII text, possibly with null
@@ -296 +372 @@
-Manager driven switch of the focus, until a key is pressed.
-
-2000 input methods are not recognized by Emacs (as of v21.1).
-
-
+input methods are not recognized by Emacs (as of v21.2).  Some
+
+in 
-characters, ISO 8859-8 for Hebrew characters, etc.).  To make this
-work, set the keyboard coding system to the appropriate value after
@@ -307 +383 @@
-yet.)
-
-2000 clipboard by
-1
-2000 uses Unicode to represent multilingual text,
-but 
+clipboard by other
+2
+uses Unicode to represent multilingual text, but
+
-means that Emacs can only interchange non-ASCII text with other
-2000 
+
-Reportedly, a partial solution is to install the Mule-UCS package and
-set selection-coding-system to utf-16-le-dos.
+
+The %h format specifier for format-time-string does not work on Windows.
+The %b format specifier 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.
@@ -373 +454 @@
-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.  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 _.
-
@@ -396 +488 @@
-src/s/hpux10.h.
-
-uncompressed GIFs
+GIF images in Emacs built
-libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
-
@@ -421 +513 @@
-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 examlpe, 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.
+
+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.
-
@@ -428 +544 @@
-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.
@@ -440 +573 @@
-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
-directory.  To
-force ange-ftp use the stock Windows client, set the variabl
-
-
+or 'C:\WINNT'
+directory.  To force ange-ftp use the stock Windows client, set th
+
+client's 
-
- (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
@@ -453 +586 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
-
-* On AIX, if linking fails because libXbsd isn't found, check if you
@@ -490 +595 @@
-Emacs so that it isn't compiled with `-O5'.
-
-
+
+
+
+
+
+
+
+
-`before-change-function' and `after-change-function', which are no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-
-* The Calc package fails to build and signals errors with Emacs 21.
@@ -663 +668 @@
-   (save-excursion
-
+Index: Makefile
---- Makefile.~1~        Sun Dec 15 23:50:45 1996
-+++ Makefile    Thu Nov 30 15:09:45 2000
@@ -687 +693 @@
- tags: TAGS
-
+Index: calc-aent.el
---- calc-aent.el.~1~    Sun Dec 15 23:50:36 1996
-+++ calc-aent.el        Tue Nov 21 18:34:33 2000
@@ -732 +739 @@
- )
- 
+Index: calc.el
---- calc.el.~1~ Sun Dec 15 23:50:47 1996
-+++ calc.el     Wed Nov 22 13:08:49 2000
@@ -860 +868 @@
-* Unicode characters are not unified with other Mule charsets.
-
-1
+2
-characters which belong to charsets such as Latin-2, Greek, Hebrew,
-etc. and the same characters in the `mule-unicode-*' charsets are
@@ -872 +880 @@
-To work around this, install some add-on package such as Mule-UCS.
-
+* Problems when using Emacs with UTF-8 locales
+
+Some systems, including recent versions of GNU/Linux, have terminals
+or X11 subsystems that can be configured to provide Unicode/UTF-8
+input and display.  Normally, such a system sets environment variables
+such as LANG, LC_CTYPE, or LC_ALL to a string which ends with a
+`.UTF-8'.  For example, a system like this in a French locale might
+use `fr_FR.UTF-8' as the value of LANG.
+
+Since Unicode support in Emacs, as of v21.2, is not yet complete (see
+the previous entry in this file), UTF-8 support is not enabled by
+default, even in UTF-8 locales.  Thus, some Emacs features, such as
+non-ASCII keyboard input, might appear to be broken in these locales.
+To solve these problems, you need to turn on some options in your
+`.emacs' file.  Specifically, the following customizations should make
+Emacs work correctly with UTF-8 input and text:
+
+    (setq locale-coding-system 'utf-8)
+    (set-terminal-coding-system 'utf-8)
+    (set-keyboard-coding-system 'utf-8)
+    (set-selection-coding-system 'utf-8)
+    (prefer-coding-system 'utf-8)
+
-* The `oc-unicode' package doesn't work with Emacs 21.
-
@@ -880 +911 @@
-correctly by Emacs 21.
-
+* 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.
+
-* Using epop3.el package causes Emacs to signal an error.
-
@@ -890 +929 @@
-for epop3 that fixes this, but perhaps a newer version of epop3
-corrects that.
+
+* The arrow indicating the current execution line in GUD is invisible.
+
+This was reported to happen when Emacs 21 is run on an xterm, and the
+python-mode package was loaded.  It appears that python-mode is
+incompatible with Emacs 21; newer versions of python-mode are likely
+to fix that.
-
-* On systems with shared libraries you might encounter run-time errors
@@ -897 +943 @@
-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
@@ -904 +953 @@
-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 could 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.
@@ -973 +1042 @@
-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 classpath.
+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.
-
@@ -986 +1081 @@
-and then choose /usr/bin/netkit-ftp.
-
+* Emacs built on Windows 9x/ME crashes at startup on Windows XP,
+or Emacs built on XP crashes at startup on Windows 9x/ME.
+
+There appear to be general problems running programs compiled on
+Windows 9x/ME on Windows XP and vice-versa, at least when compilation
+is done with MSVC 6.0.  This affects other programs as well as Emacs.
+The compatibility options in the program properties on Windows XP may
+help in some cases.
+
-* Antivirus software interacts badly with the MS-Windows version of Emacs.
-
@@ -1003 +1107 @@
-cleanly before exiting Emacs. For more details, see the FAQ at
-ftp://ftp.gnu.org/gnu/windows/emacs/doc/index.html
+
+* 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.
-
-* Mail sent through Microsoft Exchange in some encodings appears to be
@@ -1255 +1367 @@
-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.
@@ -1413 +1530 @@
-distinguish AltGr from an explicit Right-Alt and Left-Ctrl
-combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
-
+
+
-
-* Under some Windows X-servers, Emacs' display is incorrect 
@@ -1422 +1540 @@
-to be completely redisplayed and the "extra" characters will disappear.
-
-
-
+
+
+
-
-There are reports that you can solve the problem with Exceed by
@@ -1465 +1584 @@
-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.
@@ -1708 +1834 @@
-      else {
-
-* Problems running DOS programs on Windows NT versions earlier than 3.51.
-
-Some DOS programs, such as pkzip/pkunzip will not work at all, while
-others will only work if their stdin is redirected from a file or NUL.
-
-When a DOS program does not work, a new process is actually created, but
-hangs.  It cannot be interrupted from Emacs, and might need to be killed
-by an external program if Emacs is hung waiting for the process to
-finish.  If Emacs is not waiting for it, you should be able to kill the
-instance of ntvdm that is running the hung process from Emacs, if you
-can find out the process id.
-
-It is safe to run most DOS programs using call-process (eg. M-! and
-M-|) since stdin is then redirected from a file, but not with
-start-process since that redirects stdin to a pipe.  Also, running DOS
-programs in a shell buffer prompt without redirecting stdin does not
-work.
-
-* Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs:
-
@@ -1802 +1910 @@
-You can enter M-f6 by typing ESC f6.
-
- 95
+
-
-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
-
+
+
+
-
-* `tparam' reported as a multiply-defined symbol when linking with ncurses.