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