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