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