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