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