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