Mercurial > emacs
annotate etc/PROBLEMS @ 31378:f44a8a68506f
64-bit on Solaris now works.
author | Dave Love <fx@gnu.org> |
---|---|
date | Mon, 04 Sep 2000 16:25:18 +0000 |
parents | a7963e66c555 |
children | 2c900086fb10 |
rev | line source |
---|---|
25853 | 1 This file describes various problems that have been encountered |
2 in compiling, installing and running GNU Emacs. | |
3 | |
4 * Error "conflicting types for `initstate'" compiling with GCC on Irix 6. | |
5 | |
6 Install GCC 2.95 or a newer version, and this problem should go away. | |
7 It is possible that this problem results from upgrading the operating | |
8 system without reinstalling GCC; so you could also try reinstalling | |
9 the same version of GCC, and telling us whether that fixes the problem. | |
10 | |
11 * On Solaris 7, Emacs gets a segmentation fault when starting up using X. | |
12 | |
13 This results from Sun patch 107058-01 (SunOS 5.7: Patch for | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
14 assembler) if you use GCC version 2.7 or later. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
15 To work around it, either install patch 106950-03 or later, |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
16 or uninstall patch 107058-01, or install the GNU Binutils. |
25853 | 17 Then recompile Emacs, and it should work. |
18 | |
19 * With X11R6.4, public-patch-3, Emacs crashes at startup. | |
20 | |
21 Reportedly this patch in X fixes the problem. | |
22 | |
23 --- xc/lib/X11/imInt.c~ Wed Jun 30 13:31:56 1999 | |
24 +++ xc/lib/X11/imInt.c Thu Jul 1 15:10:27 1999 | |
25 @@ -1,4 +1,4 @@ | |
26 -/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */ | |
27 +/* $TOG: imInt.c /main/5 1998/05/30 21:11:16 kaleb $ */ | |
28 /****************************************************************** | |
29 | |
30 Copyright 1992, 1993, 1994 by FUJITSU LIMITED | |
31 @@ -166,8 +166,8 @@ | |
32 _XimMakeImName(lcd) | |
33 XLCd lcd; | |
34 { | |
35 - char* begin; | |
36 - char* end; | |
37 + char* begin = NULL; | |
38 + char* end = NULL; | |
39 char* ret; | |
40 int i = 0; | |
41 char* ximmodifier = XIMMODIFIER; | |
42 @@ -182,7 +182,11 @@ | |
43 } | |
44 ret = Xmalloc(end - begin + 2); | |
45 if (ret != NULL) { | |
46 - (void)strncpy(ret, begin, end - begin + 1); | |
47 + if (begin != NULL) { | |
48 + (void)strncpy(ret, begin, end - begin + 1); | |
49 + } else { | |
50 + ret[0] = '\0'; | |
51 + } | |
52 ret[end - begin + 1] = '\0'; | |
53 } | |
54 return ret; | |
55 | |
56 | |
57 * Emacs crashes on Irix 6.5 on the SGI R10K, when compiled with GCC. | |
58 | |
59 This seems to be fixed in GCC 2.95. | |
60 | |
61 * Emacs crashes in utmpname on Irix 5.3. | |
62 | |
63 This problem is fixed in Patch 3175 for Irix 5.3. | |
64 It is also fixed in Irix versions 6.2 and up. | |
65 | |
66 * On Solaris, CTRL-t is ignored by Emacs when you use | |
67 the fr.ISO-8859-15 locale (and maybe other related locales). | |
68 | |
69 You can fix this by editing the file: | |
70 | |
71 /usr/openwin/lib/locale/iso8859-15/Compose | |
72 | |
73 Near the bottom there is a line that reads: | |
74 | |
75 Ctrl<t> <quotedbl> <Y> : "\276" threequarters | |
76 | |
77 that should read: | |
78 | |
79 Ctrl<T> <quotedbl> <Y> : "\276" threequarters | |
80 | |
81 Note the lower case <t>. Changing this line should make C-t work. | |
82 | |
83 * Emacs on Digital Unix 4.0 fails to build, giving error message | |
84 Invalid dimension for the charset-ID 160 | |
85 | |
86 This is due to a bug or an installation problem in GCC 2.8.0. | |
87 Installing a more recent version of GCC fixes the problem. | |
88 | |
89 * Buffers from `with-output-to-temp-buffer' get set up in Help mode. | |
90 | |
91 Changes in Emacs 20.4 to the hooks used by that function cause | |
92 problems for some packages, specifically BBDB. See the function's | |
93 documentation for the hooks involved. BBDB 2.00.06 fixes the problem. | |
94 | |
95 * Under X, C-v and/or other keys don't work. | |
96 | |
97 These may have been intercepted by your window manager. In | |
98 particular, AfterStep 1.6 is reported to steal C-v in its default | |
99 configuration. Various Meta keys are also likely to be taken by the | |
100 configuration of the `feel'. See the WM's documentation for how to | |
101 change this. | |
102 | |
103 * When using Exceed, fonts sometimes appear too tall. | |
104 | |
105 When the display is set to an Exceed X-server and fonts are specified | |
106 (either explicitly with the -fn option or implicitly with X resources) | |
107 then the fonts may appear "too tall". The actual character sizes are | |
108 correct but there is too much vertical spacing between rows, which | |
109 gives the appearance of "double spacing". | |
110 | |
111 To prevent this, turn off the Exceed's "automatic font substitution" | |
112 feature (in the font part of the configuration window). | |
113 | |
114 * Failure in unexec while dumping emacs on Digital Unix 4.0 | |
115 | |
116 This problem manifests itself as an error message | |
117 | |
118 unexec: Bad address, writing data section to ... | |
119 | |
120 The user suspects that this happened because his X libraries | |
121 were built for an older system version, | |
122 | |
123 ./configure --x-includes=/usr/include --x-libraries=/usr/shlib | |
124 | |
125 made the problem go away. | |
126 | |
127 * No visible display on mips-sgi-irix6.2 when compiling with GCC 2.8.1. | |
128 | |
129 This problem went away after installing the latest IRIX patches | |
130 as of 8 Dec 1998. | |
131 | |
132 The same problem has been reported on Irix 6.3. | |
133 | |
134 * As of version 20.4, Emacs doesn't work properly if configured for | |
135 the Motif toolkit and linked against the free LessTif library. The | |
136 next Emacs release is expected to work with LessTif. | |
137 | |
138 * Emacs gives the error, Couldn't find per display information. | |
139 | |
140 This can result if the X server runs out of memory because Emacs uses | |
141 a large number of fonts. On systems where this happens, C-h h is | |
142 likely to cause it. | |
143 | |
144 We do not know of a way to prevent the problem. | |
145 | |
146 * Emacs makes HPUX 11.0 crash. | |
147 | |
148 This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it. | |
149 | |
150 * Emacs crashes during dumping on the HPPA machine (HPUX 10.20). | |
151 | |
152 This seems to be due to a GCC bug; it is fixed in GCC 2.8.1. | |
153 | |
154 * The Hyperbole package causes *Help* buffers not to be displayed in | |
155 Help mode due to setting `temp-buffer-show-hook' rather than using | |
156 `add-hook'. Using `(add-hook 'temp-buffer-show-hook | |
157 'help-mode-maybe)' after loading Hyperbole should fix this. | |
158 | |
159 * Versions of the PSGML package earlier than 1.0.3 (stable) or 1.1.2 | |
160 (alpha) fail to parse DTD files correctly in Emacs 20.3 and later. | |
161 Here is a patch for psgml-parse.el from PSGML 1.0.1 and, probably, | |
162 earlier versions. | |
163 | |
164 --- psgml-parse.el 1998/08/21 19:18:18 1.1 | |
165 +++ psgml-parse.el 1998/08/21 19:20:00 | |
166 @@ -2383,7 +2383,7 @@ (defun sgml-push-to-entity (entity &opti | |
167 (setq sgml-buffer-parse-state nil)) | |
168 (cond | |
169 ((stringp entity) ; a file name | |
170 - (save-excursion (insert-file-contents entity)) | |
171 + (insert-file-contents entity) | |
172 (setq default-directory (file-name-directory entity))) | |
173 ((consp (sgml-entity-text entity)) ; external id? | |
174 (let* ((extid (sgml-entity-text entity)) | |
175 | |
176 * Running TeX from AUXTeX package with Emacs 20.3 gives a Lisp error | |
177 about a read-only tex output buffer. | |
178 | |
179 This problem appeared for AUC TeX version 9.9j and some earlier | |
180 versions. Here is a patch for the file tex-buf.el in the AUC TeX | |
181 package. | |
182 | |
183 diff -c auctex/tex-buf.el~ auctex/tex-buf.el | |
184 *** auctex/tex-buf.el~ Wed Jul 29 18:35:32 1998 | |
185 --- auctex/tex-buf.el Sat Sep 5 15:20:38 1998 | |
186 *************** | |
187 *** 545,551 **** | |
188 (dir (TeX-master-directory))) | |
189 (TeX-process-check file) ; Check that no process is running | |
190 (setq TeX-command-buffer (current-buffer)) | |
191 ! (with-output-to-temp-buffer buffer) | |
192 (set-buffer buffer) | |
193 (if dir (cd dir)) | |
194 (insert "Running `" name "' on `" file "' with ``" command "''\n") | |
195 - --- 545,552 ---- | |
196 (dir (TeX-master-directory))) | |
197 (TeX-process-check file) ; Check that no process is running | |
198 (setq TeX-command-buffer (current-buffer)) | |
199 ! (let (temp-buffer-show-function temp-buffer-show-hook) | |
200 ! (with-output-to-temp-buffer buffer)) | |
201 (set-buffer buffer) | |
202 (if dir (cd dir)) | |
203 (insert "Running `" name "' on `" file "' with ``" command "''\n") | |
204 | |
205 * On Irix 6.3, substituting environment variables in file names | |
206 in the minibuffer gives peculiar error messages such as | |
207 | |
208 Substituting nonexistent environment variable "" | |
209 | |
210 This is not an Emacs bug; it is caused by something in SGI patch | |
211 003082 August 11, 1998. | |
212 | |
213 * After a while, Emacs slips into unibyte mode. | |
214 | |
215 The VM mail package, which is not part of Emacs, sometimes does | |
216 (standard-display-european t) | |
217 That should be changed to | |
218 (standard-display-european 1 t) | |
219 | |
220 * Installing Emacs gets an error running `install-info'. | |
221 | |
222 You need to install a recent version of Texinfo; that package | |
223 supplies the `install-info' command. | |
224 | |
225 * Emacs does not recognize the AltGr key, on HPUX. | |
226 | |
227 To fix this, set up a file ~/.dt/sessions/sessionetc with executable | |
228 rights, containing this text: | |
229 | |
230 -------------------------------- | |
231 xmodmap 2> /dev/null - << EOF | |
232 keysym Alt_L = Meta_L | |
233 keysym Alt_R = Meta_R | |
234 EOF | |
235 | |
236 xmodmap - << EOF | |
237 clear mod1 | |
238 keysym Mode_switch = NoSymbol | |
239 add mod1 = Meta_L | |
240 keysym Meta_R = Mode_switch | |
241 add mod2 = Mode_switch | |
242 EOF | |
243 -------------------------------- | |
244 | |
245 * Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files | |
246 in the directory with the special name `dev' under the root of any | |
247 drive, e.g. `c:/dev'. | |
248 | |
249 This is an unfortunate side-effect of the support for Unix-style | |
250 device names such as /dev/null in the DJGPP runtime library. A | |
251 work-around is to rename the problem directory to another name. | |
252 | |
253 * M-SPC seems to be ignored as input. | |
254 | |
255 See if your X server is set up to use this as a command | |
256 for character composition. | |
257 | |
258 * Emacs startup on GNU/Linux systems (and possibly other systems) is slow. | |
259 | |
260 This can happen if the system is misconfigured and Emacs can't get the | |
261 full qualified domain name, FQDN. You should have your FQDN in the | |
262 /etc/hosts file, something like this: | |
263 | |
264 127.0.0.1 localhost | |
265 129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04 | |
266 | |
267 The way to set this up may vary on non-GNU systems. | |
268 | |
269 * Garbled display on non-X terminals when Emacs runs on Digital Unix 4.0. | |
270 | |
271 So far it appears that running `tset' triggers this problem (when TERM | |
272 is vt100, at least). If you do not run `tset', then Emacs displays | |
273 properly. If someone can tell us precisely which effect of running | |
274 `tset' actually causes the problem, we may be able to implement a fix | |
275 in Emacs. | |
276 | |
277 * When you run Ispell from Emacs, it reports a "misalignment" error. | |
278 | |
279 This can happen if you compiled Ispell to use ASCII characters only | |
280 and then try to use it from Emacs with non-ASCII characters, | |
281 specifically Latin-1. The solution is to recompile Ispell with | |
282 Latin-1 support. | |
283 | |
284 This can also happen if the version of Ispell installed on your | |
285 machine is old. | |
286 | |
287 * On Linux-based GNU systems using libc versions 5.4.19 through | |
288 5.4.22, Emacs crashes at startup with a segmentation fault. | |
289 | |
290 This problem happens if libc defines the symbol __malloc_initialized. | |
291 One known solution is to upgrade to a newer libc version. 5.4.33 is | |
292 known to work. | |
293 | |
294 * On Windows, you cannot use the right-hand ALT key and the left-hand | |
295 CTRL key together to type a Control-Meta character. | |
296 | |
297 This is a consequence of a misfeature beyond Emacs's control. | |
298 | |
299 Under Windows, the AltGr key on international keyboards generates key | |
300 events with the modifiers Right-Alt and Left-Ctrl. Since Emacs cannot | |
301 distinguish AltGr from an explicit Right-Alt and Left-Ctrl | |
302 combination, whenever it sees Right-Alt and Left-Ctrl it assumes that | |
303 AltGr has been pressed. | |
304 | |
305 * Under some Windows X-servers, Emacs' display is incorrect | |
306 | |
307 The symptoms are that Emacs does not completely erase blank areas of the | |
308 screen during scrolling or some other screen operations (e.g., selective | |
309 display or when killing a region). M-x recenter will cause the screen | |
310 to be completely redisplayed and the "extra" characters will disappear. | |
311 | |
312 This is known to occur under Exceed 6, and possibly earlier versions as | |
313 well. The problem lies in the X-server settings. | |
314 | |
315 There are reports that you can solve the problem with Exceed by | |
316 running `Xconfig' from within NT, choosing "X selection", then | |
317 un-checking the boxes "auto-copy X selection" and "auto-paste to X | |
318 selection". | |
319 | |
320 Of this does not work, please inform bug-gnu-emacs@gnu.org. Then | |
321 please call support for your X-server and see if you can get a fix. | |
322 If you do, please send it to bug-gnu-emacs@gnu.org so we can list it | |
323 here. | |
324 | |
325 * On Solaris 2, Emacs dumps core when built with Motif. | |
326 | |
327 The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1. | |
328 Install the current Motif runtime library patch appropriate for your host. | |
329 (Make sure the patch is current; some older patch versions still have the bug.) | |
330 You should install the other patches recommended by Sun for your host, too. | |
331 You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/; | |
332 look for files with names ending in `.PatchReport' to see which patches | |
333 are currently recommended for your host. | |
334 | |
335 On Solaris 2.6, Emacs is said to work with Motif when Solaris patch | |
336 105284-12 is installed, but fail when 105284-15 is installed. | |
337 105284-18 might fix it again. | |
338 | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
339 * On Solaris 2.6 and 7, the Compose key does not work. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
340 |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
341 This is a bug in Motif in Solaris. Supposedly it has been fixed for |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
342 the next major release of Solaris. However, if someone with Sun |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
343 support complains to Sun about the bug, they may release a patch. |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
344 If you do this, mention Sun bug #4188711. |
25853 | 345 |
346 One workaround is to use a locale that allows non-ASCII characters. | |
347 For example, before invoking emacs, set the LC_ALL environment | |
348 variable to "en_US" (American English). The directory /usr/lib/locale | |
349 lists the supported locales; any locale other than "C" or "POSIX" | |
350 should do. | |
351 | |
26664
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
352 pen@lysator.liu.se says (Feb 1998) that the Compose key does work |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
353 if you link with the MIT X11 libraries instead of the Solaris X11 |
a7963e66c555
Update Solaris 2.6 and 7 problems.
Paul Eggert <eggert@twinsun.com>
parents:
25853
diff
changeset
|
354 libraries. |
25853 | 355 |
356 * Emacs does not know your host's fully-qualified domain name. | |
357 | |
358 You need to configure your machine with a fully qualified domain name, | |
359 either in /etc/hosts, /etc/hostname, the NIS, or wherever your system | |
360 calls for specifying this. | |
361 | |
362 If you cannot fix the configuration, you can set the Lisp variable | |
363 mail-host-address to the value you want. | |
364 | |
365 * Error 12 (virtual memory exceeded) when dumping Emacs, on UnixWare 2.1 | |
366 | |
367 Paul Abrahams (abrahams@acm.org) reports that with the installed | |
368 virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during | |
369 the "make" that builds Emacs, when running temacs to dump emacs. That | |
370 error indicates that the per-process virtual memory limit has been | |
371 exceeded. The default limit is probably 32MB. Raising the virtual | |
372 memory limit to 40MB should make it possible to finish building Emacs. | |
373 | |
374 You can do this with the command `ulimit' (sh) or `limit' (csh). | |
375 But you have to be root to do it. | |
376 | |
377 According to Martin Sohnius, you can also retune this in the kernel: | |
378 | |
379 # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit | |
380 # /etc/conf/bin/idtune HDATLIM 33554432 ## hard " | |
381 # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit | |
382 # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard " | |
383 # /etc/conf/bin/idbuild -B | |
384 | |
385 (He recommends you not change the stack limit, though.) | |
386 These changes take effect when you reboot. | |
387 | |
388 * Redisplay using X11 is much slower than previous Emacs versions. | |
389 | |
390 We've noticed that certain X servers draw the text much slower when | |
391 scroll bars are on the left. We don't know why this happens. If this | |
392 happens to you, you can work around it by putting the scroll bars | |
393 on the right (as they were in Emacs 19). | |
394 | |
395 Here's how to do this: | |
396 | |
397 (set-scroll-bar-mode 'right) | |
398 | |
399 If you're not sure whether (or how much) this problem affects you, | |
400 try that and see how much difference it makes. To set things back | |
401 to normal, do | |
402 | |
403 (set-scroll-bar-mode 'left) | |
404 | |
405 * Under X11, some characters appear as hollow boxes. | |
406 | |
407 Each X11 font covers just a fraction of the characters that Emacs | |
408 supports. To display the whole range of Emacs characters requires | |
409 many different fonts, collected into a fontset. | |
410 | |
411 If some of the fonts called for in your fontset do not exist on your X | |
412 server, then the characters that have no font appear as hollow boxes. | |
413 You can remedy the problem by installing additional fonts. | |
414 | |
415 The intlfonts distribution includes a full spectrum of fonts that can | |
416 display all the characters Emacs supports. | |
417 | |
418 * Under X11, some characters appear improperly aligned in their lines. | |
419 | |
420 You may have bad X11 fonts; try installing the intlfonts distribution. | |
421 | |
422 * Certain fonts make each line take one pixel more than it "should". | |
423 | |
424 This is because these fonts contain characters a little taller | |
425 than the font's nominal height. Emacs needs to make sure that | |
426 lines do not overlap. | |
427 | |
428 * You request inverse video, and the first Emacs frame is in inverse | |
429 video, but later frames are not in inverse video. | |
430 | |
431 This can happen if you have an old version of the custom library in | |
432 your search path for Lisp packages. Use M-x list-load-path-shadows to | |
433 check whether this is true. If it is, delete the old custom library. | |
434 | |
435 * In FreeBSD 2.1.5, useless symbolic links remain in /tmp or other | |
436 directories that have the +t bit. | |
437 | |
438 This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2). | |
439 Emacs uses symbolic links to implement file locks. In a directory | |
440 with +t bit, the directory owner becomes the owner of the symbolic | |
441 link, so that it cannot be removed by anyone else. | |
442 | |
443 If you don't like those useless links, you can let Emacs not to using | |
444 file lock by adding #undef CLASH_DETECTION to config.h. | |
445 | |
446 * When using M-x dbx with the SparcWorks debugger, the `up' and `down' | |
447 commands do not move the arrow in Emacs. | |
448 | |
449 You can fix this by adding the following line to `~/.dbxinit': | |
450 | |
451 dbxenv output_short_file_name off | |
452 | |
453 * Emacs says it has saved a file, but the file does not actually | |
454 appear on disk. | |
455 | |
456 This can happen on certain systems when you are using NFS, if the | |
457 remote disk is full. It is due to a bug in NFS (or certain NFS | |
458 implementations), and there is apparently nothing Emacs can do to | |
459 detect the problem. Emacs checks the failure codes of all the system | |
460 calls involved in writing a file, including `close'; but in the case | |
461 where the problem occurs, none of those system calls fails. | |
462 | |
463 * "Compose Character" key does strange things when used as a Meta key. | |
464 | |
465 If you define one key to serve as both Meta and Compose Character, you | |
466 will get strange results. In previous Emacs versions, this "worked" | |
467 in that the key acted as Meta--that's because the older Emacs versions | |
468 did not try to support Compose Character. Now Emacs tries to do | |
469 character composition in the standard X way. This means that you | |
470 must pick one meaning or the other for any given key. | |
471 | |
472 You can use both functions (Meta, and Compose Character) if you assign | |
473 them to two different keys. | |
474 | |
475 * Emacs gets a segmentation fault at startup, on AIX4.2. | |
476 | |
477 If you are using IBM's xlc compiler, compile emacs.c | |
478 without optimization; that should avoid the problem. | |
479 | |
480 * movemail compiled with POP support can't connect to the POP server. | |
481 | |
482 Make sure that the `pop' entry in /etc/services, or in the services | |
483 NIS map if your machine uses NIS, has the same port number as the | |
484 entry on the POP server. A common error is for the POP server to be | |
485 listening on port 110, the assigned port for the POP3 protocol, while | |
486 the client is trying to connect on port 109, the assigned port for the | |
487 old POP protocol. | |
488 | |
489 * Emacs crashes in x-popup-dialog. | |
490 | |
491 This can happen if the dialog widget cannot find the font it wants to | |
492 use. You can work around the problem by specifying another font with | |
493 an X resource--for example, `Emacs.dialog*.font: 9x15' (or any font that | |
494 happens to exist on your X server). | |
495 | |
496 * Emacs crashes when you use Bibtex mode. | |
497 | |
498 This happens if your system puts a small limit on stack size. You can | |
499 prevent the problem by using a suitable shell command (often `ulimit') | |
500 to raise the stack size limit before you run Emacs. | |
501 | |
502 Patches to raise the stack size limit automatically in `main' | |
503 (src/emacs.c) on various systems would be greatly appreciated. | |
504 | |
505 * Emacs crashes with SIGBUS or SIGSEGV on HPUX 9 after you delete a frame. | |
506 | |
507 We think this is due to a bug in the X libraries provided by HP. With | |
508 the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem | |
509 does not happen. | |
510 | |
511 * Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame. | |
512 | |
513 We suspect that this is a similar bug in the X libraries provided by | |
514 Sun. There is a report that one of these patches fixes the bug and | |
515 makes the problem stop: | |
516 | |
517 105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02 | |
518 105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03 | |
519 106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01 | |
520 105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01 | |
521 | |
522 Another person using a newer system (kernel patch level Generic_105181-06) | |
523 suspects that the bug was fixed by one of these more recent patches: | |
524 | |
525 106040-07 SunOS 5.6: X Input & Output Method patch | |
526 106222-01 OpenWindows 3.6: filemgr (ff.core) fixes | |
527 105284-12 Motif 1.2.7: sparc Runtime library patch | |
528 | |
529 * Problems running Perl under Emacs on Windows NT/95. | |
530 | |
531 `perl -de 0' just hangs when executed in an Emacs subshell. | |
532 The fault lies with Perl (indirectly with Windows NT/95). | |
533 | |
534 The problem is that the Perl debugger explicitly opens a connection to | |
535 "CON", which is the DOS/NT equivalent of "/dev/tty", for interacting | |
536 with the user. | |
537 | |
538 On Unix, this is okay, because Emacs (or the shell?) creates a | |
539 pseudo-tty so that /dev/tty is really the pipe Emacs is using to | |
540 communicate with the subprocess. | |
541 | |
542 On NT, this fails because CON always refers to the handle for the | |
543 relevant console (approximately equivalent to a tty), and cannot be | |
544 redirected to refer to the pipe Emacs assigned to the subprocess as | |
545 stdin. | |
546 | |
547 A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON. | |
548 | |
549 For Perl 4: | |
550 | |
551 *** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993 | |
552 --- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996 | |
553 *************** | |
554 *** 68,74 **** | |
555 $rcfile=".perldb"; | |
556 } | |
557 else { | |
558 ! $console = "con"; | |
559 $rcfile="perldb.ini"; | |
560 } | |
561 | |
562 --- 68,74 ---- | |
563 $rcfile=".perldb"; | |
564 } | |
565 else { | |
566 ! $console = ""; | |
567 $rcfile="perldb.ini"; | |
568 } | |
569 | |
570 | |
571 For Perl 5: | |
572 *** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995 | |
573 --- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996 | |
574 *************** | |
575 *** 22,28 **** | |
576 $rcfile=".perldb"; | |
577 } | |
578 elsif (-e "con") { | |
579 ! $console = "con"; | |
580 $rcfile="perldb.ini"; | |
581 } | |
582 else { | |
583 --- 22,28 ---- | |
584 $rcfile=".perldb"; | |
585 } | |
586 elsif (-e "con") { | |
587 ! $console = ""; | |
588 $rcfile="perldb.ini"; | |
589 } | |
590 else { | |
591 | |
592 * Problems running DOS programs on Windows NT versions earlier than 3.51. | |
593 | |
594 Some DOS programs, such as pkzip/pkunzip will not work at all, while | |
595 others will only work if their stdin is redirected from a file or NUL. | |
596 | |
597 When a DOS program does not work, a new process is actually created, but | |
598 hangs. It cannot be interrupted from Emacs, and might need to be killed | |
599 by an external program if Emacs is hung waiting for the process to | |
600 finish. If Emacs is not waiting for it, you should be able to kill the | |
601 instance of ntvdm that is running the hung process from Emacs, if you | |
602 can find out the process id. | |
603 | |
604 It is safe to run most DOS programs using call-process (eg. M-! and | |
605 M-|) since stdin is then redirected from a file, but not with | |
606 start-process since that redirects stdin to a pipe. Also, running DOS | |
607 programs in a shell buffer prompt without redirecting stdin does not | |
608 work. | |
609 | |
610 * Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs: | |
611 | |
612 There are two DJGPP library bugs which cause problems: | |
613 | |
614 * Running `shell-command' (or `compile', or `grep') you get | |
615 `Searching for program: permission denied (EACCES), c:/command.com'; | |
616 * After you shell to DOS, Ctrl-Break kills Emacs. | |
617 | |
618 To work around these bugs, you can use two files in the msdos | |
619 subdirectory: `is_exec.c' and `sigaction.c'. Compile them and link | |
620 them into the Emacs executable `temacs'; then they will replace the | |
621 incorrect library functions. | |
622 | |
623 * When compiling with DJGPP on Windows 95, Make fails for some targets | |
624 like make-docfile. | |
625 | |
626 This can happen if long file name support (the setting of environment | |
627 variable LFN) when Emacs distribution was unpacked and during | |
628 compilation are not the same. See the MSDOG section of INSTALL for | |
629 the explanation of how to avoid this problem. | |
630 | |
631 * Emacs compiled for MSDOS cannot find some Lisp files, or other | |
632 run-time support files, when long filename support is enabled. | |
633 (Usually, this problem will manifest itself when Emacs exits | |
634 immediately after flashing the startup screen, because it cannot find | |
635 the Lisp files it needs to load at startup. Redirect Emacs stdout | |
636 and stderr to a file to see the error message printed by Emacs.) | |
637 | |
638 This can happen if the Emacs distribution was unzipped without LFN | |
639 support, thus causing long filenames to be truncated to the first 6 | |
640 characters and a numeric tail that Windows 95 normally attaches to it. | |
641 You should unzip the files again with a utility that supports long | |
642 filenames (such as djtar from DJGPP or InfoZip's UnZip program | |
643 compiled with DJGPP v2). The MSDOG section of the file INSTALL | |
644 explains this issue in more detail. | |
645 | |
646 * Emacs compiled with DJGPP complains at startup: | |
647 | |
648 "Wrong type of argument: internal-facep, msdos-menu-active-face" | |
649 | |
650 This can happen if you define an environment variable `TERM'. Emacs | |
651 on MSDOS uses an internal terminal emulator which is disabled if the | |
652 value of `TERM' is anything but the string "internal". Emacs then | |
653 works as if its terminal were a dumb glass teletype that doesn't | |
654 support faces. To work around this, arrange for `TERM' to be | |
655 undefined when Emacs runs. The best way to do that is to add an | |
656 [emacs] section to the DJGPP.ENV file which defines an empty value for | |
657 `TERM'; this way, only Emacs gets the empty value, while the rest of | |
658 your system works as before. | |
659 | |
660 * On Windows 95, Alt-f6 does not get through to Emacs. | |
661 | |
662 This character seems to be trapped by the kernel in Windows 95. | |
663 You can enter M-f6 by typing ESC f6. | |
664 | |
665 * Typing Alt-Shift has strange effects on Windows 95. | |
666 | |
667 This combination of keys is a command to change keyboard layout. If | |
668 you proceed to type another non-modifier key before you let go of Alt | |
669 and Shift, the Alt and Shift act as modifiers in the usual way. | |
670 | |
671 * `tparam' reported as a multiply-defined symbol when linking with ncurses. | |
672 | |
673 This problem results from an incompatible change in ncurses, in | |
674 version 1.9.9e approximately. This version is unable to provide a | |
675 definition of tparm without also defining tparam. This is also | |
676 incompatible with Terminfo; as a result, the Emacs Terminfo support | |
677 does not work with this version of ncurses. | |
678 | |
679 The fix is to install a newer version of ncurses, such as version 4.2. | |
680 | |
681 * Strange results from format %d in a few cases, on a Sun. | |
682 | |
683 Sun compiler version SC3.0 has been found to miscompile part of | |
684 editfns.c. The workaround is to compile with some other compiler such | |
685 as GCC. | |
686 | |
687 * Output from subprocess (such as man or diff) is randomly truncated | |
688 on GNU/Linux systems. | |
689 | |
690 This is due to a kernel bug which seems to be fixed in Linux version | |
691 1.3.75. | |
692 | |
693 * Error messages `internal facep []' happen on GNU/Linux systems. | |
694 | |
695 There is a report that replacing libc.so.5.0.9 with libc.so.5.2.16 | |
696 caused this to start happening. People are not sure why, but the | |
697 problem seems unlikely to be in Emacs itself. Some suspect that it | |
698 is actually Xlib which won't work with libc.so.5.2.16. | |
699 | |
700 Using the old library version is a workaround. | |
701 | |
702 * On Solaris, Emacs crashes if you use (display-time). | |
703 | |
704 This can happen if you configure Emacs without specifying the precise | |
705 version of Solaris that you are using. | |
706 | |
707 * Emacs dumps core on startup, on Solaris. | |
708 | |
709 Bill Sebok says that the cause of this is Solaris 2.4 vendor patch | |
710 102303-05, which extends the Solaris linker to deal with the Solaris | |
711 Common Desktop Environment's linking needs. You can fix the problem | |
712 by removing this patch and installing patch 102049-02 instead. | |
713 However, that linker version won't work with CDE. | |
714 | |
715 Solaris 2.5 comes with a linker that has this bug. It is reported that if | |
716 you install all the latest patches (as of June 1996), the bug is fixed. | |
717 We suspect the crucial patch is one of these, but we don't know | |
718 for certain. | |
719 | |
720 103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes) | |
721 102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes) | |
722 103242-04: [README] SunOS 5.5: linker patch (595363 bytes) | |
723 | |
724 (One user reports that the bug was fixed by those patches together | |
725 with patches 102980-04, 103279-01, 103300-02, and 103468-01.) | |
726 | |
727 If you can determine which patch does fix the bug, please tell | |
728 bug-gnu-emacs@gnu.org. | |
729 | |
730 Meanwhile, the GNU linker links Emacs properly on both Solaris 2.4 and | |
731 Solaris 2.5. | |
732 | |
733 * Emacs dumps core if lisp-complete-symbol is called, on Solaris. | |
734 | |
735 If you compile Emacs with the -fast or -xO4 option with version 3.0.2 | |
736 of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is | |
737 called. The problem does not happen if you compile with GCC. | |
738 | |
739 * "Cannot find callback list" messages from dialog boxes on HPUX, in | |
740 Emacs built with Motif. | |
741 | |
742 This problem resulted from a bug in GCC 2.4.5. Newer GCC versions | |
743 such as 2.7.0 fix the problem. | |
744 | |
745 * On Irix 6.0, make tries (and fails) to build a program named unexelfsgi | |
746 | |
747 A compiler bug inserts spaces into the string "unexelfsgi . o" | |
748 in src/Makefile. Edit src/Makefile, after configure is run, | |
749 find that string, and take out the spaces. | |
750 | |
751 Compiler fixes in Irix 6.0.1 should eliminate this problem. | |
752 | |
753 * "out of virtual swap space" on Irix 5.3 | |
754 | |
755 This message occurs when the system runs out of swap space due to too | |
756 many large programs running. The solution is either to provide more | |
757 swap space or to reduce the number of large programs being run. You | |
758 can check the current status of the swap space by executing the | |
759 command `swap -l'. | |
760 | |
761 You can increase swap space by changing the file /etc/fstab. Adding a | |
762 line like this: | |
763 | |
764 /usr/swap/swap.more swap swap pri=3 0 0 | |
765 | |
766 where /usr/swap/swap.more is a file previously created (for instance | |
767 by using /etc/mkfile), will increase the swap space by the size of | |
768 that file. Execute `swap -m' or reboot the machine to activate the | |
769 new swap area. See the manpages for `swap' and `fstab' for further | |
770 information. | |
771 | |
772 The objectserver daemon can use up lots of memory because it can be | |
773 swamped with NIS information. It collects information about all users | |
774 on the network that can log on to the host. | |
775 | |
776 If you want to disable the objectserver completely, you can execute | |
777 the command `chkconfig objectserver off' and reboot. That may disable | |
778 some of the window system functionality, such as responding CDROM | |
779 icons. | |
780 | |
781 You can also remove NIS support from the objectserver. The SGI `admin' | |
782 FAQ has a detailed description on how to do that; see question 35 | |
783 ("Why isn't the objectserver working?"). The admin FAQ can be found at | |
784 ftp://viz.tamu.edu/pub/sgi/faq/. | |
785 | |
786 * With certain fonts, when the cursor appears on a character, the | |
787 character doesn't appear--you get a solid box instead. | |
788 | |
789 One user on a Linux-based GNU system reported that this problem went | |
790 away with installation of a new X server. The failing server was | |
791 XFree86 3.1.1. XFree86 3.1.2 works. | |
792 | |
793 * On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft. | |
794 | |
795 This happens if you configure Emacs specifying just `sparc-sun-sunos4' | |
796 on a system that is version 4.1.3. You must specify the precise | |
797 version number (or let configure figure out the configuration, which | |
798 it can do perfectly well for SunOS). | |
799 | |
800 * On SunOS 4, Emacs processes keep going after you kill the X server | |
801 (or log out, if you logged in using X). | |
802 | |
803 Someone reported that recompiling with GCC 2.7.0 fixed this problem. | |
804 | |
805 * On AIX 4, some programs fail when run in a Shell buffer | |
806 with an error message like No terminfo entry for "unknown". | |
807 | |
808 On AIX, many terminal type definitions are not installed by default. | |
809 `unknown' is one of them. Install the "Special Generic Terminal | |
810 Definitions" to make them defined. | |
811 | |
812 * On SunOS, you get linker errors | |
813 ld: Undefined symbol | |
814 _get_wmShellWidgetClass | |
815 _get_applicationShellWidgetClass | |
816 | |
817 The fix to this is to install patch 100573 for OpenWindows 3.0 | |
818 or link libXmu statically. | |
819 | |
820 * On AIX 4.1.2, linker error messages such as | |
821 ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table | |
822 of archive /usr/lib/libIM.a, was not defined in archive member shr.o. | |
823 | |
824 This is a problem in libIM.a. You can work around it by executing | |
825 these shell commands in the src subdirectory of the directory where | |
826 you build Emacs: | |
827 | |
828 cp /usr/lib/libIM.a . | |
829 chmod 664 libIM.a | |
830 ranlib libIM.a | |
831 | |
832 Then change -lIM to ./libIM.a in the command to link temacs (in | |
833 Makefile). | |
834 | |
835 * Unpredictable segmentation faults on Solaris 2.3 and 2.4. | |
836 | |
837 A user reported that this happened in 19.29 when it was compiled with | |
838 the Sun compiler, but not when he recompiled with GCC 2.7.0. | |
839 | |
840 We do not know whether something in Emacs is partly to blame for this. | |
841 | |
842 * Emacs exits with "X protocol error" when run with an X server for | |
843 Windows. | |
844 | |
845 A certain X server for Windows had a bug which caused this. | |
846 Supposedly the newer 32-bit version of this server doesn't have the | |
847 problem. | |
848 | |
849 * Emacs crashes at startup on MSDOS. | |
850 | |
851 Some users report that Emacs 19.29 requires dpmi memory management, | |
852 and crashes on startup if the system does not have it. We don't yet | |
853 know why this happens--perhaps these machines don't have enough real | |
854 memory, or perhaps something is wrong in Emacs or the compiler. | |
855 However, arranging to use dpmi support is a workaround. | |
856 | |
857 You can find out if you have a dpmi host by running go32 without | |
858 arguments; it will tell you if it uses dpmi memory. For more | |
859 information about dpmi memory, consult the djgpp FAQ. (djgpp | |
860 is the GNU C compiler as packaged for MSDOS.) | |
861 | |
862 Compiling Emacs under MSDOS is extremely sensitive for proper memory | |
863 configuration. If you experience problems during compilation, consider | |
864 removing some or all memory resident programs (notably disk caches) | |
865 and make sure that your memory managers are properly configured. See | |
866 the djgpp faq for configuration hints. | |
867 | |
868 * A position you specified in .Xdefaults is ignored, using twm. | |
869 | |
870 twm normally ignores "program-specified" positions. | |
871 You can tell it to obey them with this command in your `.twmrc' file: | |
872 | |
873 UsePPosition "on" #allow clients to request a position | |
874 | |
875 * Compiling lib-src says there is no rule to make test-distrib.c. | |
876 | |
877 This results from a bug in a VERY old version of GNU Sed. To solve | |
878 the problem, install the current version of GNU Sed, then rerun | |
879 Emacs's configure script. | |
880 | |
881 * Compiling wakeup, in lib-src, says it can't make wakeup.c. | |
882 | |
883 This results from a bug in GNU Sed version 2.03. To solve the | |
884 problem, install the current version of GNU Sed, then rerun Emacs's | |
885 configure script. | |
886 | |
887 * On Sunos 4.1.1, there are errors compiling sysdep.c. | |
888 | |
889 If you get errors such as | |
890 | |
891 "sysdep.c", line 2017: undefined structure or union | |
892 "sysdep.c", line 2017: undefined structure or union | |
893 "sysdep.c", line 2019: nodename undefined | |
894 | |
895 This can result from defining LD_LIBRARY_PATH. It is very tricky | |
896 to use that environment variable with Emacs. The Emacs configure | |
897 script links many test programs with the system libraries; you must | |
898 make sure that the libraries available to configure are the same | |
899 ones available when you build Emacs. | |
900 | |
901 * The right Alt key works wrong on German HP keyboards (and perhaps | |
902 other non-English HP keyboards too). | |
903 | |
904 This is because HPUX defines the modifiers wrong in X. Here is a | |
905 shell script to fix the problem; be sure that it is run after VUE | |
906 configures the X server. | |
907 | |
908 xmodmap 2> /dev/null - << EOF | |
909 keysym Alt_L = Meta_L | |
910 keysym Alt_R = Meta_R | |
911 EOF | |
912 | |
913 xmodmap - << EOF | |
914 clear mod1 | |
915 keysym Mode_switch = NoSymbol | |
916 add mod1 = Meta_L | |
917 keysym Meta_R = Mode_switch | |
918 add mod2 = Mode_switch | |
919 EOF | |
920 | |
921 * The Emacs window disappears when you type M-q. | |
922 | |
923 Some versions of the Open Look window manager interpret M-q as a quit | |
924 command for whatever window you are typing at. If you want to use | |
925 Emacs with that window manager, you should try to configure the window | |
926 manager to use some other command. You can disable the | |
927 shortcut keys entirely by adding this line to ~/.OWdefaults: | |
928 | |
929 OpenWindows.WindowMenuAccelerators: False | |
930 | |
931 * Emacs does not notice when you release the mouse. | |
932 | |
933 There are reports that this happened with (some) Microsoft mice and | |
934 that replacing the mouse made it stop. | |
935 | |
936 * Trouble using ptys on IRIX, or running out of ptys. | |
937 | |
938 The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to | |
939 be set-UID to root, or non-root programs like Emacs will not be able | |
940 to allocate ptys reliably. | |
941 | |
942 * On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h. | |
943 | |
944 The file cmplrs/stsupport.h was included in the wrong file set in the | |
945 Irix 5.2 distribution. You can find it in the optional fileset | |
946 compiler_dev, or copy it from some other Irix 5.2 system. A kludgy | |
947 workaround is to change unexelfsgi.c to include sym.h instead of | |
948 syms.h. | |
949 | |
950 * Slow startup on Linux-based GNU systems. | |
951 | |
952 People using systems based on the Linux kernel sometimes report that | |
953 startup takes 10 to 15 seconds longer than `usual'. | |
954 | |
955 This is because Emacs looks up the host name when it starts. | |
956 Normally, this takes negligible time; the extra delay is due to | |
957 improper system configuration. This problem can occur for both | |
958 networked and non-networked machines. | |
959 | |
960 Here is how to fix the configuration. It requires being root. | |
961 | |
962 ** Networked Case | |
963 | |
964 First, make sure the files `/etc/hosts' and `/etc/host.conf' both | |
965 exist. The first line in the `/etc/hosts' file should look like this | |
966 (replace HOSTNAME with your host name): | |
967 | |
968 127.0.0.1 HOSTNAME | |
969 | |
970 Also make sure that the `/etc/host.conf' files contains the following | |
971 lines: | |
972 | |
973 order hosts, bind | |
974 multi on | |
975 | |
976 Any changes, permanent and temporary, to the host name should be | |
977 indicated in the `/etc/hosts' file, since it acts a limited local | |
978 database of addresses and names (e.g., some SLIP connections | |
979 dynamically allocate ip addresses). | |
980 | |
981 ** Non-Networked Case | |
982 | |
983 The solution described in the networked case applies here as well. | |
984 However, if you never intend to network your machine, you can use a | |
985 simpler solution: create an empty `/etc/host.conf' file. The command | |
986 `touch /etc/host.conf' suffices to create the file. The `/etc/hosts' | |
987 file is not necessary with this approach. | |
988 | |
989 * On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs | |
990 forever waiting for termination of a subprocess that is a zombie. | |
991 | |
992 casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so | |
993 after changing the file xc/config/cf/sunLib.tmpl. Change the lines | |
994 | |
995 #if ThreadedX | |
996 #define SharedX11Reqs -lthread | |
997 #endif | |
998 | |
999 to: | |
1000 | |
1001 #if OSMinorVersion < 4 | |
1002 #if ThreadedX | |
1003 #define SharedX11Reqs -lthread | |
1004 #endif | |
1005 #endif | |
1006 | |
1007 Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4 | |
1008 (as it should be for Solaris 2.4). The file has three definitions for | |
1009 OSMinorVersion: the first is for x86, the second for SPARC under | |
1010 Solaris, and the third for SunOS 4. Make sure to update the | |
1011 definition for your type of machine and system. | |
1012 | |
1013 Then do `make Everything' in the top directory of X11R6, to rebuild | |
1014 the makefiles and rebuild X. The X built this way work only on | |
1015 Solaris 2.4, not on 2.3. | |
1016 | |
1017 For multithreaded X to work it is necessary to install patch | |
1018 101925-02 to fix problems in header files [2.4]. You need | |
1019 to reinstall gcc or re-run just-fixinc after installing that | |
1020 patch. | |
1021 | |
1022 However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution: | |
1023 he changed | |
1024 #define ThreadedX YES | |
1025 to | |
1026 #define ThreadedX NO | |
1027 in sun.cf and did `make World' to rebuild X11R6. Removing all | |
1028 `-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and | |
1029 typing 'make install' in that directory also seemed to work. | |
1030 | |
1031 * With M-x enable-flow-control, you need to type C-\ twice | |
1032 to do incremental search--a single C-\ gets no response. | |
1033 | |
1034 This has been traced to communicating with your machine via kermit, | |
1035 with C-\ as the kermit escape character. One solution is to use | |
1036 another escape character in kermit. One user did | |
1037 | |
1038 set escape-character 17 | |
1039 | |
1040 in his .kermrc file, to make C-q the kermit escape character. | |
1041 | |
1042 * The Motif version of Emacs paints the screen a solid color. | |
1043 | |
1044 This has been observed to result from the following X resource: | |
1045 | |
1046 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-* | |
1047 | |
1048 That the resource has this effect indicates a bug in something, but we | |
1049 do not yet know what. If it is an Emacs bug, we hope someone can | |
1050 explain what the bug is so we can fix it. In the mean time, removing | |
1051 the resource prevents the problem. | |
1052 | |
1053 * Emacs gets hung shortly after startup, on Sunos 4.1.3. | |
1054 | |
1055 We think this is due to a bug in Sunos. The word is that | |
1056 one of these Sunos patches fixes the bug: | |
1057 | |
1058 100075-11 100224-06 100347-03 100482-05 100557-02 100623-03 100804-03 101080-01 | |
1059 100103-12 100249-09 100496-02 100564-07 100630-02 100891-10 101134-01 | |
1060 100170-09 100296-04 100377-09 100507-04 100567-04 100650-02 101070-01 101145-01 | |
1061 100173-10 100305-15 100383-06 100513-04 100570-05 100689-01 101071-03 101200-02 | |
1062 100178-09 100338-05 100421-03 100536-02 100584-05 100784-01 101072-01 101207-01 | |
1063 | |
1064 We don't know which of these patches really matter. If you find out | |
1065 which ones, please inform bug-gnu-emacs@gnu.org. | |
1066 | |
1067 * Emacs aborts while starting up, only when run without X. | |
1068 | |
1069 This problem often results from compiling Emacs with GCC when GCC was | |
1070 installed incorrectly. The usual error in installing GCC is to | |
1071 specify --includedir=/usr/include. Installation of GCC makes | |
1072 corrected copies of the system header files. GCC is supposed to use | |
1073 the corrected copies in preference to the original system headers. | |
1074 Specifying --includedir=/usr/include causes the original system header | |
1075 files to be used. On some systems, the definition of ioctl in the | |
1076 original system header files is invalid for ANSI C and causes Emacs | |
1077 not to work. | |
1078 | |
1079 The fix is to reinstall GCC, and this time do not specify --includedir | |
1080 when you configure it. Then recompile Emacs. Specifying --includedir | |
1081 is appropriate only in very special cases and it should *never* be the | |
1082 same directory where system header files are kept. | |
1083 | |
1084 * On Solaris 2.x, GCC complains "64 bit integer types not supported" | |
1085 | |
1086 This suggests that GCC is not installed correctly. Most likely you | |
1087 are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this | |
1088 does not work without patching. To run GCC 2.7.2.3 on Solaris 2.6 or | |
1089 later, you must patch fixinc.svr4 and reinstall GCC from scratch as | |
1090 described in the Solaris FAQ | |
1091 <http://www.wins.uva.nl/pub/solaris/solaris2.html>. A better fix is | |
1092 to upgrade to GCC 2.8.1 or later. | |
1093 | |
1094 * The Compose key on a DEC keyboard does not work as Meta key. | |
1095 | |
1096 This shell command should fix it: | |
1097 | |
1098 xmodmap -e 'keycode 0xb1 = Meta_L' | |
1099 | |
1100 * Regular expressions matching bugs on SCO systems. | |
1101 | |
1102 On SCO, there are problems in regexp matching when Emacs is compiled | |
1103 with the system compiler. The compiler version is "Microsoft C | |
1104 version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick | |
1105 C Compiler Version 1.00.46 (Beta). The solution is to compile with | |
1106 GCC. | |
1107 | |
1108 * On Sunos 4, you get the error ld: Undefined symbol __lib_version. | |
1109 | |
1110 This is the result of using cc or gcc with the shared library meant | |
1111 for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete | |
1112 /usr/lang/SC2.0.1 or some similar directory. | |
1113 | |
1114 * You can't select from submenus (in the X toolkit version). | |
1115 | |
1116 On certain systems, mouse-tracking and selection in top-level menus | |
1117 works properly with the X toolkit, but neither of them works when you | |
1118 bring up a submenu (such as Bookmarks or Compare or Apply Patch, in | |
1119 the Files menu). | |
1120 | |
1121 This works on most systems. There is speculation that the failure is | |
1122 due to bugs in old versions of X toolkit libraries, but no one really | |
1123 knows. If someone debugs this and finds the precise cause, perhaps a | |
1124 workaround can be found. | |
1125 | |
1126 * Unusable default font on SCO 3.2v4. | |
1127 | |
1128 The Open Desktop environment comes with default X resource settings | |
1129 that tell Emacs to use a variable-width font. Emacs cannot use such | |
1130 fonts, so it does not work. | |
1131 | |
1132 This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is | |
1133 the application-specific resource file for the `scoterm' terminal | |
1134 emulator program. It contains several extremely general X resources | |
1135 that affect other programs besides `scoterm'. In particular, these | |
1136 resources affect Emacs also: | |
1137 | |
1138 *Font: -*-helvetica-medium-r-*--12-*-p-* | |
1139 *Background: scoBackground | |
1140 *Foreground: scoForeground | |
1141 | |
1142 The best solution is to create an application-specific resource file for | |
1143 Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents: | |
1144 | |
1145 Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
1146 Emacs*Background: white | |
1147 Emacs*Foreground: black | |
1148 | |
1149 (These settings mimic the Emacs defaults, but you can change them to | |
1150 suit your needs.) This resource file is only read when the X server | |
1151 starts up, so you should restart it by logging out of the Open Desktop | |
1152 environment or by running `scologin stop; scologin start` from the shell | |
1153 as root. Alternatively, you can put these settings in the | |
1154 /usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs, | |
1155 but then they will not affect remote invocations of Emacs that use the | |
1156 Open Desktop display. | |
1157 | |
1158 These resource files are not normally shared across a network of SCO | |
1159 machines; you must create the file on each machine individually. | |
1160 | |
1161 * rcs2log gives you the awk error message "too many fields". | |
1162 | |
1163 This is due to an arbitrary limit in certain versions of awk. | |
1164 The solution is to use gawk (GNU awk). | |
1165 | |
1166 * Emacs is slow using X11R5 on HP/UX. | |
1167 | |
1168 This happens if you use the MIT versions of the X libraries--it | |
1169 doesn't run as fast as HP's version. People sometimes use the version | |
1170 because they see the HP version doesn't have the libraries libXaw.a, | |
1171 libXmu.a, libXext.a and others. HP/UX normally doesn't come with | |
1172 those libraries installed. To get good performance, you need to | |
1173 install them and rebuild Emacs. | |
1174 | |
1175 * Loading fonts is very slow. | |
1176 | |
1177 You might be getting scalable fonts instead of precomputed bitmaps. | |
1178 Known scalable font directories are "Type1" and "Speedo". A font | |
1179 directory contains scalable fonts if it contains the file | |
1180 "fonts.scale". | |
1181 | |
1182 If this is so, re-order your X windows font path to put the scalable | |
1183 font directories last. See the documentation of `xset' for details. | |
1184 | |
1185 With some X servers, it may be necessary to take the scalable font | |
1186 directories out of your path entirely, at least for Emacs 19.26. | |
1187 Changes in the future may make this unnecessary. | |
1188 | |
1189 * On AIX 3.2.4, releasing Ctrl/Act key has no effect, if Shift is down. | |
1190 | |
1191 Due to a feature of AIX, pressing or releasing the Ctrl/Act key is | |
1192 ignored when the Shift, Alt or AltGr keys are held down. This can | |
1193 lead to the keyboard being "control-locked"--ordinary letters are | |
1194 treated as control characters. | |
1195 | |
1196 You can get out of this "control-locked" state by pressing and | |
1197 releasing Ctrl/Act while not pressing or holding any other keys. | |
1198 | |
1199 * display-time causes kernel problems on ISC systems. | |
1200 | |
1201 Under Interactive Unix versions 3.0.1 and 4.0 (and probably other | |
1202 versions), display-time causes the loss of large numbers of STREVENT | |
1203 cells. Eventually the kernel's supply of these cells is exhausted. | |
1204 This makes emacs and the whole system run slow, and can make other | |
1205 processes die, in particular pcnfsd. | |
1206 | |
1207 Other emacs functions that communicate with remote processes may have | |
1208 the same problem. Display-time seems to be far the worst. | |
1209 | |
1210 The only known fix: Don't run display-time. | |
1211 | |
1212 * On Solaris, C-x doesn't get through to Emacs when you use the console. | |
1213 | |
1214 This is a Solaris feature (at least on Intel x86 cpus). Type C-r | |
1215 C-r C-t, to toggle whether C-x gets through to Emacs. | |
1216 | |
1217 * Error message `Symbol's value as variable is void: x', followed by | |
1218 segmentation fault and core dump. | |
1219 | |
1220 This has been tracked to a bug in tar! People report that tar erroneously | |
1221 added a line like this at the beginning of files of Lisp code: | |
1222 | |
1223 x FILENAME, N bytes, B tape blocks | |
1224 | |
1225 If your tar has this problem, install GNU tar--if you can manage to | |
1226 untar it :-). | |
1227 | |
1228 * Link failure when using acc on a Sun. | |
1229 | |
1230 To use acc, you need additional options just before the libraries, such as | |
1231 | |
1232 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1 | |
1233 | |
1234 and you need to add -lansi just before -lc. | |
1235 | |
1236 The precise file names depend on the compiler version, so we | |
1237 cannot easily arrange to supply them. | |
1238 | |
1239 * Link failure on IBM AIX 1.3 ptf 0013. | |
1240 | |
1241 There is a real duplicate definition of the function `_slibc_free' in | |
1242 the library /lib/libc_s.a (just do nm on it to verify). The | |
1243 workaround/fix is: | |
1244 | |
1245 cd /lib | |
1246 ar xv libc_s.a NLtmtime.o | |
1247 ar dv libc_s.a NLtmtime.o | |
1248 | |
1249 * Undefined symbols _dlopen, _dlsym and/or _dlclose on a Sun. | |
1250 | |
1251 If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking | |
1252 with -lX11, compile and link against the file mit/util/misc/dlsym.c in | |
1253 the MIT X11R5 distribution. Alternatively, link temacs using shared | |
1254 libraries with s/sunos4shr.h. (This doesn't work if you use the X | |
1255 toolkit.) | |
1256 | |
1257 If you get the additional error that the linker could not find | |
1258 lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in | |
1259 X11R4, then use it in the link. | |
1260 | |
1261 * Error messages `Wrong number of arguments: #<subr where-is-internal>, 5' | |
1262 | |
1263 This typically results from having the powerkey library loaded. | |
1264 Powerkey was designed for Emacs 19.22. It is obsolete now because | |
1265 Emacs 19 now has this feature built in; and powerkey also calls | |
1266 where-is-internal in an obsolete way. | |
1267 | |
1268 So the fix is to arrange not to load powerkey. | |
1269 | |
1270 * In Shell mode, you get a ^M at the end of every line. | |
1271 | |
1272 This happens to people who use tcsh, because it is trying to be too | |
1273 smart. It sees that the Shell uses terminal type `unknown' and turns | |
1274 on the flag to output ^M at the end of each line. You can fix the | |
1275 problem by adding this to your .cshrc file: | |
1276 | |
1277 if ($?EMACS) then | |
1278 if ($EMACS == "t") then | |
1279 unset edit | |
1280 stty -icrnl -onlcr -echo susp ^Z | |
1281 endif | |
1282 endif | |
1283 | |
1284 * An error message such as `X protocol error: BadMatch (invalid | |
1285 parameter attributes) on protocol request 93'. | |
1286 | |
1287 This comes from having an invalid X resource, such as | |
1288 emacs*Cursor: black | |
1289 (which is invalid because it specifies a color name for something | |
1290 that isn't a color.) | |
1291 | |
1292 The fix is to correct your X resources. | |
1293 | |
1294 * Undefined symbols when linking on Sunos 4.1 using --with-x-toolkit. | |
1295 | |
1296 If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace, | |
1297 _iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after | |
1298 -lXaw in the command that links temacs. | |
1299 | |
1300 This problem seems to arise only when the international language | |
1301 extensions to X11R5 are installed. | |
1302 | |
1303 * Typing C-c C-c in Shell mode kills your X server. | |
1304 | |
1305 This happens with Linux kernel 1.0 thru 1.04, approximately. The workaround is | |
1306 to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs. | |
1307 Newer Linux kernel versions don't have this problem. | |
1308 | |
1309 * src/Makefile and lib-src/Makefile are truncated--most of the file missing. | |
1310 | |
1311 This can happen if configure uses GNU sed version 2.03. That version | |
1312 had a bug. GNU sed version 2.05 works properly. | |
1313 | |
1314 * Slow startup on X11R6 with X windows. | |
1315 | |
1316 If Emacs takes two minutes to start up on X11R6, see if your X | |
1317 resources specify any Adobe fonts. That causes the type-1 font | |
1318 renderer to start up, even if the font you asked for is not a type-1 | |
1319 font. | |
1320 | |
1321 One way to avoid this problem is to eliminate the type-1 fonts from | |
1322 your font path, like this: | |
1323 | |
1324 xset -fp /usr/X11R6/lib/X11/fonts/Type1/ | |
1325 | |
1326 * Pull-down menus appear in the wrong place, in the toolkit version of Emacs. | |
1327 | |
1328 An X resource of this form can cause the problem: | |
1329 | |
1330 Emacs*geometry: 80x55+0+0 | |
1331 | |
1332 This resource is supposed to apply, and does apply, to the menus | |
1333 individually as well as to Emacs frames. If that is not what you | |
1334 want, rewrite the resource. | |
1335 | |
1336 To check thoroughly for such resource specifications, use `xrdb | |
1337 -query' to see what resources the X server records, and also look at | |
1338 the user's ~/.Xdefaults and ~/.Xdefaults-* files. | |
1339 | |
1340 * --with-x-toolkit version crashes when used with shared libraries. | |
1341 | |
1342 On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others, | |
1343 unexec doesn't work properly with the shared library for the X | |
1344 toolkit. You might be able to work around this by using a nonshared | |
1345 libXt.a library. The real fix is to upgrade the various versions of | |
1346 unexec and/or ralloc. We think this has been fixed on Sunos 4 | |
1347 and Solaris in version 19.29. | |
1348 | |
1349 * `make install' fails on install-doc with `Error 141'. | |
1350 | |
1351 This happens on Ultrix 4.2 due to failure of a pipeline of tar | |
1352 commands. We don't know why they fail, but the bug seems not to be in | |
1353 Emacs. The workaround is to run the shell command in install-doc by | |
1354 hand. | |
1355 | |
1356 * --with-x-toolkit option configures wrong on BSD/386. | |
1357 | |
1358 This problem is due to bugs in the shell in version 1.0 of BSD/386. | |
1359 The workaround is to edit the configure file to use some other shell, | |
1360 such as bash. | |
1361 | |
1362 * Subprocesses remain, hanging but not zombies, on Sunos 5.3. | |
1363 | |
1364 A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs | |
1365 exits. Sun patch # 101415-02 is part of the fix for this, but it only | |
1366 applies to ptys, and doesn't fix the problem with subprocesses | |
1367 communicating through pipes. | |
1368 | |
1369 * Mail is lost when sent to local aliases. | |
1370 | |
1371 Many emacs mail user agents (VM and rmail, for instance) use the | |
1372 sendmail.el library. This library can arrange for mail to be | |
1373 delivered by passing messages to the /usr/lib/sendmail (usually) | |
1374 program . In doing so, it passes the '-t' flag to sendmail, which | |
1375 means that the name of the recipient of the message is not on the | |
1376 command line and, therefore, that sendmail must parse the message to | |
1377 obtain the destination address. | |
1378 | |
1379 There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail. | |
1380 In short, when given the -t flag, the SunOS sendmail won't recognize | |
1381 non-local (i.e. NIS) aliases. It has been reported that the Solaris | |
1382 2.x versions of sendmail do not have this bug. For those using SunOS | |
1383 4.1, the best fix is to install sendmail V8 or IDA sendmail (which | |
1384 have other advantages over the regular sendmail as well). At the time | |
1385 of this writing, these official versions are available: | |
1386 | |
1387 Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail: | |
1388 sendmail.8.6.9.base.tar.Z (the base system source & documentation) | |
1389 sendmail.8.6.9.cf.tar.Z (configuration files) | |
1390 sendmail.8.6.9.misc.tar.Z (miscellaneous support programs) | |
1391 sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript) | |
1392 | |
1393 IDA sendmail on vixen.cso.uiuc.edu in /pub: | |
1394 sendmail-5.67b+IDA-1.5.tar.gz | |
1395 | |
1396 * On AIX, you get this message when running Emacs: | |
1397 | |
1398 Could not load program emacs | |
1399 Symbol smtcheckinit in csh is undefined | |
1400 Error was: Exec format error | |
1401 | |
1402 or this one: | |
1403 | |
1404 Could not load program .emacs | |
1405 Symbol _system_con in csh is undefined | |
1406 Symbol _fp_trapsta in csh is undefined | |
1407 Error was: Exec format error | |
1408 | |
1409 These can happen when you try to run on AIX 3.2.5 a program that was | |
1410 compiled with 3.2.4. The fix is to recompile. | |
1411 | |
1412 * On AIX, you get this compiler error message: | |
1413 | |
1414 Processing include file ./XMenuInt.h | |
1415 1501-106: (S) Include file X11/Xlib.h not found. | |
1416 | |
1417 This means your system was installed with only the X11 runtime i.d | |
1418 libraries. You have to find your sipo (bootable tape) and install | |
1419 X11Dev... with smit. | |
1420 | |
1421 * You "lose characters" after typing Compose Character key. | |
1422 | |
1423 This is because the Compose Character key is defined as the keysym | |
1424 Multi_key, and Emacs (seeing that) does the proper X11 | |
1425 character-composition processing. If you don't want your Compose key | |
1426 to do that, you can redefine it with xmodmap. | |
1427 | |
1428 For example, here's one way to turn it into a Meta key: | |
1429 | |
1430 xmodmap -e "keysym Multi_key = Meta_L" | |
1431 | |
1432 If all users at your site of a particular keyboard prefer Meta to | |
1433 Compose, you can make the remapping happen automatically by adding the | |
1434 xmodmap command to the xdm setup script for that display. | |
1435 | |
1436 * C-z just refreshes the screen instead of suspending Emacs. | |
1437 | |
1438 You are probably using a shell that doesn't support job control, even | |
1439 though the system itself is capable of it. Either use a different shell, | |
1440 or set the variable `cannot-suspend' to a non-nil value. | |
1441 | |
1442 * Watch out for .emacs files and EMACSLOADPATH environment vars | |
1443 | |
1444 These control the actions of Emacs. | |
1445 ~/.emacs is your Emacs init file. | |
1446 EMACSLOADPATH overrides which directories the function | |
1447 "load" will search. | |
1448 | |
1449 If you observe strange problems, check for these and get rid | |
1450 of them, then try again. | |
1451 | |
1452 * After running emacs once, subsequent invocations crash. | |
1453 | |
1454 Some versions of SVR4 have a serious bug in the implementation of the | |
1455 mmap () system call in the kernel; this causes emacs to run correctly | |
1456 the first time, and then crash when run a second time. | |
1457 | |
1458 Contact your vendor and ask for the mmap bug fix; in the mean time, | |
1459 you may be able to work around the problem by adding a line to your | |
1460 operating system description file (whose name is reported by the | |
1461 configure script) that reads: | |
1462 #define SYSTEM_MALLOC | |
1463 This makes Emacs use memory less efficiently, but seems to work around | |
1464 the kernel bug. | |
1465 | |
1466 * Inability to send an Alt-modified key, when Emacs is communicating | |
1467 directly with an X server. | |
1468 | |
1469 If you have tried to bind an Alt-modified key as a command, and it | |
1470 does not work to type the command, the first thing you should check is | |
1471 whether the key is getting through to Emacs. To do this, type C-h c | |
1472 followed by the Alt-modified key. C-h c should say what kind of event | |
1473 it read. If it says it read an Alt-modified key, then make sure you | |
1474 have made the key binding correctly. | |
1475 | |
1476 If C-h c reports an event that doesn't have the Alt modifier, it may | |
1477 be because your X server has no key for the Alt modifier. The X | |
1478 server that comes from MIT does not set up the Alt modifier by | |
1479 default. | |
1480 | |
1481 If your keyboard has keys named Alt, you can enable them as follows: | |
1482 | |
1483 xmodmap -e 'add mod2 = Alt_L' | |
1484 xmodmap -e 'add mod2 = Alt_R' | |
1485 | |
1486 If the keyboard has just one key named Alt, then only one of those | |
1487 commands is needed. The modifier `mod2' is a reasonable choice if you | |
1488 are using an unmodified MIT version of X. Otherwise, choose any | |
1489 modifier bit not otherwise used. | |
1490 | |
1491 If your keyboard does not have keys named Alt, you can use some other | |
1492 keys. Use the keysym command in xmodmap to turn a function key (or | |
1493 some other 'spare' key) into Alt_L or into Alt_R, and then use the | |
1494 commands show above to make them modifier keys. | |
1495 | |
1496 Note that if you have Alt keys but no Meta keys, Emacs translates Alt | |
1497 into Meta. This is because of the great importance of Meta in Emacs. | |
1498 | |
1499 * `Pid xxx killed due to text modification or page I/O error' | |
1500 | |
1501 On HP/UX, you can get that error when the Emacs executable is on an NFS | |
1502 file system. HP/UX responds this way if it tries to swap in a page and | |
1503 does not get a response from the server within a timeout whose default | |
1504 value is just ten seconds. | |
1505 | |
1506 If this happens to you, extend the timeout period. | |
1507 | |
1508 * `expand-file-name' fails to work on any but the machine you dumped Emacs on. | |
1509 | |
1510 On Ultrix, if you use any of the functions which look up information | |
1511 in the passwd database before dumping Emacs (say, by using | |
1512 expand-file-name in site-init.el), then those functions will not work | |
1513 in the dumped Emacs on any host but the one Emacs was dumped on. | |
1514 | |
1515 The solution? Don't use expand-file-name in site-init.el, or in | |
1516 anything it loads. Yuck - some solution. | |
1517 | |
1518 I'm not sure why this happens; if you can find out exactly what is | |
1519 going on, and perhaps find a fix or a workaround, please let us know. | |
1520 Perhaps the YP functions cache some information, the cache is included | |
1521 in the dumped Emacs, and is then inaccurate on any other host. | |
1522 | |
1523 * On some variants of SVR4, Emacs does not work at all with X. | |
1524 | |
1525 Try defining BROKEN_FIONREAD in your config.h file. If this solves | |
1526 the problem, please send a bug report to tell us this is needed; be | |
1527 sure to say exactly what type of machine and system you are using. | |
1528 | |
1529 * Linking says that the functions insque and remque are undefined. | |
1530 | |
1531 Change oldXMenu/Makefile by adding insque.o to the variable OBJS. | |
1532 | |
1533 * Emacs fails to understand most Internet host names, even though | |
1534 the names work properly with other programs on the same system. | |
1535 * Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0. | |
1536 * GNUs can't make contact with the specified host for nntp. | |
1537 | |
1538 This typically happens on Suns and other systems that use shared | |
1539 libraries. The cause is that the site has installed a version of the | |
1540 shared library which uses a name server--but has not installed a | |
1541 similar version of the unshared library which Emacs uses. | |
1542 | |
1543 The result is that most programs, using the shared library, work with | |
1544 the nameserver, but Emacs does not. | |
1545 | |
1546 The fix is to install an unshared library that corresponds to what you | |
1547 installed in the shared library, and then relink Emacs. | |
1548 | |
1549 On SunOS 4.1, simply define HAVE_RES_INIT. | |
1550 | |
1551 If you have already installed the name resolver in the file libresolv.a, | |
1552 then you need to compile Emacs to use that library. The easiest way to | |
1553 do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE | |
1554 or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro | |
1555 that is already in use in your configuration to supply some other libraries, | |
1556 be careful not to lose the others. | |
1557 | |
1558 Thus, you could start by adding this to config.h: | |
1559 | |
1560 #define LIBS_SYSTEM -lresolv | |
1561 | |
1562 Then if this gives you an error for redefining a macro, and you see that | |
1563 the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h | |
1564 again to say this: | |
1565 | |
1566 #define LIBS_SYSTEM -lresolv -lfoo -lbar | |
1567 | |
1568 * On a Sun running SunOS 4.1.1, you get this error message from GNU ld: | |
1569 | |
1570 /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment | |
1571 | |
1572 The problem is in the Sun shared C library, not in GNU ld. | |
1573 | |
1574 The solution is to install Patch-ID# 100267-03 from Sun. | |
1575 | |
1576 * Self documentation messages are garbled. | |
1577 | |
1578 This means that the file `etc/DOC-...' doesn't properly correspond | |
1579 with the Emacs executable. Redumping Emacs and then installing the | |
1580 corresponding pair of files should fix the problem. | |
1581 | |
1582 * Trouble using ptys on AIX. | |
1583 | |
1584 People often install the pty devices on AIX incorrectly. | |
1585 Use `smit pty' to reinstall them properly. | |
1586 | |
1587 * Shell mode on HP/UX gives the message, "`tty`: Ambiguous". | |
1588 | |
1589 christos@theory.tn.cornell.edu says: | |
1590 | |
1591 The problem is that in your .cshrc you have something that tries to | |
1592 execute `tty`. If you are not running the shell on a real tty then | |
1593 tty will print "not a tty". Csh expects one word in some places, | |
1594 but tty is giving it back 3. | |
1595 | |
1596 The solution is to add a pair of quotes around `tty` to make it a single | |
1597 word: | |
1598 | |
1599 if (`tty` == "/dev/console") | |
1600 | |
1601 should be changed to: | |
1602 | |
1603 if ("`tty`" == "/dev/console") | |
1604 | |
1605 Even better, move things that set up terminal sections out of .cshrc | |
1606 and into .login. | |
1607 | |
1608 * Using X Windows, control-shift-leftbutton makes Emacs hang. | |
1609 | |
1610 Use the shell command `xset bc' to make the old X Menu package work. | |
1611 | |
1612 * Emacs running under X Windows does not handle mouse clicks. | |
1613 * `emacs -geometry 80x20' finds a file named `80x20'. | |
1614 | |
1615 One cause of such problems is having (setq term-file-prefix nil) in | |
1616 your .emacs file. Another cause is a bad value of EMACSLOADPATH in | |
1617 the environment. | |
1618 | |
1619 * Emacs gets error message from linker on Sun. | |
1620 | |
1621 If the error message says that a symbol such as `f68881_used' or | |
1622 `ffpa_used' or `start_float' is undefined, this probably indicates | |
1623 that you have compiled some libraries, such as the X libraries, | |
1624 with a floating point option other than the default. | |
1625 | |
1626 It's not terribly hard to make this work with small changes in | |
1627 crt0.c together with linking with Fcrt1.o, Wcrt1.o or Mcrt1.o. | |
1628 However, the easiest approach is to build Xlib with the default | |
1629 floating point option: -fsoft. | |
1630 | |
1631 * Emacs fails to get default settings from X Windows server. | |
1632 | |
1633 The X library in X11R4 has a bug; it interchanges the 2nd and 3rd | |
1634 arguments to XGetDefaults. Define the macro XBACKWARDS in config.h to | |
1635 tell Emacs to compensate for this. | |
1636 | |
1637 I don't believe there is any way Emacs can determine for itself | |
1638 whether this problem is present on a given system. | |
1639 | |
1640 * Keyboard input gets confused after a beep when using a DECserver | |
1641 as a concentrator. | |
1642 | |
1643 This problem seems to be a matter of configuring the DECserver to use | |
1644 7 bit characters rather than 8 bit characters. | |
1645 | |
1646 * M-x shell persistently reports "Process shell exited abnormally with code 1". | |
1647 | |
1648 This happened on Suns as a result of what is said to be a bug in Sunos | |
1649 version 4.0.x. The only fix was to reboot the machine. | |
1650 | |
1651 * Programs running under terminal emulator do not recognize `emacs' | |
1652 terminal type. | |
1653 | |
1654 The cause of this is a shell startup file that sets the TERMCAP | |
1655 environment variable. The terminal emulator uses that variable to | |
1656 provide the information on the special terminal type that Emacs | |
1657 emulates. | |
1658 | |
1659 Rewrite your shell startup file so that it does not change TERMCAP | |
1660 in such a case. You could use the following conditional which sets | |
1661 it only if it is undefined. | |
1662 | |
1663 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file | |
1664 | |
1665 Or you could set TERMCAP only when you set TERM--which should not | |
1666 happen in a non-login shell. | |
1667 | |
1668 * X Windows doesn't work if DISPLAY uses a hostname. | |
1669 | |
1670 People have reported kernel bugs in certain systems that cause Emacs | |
1671 not to work with X Windows if DISPLAY is set using a host name. But | |
1672 the problem does not occur if DISPLAY is set to `unix:0.0'. I think | |
1673 the bug has to do with SIGIO or FIONREAD. | |
1674 | |
1675 You may be able to compensate for the bug by doing (set-input-mode nil nil). | |
1676 However, that has the disadvantage of turning off interrupts, so that | |
1677 you are unable to quit out of a Lisp program by typing C-g. | |
1678 | |
1679 The easy way to do this is to put | |
1680 | |
1681 (setq x-sigio-bug t) | |
1682 | |
1683 in your site-init.el file. | |
1684 | |
1685 * Problem with remote X server on Suns. | |
1686 | |
1687 On a Sun, running Emacs on one machine with the X server on another | |
1688 may not work if you have used the unshared system libraries. This | |
1689 is because the unshared libraries fail to use YP for host name lookup. | |
1690 As a result, the host name you specify may not be recognized. | |
1691 | |
1692 * Shell mode ignores interrupts on Apollo Domain | |
1693 | |
1694 You may find that M-x shell prints the following message: | |
1695 | |
1696 Warning: no access to tty; thus no job control in this shell... | |
1697 | |
1698 This can happen if there are not enough ptys on your system. | |
1699 Here is how to make more of them. | |
1700 | |
1701 % cd /dev | |
1702 % ls pty* | |
1703 # shows how many pty's you have. I had 8, named pty0 to pty7) | |
1704 % /etc/crpty 8 | |
1705 # creates eight new pty's | |
1706 | |
1707 * Fatal signal in the command temacs -l loadup inc dump | |
1708 | |
1709 This command is the final stage of building Emacs. It is run by the | |
1710 Makefile in the src subdirectory, or by build.com on VMS. | |
1711 | |
1712 It has been known to get fatal errors due to insufficient swapping | |
1713 space available on the machine. | |
1714 | |
1715 On 68000's, it has also happened because of bugs in the | |
1716 subroutine `alloca'. Verify that `alloca' works right, even | |
1717 for large blocks (many pages). | |
1718 | |
1719 * test-distrib says that the distribution has been clobbered | |
1720 * or, temacs prints "Command key out of range 0-127" | |
1721 * or, temacs runs and dumps emacs, but emacs totally fails to work. | |
1722 * or, temacs gets errors dumping emacs | |
1723 | |
1724 This can be because the .elc files have been garbled. Do not be | |
1725 fooled by the fact that most of a .elc file is text: these are | |
1726 binary files and can contain all 256 byte values. | |
1727 | |
1728 In particular `shar' cannot be used for transmitting GNU Emacs. | |
1729 It typically truncates "lines". What appear to be "lines" in | |
1730 a binary file can of course be of any length. Even once `shar' | |
1731 itself is made to work correctly, `sh' discards null characters | |
1732 when unpacking the shell archive. | |
1733 | |
1734 I have also seen character \177 changed into \377. I do not know | |
1735 what transfer means caused this problem. Various network | |
1736 file transfer programs are suspected of clobbering the high bit. | |
1737 | |
1738 If you have a copy of Emacs that has been damaged in its | |
1739 nonprinting characters, you can fix them: | |
1740 | |
1741 1) Record the names of all the .elc files. | |
1742 2) Delete all the .elc files. | |
1743 3) Recompile alloc.c with a value of PURESIZE twice as large. | |
1744 (See puresize.h.) You might as well save the old alloc.o. | |
1745 4) Remake emacs. It should work now. | |
1746 5) Running emacs, do Meta-x byte-compile-file repeatedly | |
1747 to recreate all the .elc files that used to exist. | |
1748 You may need to increase the value of the variable | |
1749 max-lisp-eval-depth to succeed in running the compiler interpreted | |
1750 on certain .el files. 400 was sufficient as of last report. | |
1751 6) Reinstall the old alloc.o (undoing changes to alloc.c if any) | |
1752 and remake temacs. | |
1753 7) Remake emacs. It should work now, with valid .elc files. | |
1754 | |
1755 * temacs prints "Pure Lisp storage exhausted" | |
1756 | |
1757 This means that the Lisp code loaded from the .elc and .el | |
1758 files during temacs -l loadup inc dump took up more | |
1759 space than was allocated. | |
1760 | |
1761 This could be caused by | |
1762 1) adding code to the preloaded Lisp files | |
1763 2) adding more preloaded files in loadup.el | |
1764 3) having a site-init.el or site-load.el which loads files. | |
1765 Note that ANY site-init.el or site-load.el is nonstandard; | |
1766 if you have received Emacs from some other site | |
1767 and it contains a site-init.el or site-load.el file, consider | |
1768 deleting that file. | |
1769 4) getting the wrong .el or .elc files | |
1770 (not from the directory you expected). | |
1771 5) deleting some .elc files that are supposed to exist. | |
1772 This would cause the source files (.el files) to be | |
1773 loaded instead. They take up more room, so you lose. | |
1774 6) a bug in the Emacs distribution which underestimates | |
1775 the space required. | |
1776 | |
1777 If the need for more space is legitimate, change the definition | |
1778 of PURESIZE in puresize.h. | |
1779 | |
1780 But in some of the cases listed above, this problem is a consequence | |
1781 of something else that is wrong. Be sure to check and fix the real | |
1782 problem. | |
1783 | |
1784 * Changes made to .el files do not take effect. | |
1785 | |
1786 You may have forgotten to recompile them into .elc files. | |
1787 Then the old .elc files will be loaded, and your changes | |
1788 will not be seen. To fix this, do M-x byte-recompile-directory | |
1789 and specify the directory that contains the Lisp files. | |
1790 | |
1791 Emacs should print a warning when loading a .elc file which is older | |
1792 than the corresponding .el file. | |
1793 | |
1794 * The dumped Emacs crashes when run, trying to write pure data. | |
1795 | |
1796 Two causes have been seen for such problems. | |
1797 | |
1798 1) On a system where getpagesize is not a system call, it is defined | |
1799 as a macro. If the definition (in both unexec.c and malloc.c) is wrong, | |
1800 it can cause problems like this. You might be able to find the correct | |
1801 value in the man page for a.out (5). | |
1802 | |
1803 2) Some systems allocate variables declared static among the | |
1804 initialized variables. Emacs makes all initialized variables in most | |
1805 of its files pure after dumping, but the variables declared static and | |
1806 not initialized are not supposed to be pure. On these systems you | |
1807 may need to add "#define static" to the m- or the s- file. | |
1808 | |
1809 * Compilation errors on VMS. | |
1810 | |
1811 You will get warnings when compiling on VMS because there are | |
1812 variable names longer than 32 (or whatever it is) characters. | |
1813 This is not an error. Ignore it. | |
1814 | |
1815 VAX C does not support #if defined(foo). Uses of this construct | |
1816 were removed, but some may have crept back in. They must be rewritten. | |
1817 | |
1818 There is a bug in the C compiler which fails to sign extend characters | |
1819 in conditional expressions. The bug is: | |
1820 char c = -1, d = 1; | |
1821 int i; | |
1822 | |
1823 i = d ? c : d; | |
1824 The result is i == 255; the fix is to typecast the char in the | |
1825 conditional expression as an (int). Known occurrences of such | |
1826 constructs in Emacs have been fixed. | |
1827 | |
1828 * rmail gets error getting new mail | |
1829 | |
1830 rmail gets new mail from /usr/spool/mail/$USER using a program | |
1831 called `movemail'. This program interlocks with /bin/mail using | |
1832 the protocol defined by /bin/mail. | |
1833 | |
1834 There are two different protocols in general use. One of them uses | |
1835 the `flock' system call. The other involves creating a lock file; | |
1836 `movemail' must be able to write in /usr/spool/mail in order to do | |
1837 this. You control which one is used by defining, or not defining, | |
1838 the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes. | |
1839 IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR | |
1840 SYSTEM, YOU CAN LOSE MAIL! | |
1841 | |
1842 If your system uses the lock file protocol, and fascist restrictions | |
1843 prevent ordinary users from writing the lock files in /usr/spool/mail, | |
1844 you may need to make `movemail' setgid to a suitable group such as | |
1845 `mail'. You can use these commands (as root): | |
1846 | |
1847 chgrp mail movemail | |
1848 chmod 2755 movemail | |
1849 | |
1850 If your system uses the lock file protocol, and fascist restrictions | |
1851 prevent ordinary users from writing the lock files in /usr/spool/mail, | |
1852 you may need to make `movemail' setgid to a suitable group such as | |
1853 `mail'. To do this, use the following commands (as root) after doing the | |
1854 make install. | |
1855 | |
1856 chgrp mail movemail | |
1857 chmod 2755 movemail | |
1858 | |
1859 Installation normally copies movemail from the build directory to an | |
1860 installation directory which is usually under /usr/local/lib. The | |
1861 installed copy of movemail is usually in the directory | |
1862 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and | |
1863 mode of the installed copy; changing the group and mode of the build | |
1864 directory copy is ineffective. | |
1865 | |
1866 * Emacs spontaneously displays "I-search: " at the bottom of the screen. | |
1867 | |
1868 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being | |
1869 used. C-s/C-q flow control is bad for Emacs editors because it takes | |
1870 away C-s and C-q as user commands. Since editors do not output long | |
1871 streams of text without user commands, there is no need for a | |
1872 user-issuable "stop output" command in an editor; therefore, a | |
1873 properly designed flow control mechanism would transmit all possible | |
1874 input characters without interference. Designing such a mechanism is | |
1875 easy, for a person with at least half a brain. | |
1876 | |
1877 There are three possible reasons why flow control could be taking place: | |
1878 | |
1879 1) Terminal has not been told to disable flow control | |
1880 2) Insufficient padding for the terminal in use | |
1881 3) Some sort of terminal concentrator or line switch is responsible | |
1882 | |
1883 First of all, many terminals have a set-up mode which controls whether | |
1884 they generate XON/XOFF flow control characters. This must be set to | |
1885 "no XON/XOFF" in order for Emacs to work. Sometimes there is an | |
1886 escape sequence that the computer can send to turn flow control off | |
1887 and on. If so, perhaps the termcap `ti' string should turn flow | |
1888 control off, and the `te' string should turn it on. | |
1889 | |
1890 Once the terminal has been told "no flow control", you may find it | |
1891 needs more padding. The amount of padding Emacs sends is controlled | |
1892 by the termcap entry for the terminal in use, and by the output baud | |
1893 rate as known by the kernel. The shell command `stty' will print | |
1894 your output baud rate; `stty' with suitable arguments will set it if | |
1895 it is wrong. Setting to a higher speed causes increased padding. If | |
1896 the results are wrong for the correct speed, there is probably a | |
1897 problem in the termcap entry. You must speak to a local Unix wizard | |
1898 to fix this. Perhaps you are just using the wrong terminal type. | |
1899 | |
1900 For terminals that lack a "no flow control" mode, sometimes just | |
1901 giving lots of padding will prevent actual generation of flow control | |
1902 codes. You might as well try it. | |
1903 | |
1904 If you are really unlucky, your terminal is connected to the computer | |
1905 through a concentrator which sends XON/XOFF flow control to the | |
1906 computer, or it insists on sending flow control itself no matter how | |
1907 much padding you give it. Unless you can figure out how to turn flow | |
1908 control off on this concentrator (again, refer to your local wizard), | |
1909 you are screwed! You should have the terminal or concentrator | |
1910 replaced with a properly designed one. In the mean time, some drastic | |
1911 measures can make Emacs semi-work. | |
1912 | |
1913 You can make Emacs ignore C-s and C-q and let the operating system | |
1914 handle them. To do this on a per-session basis, just type M-x | |
1915 enable-flow-control RET. You will see a message that C-\ and C-^ are | |
1916 now translated to C-s and C-q. (Use the same command M-x | |
1917 enable-flow-control to turn *off* this special mode. It toggles flow | |
1918 control handling.) | |
1919 | |
1920 If C-\ and C-^ are inconvenient for you (for example, if one of them | |
1921 is the escape character of your terminal concentrator), you can choose | |
1922 other characters by setting the variables flow-control-c-s-replacement | |
1923 and flow-control-c-q-replacement. But choose carefully, since all | |
1924 other control characters are already used by emacs. | |
1925 | |
1926 IMPORTANT: if you type C-s by accident while flow control is enabled, | |
1927 Emacs output will freeze, and you will have to remember to type C-q in | |
1928 order to continue. | |
1929 | |
1930 If you work in an environment where a majority of terminals of a | |
1931 certain type are flow control hobbled, you can use the function | |
1932 `enable-flow-control-on' to turn on this flow control avoidance scheme | |
1933 automatically. Here is an example: | |
1934 | |
1935 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131") | |
1936 | |
1937 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled | |
1938 and good vt200 terminals), you can still run enable-flow-control | |
1939 manually. | |
1940 | |
1941 I have no intention of ever redesigning the Emacs command set for the | |
1942 assumption that terminals use C-s/C-q flow control. XON/XOFF flow | |
1943 control technique is a bad design, and terminals that need it are bad | |
1944 merchandise and should not be purchased. Now that X is becoming | |
1945 widespread, XON/XOFF seems to be on the way out. If you can get some | |
1946 use out of GNU Emacs on inferior terminals, more power to you, but I | |
1947 will not make Emacs worse for properly designed systems for the sake | |
1948 of inferior systems. | |
1949 | |
1950 * Control-S and Control-Q commands are ignored completely. | |
1951 | |
1952 For some reason, your system is using brain-damaged C-s/C-q flow | |
1953 control despite Emacs's attempts to turn it off. Perhaps your | |
1954 terminal is connected to the computer through a concentrator | |
1955 that wants to use flow control. | |
1956 | |
1957 You should first try to tell the concentrator not to use flow control. | |
1958 If you succeed in this, try making the terminal work without | |
1959 flow control, as described in the preceding section. | |
1960 | |
1961 If that line of approach is not successful, map some other characters | |
1962 into C-s and C-q using keyboard-translate-table. The example above | |
1963 shows how to do this with C-^ and C-\. | |
1964 | |
1965 * Control-S and Control-Q commands are ignored completely on a net connection. | |
1966 | |
1967 Some versions of rlogin (and possibly telnet) do not pass flow | |
1968 control characters to the remote system to which they connect. | |
1969 On such systems, emacs on the remote system cannot disable flow | |
1970 control on the local system. | |
1971 | |
1972 One way to cure this is to disable flow control on the local host | |
1973 (the one running rlogin, not the one running rlogind) using the | |
1974 stty command, before starting the rlogin process. On many systems, | |
1975 "stty start u stop u" will do this. | |
1976 | |
1977 Some versions of tcsh will prevent even this from working. One way | |
1978 around this is to start another shell before starting rlogin, and | |
1979 issue the stty command to disable flow control from that shell. | |
1980 | |
1981 If none of these methods work, the best solution is to type | |
1982 M-x enable-flow-control at the beginning of your emacs session, or | |
1983 if you expect the problem to continue, add a line such as the | |
1984 following to your .emacs (on the host running rlogind): | |
1985 | |
1986 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131") | |
1987 | |
1988 See the entry about spontaneous display of I-search (above) for more | |
1989 info. | |
1990 | |
1991 * Screen is updated wrong, but only on one kind of terminal. | |
1992 | |
1993 This could mean that the termcap entry you are using for that | |
1994 terminal is wrong, or it could mean that Emacs has a bug handing | |
1995 the combination of features specified for that terminal. | |
1996 | |
1997 The first step in tracking this down is to record what characters | |
1998 Emacs is sending to the terminal. Execute the Lisp expression | |
1999 (open-termscript "./emacs-script") to make Emacs write all | |
2000 terminal output into the file ~/emacs-script as well; then do | |
2001 what makes the screen update wrong, and look at the file | |
2002 and decode the characters using the manual for the terminal. | |
2003 There are several possibilities: | |
2004 | |
2005 1) The characters sent are correct, according to the terminal manual. | |
2006 | |
2007 In this case, there is no obvious bug in Emacs, and most likely you | |
2008 need more padding, or possibly the terminal manual is wrong. | |
2009 | |
2010 2) The characters sent are incorrect, due to an obscure aspect | |
2011 of the terminal behavior not described in an obvious way | |
2012 by termcap. | |
2013 | |
2014 This case is hard. It will be necessary to think of a way for | |
2015 Emacs to distinguish between terminals with this kind of behavior | |
2016 and other terminals that behave subtly differently but are | |
2017 classified the same by termcap; or else find an algorithm for | |
2018 Emacs to use that avoids the difference. Such changes must be | |
2019 tested on many kinds of terminals. | |
2020 | |
2021 3) The termcap entry is wrong. | |
2022 | |
2023 See the file etc/TERMS for information on changes | |
2024 that are known to be needed in commonly used termcap entries | |
2025 for certain terminals. | |
2026 | |
2027 4) The characters sent are incorrect, and clearly cannot be | |
2028 right for any terminal with the termcap entry you were using. | |
2029 | |
2030 This is unambiguously an Emacs bug, and can probably be fixed | |
2031 in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c. | |
2032 | |
2033 * Output from Control-V is slow. | |
2034 | |
2035 On many bit-map terminals, scrolling operations are fairly slow. | |
2036 Often the termcap entry for the type of terminal in use fails | |
2037 to inform Emacs of this. The two lines at the bottom of the screen | |
2038 before a Control-V command are supposed to appear at the top after | |
2039 the Control-V command. If Emacs thinks scrolling the lines is fast, | |
2040 it will scroll them to the top of the screen. | |
2041 | |
2042 If scrolling is slow but Emacs thinks it is fast, the usual reason is | |
2043 that the termcap entry for the terminal you are using does not | |
2044 specify any padding time for the `al' and `dl' strings. Emacs | |
2045 concludes that these operations take only as much time as it takes to | |
2046 send the commands at whatever line speed you are using. You must | |
2047 fix the termcap entry to specify, for the `al' and `dl', as much | |
2048 time as the operations really take. | |
2049 | |
2050 Currently Emacs thinks in terms of serial lines which send characters | |
2051 at a fixed rate, so that any operation which takes time for the | |
2052 terminal to execute must also be padded. With bit-map terminals | |
2053 operated across networks, often the network provides some sort of | |
2054 flow control so that padding is never needed no matter how slow | |
2055 an operation is. You must still specify a padding time if you want | |
2056 Emacs to realize that the operation takes a long time. This will | |
2057 cause padding characters to be sent unnecessarily, but they do | |
2058 not really cost much. They will be transmitted while the scrolling | |
2059 is happening and then discarded quickly by the terminal. | |
2060 | |
2061 Most bit-map terminals provide commands for inserting or deleting | |
2062 multiple lines at once. Define the `AL' and `DL' strings in the | |
2063 termcap entry to say how to do these things, and you will have | |
2064 fast output without wasted padding characters. These strings should | |
2065 each contain a single %-spec saying how to send the number of lines | |
2066 to be scrolled. These %-specs are like those in the termcap | |
2067 `cm' string. | |
2068 | |
2069 You should also define the `IC' and `DC' strings if your terminal | |
2070 has a command to insert or delete multiple characters. These | |
2071 take the number of positions to insert or delete as an argument. | |
2072 | |
2073 A `cs' string to set the scrolling region will reduce the amount | |
2074 of motion you see on the screen when part of the screen is scrolled. | |
2075 | |
2076 * Your Delete key sends a Backspace to the terminal, using an AIXterm. | |
2077 | |
2078 The solution is to include in your .Xdefaults the lines: | |
2079 | |
2080 *aixterm.Translations: #override <Key>BackSpace: string(0x7f) | |
2081 aixterm*ttyModes: erase ^? | |
2082 | |
2083 This makes your Backspace key send DEL (ASCII 127). | |
2084 | |
2085 * You type Control-H (Backspace) expecting to delete characters. | |
2086 | |
2087 Put `stty dec' in your .login file and your problems will disappear | |
2088 after a day or two. | |
2089 | |
2090 The choice of Backspace for erasure was based on confusion, caused by | |
2091 the fact that backspacing causes erasure (later, when you type another | |
2092 character) on most display terminals. But it is a mistake. Deletion | |
2093 of text is not the same thing as backspacing followed by failure to | |
2094 overprint. I do not wish to propagate this confusion by conforming | |
2095 to it. | |
2096 | |
2097 For this reason, I believe `stty dec' is the right mode to use, | |
2098 and I have designed Emacs to go with that. If there were a thousand | |
2099 other control characters, I would define Control-h to delete as well; | |
2100 but there are not very many other control characters, and I think | |
2101 that providing the most mnemonic possible Help character is more | |
2102 important than adapting to people who don't use `stty dec'. | |
2103 | |
2104 If you are obstinate about confusing buggy overprinting with deletion, | |
2105 you can redefine Backspace in your .emacs file: | |
2106 (global-set-key "\b" 'delete-backward-char) | |
2107 You can probably access help-command via f1. | |
2108 | |
2109 * Editing files through RFS gives spurious "file has changed" warnings. | |
2110 It is possible that a change in Emacs 18.37 gets around this problem, | |
2111 but in case not, here is a description of how to fix the RFS bug that | |
2112 causes it. | |
2113 | |
2114 There was a serious pair of bugs in the handling of the fsync() system | |
2115 call in the RFS server. | |
2116 | |
2117 The first is that the fsync() call is handled as another name for the | |
2118 close() system call (!!). It appears that fsync() is not used by very | |
2119 many programs; Emacs version 18 does an fsync() before closing files | |
2120 to make sure that the bits are on the disk. | |
2121 | |
2122 This is fixed by the enclosed patch to the RFS server. | |
2123 | |
2124 The second, more serious problem, is that fsync() is treated as a | |
2125 non-blocking system call (i.e., it's implemented as a message that | |
2126 gets sent to the remote system without waiting for a reply). Fsync is | |
2127 a useful tool for building atomic file transactions. Implementing it | |
2128 as a non-blocking RPC call (when the local call blocks until the sync | |
2129 is done) is a bad idea; unfortunately, changing it will break the RFS | |
2130 protocol. No fix was supplied for this problem. | |
2131 | |
2132 (as always, your line numbers may vary) | |
2133 | |
2134 % rcsdiff -c -r1.2 serversyscall.c | |
2135 RCS file: RCS/serversyscall.c,v | |
2136 retrieving revision 1.2 | |
2137 diff -c -r1.2 serversyscall.c | |
2138 *** /tmp/,RCSt1003677 Wed Jan 28 15:15:02 1987 | |
2139 --- serversyscall.c Wed Jan 28 15:14:48 1987 | |
2140 *************** | |
2141 *** 163,169 **** | |
2142 /* | |
2143 * No return sent for close or fsync! | |
2144 */ | |
2145 ! if (syscall == RSYS_close || syscall == RSYS_fsync) | |
2146 proc->p_returnval = deallocate_fd(proc, msg->m_args[0]); | |
2147 else | |
2148 { | |
2149 --- 166,172 ---- | |
2150 /* | |
2151 * No return sent for close or fsync! | |
2152 */ | |
2153 ! if (syscall == RSYS_close) | |
2154 proc->p_returnval = deallocate_fd(proc, msg->m_args[0]); | |
2155 else | |
2156 { | |
2157 | |
2158 * Vax C compiler bugs affecting Emacs. | |
2159 | |
2160 You may get one of these problems compiling Emacs: | |
2161 | |
2162 foo.c line nnn: compiler error: no table entry for op STASG | |
2163 foo.c: fatal error in /lib/ccom | |
2164 | |
2165 These are due to bugs in the C compiler; the code is valid C. | |
2166 Unfortunately, the bugs are unpredictable: the same construct | |
2167 may compile properly or trigger one of these bugs, depending | |
2168 on what else is in the source file being compiled. Even changes | |
2169 in header files that should not affect the file being compiled | |
2170 can affect whether the bug happens. In addition, sometimes files | |
2171 that compile correctly on one machine get this bug on another machine. | |
2172 | |
2173 As a result, it is hard for me to make sure this bug will not affect | |
2174 you. I have attempted to find and alter these constructs, but more | |
2175 can always appear. However, I can tell you how to deal with it if it | |
2176 should happen. The bug comes from having an indexed reference to an | |
2177 array of Lisp_Objects, as an argument in a function call: | |
2178 Lisp_Object *args; | |
2179 ... | |
2180 ... foo (5, args[i], ...)... | |
2181 putting the argument into a temporary variable first, as in | |
2182 Lisp_Object *args; | |
2183 Lisp_Object tem; | |
2184 ... | |
2185 tem = args[i]; | |
2186 ... foo (r, tem, ...)... | |
2187 causes the problem to go away. | |
2188 The `contents' field of a Lisp vector is an array of Lisp_Objects, | |
2189 so you may see the problem happening with indexed references to that. | |
2190 | |
2191 * 68000 C compiler problems | |
2192 | |
2193 Various 68000 compilers have different problems. | |
2194 These are some that have been observed. | |
2195 | |
2196 ** Using value of assignment expression on union type loses. | |
2197 This means that x = y = z; or foo (x = z); does not work | |
2198 if x is of type Lisp_Object. | |
2199 | |
2200 ** "cannot reclaim" error. | |
2201 | |
2202 This means that an expression is too complicated. You get the correct | |
2203 line number in the error message. The code must be rewritten with | |
2204 simpler expressions. | |
2205 | |
2206 ** XCONS, XSTRING, etc macros produce incorrect code. | |
2207 | |
2208 If temacs fails to run at all, this may be the cause. | |
2209 Compile this test program and look at the assembler code: | |
2210 | |
2211 struct foo { char x; unsigned int y : 24; }; | |
2212 | |
2213 lose (arg) | |
2214 struct foo arg; | |
2215 { | |
2216 test ((int *) arg.y); | |
2217 } | |
2218 | |
2219 If the code is incorrect, your compiler has this problem. | |
2220 In the XCONS, etc., macros in lisp.h you must replace (a).u.val with | |
2221 ((a).u.val + coercedummy) where coercedummy is declared as int. | |
2222 | |
2223 This problem will not happen if the m-...h file for your type | |
2224 of machine defines NO_UNION_TYPE. That is the recommended setting now. | |
2225 | |
2226 * C compilers lose on returning unions | |
2227 | |
2228 I hear that some C compilers cannot handle returning a union type. | |
2229 Most of the functions in GNU Emacs return type Lisp_Object, which is | |
2230 defined as a union on some rare architectures. | |
2231 | |
2232 This problem will not happen if the m-...h file for your type | |
2233 of machine defines NO_UNION_TYPE. | |
2234 |