Mercurial > emacs
annotate etc/PROBLEMS @ 42759:eb0beb585d7c
Updates for current state of Windows port.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Mon, 14 Jan 2002 21:07:59 +0000 |
parents | 0a6f6545e08f |
children | 3ff0fcbfdfa9 |
rev | line source |
---|---|
25853 | 1 This file describes various problems that have been encountered |
2 in compiling, installing and running GNU Emacs. | |
3 | |
39467 | 4 * Building Emacs with GCC 2.9x fails in the `src' directory. |
5 | |
6 This may happen if you use a development version of GNU `cpp' from one | |
7 of the GCC snapshots between Oct 2000 and Feb 2001, or from a released | |
8 version of GCC newer than 2.95.2 which was prepared around those | |
39526
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
9 dates; similar problems were reported with some snapshots of GCC 3.1 |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
10 around Sep 30 2001. The preprocessor in those versions is |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
11 incompatible with a traditional Unix cpp (e.g., it expands ".." into |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
12 ". .", which breaks relative file names that reference the parent |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
13 directory; or inserts TAB characters before lines that set Make |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
14 variables). |
39467 | 15 |
16 The solution is to make sure the preprocessor is run with the | |
39526
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
17 `-traditional' option. The `configure' script does that automatically |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
18 when it detects the known problems in your cpp, but you might hit some |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
19 unknown ones. To force the `configure' script to use `-traditional', |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
20 run the script like this: |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
21 |
40197
3ce5ada6fda1
Fix a typo in the value of CPP.
Eli Zaretskii <eliz@gnu.org>
parents:
40048
diff
changeset
|
22 CPP='gcc -E -traditional' ./configure ... |
39526
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
23 |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
24 (replace the ellipsis "..." with any additional arguments you pass to |
8c40e04af510
Mention the broken cpp from GCC snapshots around Sep 30, 2001, and show the
Eli Zaretskii <eliz@gnu.org>
parents:
39467
diff
changeset
|
25 the script). |
39467 | 26 |
27 Note that this problem does not pertain to the MS-Windows port of | |
28 Emacs, since it doesn't use the preprocessor to generate Makefiles. | |
29 | |
35871
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
30 * Building the MS-Windows port with Cygwin GCC can fail. |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
31 |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
32 Emacs may not build using recent Cygwin builds of GCC, such as Cygwin |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
33 version 1.1.8, using the default configure settings. It appears to be |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
34 necessary to specify the -mwin32 flag when compiling, and define |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
35 __MSVCRT__, like so: |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
36 |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
37 configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__ |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
38 |
1dd3524845ae
Add note about need to specify extra compiler flags
Andrew Innes <andrewi@gnu.org>
parents:
35729
diff
changeset
|
39 * Building the MS-Windows port with Leim fails in the `leim' directory. |
35499
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
40 |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
41 The error message might be something like this: |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
42 |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
43 Converting d:/emacs-21.3/leim/CXTERM-DIC/4Corner.tit to quail-package... |
35499
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
44 Invalid ENCODE: value in TIT dictionary |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
45 NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
46 '0xffffffff' |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
47 Stop. |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
48 |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
49 This can happen if the Leim distribution is unpacked with a program |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
50 which converts the `*.tit' files to DOS-style CR-LF text format. The |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
51 `*.tit' files in the leim/CXTERM-DIC directory require Unix-style line |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
52 endings to compile properly, because Emacs reads them without any code |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
53 or EOL conversions. |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
54 |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
55 The solution is to make sure the program used to unpack Leim does not |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
56 change the files' line endings behind your back. The GNU FTP site has |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
57 in the `/gnu/emacs/windows' directory a program called `djtarnt.exe' |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
58 which can be used to unpack `.tar.gz' and `.zip' archives without |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
59 mangling them. |
1f86a3c25e8d
Document problems (with WinZip) whereby *.tit files get converted
Eli Zaretskii <eliz@gnu.org>
parents:
35249
diff
changeset
|
60 |
40008
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
61 * Emacs crashes when dumping itself on Mac PPC running Yellow Dog GNU/Linux. |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
62 |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
63 The crashes happen inside the function Fmake_symbol; here's a typical |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
64 C backtrace printed by GDB: |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
65 |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
66 0x190c0c0 in Fmake_symbol () |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
67 (gdb) where |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
68 #0 0x190c0c0 in Fmake_symbol () |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
69 #1 0x1942ca4 in init_obarray () |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
70 #2 0x18b3500 in main () |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
71 #3 0x114371c in __libc_start_main (argc=5, argv=0x7ffff5b4, envp=0x7ffff5cc, |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
72 |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
73 This could happen because GCC version 2.95 and later changed the base |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
74 of the load address to 0x10000000. Emacs needs to be told about this, |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
75 but we currently cannot do that automatically, because that breaks |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
76 other versions of GNU/Linux on the MacPPC. Until we find a way to |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
77 distinguish between the Yellow Dog and the other varieties of |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
78 GNU/Linux systems on the PPC, you will have to manually uncomment the |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
79 following section near the end of the file src/m/macppc.h in the Emacs |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
80 distribution: |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
81 |
42167
7d43b2a3529d
Update location of Windows Emacs FAQ.
Richard M. Stallman <rms@gnu.org>
parents:
41893
diff
changeset
|
82 #if 0 /* This breaks things on PPC GNU/Linux except for Yellowdog, |
40008
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
83 even with identical GCC, as, ld. Let's take it out until we |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
84 know what's really going on here. */ |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
85 /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
86 0x10000000. */ |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
87 #if defined __linux__ |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
88 #if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95) |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
89 #define DATA_SEG_BITS 0x10000000 |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
90 #endif |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
91 #endif |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
92 #endif /* 0 */ |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
93 |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
94 Remove the "#if 0" and "#endif" directives which surround this, save |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
95 the file, and then reconfigure and rebuild Emacs. The dumping process |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
96 should now succeed. |
4aaeaa3a8e3b
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide
Eli Zaretskii <eliz@gnu.org>
parents:
39526
diff
changeset
|
97 |
36813 | 98 * JPEG images aren't displayed. |
99 | |
100 This has been reported when Emacs is built with jpeg-6a library. | |
101 Upgrading to jpeg-6b solves the problem. | |
102 | |
35729
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
103 * Building `ctags' for MS-Windows with the MinGW port of GCC fails. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
104 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
105 This might happen due to a bug in the MinGW header assert.h, which |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
106 defines the `assert' macro with a trailing semi-colon. The following |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
107 patch to assert.h should solve this: |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
108 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
109 *** include/assert.h.orig Sun Nov 7 02:41:36 1999 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
110 --- include/assert.h Mon Jan 29 11:49:10 2001 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
111 *************** |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
112 *** 41,47 **** |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
113 /* |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
114 * If not debugging, assert does nothing. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
115 */ |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
116 ! #define assert(x) ((void)0); |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
117 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
118 #else /* debugging enabled */ |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
119 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
120 --- 41,47 ---- |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
121 /* |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
122 * If not debugging, assert does nothing. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
123 */ |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
124 ! #define assert(x) ((void)0) |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
125 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
126 #else /* debugging enabled */ |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
127 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
128 |
39231
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
129 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
130 * Improving performance with slow X connections |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
131 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
132 If you don't need X Input Methods (XIM) for entering text in some |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
133 language you use, you can improve performance on WAN links by |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
134 configuring Emacs with option `--without-xim'. Configuring Emacs |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
135 without XIM does not affect the use of Emacs' own input methods, which |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
136 are part of the Leim package. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
137 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
138 If the connection is very slow, you might also want to consider |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
139 switching off scroll bars, menu bar, and tool bar. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
140 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
141 * Getting a Meta key on the FreeBSD console |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
142 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
143 By default, neither Alt nor any other key acts as a Meta key on |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
144 FreeBSD, but this can be changed using kbdcontrol(1). Dump the |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
145 current keymap to a file with the command |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
146 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
147 $ kbdcontrol -d >emacs.kbd |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
148 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
149 Edit emacs.kbd, and give the key you want to be the Meta key the |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
150 definition `meta'. For instance, if your keyboard has a ``Windows'' |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
151 key with scan code 105, change the line for scan code 105 in emacs.kbd |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
152 to look like this |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
153 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
154 105 meta meta meta meta meta meta meta meta O |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
155 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
156 to make the Windows key the Meta key. Load the new keymap with |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
157 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
158 $ kbdcontrol -l emacs.kbd |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
159 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
160 * Emacs' xterm-mouse-mode doesn't work on the Gnome terminal. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
161 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
162 A symptom of this bug is that double-clicks insert a control sequence |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
163 into the buffer. The reason this happens is an apparent |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
164 incompatibility of the Gnome terminal with Xterm, which also affects |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
165 other programs using the Xterm mouse interface. A problem report has |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
166 been filed. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
167 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
168 * Emacs pauses for several seconds when changing the default font |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
169 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
170 This has been reported for fvwm 2.2.5 and the window manager of KDE |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
171 2.1. The reason for the pause is Xt waiting for a ConfigureNotify |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
172 event from the window manager, which the window manager doesn't send. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
173 Xt stops waiting after a default timeout of usually 5 seconds. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
174 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
175 A workaround for this is to add something like |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
176 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
177 emacs.waitForWM: false |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
178 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
179 to your X resources. Alternatively, add `(wait-for-wm . nil)' to a |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
180 frame's parameter list, like this: |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
181 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
182 (modify-frame-parameters nil '((wait-for-wm . nil))) |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
183 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
184 (this should go into your `.emacs' file). |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
185 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
186 * Underlines appear at the wrong position. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
187 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
188 This is caused by fonts having a wrong UNDERLINE_POSITION property. |
40048
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
189 Examples are the font 7x13 on XFree prior to version 4.1, or the jmk |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
190 neep font from the Debian xfonts-jmk package. To circumvent this |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
191 problem, set x-use-underline-position-properties to nil in your |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
192 `.emacs'. |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
193 |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
194 To see what is the value of UNDERLINE_POSITION defined by the font, |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
195 type `xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION |
4b1fac13860a
More info about wrong UNDERLINE_POSITION in some fonts.
Eli Zaretskii <eliz@gnu.org>
parents:
40008
diff
changeset
|
196 property. |
39231
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
197 |
34922 | 198 * When using Xaw3d scroll bars without arrows, the very first mouse |
199 click in a scroll bar might be ignored by the scroll bar widget. This | |
200 is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the | |
201 problem disappears. | |
202 | |
40872
83db614759e5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
40618
diff
changeset
|
203 * There are known binary incompatibilities between Xaw, Xaw3d, neXtaw, |
83db614759e5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
40618
diff
changeset
|
204 XawM and the few other derivatives of Xaw. So when you compile with |
83db614759e5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
40618
diff
changeset
|
205 one of these, it may not work to dynamically link with another one. |
41892
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
206 For example, strange problems, such as Emacs exiting when you type |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
207 "C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
208 used with neXtaw at run time. |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
209 |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
210 The solution is to rebuild Emacs with the toolkit version you actually |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
211 want to use, or set LD_PRELOAD to preload the same toolkit version you |
c02c7078fc42
Add the LD_PRELOAD work-around for the Xaw/neXtaw incompatibilities.
Eli Zaretskii <eliz@gnu.org>
parents:
41836
diff
changeset
|
212 built Emacs with. |
40872
83db614759e5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
40618
diff
changeset
|
213 |
35572
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
214 * Clicking C-mouse-2 in the scroll bar doesn't split the window. |
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
215 |
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
216 This currently doesn't work with scroll-bar widgets (and we don't know |
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
217 a good way of implementing it with widgets). If Emacs is configured |
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
218 --without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work. |
1732a712675f
Document that clicking C-mouse-2 on widget scroll bars might not work.
Eli Zaretskii <eliz@gnu.org>
parents:
35499
diff
changeset
|
219 |
42521
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
220 * Emacs aborts inside the function `tparam1'. |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
221 |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
222 This can happen if Emacs was built without terminfo support, but the |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
223 terminal's capabilities use format that is only supported by terminfo. |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
224 If your system has ncurses installed, this might happen if your |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
225 version of ncurses is broken; upgrading to a newer version of ncurses |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
226 and reconfiguring and rebuilding Emacs should solve this. |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
227 |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
228 All modern systems support terminfo, so even if ncurses is not the |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
229 problem, you should look for a way to configure Emacs so that it uses |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
230 terminfo when built. |
72a5aec83cab
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
Eli Zaretskii <eliz@gnu.org>
parents:
42233
diff
changeset
|
231 |
36221
a1ee57f6f276
Document possible reasons for lack of colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
36112
diff
changeset
|
232 * Colors are not available on a tty or in xterm. |
a1ee57f6f276
Document possible reasons for lack of colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
36112
diff
changeset
|
233 |
36813 | 234 Emacs 21 supports colors on character terminals and terminal |
235 emulators, but this support relies on the terminfo or termcap database | |
236 entry to specify that the display supports color. Emacs looks at the | |
237 "Co" capability for the terminal to find out how many colors are | |
238 supported; it should be non-zero to activate the color support within | |
38054
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
239 Emacs. (Most color terminals support 8 or 16 colors.) If your system |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
240 uses terminfo, the name of the capability equivalent to "Co" is |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
241 "colors". |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
242 |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
243 In addition to the "Co" capability, Emacs needs the "op" (for |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
244 ``original pair'') capability, which tells how to switch the terminal |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
245 back to the default foreground and background colors. Emacs will not |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
246 use colors if this capability is not defined. If your terminal entry |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
247 doesn't provide such a capability, try using the ANSI standard escape |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
248 sequence \E[00m (that is, define a new termcap/terminfo entry and make |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
249 it use your current terminal's entry plus \E[00m for the "op" |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
250 capability). |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
251 |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
252 Finally, the "NC" capability (terminfo name: "ncv") tells Emacs which |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
253 attributes cannot be used with colors. Setting this capability |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
254 incorrectly might have the effect of disabling colors; try setting |
fee34716d07c
More info about fixing problems with colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
38026
diff
changeset
|
255 this capability to `0' (zero) and see if that helps. |
36813 | 256 |
257 Emacs uses the database entry for the terminal whose name is the value | |
258 of the environment variable TERM. With `xterm', a common terminal | |
36221
a1ee57f6f276
Document possible reasons for lack of colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
36112
diff
changeset
|
259 entry that supports color is `xterm-color', so setting TERM's value to |
36813 | 260 `xterm-color' might activate the color support on an xterm-compatible |
261 emulator. | |
262 | |
42748
0a6f6545e08f
Suggest to use --color if the terminal capabilities lie.
Eli Zaretskii <eliz@gnu.org>
parents:
42667
diff
changeset
|
263 Beginning with version 21.3, Emacs supports the --color command-line |
0a6f6545e08f
Suggest to use --color if the terminal capabilities lie.
Eli Zaretskii <eliz@gnu.org>
parents:
42667
diff
changeset
|
264 option which may be used to force Emacs to use one of a few popular |
0a6f6545e08f
Suggest to use --color if the terminal capabilities lie.
Eli Zaretskii <eliz@gnu.org>
parents:
42667
diff
changeset
|
265 modes for getting colors on a tty. For example, --color=ansi8 sets up |
0a6f6545e08f
Suggest to use --color if the terminal capabilities lie.
Eli Zaretskii <eliz@gnu.org>
parents:
42667
diff
changeset
|
266 for using the ANSI-standard escape sequences that support 8 colors. |
0a6f6545e08f
Suggest to use --color if the terminal capabilities lie.
Eli Zaretskii <eliz@gnu.org>
parents:
42667
diff
changeset
|
267 |
36813 | 268 Some modes do not use colors unless you turn on the Font-lock mode. |
269 Some people have long ago set their `~/.emacs' files to turn on | |
270 Font-lock on X only, so they won't see colors on a tty. The | |
271 recommended way of turning on Font-lock is by typing "M-x | |
37510
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
272 global-font-lock-mode RET" or by customizing the variable |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
273 `global-font-lock-mode'. |
36221
a1ee57f6f276
Document possible reasons for lack of colors on a tty.
Eli Zaretskii <eliz@gnu.org>
parents:
36112
diff
changeset
|
274 |
41207
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
275 * Emacs on a tty switches the cursor to large blinking block. |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
276 |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
277 This was reported to happen on some GNU/Linux systems which use |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
278 ncurses version 5.0, but could be relevant for other versions as well. |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
279 These versions of ncurses come with a `linux' terminfo entry, where |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
280 the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c" |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
281 (show cursor, change size). This escape sequence switches on a |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
282 blinking hardware text-mode cursor whose size is a full character |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
283 cell. This blinking cannot be stopped, since a hardware cursor |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
284 always blinks. |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
285 |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
286 A work-around is to redefine the "cvvis" capability so that it |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
287 enables a *software* cursor. The software cursor works by inverting |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
288 the colors of the character at point, so what you see is a block |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
289 cursor that doesn't blink. For this to work, you need to redefine |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
290 the "cnorm" capability as well, so that it operates on the software |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
291 cursor instead of the hardware cursor. |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
292 |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
293 To this end, run "infocmp linux > linux-term", edit the file |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
294 `linux-term' to make both the "cnorm" and "cvvis" capabilities send |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
295 the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
296 produce a modified terminfo entry. |
47026545f14a
A work-around for blinking block cursor on a GNU/Linux console.
Eli Zaretskii <eliz@gnu.org>
parents:
41190
diff
changeset
|
297 |
41247
78069920ddec
How to get a blinking underscore cursor inside Emacs.
Eli Zaretskii <eliz@gnu.org>
parents:
41207
diff
changeset
|
298 Alternatively, if you want a blinking underscore as your Emacs cursor, |
78069920ddec
How to get a blinking underscore cursor inside Emacs.
Eli Zaretskii <eliz@gnu.org>
parents:
41207
diff
changeset
|
299 change the "cvvis" capability to send the "\E[?25h\E[?0c" command. |
78069920ddec
How to get a blinking underscore cursor inside Emacs.
Eli Zaretskii <eliz@gnu.org>
parents:
41207
diff
changeset
|
300 |
35646
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
301 * Problems in Emacs built with LessTif. |
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
302 |
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
303 The problems seem to depend on the version of LessTif and the Motif |
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
304 emulation for which it is set up. |
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
305 |
36813 | 306 Only the Motif 1.2 emulation seems to be stable enough in LessTif. |
307 Lesstif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD. | |
308 On GNU/Linux systems, lesstif-0.92.6 configured with "./configure | |
309 --enable-build-12 --enable-default-12" is reported to be the most | |
310 successful. The binary GNU/Linux package | |
311 lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with | |
312 menu placement. | |
35646
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
313 |
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
314 On some systems, even with Motif 1.2 emulation, Emacs occasionally |
36813 | 315 locks up, grabbing all mouse and keyboard events. We still don't know |
316 what causes these problems; they are not reproducible by Emacs | |
317 developers. | |
35646
a3e5066d2077
Document problems with LessTif.
Eli Zaretskii <eliz@gnu.org>
parents:
35645
diff
changeset
|
318 |
35729
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
319 * Known problems with the MS-Windows port of Emacs 21.1. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
320 |
41481
38b7d09859ec
Remove notes about tooltips not working on Windows.
Jason Rumney <jasonr@gnu.org>
parents:
41365
diff
changeset
|
321 Emacs 21.1 built for MS-Windows doesn't support images and the tool bar. |
38b7d09859ec
Remove notes about tooltips not working on Windows.
Jason Rumney <jasonr@gnu.org>
parents:
41365
diff
changeset
|
322 Support for these will be added in future versions. |
38b7d09859ec
Remove notes about tooltips not working on Windows.
Jason Rumney <jasonr@gnu.org>
parents:
41365
diff
changeset
|
323 |
41613
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
324 Frames are not refreshed while the File or Font dialog or a pop-up menu |
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
325 is displayed. This also means help text for pop-up menu items is not |
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
326 displayed at all. This is because message handling under Windows is |
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
327 synchronous, so we cannot handle repaint (or any other) messages while |
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
328 waiting for a system function to return the result of the dialog or |
6bc4823a332a
Added note about display refresh while dialogs and pop-up menus are
Jason Rumney <jasonr@gnu.org>
parents:
41481
diff
changeset
|
329 pop-up menu interaction. |
41180
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
330 |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
331 There are problems with display if mouse-tracking is enabled and the |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
332 mouse is moved off a frame, over another frame then back over the first |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
333 frame. A workaround is to click the left mouse button inside the frame |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
334 after moving back into it. |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
335 |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
336 Some minor flickering still persists during mouse-tracking, although |
cd7095561d3e
Updated MS-Windows problems.
Jason Rumney <jasonr@gnu.org>
parents:
40872
diff
changeset
|
337 not as severely as in 21.1. |
35729
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
338 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
339 Emacs can sometimes abort when non-ASCII text, possibly with null |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
340 characters, is copied and pasted into a buffer. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
341 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
342 An inactive cursor remains in an active window after the Windows |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
343 Manager driven switch of the focus, until a key is pressed. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
344 |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
345 Windows input methods are not recognized by Emacs (as of v21.1). Some |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
346 of these input methods cause the keyboard to send characters encoded |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
347 in the appropriate coding system (e.g., ISO 8859-1 for Latin-1 |
37510
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
348 characters, ISO 8859-8 for Hebrew characters, etc.). To make this |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
349 work, set the keyboard coding system to the appropriate value after |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
350 you activate the Windows input method. For example, if you activate |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
351 the Hebrew input method, type "C-x RET k iso-8859-8 RET". (Emacs |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
352 ought to recognize the Windows language-change event and set up the |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
353 appropriate keyboard encoding automatically, but it doesn't do that |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
354 yet.) |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
355 |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
356 Multilingual text put into the Windows clipboard by other Windows |
37510
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
357 applications cannot be safely pasted into Emacs (as of v21.1). This |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
358 is because Windows uses Unicode to represent multilingual text, but |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
359 Emacs does not yet support Unicode well enough to decode it. This |
37510
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
360 means that Emacs can only interchange non-ASCII text with other |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
361 Windows programs if the characters are in the system codepage. |
37510
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
362 Reportedly, a partial solution is to install the Mule-UCS package and |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
363 set selection-coding-system to utf-16-le-dos. |
29ba8757d4dc
Document problems with NTEmacs on Windows 2000, related to the
Eli Zaretskii <eliz@gnu.org>
parents:
37480
diff
changeset
|
364 |
36004
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
365 * The `configure' script doesn't find the jpeg library. |
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
366 |
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
367 This can happen because the linker by default only looks for shared |
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
368 libraries, but jpeg distribution by default doesn't build and doesn't |
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
369 install a shared version of the library, `libjpeg.so'. One system |
36550 | 370 where this is known to happen is Compaq OSF/1 (`Tru64'), but it |
371 probably isn't limited to that system. | |
36004
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
372 |
36813 | 373 You can configure the jpeg library with the `--enable-shared' option |
374 and then rebuild libjpeg. This produces a shared version of libjpeg, | |
375 which you need to install. Finally, rerun the Emacs configure script, | |
376 which should now find the jpeg library. Alternatively, modify the | |
377 generated src/Makefile to link the .a file explicitly. | |
378 | |
379 (If you need the static version of the jpeg library as well, configure | |
380 libjpeg with both `--enable-static' and `--enable-shared' options.) | |
36004
a77b9157dd49
Document problems with libjpeg unavailable as a shared library.
Eli Zaretskii <eliz@gnu.org>
parents:
35907
diff
changeset
|
381 |
36450
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
382 * Building Emacs over NFS fails with ``Text file busy''. |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
383 |
36970
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
384 This was reported to happen when building Emacs on a GNU/Linux system |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
385 (RedHat Linux 6.2) using a build directory automounted from Solaris |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
386 (SunOS 5.6) file server, but it might not be limited to that |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
387 configuration alone. Presumably, the NFS server doesn't commit the |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
388 files' data to disk quickly enough, and the Emacs executable file is |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
389 left ``busy'' for several seconds after Emacs has finished dumping |
9477128b4fad
Say "RedHat Linux" instead of "RedHat GNU/Linux".
Eli Zaretskii <eliz@gnu.org>
parents:
36969
diff
changeset
|
390 itself. This causes the subsequent commands which invoke the dumped |
42167
7d43b2a3529d
Update location of Windows Emacs FAQ.
Richard M. Stallman <rms@gnu.org>
parents:
41893
diff
changeset
|
391 Emacs executable to fail with the above message. |
36450
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
392 |
36451 | 393 In some of these cases, a time skew between the NFS server and the |
394 machine where Emacs is built is detected and reported by GNU Make | |
395 (it says that some of the files have modification time in the future). | |
396 This might be a symptom of NFS-related problems. | |
397 | |
36450
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
398 If the NFS server runs on Solaris, apply the Solaris patch 105379-05 |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
399 (Sunos 5.6: /kernel/misc/nfssrv patch). If that doesn't work, or if |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
400 you have a different version of the OS or the NFS server, you can |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
401 force the NFS server to use 1KB blocks, which was reported to fix the |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
402 problem albeit at a price of slowing down file I/O. You can force 1KB |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
403 blocks by specifying the "-o rsize=1024,wsize=1024" options to the |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
404 `mount' command, or by adding ",rsize=1024,wsize=1024" to the mount |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
405 options in the appropriate system configuration file, such as |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
406 `/etc/auto.home'. |
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
407 |
36969
e6c28065a5f9
Minor wording changes in description of the Solaris NFS problems
Eli Zaretskii <eliz@gnu.org>
parents:
36813
diff
changeset
|
408 Alternatively, when Make fails due to this problem, you could wait for |
e6c28065a5f9
Minor wording changes in description of the Solaris NFS problems
Eli Zaretskii <eliz@gnu.org>
parents:
36813
diff
changeset
|
409 a few seconds and then invoke Make again. In one particular case, |
e6c28065a5f9
Minor wording changes in description of the Solaris NFS problems
Eli Zaretskii <eliz@gnu.org>
parents:
36813
diff
changeset
|
410 waiting for 10 or more seconds between the two Make invocations seemed |
e6c28065a5f9
Minor wording changes in description of the Solaris NFS problems
Eli Zaretskii <eliz@gnu.org>
parents:
36813
diff
changeset
|
411 to work around the problem. |
36450
a5ae1f49b2ee
Document the problems with "Text file busy" due to buggy NFS servers.
Eli Zaretskii <eliz@gnu.org>
parents:
36222
diff
changeset
|
412 |
38410
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
413 Similar problems can happen if your machine NFS-mounts a directory |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
414 onto itself. Suppose the Emacs sources live in `/usr/local/src' and |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
415 you are working on the host called `marvin'. Then an entry in the |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
416 `/etc/fstab' file like the following is asking for trouble: |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
417 |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
418 marvin:/usr/local/src /usr/local/src ...options.omitted... |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
419 |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
420 The solution is to remove this line from `etc/fstab'. |
8d7f5ed7deaa
Mounting a volume onto itself might also produce "text file busy".
Eli Zaretskii <eliz@gnu.org>
parents:
38279
diff
changeset
|
421 |
40618
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
422 * Emacs binary is not in executable format, and cannot be run. |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
423 |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
424 This was reported to happen when Emacs is built in a directory mounted |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
425 via NFS. Usually, the file `emacs' produced in these cases is full of |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
426 binary null characters, and the `file' utility says: |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
427 |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
428 emacs: ASCII text, with no line terminators |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
429 |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
430 We don't know what exactly causes this failure. A work-around is to |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
431 build Emacs in a directory on a local disk. |
04c9ddfb2b2a
Document problems with dumping on an NFS-mounted filesystem.
Eli Zaretskii <eliz@gnu.org>
parents:
40537
diff
changeset
|
432 |
36813 | 433 * Accented ISO-8859-1 characters are displayed as | or _. |
34721
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
434 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
435 Try other font set sizes (S-mouse-1). If the problem persists with |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
436 other sizes as well, your text is corrupted, probably through software |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
437 that is not 8-bit clean. If the problem goes away with another font |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
438 size, it's probably because some fonts pretend to be ISO-8859-1 fonts |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
439 when they are really ASCII fonts. In particular the schumacher-clean |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
440 fonts have this bug in some versions of X. |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
441 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
442 To see what glyphs are included in a font, use `xfd', like this: |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
443 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
444 xfd -fn -schumacher-clean-medium-r-normal--12-120-75-75-c-60-iso8859-1 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
445 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
446 If this shows only ASCII glyphs, the font is indeed the source of the |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
447 problem. |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
448 |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
449 The solution is to remove the corresponding lines from the appropriate |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
450 `fonts.alias' file, then run `mkfontdir' in that directory, and then run |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
451 `xset fp rehash'. |
4a8980d062ad
Document problems with ISO-8859 fonts which actually include only
Eli Zaretskii <eliz@gnu.org>
parents:
34695
diff
changeset
|
452 |
34695 | 453 * Large file support is disabled on HP-UX. See the comments in |
454 src/s/hpux10.h. | |
455 | |
456 * Crashes when displaying uncompressed GIFs with version | |
457 libungif-4.1.0 are resolved by using version libungif-4.1.0b1. | |
458 | |
39315
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
459 * Font Lock displays portions of the bufefr in incorrect faces. |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
460 |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
461 By far the most frequent cause of this is a parenthesis `(' or a brace |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
462 `{' in column zero. Font Lock assumes that such a paren is outside of |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
463 any comment or string. This is of course not true in general, but the |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
464 vast majority of well-formatted program source files don't have such |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
465 parens, and therefore this assumption is used to allow optimizations |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
466 in Font Lock's syntactical analysis. These optimizations avoid some |
42167
7d43b2a3529d
Update location of Windows Emacs FAQ.
Richard M. Stallman <rms@gnu.org>
parents:
41893
diff
changeset
|
467 pathological cases where jit-lock, the Just-in-Time fontification |
39315
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
468 introduced with Emacs 21.1, could significantly slow down scrolling |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
469 through the buffer, especially scrolling backwards, and also jumping |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
470 to the end of a very large buffer. |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
471 |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
472 If you don't use large buffers, or have a very fast machine which |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
473 makes the delays insignificant, you can avoid the incorrect |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
474 fontification by setting the variable |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
475 `font-lock-beginning-of-syntax-function' to a nil value. (This must |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
476 be done _after_ turning on Font Lock.) |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
477 |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
478 Another alternative is to avoid a paren in column zero. For example, |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
479 in a Lisp string you could precede the paren with a backslash. |
311556cdc15a
Document Font Lock problems with parens in column zero.
Eli Zaretskii <eliz@gnu.org>
parents:
39231
diff
changeset
|
480 |
41893
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
481 * When running on KDE, colors or fonts are not as specified for Emacs, |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
482 or messed up. |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
483 |
42167
7d43b2a3529d
Update location of Windows Emacs FAQ.
Richard M. Stallman <rms@gnu.org>
parents:
41893
diff
changeset
|
484 For example, you could see background you set for Emacs only in the |
41893
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
485 empty portions of the Emacs display, while characters have some other |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
486 background. |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
487 |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
488 This happens because KDE's defaults apply its color and font |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
489 definitions even to applications that weren't compiled for KDE. The |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
490 solution is to uncheck the "Apply fonts and colors to non-KDE apps" |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
491 option in Preferences->Look&Feel->Style. |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
492 |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
493 Alternatively, if you do want the KDE defaults to apply to other |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
494 applications, but not to Emacs, you could modify the file `Emacs.ad' |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
495 (should be in the `/usr/share/apps/kdisplay/app-defaults/' directory) |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
496 so that it doesn't set the default background and foreground only for |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
497 Emacs. For example, make sure the following resources are either not |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
498 present or commented out: |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
499 |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
500 Emacs.default.attributeForeground |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
501 Emacs.default.attributeBackground |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
502 Emacs*Foreground |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
503 Emacs*Background |
79a843a71f03
Add an entry about fonts and colors problems on KDE.
Eli Zaretskii <eliz@gnu.org>
parents:
41892
diff
changeset
|
504 |
35729
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
505 * Interrupting Cygwin port of Bash from Emacs doesn't work. |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
506 |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
507 Cygwin 1.x builds of the ported Bash cannot be interrupted from the |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
508 MS-Windows version of Emacs. This is due to some change in the Bash |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
509 port or in the Cygwin library which apparently make Bash ignore the |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
510 keyboard interrupt event sent by Emacs to Bash. (Older Cygwin ports |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
511 of Bash, up to b20.1, did receive SIGINT from Emacs.) |
bc965ab08080
Document problems with the MS-Windows port of v21.1 and with
Eli Zaretskii <eliz@gnu.org>
parents:
35677
diff
changeset
|
512 |
39231
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
513 * Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
514 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
515 If the FTP client is the Cygwin port of GNU `ftp', this appears to be |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
516 due to some bug in the Cygwin DLL or some incompatibility between it |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
517 and the implementation of asynchronous subprocesses in the Windows |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
518 port of Emacs. Specifically, some parts of the FTP server responses |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
519 are not flushed out, apparently due to buffering issues, which |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
520 confuses ange-ftp. |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
521 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
522 The solution is to downgrade to an older version of the Cygwin DLL |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
523 (version 1.3.2 was reported to solve the problem), or use the stock |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
524 Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT' |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
525 directory. To force ange-ftp use the stock Windows client, set the |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
526 variable `ange-ftp-ftp-program-name' to the absolute file name of the |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
527 client's executable. For example: |
39231
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
528 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
529 (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe") |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
530 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
531 If you want to stick with the Cygwin FTP client, you can work around |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
532 this problem by putting this in your `.emacs' file: |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
533 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
534 (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "") |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
535 |
a3c2d52350d6
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
Eli Zaretskii <eliz@gnu.org>
parents:
39069
diff
changeset
|
536 |
37770
99998083d710
Document that the W3 CVS does work with Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
37633
diff
changeset
|
537 * The latest released version of the W3 package doesn't run properly |
99998083d710
Document that the W3 CVS does work with Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
37633
diff
changeset
|
538 with Emacs 21 and needs work. However, these problems are already |
39069
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
539 fixed in W3's CVS. The patch below is reported to make w3-4.0pre.46 |
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
540 work. |
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
541 |
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
542 Some users report they are unable to byte-compile W3 with Emacs 21. |
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
543 If the patches below don't help to resolve your problems, install the |
a0e12b5f35d1
Tell them to use CVS W3 if the patch doesn't help.
Eli Zaretskii <eliz@gnu.org>
parents:
38926
diff
changeset
|
544 CVS version of W3, which should be compatible with Emacs 21. |
35152 | 545 |
546 diff -aur --new-file w3-4.0pre.46-orig/lisp/w3-display.el w3-4.0pre.46-new/lisp/w3-display.el | |
547 --- w3-4.0pre.46-orig/lisp/w3-display.el Sun Nov 14 22:00:12 1999 | |
548 +++ w3-4.0pre.46-new/lisp/w3-display.el Thu Dec 14 14:59:15 2000 | |
549 @@ -181,7 +181,8 @@ | |
550 (dispatch-event (next-command-event))) | |
551 (error nil)))) | |
552 (t | |
553 - (if (and (not (sit-for 0)) (input-pending-p)) | |
554 + ;; modified for GNU Emacs 21 by bob@rattlesnake.com on 2000 Dec 14 | |
555 + (if (and (not (sit-for 0)) nil) | |
556 (condition-case () | |
557 (progn | |
558 (setq w3-pause-keystroke | |
559 diff -aur --new-file w3-4.0pre.46-orig/lisp/w3-e21.el w3-4.0pre.46-new/lisp/w3-e21.el | |
560 --- w3-4.0pre.46-orig/lisp/w3-e21.el Thu Jan 1 00:00:00 1970 | |
561 +++ w3-4.0pre.46-new/lisp/w3-e21.el Thu Dec 14 14:54:58 2000 | |
562 @@ -0,0 +1,5 @@ | |
563 +;;; w3-e21.el --- ** required for GNU Emacs 21 ** | |
564 +;; Added by bob@rattlesnake.com on 2000 Dec 14 | |
565 + | |
566 +(require 'w3-e19) | |
567 +(provide 'w3-e21) | |
568 | |
34494 | 569 * On AIX, if linking fails because libXbsd isn't found, check if you |
570 are compiling with the system's `cc' and CFLAGS containing `-O5'. If | |
571 so, you have hit a compiler bug. Please make sure to re-configure | |
572 Emacs so that it isn't compiled with `-O5'. | |
573 | |
42228
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
574 * Compiling on AIX 4.3.x or 4.4 fails. |
42229 | 575 |
42233 | 576 This could happen if you use /bin/c89 as your compiler, instead of |
42228
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
577 the default `cc'. /bin/c89 treats certain warnings, such as benign |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
578 redefinitions of macros, as errors, and fails the build. A solution |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
579 is to use the default compiler `cc'. |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
580 |
34387 | 581 * The PSGML package uses the obsolete variables |
582 `before-change-function' and `after-change-function', which are no | |
42667 | 583 longer used by Emacs. Please use PSGML 1.2.3 or later. |
41248
74f8ac2c0480
Re-add section "TeX'ing the Calc manual fails".
Colin Walters <walters@gnu.org>
parents:
41247
diff
changeset
|
584 |
38012
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
585 * Unicode characters are not unified with other Mule charsets. |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
586 |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
587 As of v21.1, Emacs charsets are still not unified. This means that |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
588 characters which belong to charsets such as Latin-2, Greek, Hebrew, |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
589 etc. and the same characters in the `mule-unicode-*' charsets are |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
590 different characters, as far as Emacs is concerned. For example, text |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
591 which includes Unicode characters from the Latin-2 locale cannot be |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
592 encoded by Emacs with ISO 8859-2 coding system; and if you yank Greek |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
593 text from a buffer whose buffer-file-coding-system is greek-iso-8bit |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
594 into a mule-unicode-0100-24ff buffer, Emacs won't be able to save that |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
595 buffer neither as ISO 8859-7 nor as UTF-8. |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
596 |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
597 To work around this, install some add-on package such as Mule-UCS. |
3bf93c45de95
Mention that mule-unicode-* charsets aren't unified with the others.
Eli Zaretskii <eliz@gnu.org>
parents:
37770
diff
changeset
|
598 |
40488
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
599 * Problems when using Emacs with UTF-8 locales |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
600 |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
601 Some systems, including recent versions of GNU/Linux, have terminals |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
602 or X11 subsystems that can be configured to provide Unicode/UTF-8 |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
603 input and display. Normally, such a system sets environment variables |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
604 such as LANG, LC_CTYPE, or LC_ALL to a string which ends with a |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
605 `.UTF-8'. For example, a system like this in a French locale might |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
606 use `fr_FR.UTF-8' as the value of LANG. |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
607 |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
608 Since Unicode support in Emacs, as of v21.1, is not yet complete (see |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
609 the previous entry in this file), UTF-8 support is not enabled by |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
610 default, even in UTF-8 locales. Thus, some Emacs features, such as |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
611 non-ASCII keyboard input, might appear to be broken in these locales. |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
612 To solve these problems, you need to turn on some options in your |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
613 `.emacs' file. Specifically, the following customizations should make |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
614 Emacs work correctly with UTF-8 input and text: |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
615 |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
616 (setq locale-coding-system 'utf-8) |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
617 (set-terminal-coding-system 'utf-8) |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
618 (set-keyboard-coding-system 'utf-8) |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
619 (set-selection-coding-system 'utf-8) |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
620 (prefer-coding-system 'utf-8) |
554167b7ed9e
Describe Emacs setup in UTF-8 locales.
Eli Zaretskii <eliz@gnu.org>
parents:
40197
diff
changeset
|
621 |
36112
1ddf9f48dc2f
Document problems with oc-unicode.
Eli Zaretskii <eliz@gnu.org>
parents:
36004
diff
changeset
|
622 * The `oc-unicode' package doesn't work with Emacs 21. |
1ddf9f48dc2f
Document problems with oc-unicode.
Eli Zaretskii <eliz@gnu.org>
parents:
36004
diff
changeset
|
623 |
36813 | 624 This package tries to define more private charsets than there are free |
625 slots now. If the built-in Unicode/UTF-8 support is insufficient, | |
626 e.g. if you need more CJK coverage, use the current Mule-UCS package. | |
627 Any files encoded as emacs-mule using oc-unicode won't be read | |
628 correctly by Emacs 21. | |
35645
141f70353995
Add two items with solutions for Calc problems.
Eli Zaretskii <eliz@gnu.org>
parents:
35575
diff
changeset
|
629 |
39463
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
630 * Using epop3.el package causes Emacs to signal an error. |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
631 |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
632 The error message might be something like this: |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
633 |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
634 "Lisp nesting exceeds max-lisp-eval-depth" |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
635 |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
636 This happens because epop3 redefines the function gethash, which is a |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
637 built-in primitive beginning with Emacs 21.1. We don't have a patch |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
638 for epop3 that fixes this, but perhaps a newer version of epop3 |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
639 corrects that. |
6381cf3c37bd
Document the problem with epop3's redefinition of gethash.
Eli Zaretskii <eliz@gnu.org>
parents:
39348
diff
changeset
|
640 |
42228
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
641 * ps-print commands fail to find prologue files ps-prin*.ps. |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
642 |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
643 This can happen if you use an old version of X-Symbol package: it |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
644 defines compatibility functions which trick ps-print into thinking it |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
645 runs in XEmacs, and look for the prologue files in a wrong directory. |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
646 |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
647 The solution is to upgrade X-Symbol to a later version. |
b968543600c1
Document problems with AIX's /bin/c89 compiler and with old versions
Eli Zaretskii <eliz@gnu.org>
parents:
42167
diff
changeset
|
648 |
33964 | 649 * On systems with shared libraries you might encounter run-time errors |
650 from the dynamic linker telling you that it is unable to find some | |
651 shared libraries, for instance those for Xaw3d or image support. | |
652 These errors mean Emacs has been linked with a library whose shared | |
653 library is not in the default search path of the dynamic linker. | |
654 | |
40496
32b7ea7d8293
Clarify that problems with shared libraries can also happen during the build.
Eli Zaretskii <eliz@gnu.org>
parents:
40488
diff
changeset
|
655 Similar problems could prevent Emacs from building, since the build |
32b7ea7d8293
Clarify that problems with shared libraries can also happen during the build.
Eli Zaretskii <eliz@gnu.org>
parents:
40488
diff
changeset
|
656 process invokes Emacs several times. |
32b7ea7d8293
Clarify that problems with shared libraries can also happen during the build.
Eli Zaretskii <eliz@gnu.org>
parents:
40488
diff
changeset
|
657 |
33964 | 658 On many systems, it is possible to set LD_LIBRARY_PATH in your |
659 environment to specify additional directories where shared libraries | |
660 can be found. | |
661 | |
662 Other systems allow to set LD_RUN_PATH in a similar way, but before | |
663 Emacs is linked. With LD_RUN_PATH set, the linker will include a | |
664 specified run-time search path in the executable. | |
665 | |
666 Please refer to the documentation of your dynamic linker for details. | |
667 | |
33788 | 668 * On Solaris 2.7, building Emacs with WorkShop Compilers 5.0 98/12/15 |
34001 | 669 C 5.0 failed, apparently with non-default CFLAGS, most probably due to |
670 compiler bugs. Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C | |
671 release was reported to work without problems. It worked OK on | |
672 another system with Solaris 8 using apparently the same 5.0 compiler | |
673 and the default CFLAGS. | |
33788 | 674 |
38061
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
675 * Compiling syntax.c with the OPENSTEP 4.2 compiler gcc 2.7.2.1 fails. |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
676 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
677 The compiler was reported to crash while compiling syntax.c with the |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
678 following message: |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
679 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
680 cc: Internal compiler error: program cc1obj got fatal signal 11 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
681 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
682 To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD, |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
683 INC_BOTH, and INC_FROM with functions. To this end, first define 3 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
684 functions, one each for every macro. Here's an example: |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
685 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
686 static int update_syntax_table_forward(int from) |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
687 { |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
688 return(UPDATE_SYNTAX_TABLE_FORWARD(from)); |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
689 }/*update_syntax_table_forward*/ |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
690 |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
691 Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
692 with a call to the function update_syntax_table_forward. |
bef7906aca9a
Document problems with OPENSTEP's gcc. Provide a work-around.
Eli Zaretskii <eliz@gnu.org>
parents:
38058
diff
changeset
|
693 |
39464
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
694 * Emacs fails to start, complaining about missing fonts. |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
695 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
696 A typical error message might be something like |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
697 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
698 No fonts match `-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1' |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
699 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
700 This happens because some X resource specifies a bad font family for |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
701 Emacs to use. The possible places where this specification might be |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
702 are: |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
703 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
704 - in your ~/.Xdefaults file |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
705 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
706 - client-side X resource file, such as ~/Emacs or |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
707 /usr/X11R6/lib/app-defaults/Emacs or |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
708 /usr/X11R6/lib/X11/app-defaults/Emacs |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
709 |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
710 One of these files might have bad or malformed specification of a |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
711 fontset that Emacs should use. To fix the problem, you need to find |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
712 the problematic line(s) and correct them. |
b1091e5046d0
Document problems with bad specifications of the default fontset.
Eli Zaretskii <eliz@gnu.org>
parents:
39463
diff
changeset
|
713 |
38135
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
714 * Emacs 20 and later fails to load Lisp files at startup. |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
715 |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
716 The typical error message might be like this: |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
717 |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
718 "Cannot open load file: fontset" |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
719 |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
720 This could happen if you compress the file lisp/subdirs.el. That file |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
721 tells Emacs what are the directories where it should look for Lisp |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
722 files. Emacs cannot work with subdirs.el compressed, since the |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
723 Auto-compress mode it needs for this will not be loaded until later, |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
724 when your .emacs file is processed. (The package `fontset.el' is |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
725 required to set up fonts used to display text on window systems, and |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
726 its loaded very early in the startup procedure.) |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
727 |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
728 Similarly, any other .el file for which there's no corresponding .elc |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
729 file could fail to load if it is compressed. |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
730 |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
731 The solution is to uncompress all .el files which don't have a .elc |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
732 file. |
f4830f2d181b
Document problems with compressed subdirs.el.
Eli Zaretskii <eliz@gnu.org>
parents:
38061
diff
changeset
|
733 |
41697
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
734 Another possible reason for such failures is stale *.elc files |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
735 lurking somewhere on your load-path. The following command will |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
736 print any duplicate Lisp files that are present in load-path: |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
737 |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
738 emacs -q -batch -f list-load-path-shadows |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
739 |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
740 If this command prints any file names, some of these files are stale, |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
741 and should be deleted or their directories removed from your |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
742 load-path. |
48f16a4dc7fe
Another reason for failures related to fontset.elc.
Eli Zaretskii <eliz@gnu.org>
parents:
41613
diff
changeset
|
743 |
41793
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
744 * Emacs prints an error at startup after upgrading from an earlier version. |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
745 |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
746 An example of such an error is: |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
747 |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
748 x-complement-fontset-spec: "Wrong type argument: stringp, nil" |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
749 |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
750 This can be another symptom of stale *.elc files in your classpath. |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
751 The following command will print any duplicate Lisp files that are |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
752 present in load-path: |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
753 |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
754 emacs -q -batch -f list-load-path-shadows |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
755 |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
756 If this command prints any file names, some of these files are stale, |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
757 and should be deleted or their directories removed from your |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
758 load-path. |
1adf81b0d0e4
Added stale load-path problems.
Jason Rumney <jasonr@gnu.org>
parents:
41697
diff
changeset
|
759 |
37633
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
760 * Attempting to visit remote files via ange-ftp fails. |
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
761 |
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
762 If the error message is "ange-ftp-file-modtime: Specified time is not |
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
763 representable", then this could happen when `lukemftp' is used as the |
41365
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
764 ftp client. This was reported to happen on Debian GNU/Linux, kernel |
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
765 version 2.4.3, with `lukemftp' 1.5-5, but might happen on other |
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
766 systems as well. To avoid this problem, switch to using the standard |
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
767 ftp client. On a Debian system, type |
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
768 |
0b508d916f80
Remove already applied calc info patches. Clarify that there is no
Colin Walters <walters@gnu.org>
parents:
41319
diff
changeset
|
769 update-alternatives --config ftp |
37633
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
770 |
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
771 and then choose /usr/bin/netkit-ftp. |
fa0afa395c91
Document problems with lukemftp.
Eli Zaretskii <eliz@gnu.org>
parents:
37510
diff
changeset
|
772 |
38919
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
773 * Antivirus software interacts badly with the MS-Windows version of Emacs. |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
774 |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
775 The usual manifestation of these problems is that subprocesses don't |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
776 work or even wedge the entire system. In particular, "M-x shell RET" |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
777 was reported to fail to work. But other commands also sometimes don't |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
778 work when an antivirus package is installed. |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
779 |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
780 The solution is to switch the antivirus software to a less aggressive |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
781 mode (e.g., disable the ``auto-protect'' feature), or even uninstall |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
782 or disable it entirely. |
047a58ae4054
Document the problems with MS-Windows antivirus problems.
Eli Zaretskii <eliz@gnu.org>
parents:
38914
diff
changeset
|
783 |
33614
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
784 * On Windows 95/98/ME, subprocesses do not terminate properly. |
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
785 |
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
786 This is a limitation of the Operating System, and can cause problems |
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
787 when shutting down Windows. Ensure that all subprocesses are exited |
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
788 cleanly before exiting Emacs. For more details, see the FAQ at |
42167
7d43b2a3529d
Update location of Windows Emacs FAQ.
Richard M. Stallman <rms@gnu.org>
parents:
41893
diff
changeset
|
789 http://www.gnu.org/software/emacs/windows/. |
33614
9c067a999061
Added note about subprocesses on Windows 9x.
Jason Rumney <jasonr@gnu.org>
parents:
33455
diff
changeset
|
790 |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
791 * Windows 95/98/ME crashes when trying to run non-existant subprocesses. |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
792 |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
793 When a subprocess you are trying to run is not found on the PATH, |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
794 Windows might respond by crashing or locking up your system. In |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
795 particular, this has been reported when trying to compile a java |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
796 program in JDEE when javac.exe is installed, but not on the system |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
797 path. |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
798 |
33455 | 799 * Mail sent through Microsoft Exchange in some encodings appears to be |
800 mangled and is not seen correctly in Rmail or Gnus. We don't know | |
801 exactly what happens, but it isn't an Emacs problem in cases we've | |
802 seen. | |
803 | |
38580
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
804 * After upgrading to a newer version of Emacs, the Meta key stops working. |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
805 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
806 This was reported to happen on a GNU/Linux system distributed by |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
807 Mandrake. The reason is that the previous version of Emacs was |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
808 modified by Mandrake to make the Alt key act as the Meta key, on a |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
809 keyboard where the Windows key is the one which produces the Meta |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
810 modifier. A user who started using a newer version of Emacs, which |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
811 was not hacked by Mandrake, expected the Alt key to continue to act as |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
812 Meta, and was astonished when that didn't happen. |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
813 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
814 The solution is to find out what key on your keyboard produces the Meta |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
815 modifier, and use that key instead. Try all of the keys to the left |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
816 and to the right of the space bar, together with the `x' key, and see |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
817 which combination produces "M-x" in the echo area. You can also use |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
818 the `xmodmap' utility to show all the keys which produce a Meta |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
819 modifier: |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
820 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
821 xmodmap -pk | egrep -i "meta|alt" |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
822 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
823 A more convenient way of finding out which keys produce a Meta modifier |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
824 is to use the `xkbprint' utility, if it's available on your system: |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
825 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
826 xkbprint 0:0 /tmp/k.ps |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
827 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
828 This produces a PostScript file `/tmp/k.ps' with a picture of your |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
829 keyboard; printing that file on a PostScript printer will show what |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
830 keys can serve as Meta. |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
831 |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
832 The `xkeycaps' also shows a visual representation of the current |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
833 keyboard settings. It also allows to modify them. |
446aa2cd256e
More information about how to find the Meta keys.
Eli Zaretskii <eliz@gnu.org>
parents:
38558
diff
changeset
|
834 |
31514 | 835 * On OSF/Dec Unix/Tru64/<whatever it is this year> under X locally or |
836 remotely, M-SPC acts as a `compose' key with strange results. See | |
837 keyboard(5). | |
838 | |
839 Changing Alt_L to Meta_L fixes it: | |
840 % xmodmap -e 'keysym Alt_L = Meta_L Alt_L' | |
841 % xmodmap -e 'keysym Alt_R = Meta_R Alt_R' | |
842 | |
25853 | 843 * Error "conflicting types for `initstate'" compiling with GCC on Irix 6. |
844 | |
845 Install GCC 2.95 or a newer version, and this problem should go away. | |
846 It is possible that this problem results from upgrading the operating | |
847 system without reinstalling GCC; so you could also try reinstalling | |
848 the same version of GCC, and telling us whether that fixes the problem. | |
849 | |
39466
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
850 * Emacs dumps core on Solaris in function IMCheckWindow. |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
851 |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
852 This was reported to happen when Emacs runs with more than one frame, |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
853 and one of them is closed, either with "C-x 5 0" or from the window |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
854 manager. |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
855 |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
856 This bug was reported to Sun as |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
857 |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
858 Gtk apps dump core in ximlocal.so.2:IMCheckIMWindow() |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
859 Bug Reports: 4463537 |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
860 |
39467 | 861 Installing Solaris 8 patch 108773-12 for Sparc and 108774-12 for x86 |
39466
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
862 reportedly fixes the bug, which appears to be inside the shared |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
863 library xiiimp.so. |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
864 |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
865 Alternatively, you can configure Emacs with `--with-xim=no' to prevent |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
866 the core dump, but will loose X input method support, of course. (You |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
867 can use Emacs's own input methods instead, if you install Leim.) |
580933cf6f05
Move the section aboiut XIMs on Solaris 8.
Eli Zaretskii <eliz@gnu.org>
parents:
39465
diff
changeset
|
868 |
25853 | 869 * On Solaris 7, Emacs gets a segmentation fault when starting up using X. |
870 | |
871 This results from Sun patch 107058-01 (SunOS 5.7: Patch for | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
872 assembler) if you use GCC version 2.7 or later. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
873 To work around it, either install patch 106950-03 or later, |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
874 or uninstall patch 107058-01, or install the GNU Binutils. |
25853 | 875 Then recompile Emacs, and it should work. |
876 | |
877 * With X11R6.4, public-patch-3, Emacs crashes at startup. | |
878 | |
879 Reportedly this patch in X fixes the problem. | |
880 | |
881 --- xc/lib/X11/imInt.c~ Wed Jun 30 13:31:56 1999 | |
882 +++ xc/lib/X11/imInt.c Thu Jul 1 15:10:27 1999 | |
883 @@ -1,4 +1,4 @@ | |
884 -/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */ | |
885 +/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */ | |
886 /****************************************************************** | |
887 | |
888 Copyright 1992, 1993, 1994 by FUJITSU LIMITED | |
889 @@ -166,8 +166,8 @@ | |
890 _XimMakeImName(lcd) | |
891 XLCd lcd; | |
892 { | |
893 - char* begin; | |
894 - char* end; | |
895 + char* begin = NULL; | |
896 + char* end = NULL; | |
897 char* ret; | |
898 int i = 0; | |
899 char* ximmodifier = XIMMODIFIER; | |
900 @@ -182,7 +182,11 @@ | |
901 } | |
902 ret = Xmalloc(end - begin + 2); | |
903 if (ret != NULL) { | |
904 - (void)strncpy(ret, begin, end - begin + 1); | |
905 + if (begin != NULL) { | |
906 + (void)strncpy(ret, begin, end - begin + 1); | |
907 + } else { | |
908 + ret[0] = '\0'; | |
909 + } | |
910 ret[end - begin + 1] = '\0'; | |
911 } | |
912 return ret; | |
913 | |
914 | |
915 * Emacs crashes on Irix 6.5 on the SGI R10K, when compiled with GCC. | |
916 | |
917 This seems to be fixed in GCC 2.95. | |
918 | |
919 * Emacs crashes in utmpname on Irix 5.3. | |
920 | |
921 This problem is fixed in Patch 3175 for Irix 5.3. | |
922 It is also fixed in Irix versions 6.2 and up. | |
923 | |
34880
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
924 * The S-C-t key combination doesn't get passed to Emacs on X. |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
925 |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
926 This happens because some X configurations assign the Ctrl-Shift-t |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
927 combination the same meaning as the Multi_key. The offending |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
928 definition is in the file `...lib/X11/locale/iso8859-1/Compose'; there |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
929 might be other similar combinations which are grabbed by X for similar |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
930 purposes. |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
931 |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
932 We think that this can be countermanded with the `xmodmap' utility, if |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
933 you want to be able to bind one of these key sequences within Emacs. |
40a2c6e62cee
Document the problems with S-C-t on X.
Eli Zaretskii <eliz@gnu.org>
parents:
34721
diff
changeset
|
934 |
25853 | 935 * On Solaris, CTRL-t is ignored by Emacs when you use |
936 the fr.ISO-8859-15 locale (and maybe other related locales). | |
937 | |
938 You can fix this by editing the file: | |
939 | |
940 /usr/openwin/lib/locale/iso8859-15/Compose | |
941 | |
942 Near the bottom there is a line that reads: | |
943 | |
944 Ctrl<t> <quotedbl> <Y> : "\276" threequarters | |
945 | |
946 that should read: | |
947 | |
948 Ctrl<T> <quotedbl> <Y> : "\276" threequarters | |
949 | |
950 Note the lower case <t>. Changing this line should make C-t work. | |
951 | |
952 * Emacs on Digital Unix 4.0 fails to build, giving error message | |
953 Invalid dimension for the charset-ID 160 | |
954 | |
955 This is due to a bug or an installation problem in GCC 2.8.0. | |
956 Installing a more recent version of GCC fixes the problem. | |
957 | |
958 * Buffers from `with-output-to-temp-buffer' get set up in Help mode. | |
959 | |
960 Changes in Emacs 20.4 to the hooks used by that function cause | |
961 problems for some packages, specifically BBDB. See the function's | |
962 documentation for the hooks involved. BBDB 2.00.06 fixes the problem. | |
963 | |
964 * Under X, C-v and/or other keys don't work. | |
965 | |
966 These may have been intercepted by your window manager. In | |
967 particular, AfterStep 1.6 is reported to steal C-v in its default | |
968 configuration. Various Meta keys are also likely to be taken by the | |
969 configuration of the `feel'. See the WM's documentation for how to | |
970 change this. | |
971 | |
972 * When using Exceed, fonts sometimes appear too tall. | |
973 | |
974 When the display is set to an Exceed X-server and fonts are specified | |
975 (either explicitly with the -fn option or implicitly with X resources) | |
976 then the fonts may appear "too tall". The actual character sizes are | |
977 correct but there is too much vertical spacing between rows, which | |
978 gives the appearance of "double spacing". | |
979 | |
980 To prevent this, turn off the Exceed's "automatic font substitution" | |
981 feature (in the font part of the configuration window). | |
982 | |
983 * Failure in unexec while dumping emacs on Digital Unix 4.0 | |
984 | |
985 This problem manifests itself as an error message | |
986 | |
987 unexec: Bad address, writing data section to ... | |
988 | |
989 The user suspects that this happened because his X libraries | |
990 were built for an older system version, | |
991 | |
992 ./configure --x-includes=/usr/include --x-libraries=/usr/shlib | |
993 | |
994 made the problem go away. | |
995 | |
996 * No visible display on mips-sgi-irix6.2 when compiling with GCC 2.8.1. | |
997 | |
998 This problem went away after installing the latest IRIX patches | |
999 as of 8 Dec 1998. | |
1000 | |
1001 The same problem has been reported on Irix 6.3. | |
1002 | |
1003 * As of version 20.4, Emacs doesn't work properly if configured for | |
1004 the Motif toolkit and linked against the free LessTif library. The | |
1005 next Emacs release is expected to work with LessTif. | |
1006 | |
1007 * Emacs gives the error, Couldn't find per display information. | |
1008 | |
1009 This can result if the X server runs out of memory because Emacs uses | |
1010 a large number of fonts. On systems where this happens, C-h h is | |
1011 likely to cause it. | |
1012 | |
1013 We do not know of a way to prevent the problem. | |
1014 | |
1015 * Emacs makes HPUX 11.0 crash. | |
1016 | |
1017 This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it. | |
1018 | |
1019 * Emacs crashes during dumping on the HPPA machine (HPUX 10.20). | |
1020 | |
1021 This seems to be due to a GCC bug; it is fixed in GCC 2.8.1. | |
1022 | |
1023 * The Hyperbole package causes *Help* buffers not to be displayed in | |
1024 Help mode due to setting `temp-buffer-show-hook' rather than using | |
1025 `add-hook'. Using `(add-hook 'temp-buffer-show-hook | |
1026 'help-mode-maybe)' after loading Hyperbole should fix this. | |
1027 | |
1028 * Versions of the PSGML package earlier than 1.0.3 (stable) or 1.1.2 | |
1029 (alpha) fail to parse DTD files correctly in Emacs 20.3 and later. | |
1030 Here is a patch for psgml-parse.el from PSGML 1.0.1 and, probably, | |
1031 earlier versions. | |
1032 | |
1033 --- psgml-parse.el 1998/08/21 19:18:18 1.1 | |
1034 +++ psgml-parse.el 1998/08/21 19:20:00 | |
1035 @@ -2383,7 +2383,7 @@ (defun sgml-push-to-entity (entity &opti | |
1036 (setq sgml-buffer-parse-state nil)) | |
1037 (cond | |
1038 ((stringp entity) ; a file name | |
1039 - (save-excursion (insert-file-contents entity)) | |
1040 + (insert-file-contents entity) | |
1041 (setq default-directory (file-name-directory entity))) | |
1042 ((consp (sgml-entity-text entity)) ; external id? | |
1043 (let* ((extid (sgml-entity-text entity)) | |
1044 | |
35907
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1045 * Emacs 21 freezes when visiting a TeX file with AUC TeX installed. |
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1046 |
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1047 Emacs 21 needs version 10 or later of AUC TeX; upgrading should solve |
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1048 these problems. |
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1049 |
41319
e6b8eb3755a7
What to do when AUC TeX don't fontify.
Eli Zaretskii <eliz@gnu.org>
parents:
41248
diff
changeset
|
1050 * No colors in AUC TeX with Emacs 21. |
e6b8eb3755a7
What to do when AUC TeX don't fontify.
Eli Zaretskii <eliz@gnu.org>
parents:
41248
diff
changeset
|
1051 |
e6b8eb3755a7
What to do when AUC TeX don't fontify.
Eli Zaretskii <eliz@gnu.org>
parents:
41248
diff
changeset
|
1052 Upgrade to AUC TeX version 10 or later, and make sure it is |
e6b8eb3755a7
What to do when AUC TeX don't fontify.
Eli Zaretskii <eliz@gnu.org>
parents:
41248
diff
changeset
|
1053 byte-compiled with Emacs 21. |
e6b8eb3755a7
What to do when AUC TeX don't fontify.
Eli Zaretskii <eliz@gnu.org>
parents:
41248
diff
changeset
|
1054 |
35907
1dc1345e8325
Document problems with AUC TeX and Emacs 21.
Eli Zaretskii <eliz@gnu.org>
parents:
35871
diff
changeset
|
1055 * Running TeX from AUC TeX package with Emacs 20.3 gives a Lisp error |
25853 | 1056 about a read-only tex output buffer. |
1057 | |
1058 This problem appeared for AUC TeX version 9.9j and some earlier | |
1059 versions. Here is a patch for the file tex-buf.el in the AUC TeX | |
1060 package. | |
1061 | |
1062 diff -c auctex/tex-buf.el~ auctex/tex-buf.el | |
1063 *** auctex/tex-buf.el~ Wed Jul 29 18:35:32 1998 | |
1064 --- auctex/tex-buf.el Sat Sep 5 15:20:38 1998 | |
1065 *************** | |
1066 *** 545,551 **** | |
1067 (dir (TeX-master-directory))) | |
1068 (TeX-process-check file) ; Check that no process is running | |
1069 (setq TeX-command-buffer (current-buffer)) | |
1070 ! (with-output-to-temp-buffer buffer) | |
1071 (set-buffer buffer) | |
1072 (if dir (cd dir)) | |
1073 (insert "Running `" name "' on `" file "' with ``" command "''\n") | |
1074 - --- 545,552 ---- | |
1075 (dir (TeX-master-directory))) | |
1076 (TeX-process-check file) ; Check that no process is running | |
1077 (setq TeX-command-buffer (current-buffer)) | |
1078 ! (let (temp-buffer-show-function temp-buffer-show-hook) | |
1079 ! (with-output-to-temp-buffer buffer)) | |
1080 (set-buffer buffer) | |
1081 (if dir (cd dir)) | |
1082 (insert "Running `" name "' on `" file "' with ``" command "''\n") | |
1083 | |
1084 * On Irix 6.3, substituting environment variables in file names | |
1085 in the minibuffer gives peculiar error messages such as | |
1086 | |
1087 Substituting nonexistent environment variable "" | |
1088 | |
1089 This is not an Emacs bug; it is caused by something in SGI patch | |
1090 003082 August 11, 1998. | |
1091 | |
1092 * After a while, Emacs slips into unibyte mode. | |
1093 | |
1094 The VM mail package, which is not part of Emacs, sometimes does | |
1095 (standard-display-european t) | |
1096 That should be changed to | |
1097 (standard-display-european 1 t) | |
1098 | |
1099 * Installing Emacs gets an error running `install-info'. | |
1100 | |
1101 You need to install a recent version of Texinfo; that package | |
1102 supplies the `install-info' command. | |
1103 | |
1104 * Emacs does not recognize the AltGr key, on HPUX. | |
1105 | |
1106 To fix this, set up a file ~/.dt/sessions/sessionetc with executable | |
1107 rights, containing this text: | |
1108 | |
1109 -------------------------------- | |
1110 xmodmap 2> /dev/null - << EOF | |
1111 keysym Alt_L = Meta_L | |
1112 keysym Alt_R = Meta_R | |
1113 EOF | |
1114 | |
1115 xmodmap - << EOF | |
1116 clear mod1 | |
1117 keysym Mode_switch = NoSymbol | |
1118 add mod1 = Meta_L | |
1119 keysym Meta_R = Mode_switch | |
1120 add mod2 = Mode_switch | |
1121 EOF | |
1122 -------------------------------- | |
1123 | |
38058
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1124 * Emacs hangs on KDE when a large portion of text is killed. |
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1125 |
38279
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1126 This is caused by a bug in the KDE applet `klipper' which periodically |
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1127 requests the X clipboard contents from applications. Early versions |
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1128 of klipper don't implement the ICCM protocol for large selections, |
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1129 which leads to Emacs being flooded with selection requests. After a |
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1130 while, Emacs will print a message: |
38058
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1131 |
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1132 Timed out waiting for property-notify event |
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1133 |
38279
1ded478b3fda
Clarify what's the problem with KDE's klipper applet.
Gerd Moellmann <gerd@gnu.org>
parents:
38277
diff
changeset
|
1134 A workaround is to not use `klipper'. |
38058
647c8404a670
Document problems with KDE's klipper.
Eli Zaretskii <eliz@gnu.org>
parents:
38054
diff
changeset
|
1135 |
25853 | 1136 * Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files |
1137 in the directory with the special name `dev' under the root of any | |
1138 drive, e.g. `c:/dev'. | |
1139 | |
1140 This is an unfortunate side-effect of the support for Unix-style | |
1141 device names such as /dev/null in the DJGPP runtime library. A | |
1142 work-around is to rename the problem directory to another name. | |
1143 | |
1144 * M-SPC seems to be ignored as input. | |
1145 | |
1146 See if your X server is set up to use this as a command | |
1147 for character composition. | |
1148 | |
1149 * Emacs startup on GNU/Linux systems (and possibly other systems) is slow. | |
1150 | |
1151 This can happen if the system is misconfigured and Emacs can't get the | |
1152 full qualified domain name, FQDN. You should have your FQDN in the | |
1153 /etc/hosts file, something like this: | |
1154 | |
1155 127.0.0.1 localhost | |
1156 129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04 | |
1157 | |
1158 The way to set this up may vary on non-GNU systems. | |
1159 | |
1160 * Garbled display on non-X terminals when Emacs runs on Digital Unix 4.0. | |
1161 | |
1162 So far it appears that running `tset' triggers this problem (when TERM | |
1163 is vt100, at least). If you do not run `tset', then Emacs displays | |
1164 properly. If someone can tell us precisely which effect of running | |
1165 `tset' actually causes the problem, we may be able to implement a fix | |
1166 in Emacs. | |
1167 | |
1168 * When you run Ispell from Emacs, it reports a "misalignment" error. | |
1169 | |
38026
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1170 This can happen if you compiled the Ispell program to use ASCII |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1171 characters only and then try to use it from Emacs with non-ASCII |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1172 characters, like Latin-1. The solution is to recompile Ispell with |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1173 support for 8-bit characters. |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1174 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1175 To see whether your Ispell program supports 8-bit characters, type |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1176 this at your shell's prompt: |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1177 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1178 ispell -vv |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1179 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1180 and look in the output for the string "NO8BIT". If Ispell says |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1181 "!NO8BIT (8BIT)", your speller supports 8-bit characters; otherwise it |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1182 does not. |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1183 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1184 To rebuild Ispell with 8-bit character support, edit the local.h file |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1185 in the Ispell distribution and make sure it does _not_ define NO8BIT. |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1186 Then rebuild the speller. |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1187 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1188 Another possible cause for "misalignment" error messages is that the |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1189 version of Ispell installed on your machine is old. Upgrade. |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1190 |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1191 Yet another possibility is that you are trying to spell-check a word |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1192 in a language that doesn't fit the dictionary you choose for use by |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1193 Ispell. (Ispell can only spell-check one language at a time, because |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1194 it uses a single dictionary.) Make sure that the text you are |
ad9617225b8d
Clarify the causes for "misalignment" error messages in Ispell.
Eli Zaretskii <eliz@gnu.org>
parents:
38012
diff
changeset
|
1195 spelling and the dictionary used by Ispell conform to each other. |
25853 | 1196 |
1197 * On Linux-based GNU systems using libc versions 5.4.19 through | |
1198 5.4.22, Emacs crashes at startup with a segmentation fault. | |
1199 | |
1200 This problem happens if libc defines the symbol __malloc_initialized. | |
1201 One known solution is to upgrade to a newer libc version. 5.4.33 is | |
1202 known to work. | |
1203 | |
1204 * On Windows, you cannot use the right-hand ALT key and the left-hand | |
1205 CTRL key together to type a Control-Meta character. | |
1206 | |
1207 This is a consequence of a misfeature beyond Emacs's control. | |
1208 | |
1209 Under Windows, the AltGr key on international keyboards generates key | |
1210 events with the modifiers Right-Alt and Left-Ctrl. Since Emacs cannot | |
1211 distinguish AltGr from an explicit Right-Alt and Left-Ctrl | |
1212 combination, whenever it sees Right-Alt and Left-Ctrl it assumes that | |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1213 AltGr has been pressed. The variable `w32-recognize-altgr' can be set |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1214 to nil to tell Emacs that AltGr is really Ctrl and Alt. |
25853 | 1215 |
1216 * Under some Windows X-servers, Emacs' display is incorrect | |
1217 | |
1218 The symptoms are that Emacs does not completely erase blank areas of the | |
1219 screen during scrolling or some other screen operations (e.g., selective | |
1220 display or when killing a region). M-x recenter will cause the screen | |
1221 to be completely redisplayed and the "extra" characters will disappear. | |
1222 | |
1223 This is known to occur under Exceed 6, and possibly earlier versions as | |
1224 well. The problem lies in the X-server settings. | |
1225 | |
1226 There are reports that you can solve the problem with Exceed by | |
1227 running `Xconfig' from within NT, choosing "X selection", then | |
1228 un-checking the boxes "auto-copy X selection" and "auto-paste to X | |
1229 selection". | |
1230 | |
1231 Of this does not work, please inform bug-gnu-emacs@gnu.org. Then | |
1232 please call support for your X-server and see if you can get a fix. | |
1233 If you do, please send it to bug-gnu-emacs@gnu.org so we can list it | |
1234 here. | |
1235 | |
1236 * On Solaris 2, Emacs dumps core when built with Motif. | |
1237 | |
1238 The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1. | |
1239 Install the current Motif runtime library patch appropriate for your host. | |
1240 (Make sure the patch is current; some older patch versions still have the bug.) | |
1241 You should install the other patches recommended by Sun for your host, too. | |
1242 You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/; | |
1243 look for files with names ending in `.PatchReport' to see which patches | |
1244 are currently recommended for your host. | |
1245 | |
1246 On Solaris 2.6, Emacs is said to work with Motif when Solaris patch | |
1247 105284-12 is installed, but fail when 105284-15 is installed. | |
1248 105284-18 might fix it again. | |
1249 | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1250 * On Solaris 2.6 and 7, the Compose key does not work. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1251 |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1252 This is a bug in Motif in Solaris. Supposedly it has been fixed for |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1253 the next major release of Solaris. However, if someone with Sun |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1254 support complains to Sun about the bug, they may release a patch. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1255 If you do this, mention Sun bug #4188711. |
25853 | 1256 |
1257 One workaround is to use a locale that allows non-ASCII characters. | |
1258 For example, before invoking emacs, set the LC_ALL environment | |
1259 variable to "en_US" (American English). The directory /usr/lib/locale | |
1260 lists the supported locales; any locale other than "C" or "POSIX" | |
1261 should do. | |
1262 | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1263 pen@lysator.liu.se says (Feb 1998) that the Compose key does work |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1264 if you link with the MIT X11 libraries instead of the Solaris X11 |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
1265 libraries. |
25853 | 1266 |
1267 * Emacs does not know your host's fully-qualified domain name. | |
1268 | |
1269 You need to configure your machine with a fully qualified domain name, | |
1270 either in /etc/hosts, /etc/hostname, the NIS, or wherever your system | |
1271 calls for specifying this. | |
1272 | |
1273 If you cannot fix the configuration, you can set the Lisp variable | |
1274 mail-host-address to the value you want. | |
1275 | |
1276 * Error 12 (virtual memory exceeded) when dumping Emacs, on UnixWare 2.1 | |
1277 | |
1278 Paul Abrahams (abrahams@acm.org) reports that with the installed | |
1279 virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during | |
1280 the "make" that builds Emacs, when running temacs to dump emacs. That | |
1281 error indicates that the per-process virtual memory limit has been | |
1282 exceeded. The default limit is probably 32MB. Raising the virtual | |
1283 memory limit to 40MB should make it possible to finish building Emacs. | |
1284 | |
1285 You can do this with the command `ulimit' (sh) or `limit' (csh). | |
1286 But you have to be root to do it. | |
1287 | |
1288 According to Martin Sohnius, you can also retune this in the kernel: | |
1289 | |
1290 # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit | |
1291 # /etc/conf/bin/idtune HDATLIM 33554432 ## hard " | |
1292 # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit | |
1293 # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard " | |
1294 # /etc/conf/bin/idbuild -B | |
1295 | |
1296 (He recommends you not change the stack limit, though.) | |
1297 These changes take effect when you reboot. | |
1298 | |
1299 * Redisplay using X11 is much slower than previous Emacs versions. | |
1300 | |
1301 We've noticed that certain X servers draw the text much slower when | |
1302 scroll bars are on the left. We don't know why this happens. If this | |
1303 happens to you, you can work around it by putting the scroll bars | |
1304 on the right (as they were in Emacs 19). | |
1305 | |
1306 Here's how to do this: | |
1307 | |
1308 (set-scroll-bar-mode 'right) | |
1309 | |
1310 If you're not sure whether (or how much) this problem affects you, | |
1311 try that and see how much difference it makes. To set things back | |
1312 to normal, do | |
1313 | |
1314 (set-scroll-bar-mode 'left) | |
1315 | |
1316 * Under X11, some characters appear as hollow boxes. | |
1317 | |
1318 Each X11 font covers just a fraction of the characters that Emacs | |
1319 supports. To display the whole range of Emacs characters requires | |
1320 many different fonts, collected into a fontset. | |
1321 | |
1322 If some of the fonts called for in your fontset do not exist on your X | |
1323 server, then the characters that have no font appear as hollow boxes. | |
1324 You can remedy the problem by installing additional fonts. | |
1325 | |
1326 The intlfonts distribution includes a full spectrum of fonts that can | |
1327 display all the characters Emacs supports. | |
1328 | |
35249 | 1329 Another cause of this for specific characters is fonts which have a |
1330 missing glyph and no default character. This is known ot occur for | |
1331 character number 160 (no-break space) in some fonts, such as Lucida | |
1332 but Emacs sets the display table for the unibyte and Latin-1 version | |
1333 of this character to display a space. | |
1334 | |
25853 | 1335 * Under X11, some characters appear improperly aligned in their lines. |
1336 | |
1337 You may have bad X11 fonts; try installing the intlfonts distribution. | |
1338 | |
1339 * Certain fonts make each line take one pixel more than it "should". | |
1340 | |
1341 This is because these fonts contain characters a little taller | |
1342 than the font's nominal height. Emacs needs to make sure that | |
1343 lines do not overlap. | |
1344 | |
1345 * You request inverse video, and the first Emacs frame is in inverse | |
1346 video, but later frames are not in inverse video. | |
1347 | |
1348 This can happen if you have an old version of the custom library in | |
1349 your search path for Lisp packages. Use M-x list-load-path-shadows to | |
1350 check whether this is true. If it is, delete the old custom library. | |
1351 | |
1352 * In FreeBSD 2.1.5, useless symbolic links remain in /tmp or other | |
1353 directories that have the +t bit. | |
1354 | |
1355 This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2). | |
1356 Emacs uses symbolic links to implement file locks. In a directory | |
1357 with +t bit, the directory owner becomes the owner of the symbolic | |
1358 link, so that it cannot be removed by anyone else. | |
1359 | |
1360 If you don't like those useless links, you can let Emacs not to using | |
1361 file lock by adding #undef CLASH_DETECTION to config.h. | |
1362 | |
1363 * When using M-x dbx with the SparcWorks debugger, the `up' and `down' | |
1364 commands do not move the arrow in Emacs. | |
1365 | |
1366 You can fix this by adding the following line to `~/.dbxinit': | |
1367 | |
1368 dbxenv output_short_file_name off | |
1369 | |
1370 * Emacs says it has saved a file, but the file does not actually | |
1371 appear on disk. | |
1372 | |
1373 This can happen on certain systems when you are using NFS, if the | |
1374 remote disk is full. It is due to a bug in NFS (or certain NFS | |
1375 implementations), and there is apparently nothing Emacs can do to | |
1376 detect the problem. Emacs checks the failure codes of all the system | |
1377 calls involved in writing a file, including `close'; but in the case | |
1378 where the problem occurs, none of those system calls fails. | |
1379 | |
1380 * "Compose Character" key does strange things when used as a Meta key. | |
1381 | |
1382 If you define one key to serve as both Meta and Compose Character, you | |
1383 will get strange results. In previous Emacs versions, this "worked" | |
1384 in that the key acted as Meta--that's because the older Emacs versions | |
1385 did not try to support Compose Character. Now Emacs tries to do | |
1386 character composition in the standard X way. This means that you | |
1387 must pick one meaning or the other for any given key. | |
1388 | |
1389 You can use both functions (Meta, and Compose Character) if you assign | |
1390 them to two different keys. | |
1391 | |
1392 * Emacs gets a segmentation fault at startup, on AIX4.2. | |
1393 | |
1394 If you are using IBM's xlc compiler, compile emacs.c | |
1395 without optimization; that should avoid the problem. | |
1396 | |
1397 * movemail compiled with POP support can't connect to the POP server. | |
1398 | |
1399 Make sure that the `pop' entry in /etc/services, or in the services | |
1400 NIS map if your machine uses NIS, has the same port number as the | |
1401 entry on the POP server. A common error is for the POP server to be | |
1402 listening on port 110, the assigned port for the POP3 protocol, while | |
1403 the client is trying to connect on port 109, the assigned port for the | |
1404 old POP protocol. | |
1405 | |
1406 * Emacs crashes in x-popup-dialog. | |
1407 | |
1408 This can happen if the dialog widget cannot find the font it wants to | |
1409 use. You can work around the problem by specifying another font with | |
1410 an X resource--for example, `Emacs.dialog*.font: 9x15' (or any font that | |
1411 happens to exist on your X server). | |
1412 | |
1413 * Emacs crashes when you use Bibtex mode. | |
1414 | |
1415 This happens if your system puts a small limit on stack size. You can | |
1416 prevent the problem by using a suitable shell command (often `ulimit') | |
1417 to raise the stack size limit before you run Emacs. | |
1418 | |
1419 Patches to raise the stack size limit automatically in `main' | |
1420 (src/emacs.c) on various systems would be greatly appreciated. | |
1421 | |
1422 * Emacs crashes with SIGBUS or SIGSEGV on HPUX 9 after you delete a frame. | |
1423 | |
1424 We think this is due to a bug in the X libraries provided by HP. With | |
1425 the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem | |
1426 does not happen. | |
1427 | |
1428 * Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame. | |
1429 | |
1430 We suspect that this is a similar bug in the X libraries provided by | |
1431 Sun. There is a report that one of these patches fixes the bug and | |
1432 makes the problem stop: | |
1433 | |
1434 105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02 | |
1435 105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03 | |
1436 106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01 | |
1437 105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01 | |
1438 | |
1439 Another person using a newer system (kernel patch level Generic_105181-06) | |
1440 suspects that the bug was fixed by one of these more recent patches: | |
1441 | |
1442 106040-07 SunOS 5.6: X Input & Output Method patch | |
1443 106222-01 OpenWindows 3.6: filemgr (ff.core) fixes | |
1444 105284-12 Motif 1.2.7: sparc Runtime library patch | |
1445 | |
1446 * Problems running Perl under Emacs on Windows NT/95. | |
1447 | |
1448 `perl -de 0' just hangs when executed in an Emacs subshell. | |
1449 The fault lies with Perl (indirectly with Windows NT/95). | |
1450 | |
1451 The problem is that the Perl debugger explicitly opens a connection to | |
1452 "CON", which is the DOS/NT equivalent of "/dev/tty", for interacting | |
1453 with the user. | |
1454 | |
1455 On Unix, this is okay, because Emacs (or the shell?) creates a | |
1456 pseudo-tty so that /dev/tty is really the pipe Emacs is using to | |
1457 communicate with the subprocess. | |
1458 | |
1459 On NT, this fails because CON always refers to the handle for the | |
1460 relevant console (approximately equivalent to a tty), and cannot be | |
1461 redirected to refer to the pipe Emacs assigned to the subprocess as | |
1462 stdin. | |
1463 | |
1464 A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON. | |
1465 | |
1466 For Perl 4: | |
1467 | |
1468 *** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993 | |
1469 --- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996 | |
1470 *************** | |
1471 *** 68,74 **** | |
1472 $rcfile=".perldb"; | |
1473 } | |
1474 else { | |
1475 ! $console = "con"; | |
1476 $rcfile="perldb.ini"; | |
1477 } | |
1478 | |
1479 --- 68,74 ---- | |
1480 $rcfile=".perldb"; | |
1481 } | |
1482 else { | |
1483 ! $console = ""; | |
1484 $rcfile="perldb.ini"; | |
1485 } | |
1486 | |
1487 | |
1488 For Perl 5: | |
1489 *** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995 | |
1490 --- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996 | |
1491 *************** | |
1492 *** 22,28 **** | |
1493 $rcfile=".perldb"; | |
1494 } | |
1495 elsif (-e "con") { | |
1496 ! $console = "con"; | |
1497 $rcfile="perldb.ini"; | |
1498 } | |
1499 else { | |
1500 --- 22,28 ---- | |
1501 $rcfile=".perldb"; | |
1502 } | |
1503 elsif (-e "con") { | |
1504 ! $console = ""; | |
1505 $rcfile="perldb.ini"; | |
1506 } | |
1507 else { | |
1508 | |
1509 * Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs: | |
1510 | |
1511 There are two DJGPP library bugs which cause problems: | |
1512 | |
1513 * Running `shell-command' (or `compile', or `grep') you get | |
1514 `Searching for program: permission denied (EACCES), c:/command.com'; | |
1515 * After you shell to DOS, Ctrl-Break kills Emacs. | |
1516 | |
1517 To work around these bugs, you can use two files in the msdos | |
1518 subdirectory: `is_exec.c' and `sigaction.c'. Compile them and link | |
1519 them into the Emacs executable `temacs'; then they will replace the | |
1520 incorrect library functions. | |
1521 | |
37480
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1522 * When compiling with DJGPP on Windows NT, "config msdos" fails. |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1523 |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1524 If the error message is "VDM has been already loaded", this is because |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1525 Windows has a program called `redir.exe' that is incompatible with a |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1526 program by the same name supplied with DJGPP, which is used by |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1527 config.bat. To resolve this, move the DJGPP's `bin' subdirectory to |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1528 the front of your PATH environment variable. |
e3bb46df554b
Document problems with DJGPP and NT's `redir' program.
Eli Zaretskii <eliz@gnu.org>
parents:
37453
diff
changeset
|
1529 |
25853 | 1530 * When compiling with DJGPP on Windows 95, Make fails for some targets |
1531 like make-docfile. | |
1532 | |
1533 This can happen if long file name support (the setting of environment | |
1534 variable LFN) when Emacs distribution was unpacked and during | |
1535 compilation are not the same. See the MSDOG section of INSTALL for | |
1536 the explanation of how to avoid this problem. | |
1537 | |
1538 * Emacs compiled for MSDOS cannot find some Lisp files, or other | |
1539 run-time support files, when long filename support is enabled. | |
38175
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1540 |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1541 Usually, this problem will manifest itself when Emacs exits |
25853 | 1542 immediately after flashing the startup screen, because it cannot find |
1543 the Lisp files it needs to load at startup. Redirect Emacs stdout | |
38175
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1544 and stderr to a file to see the error message printed by Emacs. |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1545 |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1546 Another manifestation of this problem is that Emacs is unable to load |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1547 the support for editing program sources in languages such as C and |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1548 Lisp. |
25853 | 1549 |
1550 This can happen if the Emacs distribution was unzipped without LFN | |
1551 support, thus causing long filenames to be truncated to the first 6 | |
1552 characters and a numeric tail that Windows 95 normally attaches to it. | |
1553 You should unzip the files again with a utility that supports long | |
1554 filenames (such as djtar from DJGPP or InfoZip's UnZip program | |
1555 compiled with DJGPP v2). The MSDOG section of the file INSTALL | |
1556 explains this issue in more detail. | |
1557 | |
38175
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1558 Another possible reason for such failures is that Emacs compiled for |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1559 MSDOS is used on Windows NT, where long file names are not supported |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1560 by this version of Emacs, but the distribution was unpacked by an |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1561 unzip program that preserved the long file names instead of truncating |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1562 them to DOS 8+3 limits. To be useful on NT, the MSDOS port of Emacs |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1563 must be unzipped by a DOS utility, so that long file names are |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1564 properly truncated. |
8976a1349254
More about long file names and the MSDOS port.
Eli Zaretskii <eliz@gnu.org>
parents:
38135
diff
changeset
|
1565 |
25853 | 1566 * Emacs compiled with DJGPP complains at startup: |
1567 | |
1568 "Wrong type of argument: internal-facep, msdos-menu-active-face" | |
1569 | |
1570 This can happen if you define an environment variable `TERM'. Emacs | |
1571 on MSDOS uses an internal terminal emulator which is disabled if the | |
1572 value of `TERM' is anything but the string "internal". Emacs then | |
1573 works as if its terminal were a dumb glass teletype that doesn't | |
1574 support faces. To work around this, arrange for `TERM' to be | |
1575 undefined when Emacs runs. The best way to do that is to add an | |
1576 [emacs] section to the DJGPP.ENV file which defines an empty value for | |
1577 `TERM'; this way, only Emacs gets the empty value, while the rest of | |
1578 your system works as before. | |
1579 | |
1580 * On Windows 95, Alt-f6 does not get through to Emacs. | |
1581 | |
1582 This character seems to be trapped by the kernel in Windows 95. | |
1583 You can enter M-f6 by typing ESC f6. | |
1584 | |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1585 * Typing Alt-Shift has strange effects on Windows. |
25853 | 1586 |
1587 This combination of keys is a command to change keyboard layout. If | |
1588 you proceed to type another non-modifier key before you let go of Alt | |
42759
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1589 and Shift, the Alt and Shift act as modifiers in the usual way. A |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1590 more permanent work around is to change it to another key combination, |
eb0beb585d7c
Updates for current state of Windows port.
Jason Rumney <jasonr@gnu.org>
parents:
42748
diff
changeset
|
1591 or disable it in the keyboard control panel. |
25853 | 1592 |
1593 * `tparam' reported as a multiply-defined symbol when linking with ncurses. | |
1594 | |
1595 This problem results from an incompatible change in ncurses, in | |
1596 version 1.9.9e approximately. This version is unable to provide a | |
1597 definition of tparm without also defining tparam. This is also | |
1598 incompatible with Terminfo; as a result, the Emacs Terminfo support | |
1599 does not work with this version of ncurses. | |
1600 | |
1601 The fix is to install a newer version of ncurses, such as version 4.2. | |
1602 | |
1603 * Strange results from format %d in a few cases, on a Sun. | |
1604 | |
1605 Sun compiler version SC3.0 has been found to miscompile part of | |
1606 editfns.c. The workaround is to compile with some other compiler such | |
1607 as GCC. | |
1608 | |
1609 * Output from subprocess (such as man or diff) is randomly truncated | |
1610 on GNU/Linux systems. | |
1611 | |
1612 This is due to a kernel bug which seems to be fixed in Linux version | |
1613 1.3.75. | |
1614 | |
1615 * Error messages `internal facep []' happen on GNU/Linux systems. | |
1616 | |
1617 There is a report that replacing libc.so.5.0.9 with libc.so.5.2.16 | |
1618 caused this to start happening. People are not sure why, but the | |
1619 problem seems unlikely to be in Emacs itself. Some suspect that it | |
1620 is actually Xlib which won't work with libc.so.5.2.16. | |
1621 | |
1622 Using the old library version is a workaround. | |
1623 | |
1624 * On Solaris, Emacs crashes if you use (display-time). | |
1625 | |
1626 This can happen if you configure Emacs without specifying the precise | |
1627 version of Solaris that you are using. | |
1628 | |
1629 * Emacs dumps core on startup, on Solaris. | |
1630 | |
1631 Bill Sebok says that the cause of this is Solaris 2.4 vendor patch | |
1632 102303-05, which extends the Solaris linker to deal with the Solaris | |
1633 Common Desktop Environment's linking needs. You can fix the problem | |
1634 by removing this patch and installing patch 102049-02 instead. | |
1635 However, that linker version won't work with CDE. | |
1636 | |
1637 Solaris 2.5 comes with a linker that has this bug. It is reported that if | |
1638 you install all the latest patches (as of June 1996), the bug is fixed. | |
1639 We suspect the crucial patch is one of these, but we don't know | |
1640 for certain. | |
1641 | |
1642 103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes) | |
1643 102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes) | |
1644 103242-04: [README] SunOS 5.5: linker patch (595363 bytes) | |
1645 | |
1646 (One user reports that the bug was fixed by those patches together | |
1647 with patches 102980-04, 103279-01, 103300-02, and 103468-01.) | |
1648 | |
1649 If you can determine which patch does fix the bug, please tell | |
1650 bug-gnu-emacs@gnu.org. | |
1651 | |
1652 Meanwhile, the GNU linker links Emacs properly on both Solaris 2.4 and | |
1653 Solaris 2.5. | |
1654 | |
1655 * Emacs dumps core if lisp-complete-symbol is called, on Solaris. | |
1656 | |
1657 If you compile Emacs with the -fast or -xO4 option with version 3.0.2 | |
1658 of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is | |
1659 called. The problem does not happen if you compile with GCC. | |
1660 | |
1661 * "Cannot find callback list" messages from dialog boxes on HPUX, in | |
1662 Emacs built with Motif. | |
1663 | |
1664 This problem resulted from a bug in GCC 2.4.5. Newer GCC versions | |
1665 such as 2.7.0 fix the problem. | |
1666 | |
1667 * On Irix 6.0, make tries (and fails) to build a program named unexelfsgi | |
1668 | |
1669 A compiler bug inserts spaces into the string "unexelfsgi . o" | |
1670 in src/Makefile. Edit src/Makefile, after configure is run, | |
1671 find that string, and take out the spaces. | |
1672 | |
1673 Compiler fixes in Irix 6.0.1 should eliminate this problem. | |
1674 | |
1675 * "out of virtual swap space" on Irix 5.3 | |
1676 | |
1677 This message occurs when the system runs out of swap space due to too | |
1678 many large programs running. The solution is either to provide more | |
1679 swap space or to reduce the number of large programs being run. You | |
1680 can check the current status of the swap space by executing the | |
1681 command `swap -l'. | |
1682 | |
1683 You can increase swap space by changing the file /etc/fstab. Adding a | |
1684 line like this: | |
1685 | |
1686 /usr/swap/swap.more swap swap pri=3 0 0 | |
1687 | |
1688 where /usr/swap/swap.more is a file previously created (for instance | |
1689 by using /etc/mkfile), will increase the swap space by the size of | |
1690 that file. Execute `swap -m' or reboot the machine to activate the | |
1691 new swap area. See the manpages for `swap' and `fstab' for further | |
1692 information. | |
1693 | |
1694 The objectserver daemon can use up lots of memory because it can be | |
1695 swamped with NIS information. It collects information about all users | |
1696 on the network that can log on to the host. | |
1697 | |
1698 If you want to disable the objectserver completely, you can execute | |
1699 the command `chkconfig objectserver off' and reboot. That may disable | |
1700 some of the window system functionality, such as responding CDROM | |
1701 icons. | |
1702 | |
1703 You can also remove NIS support from the objectserver. The SGI `admin' | |
1704 FAQ has a detailed description on how to do that; see question 35 | |
1705 ("Why isn't the objectserver working?"). The admin FAQ can be found at | |
1706 ftp://viz.tamu.edu/pub/sgi/faq/. | |
1707 | |
1708 * With certain fonts, when the cursor appears on a character, the | |
1709 character doesn't appear--you get a solid box instead. | |
1710 | |
1711 One user on a Linux-based GNU system reported that this problem went | |
1712 away with installation of a new X server. The failing server was | |
1713 XFree86 3.1.1. XFree86 3.1.2 works. | |
1714 | |
1715 * On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft. | |
1716 | |
1717 This happens if you configure Emacs specifying just `sparc-sun-sunos4' | |
1718 on a system that is version 4.1.3. You must specify the precise | |
1719 version number (or let configure figure out the configuration, which | |
1720 it can do perfectly well for SunOS). | |
1721 | |
1722 * On SunOS 4, Emacs processes keep going after you kill the X server | |
1723 (or log out, if you logged in using X). | |
1724 | |
1725 Someone reported that recompiling with GCC 2.7.0 fixed this problem. | |
1726 | |
1727 * On AIX 4, some programs fail when run in a Shell buffer | |
1728 with an error message like No terminfo entry for "unknown". | |
1729 | |
1730 On AIX, many terminal type definitions are not installed by default. | |
1731 `unknown' is one of them. Install the "Special Generic Terminal | |
1732 Definitions" to make them defined. | |
1733 | |
1734 * On SunOS, you get linker errors | |
1735 ld: Undefined symbol | |
1736 _get_wmShellWidgetClass | |
1737 _get_applicationShellWidgetClass | |
1738 | |
1739 The fix to this is to install patch 100573 for OpenWindows 3.0 | |
1740 or link libXmu statically. | |
1741 | |
1742 * On AIX 4.1.2, linker error messages such as | |
1743 ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table | |
1744 of archive /usr/lib/libIM.a, was not defined in archive member shr.o. | |
1745 | |
1746 This is a problem in libIM.a. You can work around it by executing | |
1747 these shell commands in the src subdirectory of the directory where | |
1748 you build Emacs: | |
1749 | |
1750 cp /usr/lib/libIM.a . | |
1751 chmod 664 libIM.a | |
1752 ranlib libIM.a | |
1753 | |
1754 Then change -lIM to ./libIM.a in the command to link temacs (in | |
1755 Makefile). | |
1756 | |
1757 * Unpredictable segmentation faults on Solaris 2.3 and 2.4. | |
1758 | |
1759 A user reported that this happened in 19.29 when it was compiled with | |
1760 the Sun compiler, but not when he recompiled with GCC 2.7.0. | |
1761 | |
1762 We do not know whether something in Emacs is partly to blame for this. | |
1763 | |
1764 * Emacs exits with "X protocol error" when run with an X server for | |
1765 Windows. | |
1766 | |
1767 A certain X server for Windows had a bug which caused this. | |
1768 Supposedly the newer 32-bit version of this server doesn't have the | |
1769 problem. | |
1770 | |
1771 * Emacs crashes at startup on MSDOS. | |
1772 | |
1773 Some users report that Emacs 19.29 requires dpmi memory management, | |
1774 and crashes on startup if the system does not have it. We don't yet | |
1775 know why this happens--perhaps these machines don't have enough real | |
1776 memory, or perhaps something is wrong in Emacs or the compiler. | |
1777 However, arranging to use dpmi support is a workaround. | |
1778 | |
1779 You can find out if you have a dpmi host by running go32 without | |
1780 arguments; it will tell you if it uses dpmi memory. For more | |
1781 information about dpmi memory, consult the djgpp FAQ. (djgpp | |
1782 is the GNU C compiler as packaged for MSDOS.) | |
1783 | |
1784 Compiling Emacs under MSDOS is extremely sensitive for proper memory | |
1785 configuration. If you experience problems during compilation, consider | |
1786 removing some or all memory resident programs (notably disk caches) | |
1787 and make sure that your memory managers are properly configured. See | |
1788 the djgpp faq for configuration hints. | |
1789 | |
1790 * A position you specified in .Xdefaults is ignored, using twm. | |
1791 | |
1792 twm normally ignores "program-specified" positions. | |
1793 You can tell it to obey them with this command in your `.twmrc' file: | |
1794 | |
1795 UsePPosition "on" #allow clients to request a position | |
1796 | |
1797 * Compiling lib-src says there is no rule to make test-distrib.c. | |
1798 | |
1799 This results from a bug in a VERY old version of GNU Sed. To solve | |
1800 the problem, install the current version of GNU Sed, then rerun | |
1801 Emacs's configure script. | |
1802 | |
1803 * Compiling wakeup, in lib-src, says it can't make wakeup.c. | |
1804 | |
1805 This results from a bug in GNU Sed version 2.03. To solve the | |
1806 problem, install the current version of GNU Sed, then rerun Emacs's | |
1807 configure script. | |
1808 | |
1809 * On Sunos 4.1.1, there are errors compiling sysdep.c. | |
1810 | |
1811 If you get errors such as | |
1812 | |
1813 "sysdep.c", line 2017: undefined structure or union | |
1814 "sysdep.c", line 2017: undefined structure or union | |
1815 "sysdep.c", line 2019: nodename undefined | |
1816 | |
1817 This can result from defining LD_LIBRARY_PATH. It is very tricky | |
1818 to use that environment variable with Emacs. The Emacs configure | |
1819 script links many test programs with the system libraries; you must | |
1820 make sure that the libraries available to configure are the same | |
1821 ones available when you build Emacs. | |
1822 | |
1823 * The right Alt key works wrong on German HP keyboards (and perhaps | |
1824 other non-English HP keyboards too). | |
1825 | |
1826 This is because HPUX defines the modifiers wrong in X. Here is a | |
1827 shell script to fix the problem; be sure that it is run after VUE | |
1828 configures the X server. | |
1829 | |
1830 xmodmap 2> /dev/null - << EOF | |
1831 keysym Alt_L = Meta_L | |
1832 keysym Alt_R = Meta_R | |
1833 EOF | |
1834 | |
1835 xmodmap - << EOF | |
1836 clear mod1 | |
1837 keysym Mode_switch = NoSymbol | |
1838 add mod1 = Meta_L | |
1839 keysym Meta_R = Mode_switch | |
1840 add mod2 = Mode_switch | |
1841 EOF | |
1842 | |
1843 * The Emacs window disappears when you type M-q. | |
1844 | |
1845 Some versions of the Open Look window manager interpret M-q as a quit | |
1846 command for whatever window you are typing at. If you want to use | |
1847 Emacs with that window manager, you should try to configure the window | |
1848 manager to use some other command. You can disable the | |
1849 shortcut keys entirely by adding this line to ~/.OWdefaults: | |
1850 | |
1851 OpenWindows.WindowMenuAccelerators: False | |
1852 | |
1853 * Emacs does not notice when you release the mouse. | |
1854 | |
1855 There are reports that this happened with (some) Microsoft mice and | |
1856 that replacing the mouse made it stop. | |
1857 | |
1858 * Trouble using ptys on IRIX, or running out of ptys. | |
1859 | |
1860 The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to | |
1861 be set-UID to root, or non-root programs like Emacs will not be able | |
1862 to allocate ptys reliably. | |
1863 | |
1864 * On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h. | |
1865 | |
1866 The file cmplrs/stsupport.h was included in the wrong file set in the | |
1867 Irix 5.2 distribution. You can find it in the optional fileset | |
1868 compiler_dev, or copy it from some other Irix 5.2 system. A kludgy | |
1869 workaround is to change unexelfsgi.c to include sym.h instead of | |
1870 syms.h. | |
1871 | |
1872 * Slow startup on Linux-based GNU systems. | |
1873 | |
1874 People using systems based on the Linux kernel sometimes report that | |
1875 startup takes 10 to 15 seconds longer than `usual'. | |
1876 | |
1877 This is because Emacs looks up the host name when it starts. | |
1878 Normally, this takes negligible time; the extra delay is due to | |
1879 improper system configuration. This problem can occur for both | |
1880 networked and non-networked machines. | |
1881 | |
1882 Here is how to fix the configuration. It requires being root. | |
1883 | |
1884 ** Networked Case | |
1885 | |
1886 First, make sure the files `/etc/hosts' and `/etc/host.conf' both | |
1887 exist. The first line in the `/etc/hosts' file should look like this | |
1888 (replace HOSTNAME with your host name): | |
1889 | |
1890 127.0.0.1 HOSTNAME | |
1891 | |
1892 Also make sure that the `/etc/host.conf' files contains the following | |
1893 lines: | |
1894 | |
1895 order hosts, bind | |
1896 multi on | |
1897 | |
1898 Any changes, permanent and temporary, to the host name should be | |
1899 indicated in the `/etc/hosts' file, since it acts a limited local | |
1900 database of addresses and names (e.g., some SLIP connections | |
1901 dynamically allocate ip addresses). | |
1902 | |
1903 ** Non-Networked Case | |
1904 | |
1905 The solution described in the networked case applies here as well. | |
1906 However, if you never intend to network your machine, you can use a | |
1907 simpler solution: create an empty `/etc/host.conf' file. The command | |
1908 `touch /etc/host.conf' suffices to create the file. The `/etc/hosts' | |
1909 file is not necessary with this approach. | |
1910 | |
1911 * On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs | |
1912 forever waiting for termination of a subprocess that is a zombie. | |
1913 | |
1914 casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so | |
1915 after changing the file xc/config/cf/sunLib.tmpl. Change the lines | |
1916 | |
1917 #if ThreadedX | |
1918 #define SharedX11Reqs -lthread | |
1919 #endif | |
1920 | |
1921 to: | |
1922 | |
1923 #if OSMinorVersion < 4 | |
1924 #if ThreadedX | |
1925 #define SharedX11Reqs -lthread | |
1926 #endif | |
1927 #endif | |
1928 | |
1929 Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4 | |
1930 (as it should be for Solaris 2.4). The file has three definitions for | |
1931 OSMinorVersion: the first is for x86, the second for SPARC under | |
1932 Solaris, and the third for SunOS 4. Make sure to update the | |
1933 definition for your type of machine and system. | |
1934 | |
1935 Then do `make Everything' in the top directory of X11R6, to rebuild | |
1936 the makefiles and rebuild X. The X built this way work only on | |
1937 Solaris 2.4, not on 2.3. | |
1938 | |
1939 For multithreaded X to work it is necessary to install patch | |
1940 101925-02 to fix problems in header files [2.4]. You need | |
1941 to reinstall gcc or re-run just-fixinc after installing that | |
1942 patch. | |
1943 | |
1944 However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution: | |
1945 he changed | |
1946 #define ThreadedX YES | |
1947 to | |
1948 #define ThreadedX NO | |
1949 in sun.cf and did `make World' to rebuild X11R6. Removing all | |
1950 `-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and | |
1951 typing 'make install' in that directory also seemed to work. | |
1952 | |
1953 * With M-x enable-flow-control, you need to type C-\ twice | |
1954 to do incremental search--a single C-\ gets no response. | |
1955 | |
1956 This has been traced to communicating with your machine via kermit, | |
1957 with C-\ as the kermit escape character. One solution is to use | |
1958 another escape character in kermit. One user did | |
1959 | |
1960 set escape-character 17 | |
1961 | |
1962 in his .kermrc file, to make C-q the kermit escape character. | |
1963 | |
1964 * The Motif version of Emacs paints the screen a solid color. | |
1965 | |
1966 This has been observed to result from the following X resource: | |
1967 | |
1968 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-* | |
1969 | |
1970 That the resource has this effect indicates a bug in something, but we | |
1971 do not yet know what. If it is an Emacs bug, we hope someone can | |
1972 explain what the bug is so we can fix it. In the mean time, removing | |
1973 the resource prevents the problem. | |
1974 | |
1975 * Emacs gets hung shortly after startup, on Sunos 4.1.3. | |
1976 | |
1977 We think this is due to a bug in Sunos. The word is that | |
1978 one of these Sunos patches fixes the bug: | |
1979 | |
1980 100075-11 100224-06 100347-03 100482-05 100557-02 100623-03 100804-03 101080-01 | |
1981 100103-12 100249-09 100496-02 100564-07 100630-02 100891-10 101134-01 | |
1982 100170-09 100296-04 100377-09 100507-04 100567-04 100650-02 101070-01 101145-01 | |
1983 100173-10 100305-15 100383-06 100513-04 100570-05 100689-01 101071-03 101200-02 | |
1984 100178-09 100338-05 100421-03 100536-02 100584-05 100784-01 101072-01 101207-01 | |
1985 | |
1986 We don't know which of these patches really matter. If you find out | |
1987 which ones, please inform bug-gnu-emacs@gnu.org. | |
1988 | |
1989 * Emacs aborts while starting up, only when run without X. | |
1990 | |
1991 This problem often results from compiling Emacs with GCC when GCC was | |
1992 installed incorrectly. The usual error in installing GCC is to | |
1993 specify --includedir=/usr/include. Installation of GCC makes | |
1994 corrected copies of the system header files. GCC is supposed to use | |
1995 the corrected copies in preference to the original system headers. | |
1996 Specifying --includedir=/usr/include causes the original system header | |
1997 files to be used. On some systems, the definition of ioctl in the | |
1998 original system header files is invalid for ANSI C and causes Emacs | |
1999 not to work. | |
2000 | |
2001 The fix is to reinstall GCC, and this time do not specify --includedir | |
2002 when you configure it. Then recompile Emacs. Specifying --includedir | |
2003 is appropriate only in very special cases and it should *never* be the | |
2004 same directory where system header files are kept. | |
2005 | |
2006 * On Solaris 2.x, GCC complains "64 bit integer types not supported" | |
2007 | |
2008 This suggests that GCC is not installed correctly. Most likely you | |
2009 are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this | |
2010 does not work without patching. To run GCC 2.7.2.3 on Solaris 2.6 or | |
2011 later, you must patch fixinc.svr4 and reinstall GCC from scratch as | |
2012 described in the Solaris FAQ | |
2013 <http://www.wins.uva.nl/pub/solaris/solaris2.html>. A better fix is | |
2014 to upgrade to GCC 2.8.1 or later. | |
2015 | |
2016 * The Compose key on a DEC keyboard does not work as Meta key. | |
2017 | |
2018 This shell command should fix it: | |
2019 | |
2020 xmodmap -e 'keycode 0xb1 = Meta_L' | |
2021 | |
2022 * Regular expressions matching bugs on SCO systems. | |
2023 | |
2024 On SCO, there are problems in regexp matching when Emacs is compiled | |
2025 with the system compiler. The compiler version is "Microsoft C | |
2026 version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick | |
2027 C Compiler Version 1.00.46 (Beta). The solution is to compile with | |
2028 GCC. | |
2029 | |
2030 * On Sunos 4, you get the error ld: Undefined symbol __lib_version. | |
2031 | |
2032 This is the result of using cc or gcc with the shared library meant | |
2033 for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete | |
2034 /usr/lang/SC2.0.1 or some similar directory. | |
2035 | |
2036 * You can't select from submenus (in the X toolkit version). | |
2037 | |
2038 On certain systems, mouse-tracking and selection in top-level menus | |
2039 works properly with the X toolkit, but neither of them works when you | |
2040 bring up a submenu (such as Bookmarks or Compare or Apply Patch, in | |
2041 the Files menu). | |
2042 | |
2043 This works on most systems. There is speculation that the failure is | |
2044 due to bugs in old versions of X toolkit libraries, but no one really | |
2045 knows. If someone debugs this and finds the precise cause, perhaps a | |
2046 workaround can be found. | |
2047 | |
2048 * Unusable default font on SCO 3.2v4. | |
2049 | |
2050 The Open Desktop environment comes with default X resource settings | |
2051 that tell Emacs to use a variable-width font. Emacs cannot use such | |
2052 fonts, so it does not work. | |
2053 | |
2054 This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is | |
2055 the application-specific resource file for the `scoterm' terminal | |
2056 emulator program. It contains several extremely general X resources | |
2057 that affect other programs besides `scoterm'. In particular, these | |
2058 resources affect Emacs also: | |
2059 | |
2060 *Font: -*-helvetica-medium-r-*--12-*-p-* | |
2061 *Background: scoBackground | |
2062 *Foreground: scoForeground | |
2063 | |
2064 The best solution is to create an application-specific resource file for | |
2065 Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents: | |
2066 | |
2067 Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
2068 Emacs*Background: white | |
2069 Emacs*Foreground: black | |
2070 | |
2071 (These settings mimic the Emacs defaults, but you can change them to | |
2072 suit your needs.) This resource file is only read when the X server | |
2073 starts up, so you should restart it by logging out of the Open Desktop | |
2074 environment or by running `scologin stop; scologin start` from the shell | |
2075 as root. Alternatively, you can put these settings in the | |
2076 /usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs, | |
2077 but then they will not affect remote invocations of Emacs that use the | |
2078 Open Desktop display. | |
2079 | |
2080 These resource files are not normally shared across a network of SCO | |
2081 machines; you must create the file on each machine individually. | |
2082 | |
2083 * rcs2log gives you the awk error message "too many fields". | |
2084 | |
2085 This is due to an arbitrary limit in certain versions of awk. | |
2086 The solution is to use gawk (GNU awk). | |
2087 | |
2088 * Emacs is slow using X11R5 on HP/UX. | |
2089 | |
2090 This happens if you use the MIT versions of the X libraries--it | |
2091 doesn't run as fast as HP's version. People sometimes use the version | |
2092 because they see the HP version doesn't have the libraries libXaw.a, | |
2093 libXmu.a, libXext.a and others. HP/UX normally doesn't come with | |
2094 those libraries installed. To get good performance, you need to | |
2095 install them and rebuild Emacs. | |
2096 | |
2097 * Loading fonts is very slow. | |
2098 | |
2099 You might be getting scalable fonts instead of precomputed bitmaps. | |
2100 Known scalable font directories are "Type1" and "Speedo". A font | |
2101 directory contains scalable fonts if it contains the file | |
2102 "fonts.scale". | |
2103 | |
2104 If this is so, re-order your X windows font path to put the scalable | |
2105 font directories last. See the documentation of `xset' for details. | |
2106 | |
2107 With some X servers, it may be necessary to take the scalable font | |
2108 directories out of your path entirely, at least for Emacs 19.26. | |
2109 Changes in the future may make this unnecessary. | |
2110 | |
2111 * On AIX 3.2.4, releasing Ctrl/Act key has no effect, if Shift is down. | |
2112 | |
2113 Due to a feature of AIX, pressing or releasing the Ctrl/Act key is | |
2114 ignored when the Shift, Alt or AltGr keys are held down. This can | |
2115 lead to the keyboard being "control-locked"--ordinary letters are | |
2116 treated as control characters. | |
2117 | |
2118 You can get out of this "control-locked" state by pressing and | |
2119 releasing Ctrl/Act while not pressing or holding any other keys. | |
2120 | |
2121 * display-time causes kernel problems on ISC systems. | |
2122 | |
2123 Under Interactive Unix versions 3.0.1 and 4.0 (and probably other | |
2124 versions), display-time causes the loss of large numbers of STREVENT | |
2125 cells. Eventually the kernel's supply of these cells is exhausted. | |
2126 This makes emacs and the whole system run slow, and can make other | |
2127 processes die, in particular pcnfsd. | |
2128 | |
2129 Other emacs functions that communicate with remote processes may have | |
2130 the same problem. Display-time seems to be far the worst. | |
2131 | |
2132 The only known fix: Don't run display-time. | |
2133 | |
2134 * On Solaris, C-x doesn't get through to Emacs when you use the console. | |
2135 | |
2136 This is a Solaris feature (at least on Intel x86 cpus). Type C-r | |
2137 C-r C-t, to toggle whether C-x gets through to Emacs. | |
2138 | |
2139 * Error message `Symbol's value as variable is void: x', followed by | |
2140 segmentation fault and core dump. | |
2141 | |
2142 This has been tracked to a bug in tar! People report that tar erroneously | |
2143 added a line like this at the beginning of files of Lisp code: | |
2144 | |
2145 x FILENAME, N bytes, B tape blocks | |
2146 | |
2147 If your tar has this problem, install GNU tar--if you can manage to | |
2148 untar it :-). | |
2149 | |
2150 * Link failure when using acc on a Sun. | |
2151 | |
2152 To use acc, you need additional options just before the libraries, such as | |
2153 | |
2154 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1 | |
2155 | |
2156 and you need to add -lansi just before -lc. | |
2157 | |
2158 The precise file names depend on the compiler version, so we | |
2159 cannot easily arrange to supply them. | |
2160 | |
2161 * Link failure on IBM AIX 1.3 ptf 0013. | |
2162 | |
2163 There is a real duplicate definition of the function `_slibc_free' in | |
2164 the library /lib/libc_s.a (just do nm on it to verify). The | |
2165 workaround/fix is: | |
2166 | |
2167 cd /lib | |
2168 ar xv libc_s.a NLtmtime.o | |
2169 ar dv libc_s.a NLtmtime.o | |
2170 | |
2171 * Undefined symbols _dlopen, _dlsym and/or _dlclose on a Sun. | |
2172 | |
2173 If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking | |
2174 with -lX11, compile and link against the file mit/util/misc/dlsym.c in | |
2175 the MIT X11R5 distribution. Alternatively, link temacs using shared | |
2176 libraries with s/sunos4shr.h. (This doesn't work if you use the X | |
2177 toolkit.) | |
2178 | |
2179 If you get the additional error that the linker could not find | |
2180 lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in | |
2181 X11R4, then use it in the link. | |
2182 | |
2183 * Error messages `Wrong number of arguments: #<subr where-is-internal>, 5' | |
2184 | |
2185 This typically results from having the powerkey library loaded. | |
2186 Powerkey was designed for Emacs 19.22. It is obsolete now because | |
2187 Emacs 19 now has this feature built in; and powerkey also calls | |
2188 where-is-internal in an obsolete way. | |
2189 | |
2190 So the fix is to arrange not to load powerkey. | |
2191 | |
2192 * In Shell mode, you get a ^M at the end of every line. | |
2193 | |
2194 This happens to people who use tcsh, because it is trying to be too | |
2195 smart. It sees that the Shell uses terminal type `unknown' and turns | |
2196 on the flag to output ^M at the end of each line. You can fix the | |
2197 problem by adding this to your .cshrc file: | |
2198 | |
2199 if ($?EMACS) then | |
2200 if ($EMACS == "t") then | |
2201 unset edit | |
2202 stty -icrnl -onlcr -echo susp ^Z | |
2203 endif | |
2204 endif | |
2205 | |
2206 * An error message such as `X protocol error: BadMatch (invalid | |
2207 parameter attributes) on protocol request 93'. | |
2208 | |
2209 This comes from having an invalid X resource, such as | |
2210 emacs*Cursor: black | |
2211 (which is invalid because it specifies a color name for something | |
2212 that isn't a color.) | |
2213 | |
2214 The fix is to correct your X resources. | |
2215 | |
2216 * Undefined symbols when linking on Sunos 4.1 using --with-x-toolkit. | |
2217 | |
2218 If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace, | |
2219 _iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after | |
2220 -lXaw in the command that links temacs. | |
2221 | |
2222 This problem seems to arise only when the international language | |
2223 extensions to X11R5 are installed. | |
2224 | |
2225 * Typing C-c C-c in Shell mode kills your X server. | |
2226 | |
2227 This happens with Linux kernel 1.0 thru 1.04, approximately. The workaround is | |
2228 to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs. | |
2229 Newer Linux kernel versions don't have this problem. | |
2230 | |
2231 * src/Makefile and lib-src/Makefile are truncated--most of the file missing. | |
2232 | |
2233 This can happen if configure uses GNU sed version 2.03. That version | |
2234 had a bug. GNU sed version 2.05 works properly. | |
2235 | |
2236 * Slow startup on X11R6 with X windows. | |
2237 | |
2238 If Emacs takes two minutes to start up on X11R6, see if your X | |
2239 resources specify any Adobe fonts. That causes the type-1 font | |
2240 renderer to start up, even if the font you asked for is not a type-1 | |
2241 font. | |
2242 | |
2243 One way to avoid this problem is to eliminate the type-1 fonts from | |
2244 your font path, like this: | |
2245 | |
2246 xset -fp /usr/X11R6/lib/X11/fonts/Type1/ | |
2247 | |
2248 * Pull-down menus appear in the wrong place, in the toolkit version of Emacs. | |
2249 | |
2250 An X resource of this form can cause the problem: | |
2251 | |
2252 Emacs*geometry: 80x55+0+0 | |
2253 | |
2254 This resource is supposed to apply, and does apply, to the menus | |
2255 individually as well as to Emacs frames. If that is not what you | |
2256 want, rewrite the resource. | |
2257 | |
2258 To check thoroughly for such resource specifications, use `xrdb | |
2259 -query' to see what resources the X server records, and also look at | |
2260 the user's ~/.Xdefaults and ~/.Xdefaults-* files. | |
2261 | |
2262 * --with-x-toolkit version crashes when used with shared libraries. | |
2263 | |
2264 On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others, | |
2265 unexec doesn't work properly with the shared library for the X | |
2266 toolkit. You might be able to work around this by using a nonshared | |
2267 libXt.a library. The real fix is to upgrade the various versions of | |
2268 unexec and/or ralloc. We think this has been fixed on Sunos 4 | |
2269 and Solaris in version 19.29. | |
2270 | |
2271 * `make install' fails on install-doc with `Error 141'. | |
2272 | |
2273 This happens on Ultrix 4.2 due to failure of a pipeline of tar | |
2274 commands. We don't know why they fail, but the bug seems not to be in | |
2275 Emacs. The workaround is to run the shell command in install-doc by | |
2276 hand. | |
2277 | |
2278 * --with-x-toolkit option configures wrong on BSD/386. | |
2279 | |
2280 This problem is due to bugs in the shell in version 1.0 of BSD/386. | |
2281 The workaround is to edit the configure file to use some other shell, | |
2282 such as bash. | |
2283 | |
2284 * Subprocesses remain, hanging but not zombies, on Sunos 5.3. | |
2285 | |
2286 A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs | |
2287 exits. Sun patch # 101415-02 is part of the fix for this, but it only | |
2288 applies to ptys, and doesn't fix the problem with subprocesses | |
2289 communicating through pipes. | |
2290 | |
2291 * Mail is lost when sent to local aliases. | |
2292 | |
2293 Many emacs mail user agents (VM and rmail, for instance) use the | |
2294 sendmail.el library. This library can arrange for mail to be | |
2295 delivered by passing messages to the /usr/lib/sendmail (usually) | |
2296 program . In doing so, it passes the '-t' flag to sendmail, which | |
2297 means that the name of the recipient of the message is not on the | |
2298 command line and, therefore, that sendmail must parse the message to | |
2299 obtain the destination address. | |
2300 | |
2301 There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail. | |
2302 In short, when given the -t flag, the SunOS sendmail won't recognize | |
2303 non-local (i.e. NIS) aliases. It has been reported that the Solaris | |
2304 2.x versions of sendmail do not have this bug. For those using SunOS | |
2305 4.1, the best fix is to install sendmail V8 or IDA sendmail (which | |
2306 have other advantages over the regular sendmail as well). At the time | |
2307 of this writing, these official versions are available: | |
2308 | |
2309 Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail: | |
2310 sendmail.8.6.9.base.tar.Z (the base system source & documentation) | |
2311 sendmail.8.6.9.cf.tar.Z (configuration files) | |
2312 sendmail.8.6.9.misc.tar.Z (miscellaneous support programs) | |
2313 sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript) | |
2314 | |
2315 IDA sendmail on vixen.cso.uiuc.edu in /pub: | |
2316 sendmail-5.67b+IDA-1.5.tar.gz | |
2317 | |
2318 * On AIX, you get this message when running Emacs: | |
2319 | |
2320 Could not load program emacs | |
2321 Symbol smtcheckinit in csh is undefined | |
2322 Error was: Exec format error | |
2323 | |
2324 or this one: | |
2325 | |
2326 Could not load program .emacs | |
2327 Symbol _system_con in csh is undefined | |
2328 Symbol _fp_trapsta in csh is undefined | |
2329 Error was: Exec format error | |
2330 | |
2331 These can happen when you try to run on AIX 3.2.5 a program that was | |
2332 compiled with 3.2.4. The fix is to recompile. | |
2333 | |
2334 * On AIX, you get this compiler error message: | |
2335 | |
2336 Processing include file ./XMenuInt.h | |
2337 1501-106: (S) Include file X11/Xlib.h not found. | |
2338 | |
2339 This means your system was installed with only the X11 runtime i.d | |
2340 libraries. You have to find your sipo (bootable tape) and install | |
2341 X11Dev... with smit. | |
2342 | |
2343 * You "lose characters" after typing Compose Character key. | |
2344 | |
2345 This is because the Compose Character key is defined as the keysym | |
2346 Multi_key, and Emacs (seeing that) does the proper X11 | |
2347 character-composition processing. If you don't want your Compose key | |
2348 to do that, you can redefine it with xmodmap. | |
2349 | |
2350 For example, here's one way to turn it into a Meta key: | |
2351 | |
2352 xmodmap -e "keysym Multi_key = Meta_L" | |
2353 | |
2354 If all users at your site of a particular keyboard prefer Meta to | |
2355 Compose, you can make the remapping happen automatically by adding the | |
2356 xmodmap command to the xdm setup script for that display. | |
2357 | |
2358 * C-z just refreshes the screen instead of suspending Emacs. | |
2359 | |
2360 You are probably using a shell that doesn't support job control, even | |
2361 though the system itself is capable of it. Either use a different shell, | |
2362 or set the variable `cannot-suspend' to a non-nil value. | |
2363 | |
2364 * Watch out for .emacs files and EMACSLOADPATH environment vars | |
2365 | |
2366 These control the actions of Emacs. | |
2367 ~/.emacs is your Emacs init file. | |
2368 EMACSLOADPATH overrides which directories the function | |
2369 "load" will search. | |
2370 | |
2371 If you observe strange problems, check for these and get rid | |
2372 of them, then try again. | |
2373 | |
2374 * After running emacs once, subsequent invocations crash. | |
2375 | |
2376 Some versions of SVR4 have a serious bug in the implementation of the | |
2377 mmap () system call in the kernel; this causes emacs to run correctly | |
2378 the first time, and then crash when run a second time. | |
2379 | |
2380 Contact your vendor and ask for the mmap bug fix; in the mean time, | |
2381 you may be able to work around the problem by adding a line to your | |
2382 operating system description file (whose name is reported by the | |
2383 configure script) that reads: | |
2384 #define SYSTEM_MALLOC | |
2385 This makes Emacs use memory less efficiently, but seems to work around | |
2386 the kernel bug. | |
2387 | |
2388 * Inability to send an Alt-modified key, when Emacs is communicating | |
2389 directly with an X server. | |
2390 | |
2391 If you have tried to bind an Alt-modified key as a command, and it | |
2392 does not work to type the command, the first thing you should check is | |
2393 whether the key is getting through to Emacs. To do this, type C-h c | |
2394 followed by the Alt-modified key. C-h c should say what kind of event | |
2395 it read. If it says it read an Alt-modified key, then make sure you | |
2396 have made the key binding correctly. | |
2397 | |
2398 If C-h c reports an event that doesn't have the Alt modifier, it may | |
2399 be because your X server has no key for the Alt modifier. The X | |
2400 server that comes from MIT does not set up the Alt modifier by | |
2401 default. | |
2402 | |
2403 If your keyboard has keys named Alt, you can enable them as follows: | |
2404 | |
2405 xmodmap -e 'add mod2 = Alt_L' | |
2406 xmodmap -e 'add mod2 = Alt_R' | |
2407 | |
2408 If the keyboard has just one key named Alt, then only one of those | |
2409 commands is needed. The modifier `mod2' is a reasonable choice if you | |
2410 are using an unmodified MIT version of X. Otherwise, choose any | |
2411 modifier bit not otherwise used. | |
2412 | |
2413 If your keyboard does not have keys named Alt, you can use some other | |
2414 keys. Use the keysym command in xmodmap to turn a function key (or | |
2415 some other 'spare' key) into Alt_L or into Alt_R, and then use the | |
2416 commands show above to make them modifier keys. | |
2417 | |
2418 Note that if you have Alt keys but no Meta keys, Emacs translates Alt | |
2419 into Meta. This is because of the great importance of Meta in Emacs. | |
2420 | |
2421 * `Pid xxx killed due to text modification or page I/O error' | |
2422 | |
2423 On HP/UX, you can get that error when the Emacs executable is on an NFS | |
2424 file system. HP/UX responds this way if it tries to swap in a page and | |
2425 does not get a response from the server within a timeout whose default | |
2426 value is just ten seconds. | |
2427 | |
2428 If this happens to you, extend the timeout period. | |
2429 | |
2430 * `expand-file-name' fails to work on any but the machine you dumped Emacs on. | |
2431 | |
2432 On Ultrix, if you use any of the functions which look up information | |
2433 in the passwd database before dumping Emacs (say, by using | |
2434 expand-file-name in site-init.el), then those functions will not work | |
2435 in the dumped Emacs on any host but the one Emacs was dumped on. | |
2436 | |
2437 The solution? Don't use expand-file-name in site-init.el, or in | |
2438 anything it loads. Yuck - some solution. | |
2439 | |
2440 I'm not sure why this happens; if you can find out exactly what is | |
2441 going on, and perhaps find a fix or a workaround, please let us know. | |
2442 Perhaps the YP functions cache some information, the cache is included | |
2443 in the dumped Emacs, and is then inaccurate on any other host. | |
2444 | |
2445 * On some variants of SVR4, Emacs does not work at all with X. | |
2446 | |
2447 Try defining BROKEN_FIONREAD in your config.h file. If this solves | |
2448 the problem, please send a bug report to tell us this is needed; be | |
2449 sure to say exactly what type of machine and system you are using. | |
2450 | |
2451 * Linking says that the functions insque and remque are undefined. | |
2452 | |
2453 Change oldXMenu/Makefile by adding insque.o to the variable OBJS. | |
2454 | |
2455 * Emacs fails to understand most Internet host names, even though | |
2456 the names work properly with other programs on the same system. | |
2457 * Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0. | |
2458 * GNUs can't make contact with the specified host for nntp. | |
2459 | |
2460 This typically happens on Suns and other systems that use shared | |
2461 libraries. The cause is that the site has installed a version of the | |
2462 shared library which uses a name server--but has not installed a | |
2463 similar version of the unshared library which Emacs uses. | |
2464 | |
2465 The result is that most programs, using the shared library, work with | |
2466 the nameserver, but Emacs does not. | |
2467 | |
2468 The fix is to install an unshared library that corresponds to what you | |
2469 installed in the shared library, and then relink Emacs. | |
2470 | |
2471 On SunOS 4.1, simply define HAVE_RES_INIT. | |
2472 | |
2473 If you have already installed the name resolver in the file libresolv.a, | |
2474 then you need to compile Emacs to use that library. The easiest way to | |
2475 do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE | |
2476 or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro | |
2477 that is already in use in your configuration to supply some other libraries, | |
2478 be careful not to lose the others. | |
2479 | |
2480 Thus, you could start by adding this to config.h: | |
2481 | |
2482 #define LIBS_SYSTEM -lresolv | |
2483 | |
2484 Then if this gives you an error for redefining a macro, and you see that | |
2485 the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h | |
2486 again to say this: | |
2487 | |
2488 #define LIBS_SYSTEM -lresolv -lfoo -lbar | |
2489 | |
2490 * On a Sun running SunOS 4.1.1, you get this error message from GNU ld: | |
2491 | |
2492 /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment | |
2493 | |
2494 The problem is in the Sun shared C library, not in GNU ld. | |
2495 | |
2496 The solution is to install Patch-ID# 100267-03 from Sun. | |
2497 | |
2498 * Self documentation messages are garbled. | |
2499 | |
2500 This means that the file `etc/DOC-...' doesn't properly correspond | |
2501 with the Emacs executable. Redumping Emacs and then installing the | |
2502 corresponding pair of files should fix the problem. | |
2503 | |
2504 * Trouble using ptys on AIX. | |
2505 | |
2506 People often install the pty devices on AIX incorrectly. | |
2507 Use `smit pty' to reinstall them properly. | |
2508 | |
2509 * Shell mode on HP/UX gives the message, "`tty`: Ambiguous". | |
2510 | |
2511 christos@theory.tn.cornell.edu says: | |
2512 | |
2513 The problem is that in your .cshrc you have something that tries to | |
2514 execute `tty`. If you are not running the shell on a real tty then | |
2515 tty will print "not a tty". Csh expects one word in some places, | |
2516 but tty is giving it back 3. | |
2517 | |
2518 The solution is to add a pair of quotes around `tty` to make it a single | |
2519 word: | |
2520 | |
2521 if (`tty` == "/dev/console") | |
2522 | |
2523 should be changed to: | |
2524 | |
2525 if ("`tty`" == "/dev/console") | |
2526 | |
2527 Even better, move things that set up terminal sections out of .cshrc | |
2528 and into .login. | |
2529 | |
2530 * Using X Windows, control-shift-leftbutton makes Emacs hang. | |
2531 | |
2532 Use the shell command `xset bc' to make the old X Menu package work. | |
2533 | |
2534 * Emacs running under X Windows does not handle mouse clicks. | |
2535 * `emacs -geometry 80x20' finds a file named `80x20'. | |
2536 | |
2537 One cause of such problems is having (setq term-file-prefix nil) in | |
2538 your .emacs file. Another cause is a bad value of EMACSLOADPATH in | |
2539 the environment. | |
2540 | |
2541 * Emacs gets error message from linker on Sun. | |
2542 | |
2543 If the error message says that a symbol such as `f68881_used' or | |
2544 `ffpa_used' or `start_float' is undefined, this probably indicates | |
2545 that you have compiled some libraries, such as the X libraries, | |
2546 with a floating point option other than the default. | |
2547 | |
2548 It's not terribly hard to make this work with small changes in | |
2549 crt0.c together with linking with Fcrt1.o, Wcrt1.o or Mcrt1.o. | |
2550 However, the easiest approach is to build Xlib with the default | |
2551 floating point option: -fsoft. | |
2552 | |
2553 * Emacs fails to get default settings from X Windows server. | |
2554 | |
2555 The X library in X11R4 has a bug; it interchanges the 2nd and 3rd | |
2556 arguments to XGetDefaults. Define the macro XBACKWARDS in config.h to | |
2557 tell Emacs to compensate for this. | |
2558 | |
2559 I don't believe there is any way Emacs can determine for itself | |
2560 whether this problem is present on a given system. | |
2561 | |
2562 * Keyboard input gets confused after a beep when using a DECserver | |
2563 as a concentrator. | |
2564 | |
2565 This problem seems to be a matter of configuring the DECserver to use | |
2566 7 bit characters rather than 8 bit characters. | |
2567 | |
2568 * M-x shell persistently reports "Process shell exited abnormally with code 1". | |
2569 | |
2570 This happened on Suns as a result of what is said to be a bug in Sunos | |
2571 version 4.0.x. The only fix was to reboot the machine. | |
2572 | |
2573 * Programs running under terminal emulator do not recognize `emacs' | |
2574 terminal type. | |
2575 | |
2576 The cause of this is a shell startup file that sets the TERMCAP | |
2577 environment variable. The terminal emulator uses that variable to | |
2578 provide the information on the special terminal type that Emacs | |
2579 emulates. | |
2580 | |
2581 Rewrite your shell startup file so that it does not change TERMCAP | |
2582 in such a case. You could use the following conditional which sets | |
2583 it only if it is undefined. | |
2584 | |
2585 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file | |
2586 | |
2587 Or you could set TERMCAP only when you set TERM--which should not | |
2588 happen in a non-login shell. | |
2589 | |
2590 * X Windows doesn't work if DISPLAY uses a hostname. | |
2591 | |
2592 People have reported kernel bugs in certain systems that cause Emacs | |
2593 not to work with X Windows if DISPLAY is set using a host name. But | |
2594 the problem does not occur if DISPLAY is set to `unix:0.0'. I think | |
2595 the bug has to do with SIGIO or FIONREAD. | |
2596 | |
2597 You may be able to compensate for the bug by doing (set-input-mode nil nil). | |
2598 However, that has the disadvantage of turning off interrupts, so that | |
2599 you are unable to quit out of a Lisp program by typing C-g. | |
2600 | |
2601 The easy way to do this is to put | |
2602 | |
2603 (setq x-sigio-bug t) | |
2604 | |
2605 in your site-init.el file. | |
2606 | |
2607 * Problem with remote X server on Suns. | |
2608 | |
2609 On a Sun, running Emacs on one machine with the X server on another | |
2610 may not work if you have used the unshared system libraries. This | |
2611 is because the unshared libraries fail to use YP for host name lookup. | |
2612 As a result, the host name you specify may not be recognized. | |
2613 | |
2614 * Shell mode ignores interrupts on Apollo Domain | |
2615 | |
2616 You may find that M-x shell prints the following message: | |
2617 | |
2618 Warning: no access to tty; thus no job control in this shell... | |
2619 | |
2620 This can happen if there are not enough ptys on your system. | |
2621 Here is how to make more of them. | |
2622 | |
2623 % cd /dev | |
2624 % ls pty* | |
2625 # shows how many pty's you have. I had 8, named pty0 to pty7) | |
2626 % /etc/crpty 8 | |
2627 # creates eight new pty's | |
2628 | |
2629 * Fatal signal in the command temacs -l loadup inc dump | |
2630 | |
2631 This command is the final stage of building Emacs. It is run by the | |
2632 Makefile in the src subdirectory, or by build.com on VMS. | |
2633 | |
2634 It has been known to get fatal errors due to insufficient swapping | |
2635 space available on the machine. | |
2636 | |
2637 On 68000's, it has also happened because of bugs in the | |
2638 subroutine `alloca'. Verify that `alloca' works right, even | |
2639 for large blocks (many pages). | |
2640 | |
2641 * test-distrib says that the distribution has been clobbered | |
2642 * or, temacs prints "Command key out of range 0-127" | |
2643 * or, temacs runs and dumps emacs, but emacs totally fails to work. | |
2644 * or, temacs gets errors dumping emacs | |
2645 | |
2646 This can be because the .elc files have been garbled. Do not be | |
2647 fooled by the fact that most of a .elc file is text: these are | |
2648 binary files and can contain all 256 byte values. | |
2649 | |
2650 In particular `shar' cannot be used for transmitting GNU Emacs. | |
2651 It typically truncates "lines". What appear to be "lines" in | |
2652 a binary file can of course be of any length. Even once `shar' | |
2653 itself is made to work correctly, `sh' discards null characters | |
2654 when unpacking the shell archive. | |
2655 | |
2656 I have also seen character \177 changed into \377. I do not know | |
2657 what transfer means caused this problem. Various network | |
2658 file transfer programs are suspected of clobbering the high bit. | |
2659 | |
2660 If you have a copy of Emacs that has been damaged in its | |
2661 nonprinting characters, you can fix them: | |
2662 | |
2663 1) Record the names of all the .elc files. | |
2664 2) Delete all the .elc files. | |
2665 3) Recompile alloc.c with a value of PURESIZE twice as large. | |
2666 (See puresize.h.) You might as well save the old alloc.o. | |
2667 4) Remake emacs. It should work now. | |
2668 5) Running emacs, do Meta-x byte-compile-file repeatedly | |
2669 to recreate all the .elc files that used to exist. | |
2670 You may need to increase the value of the variable | |
2671 max-lisp-eval-depth to succeed in running the compiler interpreted | |
2672 on certain .el files. 400 was sufficient as of last report. | |
2673 6) Reinstall the old alloc.o (undoing changes to alloc.c if any) | |
2674 and remake temacs. | |
2675 7) Remake emacs. It should work now, with valid .elc files. | |
2676 | |
2677 * temacs prints "Pure Lisp storage exhausted" | |
2678 | |
2679 This means that the Lisp code loaded from the .elc and .el | |
2680 files during temacs -l loadup inc dump took up more | |
2681 space than was allocated. | |
2682 | |
2683 This could be caused by | |
2684 1) adding code to the preloaded Lisp files | |
2685 2) adding more preloaded files in loadup.el | |
2686 3) having a site-init.el or site-load.el which loads files. | |
2687 Note that ANY site-init.el or site-load.el is nonstandard; | |
2688 if you have received Emacs from some other site | |
2689 and it contains a site-init.el or site-load.el file, consider | |
2690 deleting that file. | |
2691 4) getting the wrong .el or .elc files | |
2692 (not from the directory you expected). | |
2693 5) deleting some .elc files that are supposed to exist. | |
2694 This would cause the source files (.el files) to be | |
2695 loaded instead. They take up more room, so you lose. | |
2696 6) a bug in the Emacs distribution which underestimates | |
2697 the space required. | |
2698 | |
2699 If the need for more space is legitimate, change the definition | |
2700 of PURESIZE in puresize.h. | |
2701 | |
2702 But in some of the cases listed above, this problem is a consequence | |
2703 of something else that is wrong. Be sure to check and fix the real | |
2704 problem. | |
2705 | |
2706 * Changes made to .el files do not take effect. | |
2707 | |
2708 You may have forgotten to recompile them into .elc files. | |
2709 Then the old .elc files will be loaded, and your changes | |
2710 will not be seen. To fix this, do M-x byte-recompile-directory | |
2711 and specify the directory that contains the Lisp files. | |
2712 | |
2713 Emacs should print a warning when loading a .elc file which is older | |
2714 than the corresponding .el file. | |
2715 | |
2716 * The dumped Emacs crashes when run, trying to write pure data. | |
2717 | |
2718 Two causes have been seen for such problems. | |
2719 | |
2720 1) On a system where getpagesize is not a system call, it is defined | |
2721 as a macro. If the definition (in both unexec.c and malloc.c) is wrong, | |
2722 it can cause problems like this. You might be able to find the correct | |
2723 value in the man page for a.out (5). | |
2724 | |
2725 2) Some systems allocate variables declared static among the | |
2726 initialized variables. Emacs makes all initialized variables in most | |
2727 of its files pure after dumping, but the variables declared static and | |
2728 not initialized are not supposed to be pure. On these systems you | |
2729 may need to add "#define static" to the m- or the s- file. | |
2730 | |
2731 * Compilation errors on VMS. | |
2732 | |
2733 You will get warnings when compiling on VMS because there are | |
2734 variable names longer than 32 (or whatever it is) characters. | |
2735 This is not an error. Ignore it. | |
2736 | |
2737 VAX C does not support #if defined(foo). Uses of this construct | |
2738 were removed, but some may have crept back in. They must be rewritten. | |
2739 | |
2740 There is a bug in the C compiler which fails to sign extend characters | |
2741 in conditional expressions. The bug is: | |
2742 char c = -1, d = 1; | |
2743 int i; | |
2744 | |
2745 i = d ? c : d; | |
2746 The result is i == 255; the fix is to typecast the char in the | |
2747 conditional expression as an (int). Known occurrences of such | |
2748 constructs in Emacs have been fixed. | |
2749 | |
2750 * rmail gets error getting new mail | |
2751 | |
2752 rmail gets new mail from /usr/spool/mail/$USER using a program | |
2753 called `movemail'. This program interlocks with /bin/mail using | |
2754 the protocol defined by /bin/mail. | |
2755 | |
2756 There are two different protocols in general use. One of them uses | |
2757 the `flock' system call. The other involves creating a lock file; | |
2758 `movemail' must be able to write in /usr/spool/mail in order to do | |
2759 this. You control which one is used by defining, or not defining, | |
2760 the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes. | |
2761 IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR | |
2762 SYSTEM, YOU CAN LOSE MAIL! | |
2763 | |
2764 If your system uses the lock file protocol, and fascist restrictions | |
2765 prevent ordinary users from writing the lock files in /usr/spool/mail, | |
2766 you may need to make `movemail' setgid to a suitable group such as | |
2767 `mail'. You can use these commands (as root): | |
2768 | |
2769 chgrp mail movemail | |
2770 chmod 2755 movemail | |
2771 | |
2772 If your system uses the lock file protocol, and fascist restrictions | |
2773 prevent ordinary users from writing the lock files in /usr/spool/mail, | |
2774 you may need to make `movemail' setgid to a suitable group such as | |
2775 `mail'. To do this, use the following commands (as root) after doing the | |
2776 make install. | |
2777 | |
2778 chgrp mail movemail | |
2779 chmod 2755 movemail | |
2780 | |
2781 Installation normally copies movemail from the build directory to an | |
2782 installation directory which is usually under /usr/local/lib. The | |
2783 installed copy of movemail is usually in the directory | |
2784 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and | |
2785 mode of the installed copy; changing the group and mode of the build | |
2786 directory copy is ineffective. | |
2787 | |
2788 * Emacs spontaneously displays "I-search: " at the bottom of the screen. | |
2789 | |
2790 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being | |
2791 used. C-s/C-q flow control is bad for Emacs editors because it takes | |
2792 away C-s and C-q as user commands. Since editors do not output long | |
2793 streams of text without user commands, there is no need for a | |
2794 user-issuable "stop output" command in an editor; therefore, a | |
2795 properly designed flow control mechanism would transmit all possible | |
2796 input characters without interference. Designing such a mechanism is | |
2797 easy, for a person with at least half a brain. | |
2798 | |
2799 There are three possible reasons why flow control could be taking place: | |
2800 | |
2801 1) Terminal has not been told to disable flow control | |
2802 2) Insufficient padding for the terminal in use | |
2803 3) Some sort of terminal concentrator or line switch is responsible | |
2804 | |
2805 First of all, many terminals have a set-up mode which controls whether | |
2806 they generate XON/XOFF flow control characters. This must be set to | |
2807 "no XON/XOFF" in order for Emacs to work. Sometimes there is an | |
2808 escape sequence that the computer can send to turn flow control off | |
2809 and on. If so, perhaps the termcap `ti' string should turn flow | |
2810 control off, and the `te' string should turn it on. | |
2811 | |
2812 Once the terminal has been told "no flow control", you may find it | |
2813 needs more padding. The amount of padding Emacs sends is controlled | |
2814 by the termcap entry for the terminal in use, and by the output baud | |
2815 rate as known by the kernel. The shell command `stty' will print | |
2816 your output baud rate; `stty' with suitable arguments will set it if | |
2817 it is wrong. Setting to a higher speed causes increased padding. If | |
2818 the results are wrong for the correct speed, there is probably a | |
2819 problem in the termcap entry. You must speak to a local Unix wizard | |
2820 to fix this. Perhaps you are just using the wrong terminal type. | |
2821 | |
2822 For terminals that lack a "no flow control" mode, sometimes just | |
2823 giving lots of padding will prevent actual generation of flow control | |
2824 codes. You might as well try it. | |
2825 | |
2826 If you are really unlucky, your terminal is connected to the computer | |
2827 through a concentrator which sends XON/XOFF flow control to the | |
2828 computer, or it insists on sending flow control itself no matter how | |
2829 much padding you give it. Unless you can figure out how to turn flow | |
2830 control off on this concentrator (again, refer to your local wizard), | |
2831 you are screwed! You should have the terminal or concentrator | |
2832 replaced with a properly designed one. In the mean time, some drastic | |
2833 measures can make Emacs semi-work. | |
2834 | |
2835 You can make Emacs ignore C-s and C-q and let the operating system | |
2836 handle them. To do this on a per-session basis, just type M-x | |
2837 enable-flow-control RET. You will see a message that C-\ and C-^ are | |
2838 now translated to C-s and C-q. (Use the same command M-x | |
2839 enable-flow-control to turn *off* this special mode. It toggles flow | |
2840 control handling.) | |
2841 | |
2842 If C-\ and C-^ are inconvenient for you (for example, if one of them | |
2843 is the escape character of your terminal concentrator), you can choose | |
2844 other characters by setting the variables flow-control-c-s-replacement | |
2845 and flow-control-c-q-replacement. But choose carefully, since all | |
2846 other control characters are already used by emacs. | |
2847 | |
2848 IMPORTANT: if you type C-s by accident while flow control is enabled, | |
2849 Emacs output will freeze, and you will have to remember to type C-q in | |
2850 order to continue. | |
2851 | |
2852 If you work in an environment where a majority of terminals of a | |
2853 certain type are flow control hobbled, you can use the function | |
2854 `enable-flow-control-on' to turn on this flow control avoidance scheme | |
2855 automatically. Here is an example: | |
2856 | |
2857 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131") | |
2858 | |
2859 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled | |
2860 and good vt200 terminals), you can still run enable-flow-control | |
2861 manually. | |
2862 | |
2863 I have no intention of ever redesigning the Emacs command set for the | |
2864 assumption that terminals use C-s/C-q flow control. XON/XOFF flow | |
2865 control technique is a bad design, and terminals that need it are bad | |
2866 merchandise and should not be purchased. Now that X is becoming | |
2867 widespread, XON/XOFF seems to be on the way out. If you can get some | |
2868 use out of GNU Emacs on inferior terminals, more power to you, but I | |
2869 will not make Emacs worse for properly designed systems for the sake | |
2870 of inferior systems. | |
2871 | |
2872 * Control-S and Control-Q commands are ignored completely. | |
2873 | |
2874 For some reason, your system is using brain-damaged C-s/C-q flow | |
2875 control despite Emacs's attempts to turn it off. Perhaps your | |
2876 terminal is connected to the computer through a concentrator | |
2877 that wants to use flow control. | |
2878 | |
2879 You should first try to tell the concentrator not to use flow control. | |
2880 If you succeed in this, try making the terminal work without | |
2881 flow control, as described in the preceding section. | |
2882 | |
2883 If that line of approach is not successful, map some other characters | |
2884 into C-s and C-q using keyboard-translate-table. The example above | |
2885 shows how to do this with C-^ and C-\. | |
2886 | |
2887 * Control-S and Control-Q commands are ignored completely on a net connection. | |
2888 | |
2889 Some versions of rlogin (and possibly telnet) do not pass flow | |
2890 control characters to the remote system to which they connect. | |
2891 On such systems, emacs on the remote system cannot disable flow | |
2892 control on the local system. | |
2893 | |
2894 One way to cure this is to disable flow control on the local host | |
2895 (the one running rlogin, not the one running rlogind) using the | |
2896 stty command, before starting the rlogin process. On many systems, | |
2897 "stty start u stop u" will do this. | |
2898 | |
2899 Some versions of tcsh will prevent even this from working. One way | |
2900 around this is to start another shell before starting rlogin, and | |
2901 issue the stty command to disable flow control from that shell. | |
2902 | |
2903 If none of these methods work, the best solution is to type | |
2904 M-x enable-flow-control at the beginning of your emacs session, or | |
2905 if you expect the problem to continue, add a line such as the | |
2906 following to your .emacs (on the host running rlogind): | |
2907 | |
2908 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131") | |
2909 | |
2910 See the entry about spontaneous display of I-search (above) for more | |
2911 info. | |
2912 | |
2913 * Screen is updated wrong, but only on one kind of terminal. | |
2914 | |
2915 This could mean that the termcap entry you are using for that | |
2916 terminal is wrong, or it could mean that Emacs has a bug handing | |
2917 the combination of features specified for that terminal. | |
2918 | |
2919 The first step in tracking this down is to record what characters | |
2920 Emacs is sending to the terminal. Execute the Lisp expression | |
2921 (open-termscript "./emacs-script") to make Emacs write all | |
2922 terminal output into the file ~/emacs-script as well; then do | |
2923 what makes the screen update wrong, and look at the file | |
2924 and decode the characters using the manual for the terminal. | |
2925 There are several possibilities: | |
2926 | |
2927 1) The characters sent are correct, according to the terminal manual. | |
2928 | |
2929 In this case, there is no obvious bug in Emacs, and most likely you | |
2930 need more padding, or possibly the terminal manual is wrong. | |
2931 | |
2932 2) The characters sent are incorrect, due to an obscure aspect | |
2933 of the terminal behavior not described in an obvious way | |
2934 by termcap. | |
2935 | |
2936 This case is hard. It will be necessary to think of a way for | |
2937 Emacs to distinguish between terminals with this kind of behavior | |
2938 and other terminals that behave subtly differently but are | |
2939 classified the same by termcap; or else find an algorithm for | |
2940 Emacs to use that avoids the difference. Such changes must be | |
2941 tested on many kinds of terminals. | |
2942 | |
2943 3) The termcap entry is wrong. | |
2944 | |
2945 See the file etc/TERMS for information on changes | |
2946 that are known to be needed in commonly used termcap entries | |
2947 for certain terminals. | |
2948 | |
2949 4) The characters sent are incorrect, and clearly cannot be | |
2950 right for any terminal with the termcap entry you were using. | |
2951 | |
2952 This is unambiguously an Emacs bug, and can probably be fixed | |
2953 in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c. | |
2954 | |
2955 * Output from Control-V is slow. | |
2956 | |
2957 On many bit-map terminals, scrolling operations are fairly slow. | |
2958 Often the termcap entry for the type of terminal in use fails | |
2959 to inform Emacs of this. The two lines at the bottom of the screen | |
2960 before a Control-V command are supposed to appear at the top after | |
2961 the Control-V command. If Emacs thinks scrolling the lines is fast, | |
2962 it will scroll them to the top of the screen. | |
2963 | |
2964 If scrolling is slow but Emacs thinks it is fast, the usual reason is | |
2965 that the termcap entry for the terminal you are using does not | |
2966 specify any padding time for the `al' and `dl' strings. Emacs | |
2967 concludes that these operations take only as much time as it takes to | |
2968 send the commands at whatever line speed you are using. You must | |
2969 fix the termcap entry to specify, for the `al' and `dl', as much | |
2970 time as the operations really take. | |
2971 | |
2972 Currently Emacs thinks in terms of serial lines which send characters | |
2973 at a fixed rate, so that any operation which takes time for the | |
2974 terminal to execute must also be padded. With bit-map terminals | |
2975 operated across networks, often the network provides some sort of | |
2976 flow control so that padding is never needed no matter how slow | |
2977 an operation is. You must still specify a padding time if you want | |
2978 Emacs to realize that the operation takes a long time. This will | |
2979 cause padding characters to be sent unnecessarily, but they do | |
2980 not really cost much. They will be transmitted while the scrolling | |
2981 is happening and then discarded quickly by the terminal. | |
2982 | |
2983 Most bit-map terminals provide commands for inserting or deleting | |
2984 multiple lines at once. Define the `AL' and `DL' strings in the | |
2985 termcap entry to say how to do these things, and you will have | |
2986 fast output without wasted padding characters. These strings should | |
2987 each contain a single %-spec saying how to send the number of lines | |
2988 to be scrolled. These %-specs are like those in the termcap | |
2989 `cm' string. | |
2990 | |
2991 You should also define the `IC' and `DC' strings if your terminal | |
2992 has a command to insert or delete multiple characters. These | |
2993 take the number of positions to insert or delete as an argument. | |
2994 | |
2995 A `cs' string to set the scrolling region will reduce the amount | |
2996 of motion you see on the screen when part of the screen is scrolled. | |
2997 | |
2998 * Your Delete key sends a Backspace to the terminal, using an AIXterm. | |
2999 | |
3000 The solution is to include in your .Xdefaults the lines: | |
3001 | |
3002 *aixterm.Translations: #override <Key>BackSpace: string(0x7f) | |
3003 aixterm*ttyModes: erase ^? | |
3004 | |
3005 This makes your Backspace key send DEL (ASCII 127). | |
3006 | |
3007 * You type Control-H (Backspace) expecting to delete characters. | |
3008 | |
3009 Put `stty dec' in your .login file and your problems will disappear | |
3010 after a day or two. | |
3011 | |
3012 The choice of Backspace for erasure was based on confusion, caused by | |
3013 the fact that backspacing causes erasure (later, when you type another | |
3014 character) on most display terminals. But it is a mistake. Deletion | |
3015 of text is not the same thing as backspacing followed by failure to | |
3016 overprint. I do not wish to propagate this confusion by conforming | |
3017 to it. | |
3018 | |
3019 For this reason, I believe `stty dec' is the right mode to use, | |
3020 and I have designed Emacs to go with that. If there were a thousand | |
3021 other control characters, I would define Control-h to delete as well; | |
3022 but there are not very many other control characters, and I think | |
3023 that providing the most mnemonic possible Help character is more | |
3024 important than adapting to people who don't use `stty dec'. | |
3025 | |
3026 If you are obstinate about confusing buggy overprinting with deletion, | |
3027 you can redefine Backspace in your .emacs file: | |
3028 (global-set-key "\b" 'delete-backward-char) | |
3029 You can probably access help-command via f1. | |
3030 | |
3031 * Editing files through RFS gives spurious "file has changed" warnings. | |
3032 It is possible that a change in Emacs 18.37 gets around this problem, | |
3033 but in case not, here is a description of how to fix the RFS bug that | |
3034 causes it. | |
3035 | |
3036 There was a serious pair of bugs in the handling of the fsync() system | |
3037 call in the RFS server. | |
3038 | |
3039 The first is that the fsync() call is handled as another name for the | |
3040 close() system call (!!). It appears that fsync() is not used by very | |
3041 many programs; Emacs version 18 does an fsync() before closing files | |
3042 to make sure that the bits are on the disk. | |
3043 | |
3044 This is fixed by the enclosed patch to the RFS server. | |
3045 | |
3046 The second, more serious problem, is that fsync() is treated as a | |
3047 non-blocking system call (i.e., it's implemented as a message that | |
3048 gets sent to the remote system without waiting for a reply). Fsync is | |
3049 a useful tool for building atomic file transactions. Implementing it | |
3050 as a non-blocking RPC call (when the local call blocks until the sync | |
3051 is done) is a bad idea; unfortunately, changing it will break the RFS | |
3052 protocol. No fix was supplied for this problem. | |
3053 | |
3054 (as always, your line numbers may vary) | |
3055 | |
3056 % rcsdiff -c -r1.2 serversyscall.c | |
3057 RCS file: RCS/serversyscall.c,v | |
3058 retrieving revision 1.2 | |
3059 diff -c -r1.2 serversyscall.c | |
3060 *** /tmp/,RCSt1003677 Wed Jan 28 15:15:02 1987 | |
3061 --- serversyscall.c Wed Jan 28 15:14:48 1987 | |
3062 *************** | |
3063 *** 163,169 **** | |
3064 /* | |
3065 * No return sent for close or fsync! | |
3066 */ | |
3067 ! if (syscall == RSYS_close || syscall == RSYS_fsync) | |
3068 proc->p_returnval = deallocate_fd(proc, msg->m_args[0]); | |
3069 else | |
3070 { | |
3071 --- 166,172 ---- | |
3072 /* | |
3073 * No return sent for close or fsync! | |
3074 */ | |
3075 ! if (syscall == RSYS_close) | |
3076 proc->p_returnval = deallocate_fd(proc, msg->m_args[0]); | |
3077 else | |
3078 { | |
3079 | |
3080 * Vax C compiler bugs affecting Emacs. | |
3081 | |
3082 You may get one of these problems compiling Emacs: | |
3083 | |
3084 foo.c line nnn: compiler error: no table entry for op STASG | |
3085 foo.c: fatal error in /lib/ccom | |
3086 | |
3087 These are due to bugs in the C compiler; the code is valid C. | |
3088 Unfortunately, the bugs are unpredictable: the same construct | |
3089 may compile properly or trigger one of these bugs, depending | |
3090 on what else is in the source file being compiled. Even changes | |
3091 in header files that should not affect the file being compiled | |
3092 can affect whether the bug happens. In addition, sometimes files | |
3093 that compile correctly on one machine get this bug on another machine. | |
3094 | |
3095 As a result, it is hard for me to make sure this bug will not affect | |
3096 you. I have attempted to find and alter these constructs, but more | |
3097 can always appear. However, I can tell you how to deal with it if it | |
3098 should happen. The bug comes from having an indexed reference to an | |
3099 array of Lisp_Objects, as an argument in a function call: | |
3100 Lisp_Object *args; | |
3101 ... | |
3102 ... foo (5, args[i], ...)... | |
3103 putting the argument into a temporary variable first, as in | |
3104 Lisp_Object *args; | |
3105 Lisp_Object tem; | |
3106 ... | |
3107 tem = args[i]; | |
3108 ... foo (r, tem, ...)... | |
3109 causes the problem to go away. | |
3110 The `contents' field of a Lisp vector is an array of Lisp_Objects, | |
3111 so you may see the problem happening with indexed references to that. | |
3112 | |
3113 * 68000 C compiler problems | |
3114 | |
3115 Various 68000 compilers have different problems. | |
3116 These are some that have been observed. | |
3117 | |
3118 ** Using value of assignment expression on union type loses. | |
3119 This means that x = y = z; or foo (x = z); does not work | |
3120 if x is of type Lisp_Object. | |
3121 | |
3122 ** "cannot reclaim" error. | |
3123 | |
3124 This means that an expression is too complicated. You get the correct | |
3125 line number in the error message. The code must be rewritten with | |
3126 simpler expressions. | |
3127 | |
3128 ** XCONS, XSTRING, etc macros produce incorrect code. | |
3129 | |
3130 If temacs fails to run at all, this may be the cause. | |
3131 Compile this test program and look at the assembler code: | |
3132 | |
3133 struct foo { char x; unsigned int y : 24; }; | |
3134 | |
3135 lose (arg) | |
3136 struct foo arg; | |
3137 { | |
3138 test ((int *) arg.y); | |
3139 } | |
3140 | |
3141 If the code is incorrect, your compiler has this problem. | |
3142 In the XCONS, etc., macros in lisp.h you must replace (a).u.val with | |
3143 ((a).u.val + coercedummy) where coercedummy is declared as int. | |
3144 | |
3145 This problem will not happen if the m-...h file for your type | |
3146 of machine defines NO_UNION_TYPE. That is the recommended setting now. | |
3147 | |
3148 * C compilers lose on returning unions | |
3149 | |
3150 I hear that some C compilers cannot handle returning a union type. | |
3151 Most of the functions in GNU Emacs return type Lisp_Object, which is | |
3152 defined as a union on some rare architectures. | |
3153 | |
3154 This problem will not happen if the m-...h file for your type | |
3155 of machine defines NO_UNION_TYPE. | |
3156 | |
41836 | 3157 |
3158 Local variables: | |
3159 mode: outline | |
3160 paragraph-separate: "[ ]*$" | |
3161 end: |