1 |
This file describes various problems that have been encountered |
This file describes various problems that have been encountered |
2 |
in compiling, installing and running GNU Emacs. |
in compiling, installing and running GNU Emacs. |
3 |
|
|
4 |
|
* Emacs crashes on Mac OS X (Carbon) after system software upgrade. |
5 |
|
|
6 |
|
This problem seems to be now solved by Steven Tamm's patch to |
7 |
|
unexmacosx.c on Nov 24, 2002. |
8 |
|
|
9 |
|
Between Mac OS X release 10.2.1 and 10.2.2 there was an incompatible |
10 |
|
change in the memory allocator that causes a EXC_BAD_ACCESS error near |
11 |
|
xrealloc(). Relinking the application (by deleting src/temacs and |
12 |
|
running make) will solve the problem. It appears to be caused by some |
13 |
|
problems with the unexec code and its interaction with libSystem.B. |
14 |
|
|
15 |
|
* Characters from the mule-unicode charsets aren't displayed under X. |
16 |
|
|
17 |
|
XFree86 4 contains many fonts in iso10646-1 encoding which have |
18 |
|
minimal character repertoires (whereas the encoding is meant to be a |
19 |
|
reasonable indication of the repertoire). Emacs may choose one of |
20 |
|
these to display characters from the mule-unicode charsets and then |
21 |
|
typically won't be able to find the glyphs to display many characters. |
22 |
|
(Check with C-u C-x = .) To avoid this, you may need to use a fontset |
23 |
|
which sets the font for the mule-unicode sets explicitly. E.g. to use |
24 |
|
GNU unifont, include in the fontset spec: |
25 |
|
|
26 |
|
mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\ |
27 |
|
mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\ |
28 |
|
mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1 |
29 |
|
|
30 |
|
* Problems with file dialogs in Emacs built with Open Motif. |
31 |
|
|
32 |
|
When Emacs 21 is built with Open Motif 2.1, it can happen that the |
33 |
|
graphical file dialog boxes do not work properly. The "OK", "Filter" |
34 |
|
and "Cancel" buttons do not respond to mouse clicks. Dragging the |
35 |
|
file dialog window usually causes the buttons to work again. |
36 |
|
|
37 |
|
The solution is to use LessTif instead. LessTif is a free replacement |
38 |
|
for Motif. See the file INSTALL for information on how to do this. |
39 |
|
|
40 |
|
Another workaround is not to use the mouse to trigger file prompts, |
41 |
|
but to use the keyboard. This way, you will be prompted for a file in |
42 |
|
the minibuffer instead of a graphical file dialog. |
43 |
|
|
44 |
|
* Emacs reports a BadAtom error (from X) running on Solaris 7 or 8. |
45 |
|
|
46 |
|
This happens when Emacs was built on some other version of Solaris. |
47 |
|
Rebuild it on Solaris 8. |
48 |
|
|
49 |
|
* Mule-UCS loads very slowly. |
50 |
|
|
51 |
|
Changes to Emacs internals interact badly with Mule-UCS's `un-define' |
52 |
|
library, which is the usual interface to Mule-UCS. Apply the |
53 |
|
following patch to Mule-UCS 0.84 and rebuild it. That will help, |
54 |
|
though loading will still be slower than in Emacs 20. (Some |
55 |
|
distributions, such as Debian, may already have applied such a patch.) |
56 |
|
|
57 |
|
--- lisp/un-define.el 6 Mar 2001 22:41:38 -0000 1.30 |
58 |
|
+++ lisp/un-define.el 19 Apr 2002 18:34:26 -0000 |
59 |
|
@@ -610,13 +624,21 @@ by calling post-read-conversion and pre- |
60 |
|
|
61 |
|
(mapcar |
62 |
|
(lambda (x) |
63 |
|
- (mapcar |
64 |
|
- (lambda (y) |
65 |
|
- (mucs-define-coding-system |
66 |
|
- (nth 0 y) (nth 1 y) (nth 2 y) |
67 |
|
- (nth 3 y) (nth 4 y) (nth 5 y) (nth 6 y)) |
68 |
|
- (coding-system-put (car y) 'alias-coding-systems (list (car x)))) |
69 |
|
- (cdr x))) |
70 |
|
+ (if (fboundp 'register-char-codings) |
71 |
|
+ ;; Mule 5, where we don't need the eol-type specified and |
72 |
|
+ ;; register-char-codings may be very slow for these coding |
73 |
|
+ ;; system definitions. |
74 |
|
+ (let ((y (cadr x))) |
75 |
|
+ (mucs-define-coding-system |
76 |
|
+ (car x) (nth 1 y) (nth 2 y) |
77 |
|
+ (nth 3 y) (nth 4 y) (nth 5 y))) |
78 |
|
+ (mapcar |
79 |
|
+ (lambda (y) |
80 |
|
+ (mucs-define-coding-system |
81 |
|
+ (nth 0 y) (nth 1 y) (nth 2 y) |
82 |
|
+ (nth 3 y) (nth 4 y) (nth 5 y) (nth 6 y)) |
83 |
|
+ (coding-system-put (car y) 'alias-coding-systems (list (car x))))) |
84 |
|
+ (cdr x))) |
85 |
|
`((utf-8 |
86 |
|
(utf-8-unix |
87 |
|
?u "UTF-8 coding system" |
88 |
|
|
89 |
|
Note that Emacs has native support for Unicode, roughly equivalent to |
90 |
|
Mule-UCS's, so you may not need it. |
91 |
|
|
92 |
* Building Emacs with GCC 2.9x fails in the `src' directory. |
* Building Emacs with GCC 2.9x fails in the `src' directory. |
93 |
|
|
94 |
This may happen if you use a development version of GNU `cpp' from one |
This may happen if you use a development version of GNU `cpp' from one |
203 |
* JPEG images aren't displayed. |
* JPEG images aren't displayed. |
204 |
|
|
205 |
This has been reported when Emacs is built with jpeg-6a library. |
This has been reported when Emacs is built with jpeg-6a library. |
206 |
Upgrading to jpeg-6b solves the problem. |
Upgrading to jpeg-6b solves the problem. Configure checks for the |
207 |
|
correct version, but this problem could occur if a binary built |
208 |
|
against a shared libjpeg is run on a system with an older version. |
209 |
|
|
210 |
* Building `ctags' for MS-Windows with the MinGW port of GCC fails. |
* Building `ctags' for MS-Windows with the MinGW port of GCC fails. |
211 |
|
|
221 |
* If not debugging, assert does nothing. |
* If not debugging, assert does nothing. |
222 |
*/ |
*/ |
223 |
! #define assert(x) ((void)0); |
! #define assert(x) ((void)0); |
224 |
|
|
225 |
#else /* debugging enabled */ |
#else /* debugging enabled */ |
226 |
|
|
227 |
--- 41,47 ---- |
--- 41,47 ---- |
228 |
/* |
/* |
229 |
* If not debugging, assert does nothing. |
* If not debugging, assert does nothing. |
230 |
*/ |
*/ |
231 |
! #define assert(x) ((void)0) |
! #define assert(x) ((void)0) |
232 |
|
|
233 |
#else /* debugging enabled */ |
#else /* debugging enabled */ |
234 |
|
|
235 |
|
|
236 |
|
|
237 |
* Improving performance with slow X connections |
* Improving performance with slow X connections |
238 |
|
|
239 |
If you don't need X Input Methods (XIM) for entering text in some |
There are several ways to improve this performance, any subset of which can |
240 |
language you use, you can improve performance on WAN links by |
be carried out at the same time: |
|
configuring Emacs with option `--without-xim'. Configuring Emacs |
|
|
without XIM does not affect the use of Emacs' own input methods, which |
|
|
are part of the Leim package. |
|
241 |
|
|
242 |
If the connection is very slow, you might also want to consider |
1) If you don't need X Input Methods (XIM) for entering text in some |
243 |
switching off scroll bars, menu bar, and tool bar. |
language you use, you can improve performance on WAN links by |
244 |
|
configuring Emacs with option `--without-xim'. Configuring Emacs |
245 |
|
without XIM does not affect the use of Emacs' own input methods, which |
246 |
|
are part of the Leim package. |
247 |
|
|
248 |
|
2) If the connection is very slow, you might also want to consider |
249 |
|
switching off scroll bars, menu bar, and tool bar. |
250 |
|
|
251 |
|
3) Use ssh to forward the X connection, and enable compression on this |
252 |
|
forwarded X connection (ssh -XC remotehostname emacs ...). |
253 |
|
|
254 |
|
4) Use lbxproxy on the remote end of the connection. This is an interface |
255 |
|
to the low bandwidth X extension in most modern X servers, which |
256 |
|
improves performance dramatically, at the slight expense of correctness |
257 |
|
of the X protocol. lbxproxy acheives the performance gain by grouping |
258 |
|
several X requests in one TCP packet and sending them off together, |
259 |
|
instead of requiring a round-trip for each X request in a seperate |
260 |
|
packet. The switches that seem to work best for emacs are: |
261 |
|
-noatomsfile -nowinattr -cheaterrors -cheatevents |
262 |
|
Note that the -nograbcmap option is known to cause problems. |
263 |
|
For more about lbxproxy, see: |
264 |
|
http://www.xfree86.org/4.2.0/lbxproxy.1.html |
265 |
|
|
266 |
* Getting a Meta key on the FreeBSD console |
* Getting a Meta key on the FreeBSD console |
267 |
|
|
494 |
appropriate keyboard encoding automatically, but it doesn't do that |
appropriate keyboard encoding automatically, but it doesn't do that |
495 |
yet.) |
yet.) |
496 |
|
|
497 |
Multilingual text put into the Windows clipboard by other Windows |
Windows uses UTF-16 encoding to deal with multilingual text (text not |
498 |
applications cannot be safely pasted into Emacs (as of v21.2). This |
encodable in the `system codepage') in the clipboard. To deal with |
499 |
is because Windows uses Unicode to represent multilingual text, but |
this, load the library `utf-16' and use `set-selection-coding-system' |
500 |
Emacs does not yet support Unicode well enough to decode it. This |
to set the clipboard coding system to `utf-16-le-dos'. This won't |
501 |
means that Emacs can only interchange non-ASCII text with other |
cope with Far Eastern (`CJK') text; if necessary, install the Mule-UCS |
502 |
Windows programs if the characters are in the system codepage. |
package (see etc/MORE.STUFF), whose `utf-16-le-dos' coding system does |
503 |
Reportedly, a partial solution is to install the Mule-UCS package and |
encode a lot of CJK characters. |
|
set selection-coding-system to utf-16-le-dos. |
|
504 |
|
|
505 |
The %b specifier for format-time-string does not produce abbreviated |
The %b specifier for format-time-string does not produce abbreviated |
506 |
month names with consistent widths for some locales on some versions |
month names with consistent widths for some locales on some versions |
509 |
|
|
510 |
* The `configure' script doesn't find the jpeg library. |
* The `configure' script doesn't find the jpeg library. |
511 |
|
|
512 |
This can happen because the linker by default only looks for shared |
There are reports that this happens on some systems because the linker |
513 |
libraries, but jpeg distribution by default doesn't build and doesn't |
by default only looks for shared libraries, but jpeg distribution by |
514 |
install a shared version of the library, `libjpeg.so'. One system |
default only installs a nonshared version of the library, `libjpeg.a'. |
515 |
where this is known to happen is Compaq OSF/1 (`Tru64'), but it |
|
516 |
probably isn't limited to that system. |
If this is the problem, you can configure the jpeg library with the |
517 |
|
`--enable-shared' option and then rebuild libjpeg. This produces a |
518 |
You can configure the jpeg library with the `--enable-shared' option |
shared version of libjpeg, which you need to install. Finally, rerun |
519 |
and then rebuild libjpeg. This produces a shared version of libjpeg, |
the Emacs configure script, which should now find the jpeg library. |
520 |
which you need to install. Finally, rerun the Emacs configure script, |
Alternatively, modify the generated src/Makefile to link the .a file |
521 |
which should now find the jpeg library. Alternatively, modify the |
explicitly, and edit src/config.h to define HAVE_JPEG. |
|
generated src/Makefile to link the .a file explicitly. |
|
|
|
|
|
(If you need the static version of the jpeg library as well, configure |
|
|
libjpeg with both `--enable-static' and `--enable-shared' options.) |
|
522 |
|
|
523 |
* Building Emacs over NFS fails with ``Text file busy''. |
* Building Emacs over NFS fails with ``Text file busy''. |
524 |
|
|
596 |
|
|
597 |
* Crashes when displaying GIF images in Emacs built with version |
* Crashes when displaying GIF images in Emacs built with version |
598 |
libungif-4.1.0 are resolved by using version libungif-4.1.0b1. |
libungif-4.1.0 are resolved by using version libungif-4.1.0b1. |
599 |
|
Configure checks for the correct version, but this problem could occur |
600 |
Beginning with version 21.3, Emacs refuses to link against libungif |
if a binary built against a shared libungif is run on a system with an |
601 |
whose version is 4.1.0 or older (the `configure' script behaves as if |
older version. |
|
libungif were not available at all). |
|
602 |
|
|
603 |
* Font Lock displays portions of the buffer in incorrect faces. |
* Font Lock displays portions of the buffer in incorrect faces. |
604 |
|
|
637 |
This happens because KDE's defaults apply its color and font |
This happens because KDE's defaults apply its color and font |
638 |
definitions even to applications that weren't compiled for KDE. The |
definitions even to applications that weren't compiled for KDE. The |
639 |
solution is to uncheck the "Apply fonts and colors to non-KDE apps" |
solution is to uncheck the "Apply fonts and colors to non-KDE apps" |
640 |
option in Preferences->Look&Feel->Style. |
option in Preferences->Look&Feel->Style (KDE 2). In KDE 3, this option |
641 |
|
is in the "Colors" section, rather than "Style". |
642 |
|
|
643 |
Alternatively, if you do want the KDE defaults to apply to other |
Alternatively, if you do want the KDE defaults to apply to other |
644 |
applications, but not to Emacs, you could modify the file `Emacs.ad' |
applications, but not to Emacs, you could modify the file `Emacs.ad' |
700 |
|
|
701 |
(setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "") |
(setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "") |
702 |
|
|
703 |
* Some versions of the W3 package released before Emacs 21.1 don't run |
* Versions of the W3 package released before Emacs 21.1 don't run |
704 |
properly with Emacs 21. These problems are fixed in W3 version |
under Emacs 21. This fixed in W3 version 4.0pre.47. |
|
4.0pre.47. |
|
705 |
|
|
706 |
* On AIX, if linking fails because libXbsd isn't found, check if you |
* On AIX, if linking fails because libXbsd isn't found, check if you |
707 |
are compiling with the system's `cc' and CFLAGS containing `-O5'. If |
are compiling with the system's `cc' and CFLAGS containing `-O5'. If |
736 |
please upgrade to version 2. As a temporary workaround, remove |
please upgrade to version 2. As a temporary workaround, remove |
737 |
argument "-x" from the variable `ldap-ldapsearch-args'. |
argument "-x" from the variable `ldap-ldapsearch-args'. |
738 |
|
|
|
* Unicode characters are not unified with other Mule charsets. |
|
|
|
|
|
As of v21.1, Emacs charsets are still not unified. This means that |
|
|
characters which belong to charsets such as Latin-2, Greek, Hebrew, |
|
|
etc. and the same characters in the `mule-unicode-*' charsets are |
|
|
different characters, as far as Emacs is concerned. For example, text |
|
|
which includes Unicode characters from the Latin-2 locale cannot be |
|
|
encoded by Emacs with ISO 8859-2 coding system; and if you yank Greek |
|
|
text from a buffer whose buffer-file-coding-system is greek-iso-8bit |
|
|
into a mule-unicode-0100-24ff buffer, Emacs won't be able to save that |
|
|
buffer neither as ISO 8859-7 nor as UTF-8. |
|
|
|
|
|
To work around this, install some add-on package such as Mule-UCS. |
|
|
|
|
|
* Problems when using Emacs with UTF-8 locales |
|
|
|
|
|
Some systems, including recent versions of GNU/Linux, have terminals |
|
|
or X11 subsystems that can be configured to provide Unicode/UTF-8 |
|
|
input and display. Normally, such a system sets environment variables |
|
|
such as LANG, LC_CTYPE, or LC_ALL to a string which ends with a |
|
|
`.UTF-8'. For example, a system like this in a French locale might |
|
|
use `fr_FR.UTF-8' as the value of LANG. |
|
|
|
|
|
Since Unicode support in Emacs, as of v21.1, is not yet complete (see |
|
|
the previous entry in this file), UTF-8 support is not enabled by |
|
|
default, even in UTF-8 locales. Thus, some Emacs features, such as |
|
|
non-ASCII keyboard input, might appear to be broken in these locales. |
|
|
To solve these problems, you need to turn on some options in your |
|
|
`.emacs' file. Specifically, the following customizations should make |
|
|
Emacs work correctly with UTF-8 input and text: |
|
|
|
|
|
(setq locale-coding-system 'utf-8) |
|
|
(set-terminal-coding-system 'utf-8) |
|
|
(set-keyboard-coding-system 'utf-8) |
|
|
(set-selection-coding-system 'utf-8) |
|
|
(prefer-coding-system 'utf-8) |
|
|
|
|
739 |
* The `oc-unicode' package doesn't work with Emacs 21. |
* The `oc-unicode' package doesn't work with Emacs 21. |
740 |
|
|
741 |
This package tries to define more private charsets than there are free |
This package tries to define more private charsets than there are free |
882 |
|
|
883 |
An example of such an error is: |
An example of such an error is: |
884 |
|
|
885 |
x-complement-fontset-spec: "Wrong type argument: stringp, nil" |
x-complement-fontset-spec: "Wrong type argument: stringp, nil" |
886 |
|
|
887 |
This can be another symptom of stale *.elc files in your classpath. |
This can be another symptom of stale *.elc files in your classpath. |
888 |
The following command will print any duplicate Lisp files that are |
The following command will print any duplicate Lisp files that are |
907 |
|
|
908 |
and then choose /usr/bin/netkit-ftp. |
and then choose /usr/bin/netkit-ftp. |
909 |
|
|
|
* Emacs built on Windows 9x/ME crashes at startup on Windows XP, |
|
|
or Emacs built on XP crashes at startup on Windows 9x/ME. |
|
|
|
|
|
There appear to be general problems running programs compiled on |
|
|
Windows 9x/ME on Windows XP and vice-versa, at least when compilation |
|
|
is done with MSVC 6.0. This affects other programs as well as Emacs. |
|
|
The compatibility options in the program properties on Windows XP may |
|
|
help in some cases. |
|
|
|
|
910 |
* Antivirus software interacts badly with the MS-Windows version of Emacs. |
* Antivirus software interacts badly with the MS-Windows version of Emacs. |
911 |
|
|
912 |
The usual manifestation of these problems is that subprocesses don't |
The usual manifestation of these problems is that subprocesses don't |
918 |
mode (e.g., disable the ``auto-protect'' feature), or even uninstall |
mode (e.g., disable the ``auto-protect'' feature), or even uninstall |
919 |
or disable it entirely. |
or disable it entirely. |
920 |
|
|
921 |
* On Windows 95/98/ME, subprocesses do not terminate properly. |
* On MS-Windows 95/98/ME, subprocesses do not terminate properly. |
922 |
|
|
923 |
This is a limitation of the Operating System, and can cause problems |
This is a limitation of the Operating System, and can cause problems |
924 |
when shutting down Windows. Ensure that all subprocesses are exited |
when shutting down Windows. Ensure that all subprocesses are exited |
925 |
cleanly before exiting Emacs. For more details, see the FAQ at |
cleanly before exiting Emacs. For more details, see the FAQ at |
926 |
http://www.gnu.org/software/emacs/windows/. |
http://www.gnu.org/software/emacs/windows/. |
927 |
|
|
928 |
* Windows 95/98/ME crashes when Emacs invokes non-existent programs. |
* MS-Windows 95/98/ME crashes when Emacs invokes non-existent programs. |
929 |
|
|
930 |
When a program you are trying to run is not found on the PATH, |
When a program you are trying to run is not found on the PATH, |
931 |
Windows might respond by crashing or locking up your system. In |
Windows might respond by crashing or locking up your system. In |
975 |
|
|
976 |
Changing Alt_L to Meta_L fixes it: |
Changing Alt_L to Meta_L fixes it: |
977 |
% xmodmap -e 'keysym Alt_L = Meta_L Alt_L' |
% xmodmap -e 'keysym Alt_L = Meta_L Alt_L' |
978 |
% xmodmap -e 'keysym Alt_R = Meta_R Alt_R' |
% xmodmap -e 'keysym Alt_R = Meta_R Alt_R' |
979 |
|
|
980 |
* Error "conflicting types for `initstate'" compiling with GCC on Irix 6. |
* Error "conflicting types for `initstate'" compiling with GCC on Irix 6. |
981 |
|
|
1050 |
|
|
1051 |
|
|
1052 |
* Emacs crashes on Irix 6.5 on the SGI R10K, when compiled with GCC. |
* Emacs crashes on Irix 6.5 on the SGI R10K, when compiled with GCC. |
1053 |
|
|
1054 |
This seems to be fixed in GCC 2.95. |
This seems to be fixed in GCC 2.95. |
1055 |
|
|
1056 |
* Emacs crashes in utmpname on Irix 5.3. |
* Emacs crashes in utmpname on Irix 5.3. |
1075 |
You can fix this by editing the file: |
You can fix this by editing the file: |
1076 |
|
|
1077 |
/usr/openwin/lib/locale/iso8859-15/Compose |
/usr/openwin/lib/locale/iso8859-15/Compose |
1078 |
|
|
1079 |
Near the bottom there is a line that reads: |
Near the bottom there is a line that reads: |
1080 |
|
|
1081 |
Ctrl<t> <quotedbl> <Y> : "\276" threequarters |
Ctrl<t> <quotedbl> <Y> : "\276" threequarters |
1111 |
When the display is set to an Exceed X-server and fonts are specified |
When the display is set to an Exceed X-server and fonts are specified |
1112 |
(either explicitly with the -fn option or implicitly with X resources) |
(either explicitly with the -fn option or implicitly with X resources) |
1113 |
then the fonts may appear "too tall". The actual character sizes are |
then the fonts may appear "too tall". The actual character sizes are |
1114 |
correct but there is too much vertical spacing between rows, which |
correct but there is too much vertical spacing between rows, which |
1115 |
gives the appearance of "double spacing". |
gives the appearance of "double spacing". |
1116 |
|
|
1117 |
To prevent this, turn off the Exceed's "automatic font substitution" |
To prevent this, turn off the Exceed's "automatic font substitution" |
1118 |
feature (in the font part of the configuration window). |
feature (in the font part of the configuration window). |
1230 |
|
|
1231 |
The VM mail package, which is not part of Emacs, sometimes does |
The VM mail package, which is not part of Emacs, sometimes does |
1232 |
(standard-display-european t) |
(standard-display-european t) |
1233 |
That should be changed to |
That should be changed to |
1234 |
(standard-display-european 1 t) |
(standard-display-european 1 t) |
1235 |
|
|
1236 |
* Installing Emacs gets an error running `install-info'. |
* Installing Emacs gets an error running `install-info'. |
1331 |
it uses a single dictionary.) Make sure that the text you are |
it uses a single dictionary.) Make sure that the text you are |
1332 |
spelling and the dictionary used by Ispell conform to each other. |
spelling and the dictionary used by Ispell conform to each other. |
1333 |
|
|
1334 |
|
If your spell-checking program is Aspell, it has been reported that if |
1335 |
|
you have a personal configuration file (normally ~/.aspell.conf), it |
1336 |
|
can cause this error. Remove that file, execute `ispell-kill-ispell' |
1337 |
|
in Emacs, and then try spell-checking again. |
1338 |
|
|
1339 |
* On Linux-based GNU systems using libc versions 5.4.19 through |
* On Linux-based GNU systems using libc versions 5.4.19 through |
1340 |
5.4.22, Emacs crashes at startup with a segmentation fault. |
5.4.22, Emacs crashes at startup with a segmentation fault. |
1341 |
|
|
1343 |
One known solution is to upgrade to a newer libc version. 5.4.33 is |
One known solution is to upgrade to a newer libc version. 5.4.33 is |
1344 |
known to work. |
known to work. |
1345 |
|
|
1346 |
* On Windows, you cannot use the right-hand ALT key and the left-hand |
* On MS-Windows, you cannot use the right-hand ALT key and the left-hand |
1347 |
CTRL key together to type a Control-Meta character. |
CTRL key together to type a Control-Meta character. |
1348 |
|
|
1349 |
This is a consequence of a misfeature beyond Emacs's control. |
This is a consequence of a misfeature beyond Emacs's control. |
1360 |
If you are using Exceed 6.1, upgrade to a later version. This was |
If you are using Exceed 6.1, upgrade to a later version. This was |
1361 |
reported to prevent the crashes. |
reported to prevent the crashes. |
1362 |
|
|
1363 |
* Under some Windows X-servers, Emacs' display is incorrect |
* Under some X-servers running on MS-Windows, Emacs' display is incorrect |
1364 |
|
|
1365 |
The symptoms are that Emacs does not completely erase blank areas of the |
The symptoms are that Emacs does not completely erase blank areas of the |
1366 |
screen during scrolling or some other screen operations (e.g., selective |
screen during scrolling or some other screen operations (e.g., selective |
1598 |
106222-01 OpenWindows 3.6: filemgr (ff.core) fixes |
106222-01 OpenWindows 3.6: filemgr (ff.core) fixes |
1599 |
105284-12 Motif 1.2.7: sparc Runtime library patch |
105284-12 Motif 1.2.7: sparc Runtime library patch |
1600 |
|
|
1601 |
* Problems running Perl under Emacs on Windows NT/95. |
* Problems running Perl under Emacs on MS-Windows NT/95. |
1602 |
|
|
1603 |
`perl -de 0' just hangs when executed in an Emacs subshell. |
`perl -de 0' just hangs when executed in an Emacs subshell. |
1604 |
The fault lies with Perl (indirectly with Windows NT/95). |
The fault lies with Perl (indirectly with Windows NT/95). |
1674 |
them into the Emacs executable `temacs'; then they will replace the |
them into the Emacs executable `temacs'; then they will replace the |
1675 |
incorrect library functions. |
incorrect library functions. |
1676 |
|
|
1677 |
* When compiling with DJGPP on Windows NT, "config msdos" fails. |
* When compiling with DJGPP on MS-Windows NT, "config msdos" fails. |
1678 |
|
|
1679 |
If the error message is "VDM has been already loaded", this is because |
If the error message is "VDM has been already loaded", this is because |
1680 |
Windows has a program called `redir.exe' that is incompatible with a |
Windows has a program called `redir.exe' that is incompatible with a |
1682 |
config.bat. To resolve this, move the DJGPP's `bin' subdirectory to |
config.bat. To resolve this, move the DJGPP's `bin' subdirectory to |
1683 |
the front of your PATH environment variable. |
the front of your PATH environment variable. |
1684 |
|
|
1685 |
* When compiling with DJGPP on Windows 95, Make fails for some targets |
* When compiling with DJGPP on MS-Windows 95, Make fails for some targets |
1686 |
like make-docfile. |
like make-docfile. |
1687 |
|
|
1688 |
This can happen if long file name support (the setting of environment |
This can happen if long file name support (the setting of environment |
1732 |
`TERM'; this way, only Emacs gets the empty value, while the rest of |
`TERM'; this way, only Emacs gets the empty value, while the rest of |
1733 |
your system works as before. |
your system works as before. |
1734 |
|
|
1735 |
* On Windows 95, Alt-f6 does not get through to Emacs. |
* On MS-Windows 95, Alt-f6 does not get through to Emacs. |
1736 |
|
|
1737 |
This character seems to be trapped by the kernel in Windows 95. |
This character seems to be trapped by the kernel in Windows 95. |
1738 |
You can enter M-f6 by typing ESC f6. |
You can enter M-f6 by typing ESC f6. |
1739 |
|
|
1740 |
* Typing Alt-Shift has strange effects on Windows. |
* Typing Alt-Shift has strange effects on MS-Windows. |
1741 |
|
|
1742 |
This combination of keys is a command to change keyboard layout. If |
This combination of keys is a command to change keyboard layout. If |
1743 |
you proceed to type another non-modifier key before you let go of Alt |
you proceed to type another non-modifier key before you let go of Alt |
1755 |
|
|
1756 |
The fix is to install a newer version of ncurses, such as version 4.2. |
The fix is to install a newer version of ncurses, such as version 4.2. |
1757 |
|
|
1758 |
* Emacs does not start complaining that it cannot open termcap database file. |
* Emacs does not start, complaining that it cannot open termcap database file. |
|
|
|
|
If your system uses Terminfo rather than termcap (most modern systems |
|
|
do), this could happen if you have an old version of ncurses |
|
|
installed, or if the newer version is not visible to the Emacs |
|
|
configure script (i.e. it cannot be found along the usual path the |
|
|
linker looks for libraries). |
|
1759 |
|
|
1760 |
The solution is to install a newer version of ncurses, and make sure |
If your system uses Terminfo rather than termcap (most modern |
1761 |
the linker can find it. |
systems do), this could happen if the proper version of |
1762 |
|
ncurses is not visible to the Emacs configure script (i.e. it |
1763 |
|
cannot be found along the usual path the linker looks for |
1764 |
|
libraries). It can happen because your version of ncurses is |
1765 |
|
obsolete, or is available only in form of binaries. |
1766 |
|
|
1767 |
|
The solution is to install an up-to-date version of ncurses in |
1768 |
|
the developer's form (header files, static libraries and |
1769 |
|
symbolic links); in some GNU/Linux distributions (e.g. Debian) |
1770 |
|
it constitutes a separate package. |
1771 |
|
|
1772 |
* Strange results from format %d in a few cases, on a Sun. |
* Strange results from format %d in a few cases, on a Sun. |
1773 |
|
|
1808 |
We suspect the crucial patch is one of these, but we don't know |
We suspect the crucial patch is one of these, but we don't know |
1809 |
for certain. |
for certain. |
1810 |
|
|
1811 |
103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes) |
103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes) |
1812 |
102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes) |
102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes) |
1813 |
103242-04: [README] SunOS 5.5: linker patch (595363 bytes) |
103242-04: [README] SunOS 5.5: linker patch (595363 bytes) |
1814 |
|
|
1815 |
(One user reports that the bug was fixed by those patches together |
(One user reports that the bug was fixed by those patches together |
1901 |
Definitions" to make them defined. |
Definitions" to make them defined. |
1902 |
|
|
1903 |
* On SunOS, you get linker errors |
* On SunOS, you get linker errors |
1904 |
ld: Undefined symbol |
ld: Undefined symbol |
1905 |
_get_wmShellWidgetClass |
_get_wmShellWidgetClass |
1906 |
_get_applicationShellWidgetClass |
_get_applicationShellWidgetClass |
1907 |
|
|
1931 |
We do not know whether something in Emacs is partly to blame for this. |
We do not know whether something in Emacs is partly to blame for this. |
1932 |
|
|
1933 |
* Emacs exits with "X protocol error" when run with an X server for |
* Emacs exits with "X protocol error" when run with an X server for |
1934 |
Windows. |
MS-Windows. |
1935 |
|
|
1936 |
A certain X server for Windows had a bug which caused this. |
A certain X server for Windows had a bug which caused this. |
1937 |
Supposedly the newer 32-bit version of this server doesn't have the |
Supposedly the newer 32-bit version of this server doesn't have the |
2061 |
Also make sure that the `/etc/host.conf' files contains the following |
Also make sure that the `/etc/host.conf' files contains the following |
2062 |
lines: |
lines: |
2063 |
|
|
2064 |
order hosts, bind |
order hosts, bind |
2065 |
multi on |
multi on |
2066 |
|
|
2067 |
Any changes, permanent and temporary, to the host name should be |
Any changes, permanent and temporary, to the host name should be |
2290 |
* display-time causes kernel problems on ISC systems. |
* display-time causes kernel problems on ISC systems. |
2291 |
|
|
2292 |
Under Interactive Unix versions 3.0.1 and 4.0 (and probably other |
Under Interactive Unix versions 3.0.1 and 4.0 (and probably other |
2293 |
versions), display-time causes the loss of large numbers of STREVENT |
versions), display-time causes the loss of large numbers of STREVENT |
2294 |
cells. Eventually the kernel's supply of these cells is exhausted. |
cells. Eventually the kernel's supply of these cells is exhausted. |
2295 |
This makes emacs and the whole system run slow, and can make other |
This makes emacs and the whole system run slow, and can make other |
2296 |
processes die, in particular pcnfsd. |
processes die, in particular pcnfsd. |
2297 |
|
|
2298 |
Other emacs functions that communicate with remote processes may have |
Other emacs functions that communicate with remote processes may have |
2299 |
the same problem. Display-time seems to be far the worst. |
the same problem. Display-time seems to be far the worst. |
2300 |
|
|
2301 |
The only known fix: Don't run display-time. |
The only known fix: Don't run display-time. |
2367 |
|
|
2368 |
if ($?EMACS) then |
if ($?EMACS) then |
2369 |
if ($EMACS == "t") then |
if ($EMACS == "t") then |
2370 |
unset edit |
unset edit |
2371 |
stty -icrnl -onlcr -echo susp ^Z |
stty -icrnl -onlcr -echo susp ^Z |
2372 |
endif |
endif |
2373 |
endif |
endif |
2658 |
|
|
2659 |
* On a Sun running SunOS 4.1.1, you get this error message from GNU ld: |
* On a Sun running SunOS 4.1.1, you get this error message from GNU ld: |
2660 |
|
|
2661 |
/lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment |
/lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment |
2662 |
|
|
2663 |
The problem is in the Sun shared C library, not in GNU ld. |
The problem is in the Sun shared C library, not in GNU ld. |
2664 |
|
|
2680 |
christos@theory.tn.cornell.edu says: |
christos@theory.tn.cornell.edu says: |
2681 |
|
|
2682 |
The problem is that in your .cshrc you have something that tries to |
The problem is that in your .cshrc you have something that tries to |
2683 |
execute `tty`. If you are not running the shell on a real tty then |
execute `tty`. If you are not running the shell on a real tty then |
2684 |
tty will print "not a tty". Csh expects one word in some places, |
tty will print "not a tty". Csh expects one word in some places, |
2685 |
but tty is giving it back 3. |
but tty is giving it back 3. |
2686 |
|
|
2687 |
The solution is to add a pair of quotes around `tty` to make it a single |
The solution is to add a pair of quotes around `tty` to make it a single |
2688 |
word: |
word: |
2689 |
|
|
2690 |
if (`tty` == "/dev/console") |
if (`tty` == "/dev/console") |
2691 |
|
|
2692 |
should be changed to: |
should be changed to: |
2693 |
|
|
2694 |
if ("`tty`" == "/dev/console") |
if ("`tty`" == "/dev/console") |
2695 |
|
|
2696 |
Even better, move things that set up terminal sections out of .cshrc |
Even better, move things that set up terminal sections out of .cshrc |
2697 |
and into .login. |
and into .login. |
2711 |
|
|
2712 |
If the error message says that a symbol such as `f68881_used' or |
If the error message says that a symbol such as `f68881_used' or |
2713 |
`ffpa_used' or `start_float' is undefined, this probably indicates |
`ffpa_used' or `start_float' is undefined, this probably indicates |
2714 |
that you have compiled some libraries, such as the X libraries, |
that you have compiled some libraries, such as the X libraries, |
2715 |
with a floating point option other than the default. |
with a floating point option other than the default. |
2716 |
|
|
2717 |
It's not terribly hard to make this work with small changes in |
It's not terribly hard to make this work with small changes in |
2737 |
* M-x shell persistently reports "Process shell exited abnormally with code 1". |
* M-x shell persistently reports "Process shell exited abnormally with code 1". |
2738 |
|
|
2739 |
This happened on Suns as a result of what is said to be a bug in Sunos |
This happened on Suns as a result of what is said to be a bug in Sunos |
2740 |
version 4.0.x. The only fix was to reboot the machine. |
version 4.0.x. The only fix was to reboot the machine. |
2741 |
|
|
2742 |
* Programs running under terminal emulator do not recognize `emacs' |
* Programs running under terminal emulator do not recognize `emacs' |
2743 |
terminal type. |
terminal type. |
2767 |
However, that has the disadvantage of turning off interrupts, so that |
However, that has the disadvantage of turning off interrupts, so that |
2768 |
you are unable to quit out of a Lisp program by typing C-g. |
you are unable to quit out of a Lisp program by typing C-g. |
2769 |
|
|
2770 |
The easy way to do this is to put |
The easy way to do this is to put |
2771 |
|
|
2772 |
(setq x-sigio-bug t) |
(setq x-sigio-bug t) |
2773 |
|
|
3324 |
of machine defines NO_UNION_TYPE. |
of machine defines NO_UNION_TYPE. |
3325 |
|
|
3326 |
|
|
3327 |
|
Copyright 1987,88,89,93,94,95,96,97,98,1999,2001,2002 |
3328 |
|
Free Software Foundation, Inc. |
3329 |
|
|
3330 |
|
Copying and redistribution of this file with or without modification |
3331 |
|
are permitted without royalty provided this notice is preserved. |
3332 |
|
|
3333 |
Local variables: |
Local variables: |
3334 |
mode: outline |
mode: outline |
3335 |
paragraph-separate: "[ ]*$" |
paragraph-separate: "[ ]*$" |