|
88
|
1 -*- mode:outline; minor-mode:outl-mouse -*-
|
|
0
|
2 This file describes various problems that have been encountered
|
|
|
3 in compiling, installing and running XEmacs.
|
|
|
4
|
|
124
|
5 This file is large, but we have tried to sort the entries by their
|
|
|
6 respective relevance for XEmacs, but may have not succeeded completely
|
|
|
7 in that task. Try finding the things you need using one of the search
|
|
|
8 commands XEmacs provides (e.g. `C-s').
|
|
|
9
|
|
144
|
10 (updated for 20.2)
|
|
120
|
11
|
|
|
12 * Watch out for .emacs file
|
|
|
13
|
|
|
14 ~/.emacs is your Emacs init file. If you observe strange problems,
|
|
|
15 invoke XEmacs with the `-q' option and see if you can repeat the
|
|
|
16 problem.
|
|
|
17
|
|
124
|
18 * Problems with building XEmacs
|
|
0
|
19
|
|
124
|
20 ** The compiler generates lots and lots of syntax errors.
|
|
0
|
21
|
|
|
22 Are you using an ANSI C compiler, like lcc or gcc? The SunOS 4.1 bundled cc
|
|
|
23 is not ANSI.
|
|
|
24
|
|
|
25 If X has not been configured to compile itself using lcc, gcc, or another ANSI
|
|
|
26 compiler, then you will have to hack the automatically-generated makefile in
|
|
|
27 the `lwlib' directory by hand to make it use an ANSI compiler.
|
|
|
28
|
|
124
|
29 ** test-distrib says that the distribution has been clobbered
|
|
|
30 ** or, temacs prints "Command key out of range 0-127"
|
|
|
31 ** or, temacs runs and dumps xemacs, but xemacs totally fails to work.
|
|
|
32 ** or, temacs gets errors dumping xemacs
|
|
0
|
33
|
|
|
34 This can be because the .elc files have been garbled. Do not be
|
|
|
35 fooled by the fact that most of a .elc file is text: these are
|
|
|
36 binary files and can contain all 256 byte values.
|
|
|
37
|
|
|
38 In particular `shar' cannot be used for transmitting GNU Emacs.
|
|
|
39 It typically truncates "lines". What appear to be "lines" in
|
|
|
40 a binary file can of course be of any length. Even once `shar'
|
|
|
41 itself is made to work correctly, `sh' discards null characters
|
|
|
42 when unpacking the shell archive.
|
|
|
43
|
|
|
44 I have also seen character \177 changed into \377. I do not know
|
|
|
45 what transfer means caused this problem. Various network
|
|
|
46 file transfer programs are suspected of clobbering the high bit.
|
|
|
47
|
|
|
48 If you have a copy of Emacs that has been damaged in its
|
|
|
49 nonprinting characters, you can fix them:
|
|
|
50
|
|
|
51 1) Record the names of all the .elc files.
|
|
|
52 2) Delete all the .elc files.
|
|
|
53 3) Recompile alloc.c with a value of PURESIZE twice as large.
|
|
|
54 You might as well save the old alloc.o.
|
|
|
55 4) Remake xemacs. It should work now.
|
|
|
56 5) Running xemacs, do Meta-x byte-compile-file repeatedly
|
|
|
57 to recreate all the .elc files that used to exist.
|
|
|
58 You may need to increase the value of the variable
|
|
|
59 max-lisp-eval-depth to succeed in running the compiler interpreted
|
|
|
60 on certain .el files. 400 was sufficient as of last report.
|
|
|
61 6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
|
|
|
62 and remake temacs.
|
|
|
63 7) Remake xemacs. It should work now, with valid .elc files.
|
|
|
64
|
|
124
|
65 ** temacs prints "Pure Lisp storage exhausted"
|
|
0
|
66
|
|
|
67 This means that the Lisp code loaded from the .elc and .el
|
|
|
68 files during temacs -l loadup inc dump took up more
|
|
|
69 space than was allocated.
|
|
|
70
|
|
|
71 This could be caused by
|
|
|
72 1) adding code to the preloaded Lisp files
|
|
|
73 2) adding more preloaded files in loadup.el
|
|
|
74 3) having a site-init.el or site-load.el which loads files.
|
|
|
75 Note that ANY site-init.el or site-load.el is nonstandard;
|
|
|
76 if you have received Emacs from some other site
|
|
|
77 and it contains a site-init.el or site-load.el file, consider
|
|
|
78 deleting that file.
|
|
|
79 4) getting the wrong .el or .elc files
|
|
|
80 (not from the directory you expected).
|
|
|
81 5) deleting some .elc files that are supposed to exist.
|
|
|
82 This would cause the source files (.el files) to be
|
|
|
83 loaded instead. They take up more room, so you lose.
|
|
|
84 6) a bug in the Emacs distribution which underestimates
|
|
|
85 the space required.
|
|
|
86
|
|
|
87 If the need for more space is legitimate, use the --puresize option
|
|
|
88 to `configure' to specify more pure space.
|
|
|
89
|
|
|
90 But in some of the cases listed above, this problem is a consequence
|
|
|
91 of something else that is wrong. Be sure to check and fix the real
|
|
|
92 problem.
|
|
|
93
|
|
124
|
94 ** Don't use -O2 with gcc 2.7.2 under Linux without also using
|
|
|
95 `-fno-strength-reduce'.
|
|
|
96
|
|
|
97 gcc will generate incorrect code otherwise. This bug is present in at
|
|
|
98 least 2.6.x and 2.7.[0-2]. This bug has been fixed in GCC 2.7.2.1 and
|
|
|
99 later.
|
|
|
100
|
|
|
101 ** `Error: No ExtNode to pop!' on Linux systems with Lesstif.
|
|
|
102
|
|
|
103 This error message has been observed with lesstif-0.75a. It does not
|
|
|
104 appear to cause any harm.
|
|
|
105
|
|
126
|
106 ** Movemail on Linux doesn't work any more
|
|
|
107
|
|
|
108 Linux now defaults to using .lock mail locking. To get back to the
|
|
|
109 previous flock locking, edit src/s/linux.h and uncomment out the
|
|
|
110 `# define MAIL_USE_FLOCK' line.
|
|
|
111
|
|
124
|
112 ** Sparc Linux -vs- libXmu.
|
|
|
113
|
|
|
114 There have been reports of configure not detecting libXmu on
|
|
|
115 SparcLinux. The fix is to add -lXmu to the link flags.
|
|
|
116
|
|
|
117 ** Debian Linux and Berkeley db include files.
|
|
|
118
|
|
|
119 Debian Linux puts the Berkeley db include files in /usr/include/db
|
|
|
120 instead of /usr/include. The fix is to use
|
|
|
121 --site-includes=/usr/include/db with configure.
|
|
|
122
|
|
|
123 ** alloc.c will not compile without -P on HP-UX 9.05
|
|
|
124
|
|
|
125 Pekka Marjola <pema@iki.fi> writes:
|
|
|
126 Gcc (2.7.2, with cpplib IIRC) required something (-P worked :) to
|
|
|
127 get it to compile. Otherwise it failed on those DEFUN macros with
|
|
|
128 comments inside parameter lists (like buffer.c, line 296).
|
|
|
129
|
|
|
130 ** Excessive optimization with pgcc can break XEmacs
|
|
|
131
|
|
|
132 It has been reported on some systems that compiling with -O6 can lead
|
|
|
133 to XEmacs failures. The workaround is to use a lower optimization
|
|
|
134 level. -O2 and -O4 have been tested extensively.
|
|
|
135
|
|
|
136 ** -O2 optimization on Irix 5.3 can cause compiler complaint.
|
|
|
137
|
|
|
138 Nick J. Crabtree <nickc@scopic.com> writes:
|
|
|
139 Comes up OK on a tty (all I have available over this slow link). Ill
|
|
|
140 give it a hammering tomorrow. The -O2 optimisation complained about
|
|
|
141 sizes exceeding thresholds; I haven't bothered to use the -Olimit
|
|
|
142 option it recommends.
|
|
|
143
|
|
|
144 ** Excessive optimization on AIX 4.2 can lead to compiler failure.
|
|
|
145
|
|
|
146 Valdis.Kletnieks@vt.edu writes:
|
|
|
147 At least at the b34 level, and the latest-and-greatest IBM xlc
|
|
|
148 (3.1.4.4), there are problems with -O3. I haven't investigated
|
|
|
149 further.
|
|
|
150
|
|
|
151 ** Sed problems on Solaris 2.5
|
|
|
152
|
|
|
153 There have been reports of Sun sed truncating very lines in the
|
|
|
154 Makefile during configuration. The workaround is to use GNU sed or,
|
|
|
155 even better, think of a better way to generate Makefile, and send us a
|
|
|
156 patch. :-)
|
|
|
157
|
|
|
158 ** Linking with -rpath on IRIX.
|
|
|
159
|
|
|
160 Darrell Kindred <dkindred@cmu.edu> writes:
|
|
|
161 There are a couple of problems [with use of -rpath with Irix ld], though:
|
|
|
162
|
|
|
163 1. The ld in IRIX 5.3 ignores all but the last -rpath
|
|
|
164 spec, so the patched configure spits out a warning
|
|
|
165 if --x-libraries or --site-runtime-libraries are
|
|
|
166 specified under irix 5.x, and it only adds -rpath
|
|
|
167 entries for the --site-runtime-libraries. This bug was
|
|
|
168 fixed sometime between 5.3 and 6.2.
|
|
|
169
|
|
|
170 2. IRIX gcc 2.7.2 doesn't accept -rpath directly, so
|
|
|
171 it would have to be prefixed by -Xlinker or "-Wl,".
|
|
|
172 This would be fine, except that configure compiles with
|
|
|
173 ${CC-cc} $CFLAGS $LDFLAGS ...
|
|
|
174 rather than quoting $LDFLAGS with prefix-args, like
|
|
|
175 src/Makefile does. So if you specify --x-libraries
|
|
|
176 or --site-runtime-libraries, you must use --use-gcc=no,
|
|
|
177 or configure will fail.
|
|
|
178
|
|
|
179 ** On Irix 5.x and 6.x, the dumped XEmacs (xemacs) core dumps when executed
|
|
|
180 on another machine, or after newer SGI IRIX patches have been installed.
|
|
|
181
|
|
|
182 The xemacs binary must be executed with the same "libc.so" file which
|
|
|
183 was used when the xemacs binary was dumped. Some SGI IRIX patches
|
|
|
184 update this file. Make sure that all machines using the xemacs binary
|
|
|
185 are using the same set of IRIX patches. If xemacs core dumps after a
|
|
|
186 patch upgrade then you will have to redump it from temacs.
|
|
|
187
|
|
|
188 ** xemacs: can't resolve symbol '__malloc_hook'
|
|
|
189
|
|
|
190 This is a Linux problem where you've compiled the XEmacs binary on a libc
|
|
|
191 5.4 with version higher than 5.4.19 and attempted to run the binary against
|
|
|
192 an earlier version. The solution is to upgrade your old library.
|
|
|
193
|
|
|
194 ** Compilation errors on VMS.
|
|
|
195
|
|
|
196 Sorry, XEmacs does not work under VMS. You might consider working on
|
|
|
197 the port if you really want to have XEmacs work under VMS.
|
|
|
198
|
|
|
199 ** On HP/UX configure selects gcc even though it isn't actually present.
|
|
|
200
|
|
|
201 Some versions of SoftBench have an executable called 'gcc' that is not
|
|
|
202 actually the GNU C compiler. Use the --with-gcc=no flag when running
|
|
|
203 configure.
|
|
|
204
|
|
|
205 ** On Solaris 2.* I get undefined symbols from libcurses.a.
|
|
|
206
|
|
|
207 You probably have /usr/ucblib/ on your LD_LIBRARY_PATH. Do the link with
|
|
|
208 LD_LIBRARY_PATH unset.
|
|
|
209
|
|
|
210 ** On Solaris 2.* I cannot make alloc.o, glyphs.o or process.o.
|
|
|
211
|
|
|
212 The SparcWorks C compiler may have difficulty building those modules
|
|
|
213 with optimization level -xO4. Try using only "-fast" optimization
|
|
|
214 for just those modules. (Or use gcc).
|
|
|
215
|
|
|
216 ** On Digital UNIX, the DEC C compiler might have a problem compiling
|
|
|
217 some files.
|
|
|
218
|
|
|
219 In particular, src/extents.c and src/faces.c might cause the DEC C
|
|
|
220 compiler to abort. When this happens: cd src, compile the files by
|
|
|
221 hand, cd .., and redo the "make" command. When recompiling the files by
|
|
|
222 hand, use the old C compiler for the following versions of Digital UNIX:
|
|
|
223 - V3.n: Remove "-migrate" from the compile command.
|
|
|
224 - V4.n: Add "-oldc" to the compile command.
|
|
|
225
|
|
126
|
226 ** On Digital UNIX, TOOLTALK gets misdetected and misconfigured
|
|
|
227
|
|
|
228 This problem manifested itself in the beta cycle as putting a literal
|
|
|
229 LIB_TOOLTALK string into the Makefile.
|
|
|
230
|
|
124
|
231 ** On HPUX, the HP C compiler might have a problem compiling some files
|
|
|
232 with optimization.
|
|
|
233
|
|
|
234 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
|
235
|
|
|
236 Had to drop once again to level 2 optimization, at least to
|
|
|
237 compile lstream.c. Otherwise, I get a "variable is void: \if"
|
|
|
238 problem while dumping (this is a problem I already reported
|
|
|
239 with vanilla hpux 10.01 and 9.07, which went away after
|
|
|
240 applying patches for the C compiler). Trouble is I still
|
|
|
241 haven't found the same patch for hpux 10.10, and I don't
|
|
|
242 remember the patch numbers. I think potential XEmacs builders
|
|
|
243 on HP should be warned about this.
|
|
|
244
|
|
|
245 ** I don't have `xmkmf' and `imake' on my HP.
|
|
|
246
|
|
|
247 You can get these standard X tools by anonymous FTP to hpcvaaz.cv.hp.com.
|
|
|
248 Essentially all X programs need these.
|
|
|
249
|
|
|
250 ** Solaris 2.3 /bin/sh coredumps during configuration.
|
|
|
251
|
|
|
252 This only occurs if you have LANG != C. This is a known bug with
|
|
|
253 /bin/sh fixed by installing Patch-ID# 101613-01.
|
|
|
254
|
|
|
255 ** On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
|
|
|
256
|
|
|
257 A compiler bug inserts spaces into the string "unexelfsgi . o"
|
|
|
258 in src/Makefile. Edit src/Makefile, after configure is run,
|
|
|
259 find that string, and take out the spaces.
|
|
|
260
|
|
|
261 Compiler fixes in Irix 6.0.1 should eliminate this problem.
|
|
|
262
|
|
|
263 ** Native cc on SCO OpenServer 5 is now OK. Icc may still throw you
|
|
|
264 a curve. Here is what Robert Lipe <robertl@arnet.com> says:
|
|
|
265
|
|
|
266 Unlike XEmacs 19.13, building with the native cc on SCO OpenServer 5
|
|
|
267 now produces a functional binary. I will typically build this
|
|
|
268 configuration for COFF with:
|
|
|
269
|
|
|
270 /path_to_XEmacs_source/configure --with-gcc=no \
|
|
|
271 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
|
|
|
272 --with-xpm --with-xface --with-sound=nas
|
|
|
273
|
|
|
274 This version now supports ELF builds. I highly recommend this to
|
|
|
275 reduce the in-core footprint of XEmacs. This is now how I compile
|
|
|
276 all my test releases. Build it like this:
|
|
|
277
|
|
|
278 /path_to_XEmacs_source/configure --with-gcc=no \
|
|
|
279 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
|
|
|
280 --with-xpm --with-xface --with-sound=nas --dynamic
|
|
|
281
|
|
|
282 The compiler known as icc [ supplied with the OpenServer 5 Development
|
|
|
283 System ] generates a working binary, but it takes forever to generate
|
|
|
284 XEmacs. ICC also whines more about the code than /bin/cc does. I do
|
|
|
285 believe all its whining is legitimate, however. Note that you do
|
|
|
286 have to 'cd src ; make LD=icc' to avoid linker errors.
|
|
|
287
|
|
|
288 The way I handle the build procedure is:
|
|
|
289
|
|
|
290 /path_to_XEmacs_source/configure --with-gcc=no \
|
|
|
291 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
|
|
|
292 --with-xpm --with-xface --with-sound=nas --dynamic --compiler="icc"
|
|
|
293
|
|
|
294 NOTE I have the xpm, xface, and audio libraries and includes in
|
|
|
295 /usr/local/lib, /usr/local/include. If you don't have these,
|
|
|
296 don't include the "--with-*" arguments in any of my examples.
|
|
|
297
|
|
|
298 In previous versions of XEmacs, you had to override the defaults while
|
|
|
299 compiling font-lock.o and extents.o when building with icc. This seems
|
|
|
300 to no longer be true, but I'm including this old information in case it
|
|
|
301 resurfaces. The process I used was:
|
|
|
302
|
|
|
303 make -k
|
|
|
304 [ procure pizza, beer, repeat ]
|
|
|
305 cd src
|
|
|
306 make CC="icc -W0,-mP1COPT_max_tree_size=3000" font-lock.o extents.o
|
|
|
307 make LD=icc
|
|
|
308
|
|
|
309 If you want sound support, get the tls566 supplement from
|
|
|
310 ftp.sco.com:/TLS or any of its mirrors. It works just groovy
|
|
|
311 with XEmacs.
|
|
|
312
|
|
|
313 The M-x manual-entry is known not to work. If you know Lisp and would
|
|
|
314 like help in making it work, e-mail me at <robertl@dgii.com>.
|
|
|
315 (UNCHECKED for 19.15 -- it might work).
|
|
|
316
|
|
|
317 In earlier releases, gnuserv/gnuclient/gnudoit would open a frame
|
|
|
318 just fine, but the client would lock up and the server would
|
|
|
319 terminate when you used C-x # to close the frame. This is now
|
|
|
320 fixed in XEmacs.
|
|
|
321
|
|
|
322 In etc/ there are two files of note. emacskeys.sco and emacsstrs.sco.
|
|
|
323 The comments at the top of emacskeys.sco describe its function, and
|
|
|
324 the emacstrs.sco is a suitable candidate for /usr/lib/keyboard/strings
|
|
|
325 to take advantage of the keyboard map in emacskeys.sco.
|
|
|
326
|
|
|
327 ** Under some versions of OSF XEmacs runs fine if built without
|
|
|
328 optimization but will crash randomly if built with optimization.
|
|
|
329
|
|
|
330 Using 'cc -g' is not sufficient to eliminate all optimization. Try
|
|
|
331 'cc -g -O0' instead.
|
|
|
332
|
|
|
333 ** On SunOS, you get linker errors
|
|
|
334 ld: Undefined symbol
|
|
|
335 _get_wmShellWidgetClass
|
|
|
336 _get_applicationShellWidgetClass
|
|
|
337
|
|
|
338 The fix to this is to install patch 100573 for OpenWindows 3.0
|
|
|
339 or link libXmu statically.
|
|
|
340
|
|
|
341 ** On Sunos 4, you get the error ld: Undefined symbol __lib_version.
|
|
|
342
|
|
|
343 This is the result of using cc or gcc with the shared library meant
|
|
|
344 for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete
|
|
|
345 /usr/lang/SC2.0.1 or some similar directory.
|
|
|
346
|
|
|
347 ** On AIX 4.1.2, linker error messages such as
|
|
|
348 ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
|
|
|
349 of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
|
|
|
350
|
|
|
351 This is a problem in libIM.a. You can work around it by executing
|
|
|
352 these shell commands in the src subdirectory of the directory where
|
|
|
353 you build Emacs:
|
|
|
354
|
|
|
355 cp /usr/lib/libIM.a .
|
|
|
356 chmod 664 libIM.a
|
|
|
357 ranlib libIM.a
|
|
|
358
|
|
|
359 Then change -lIM to ./libIM.a in the command to link temacs (in
|
|
|
360 Makefile).
|
|
|
361
|
|
|
362 ** On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
|
|
|
363
|
|
|
364 The file cmplrs/stsupport.h was included in the wrong file set in the
|
|
|
365 Irix 5.2 distribution. You can find it in the optional fileset
|
|
|
366 compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
|
|
|
367 workaround is to change unexelfsgi.c to include sym.h instead of
|
|
|
368 syms.h.
|
|
|
369
|
|
|
370 ** Link failure when using acc on a Sun.
|
|
|
371
|
|
|
372 To use acc, you need additional options just before the libraries, such as
|
|
|
373
|
|
|
374 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
|
|
|
375
|
|
|
376 and you need to add -lansi just before -lc.
|
|
|
377
|
|
|
378 The precise file names depend on the compiler version, so we
|
|
|
379 cannot easily arrange to supply them.
|
|
|
380
|
|
|
381 ** Link failure on IBM AIX 1.3 ptf 0013.
|
|
|
382
|
|
|
383 There is a real duplicate definition of the function `_slibc_free' in
|
|
|
384 the library /lib/libc_s.a (just do nm on it to verify). The
|
|
|
385 workaround/fix is:
|
|
|
386
|
|
|
387 cd /lib
|
|
|
388 ar xv libc_s.a NLtmtime.o
|
|
|
389 ar dv libc_s.a NLtmtime.o
|
|
|
390
|
|
|
391 ** Undefined symbols _dlopen, _dlsym and/or _dlclose on a Sun.
|
|
|
392
|
|
|
393 If you see undefined symbols _dlopen, _dlsym, or _dlclose when linking
|
|
|
394 with -lX11, compile and link against the file mit/util/misc/dlsym.c in
|
|
|
395 the MIT X11R5 distribution. Alternatively, link temacs using shared
|
|
|
396 libraries with s/sunos4shr.h. (This doesn't work if you use the X
|
|
|
397 toolkit.)
|
|
|
398
|
|
|
399 If you get the additional error that the linker could not find
|
|
|
400 lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in
|
|
|
401 X11R4, then use it in the link.
|
|
|
402
|
|
|
403 ** Undefined symbols when linking on Sunos 4.1.
|
|
|
404
|
|
|
405 If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
|
|
|
406 _iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
|
|
|
407 -lXaw in the command that links temacs.
|
|
|
408
|
|
|
409 This problem seems to arise only when the international language
|
|
|
410 extensions to X11R5 are installed.
|
|
|
411
|
|
|
412 ** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
|
|
|
413
|
|
|
414 This can happen if configure uses GNU sed version 2.03. That version
|
|
|
415 had a bug. GNU sed version 2.05 works properly.
|
|
|
416
|
|
|
417 ** On AIX, you get this compiler error message:
|
|
|
418
|
|
|
419 Processing include file ./XMenuInt.h
|
|
|
420 1501-106: (S) Include file X11/Xlib.h not found.
|
|
|
421
|
|
|
422 This means your system was installed with only the X11 runtime i.d
|
|
|
423 libraries. You have to find your sipo (bootable tape) and install
|
|
|
424 X11Dev... with smit.
|
|
|
425
|
|
|
426 ** C-z just refreshes the screen instead of suspending Emacs.
|
|
|
427
|
|
|
428 You are probably using a shell that doesn't support job control, even
|
|
|
429 though the system itself is capable of it. Either use a different shell,
|
|
|
430 or set the variable `cannot-suspend' to a non-nil value.
|
|
|
431
|
|
|
432 ** On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
|
|
|
433
|
|
|
434 /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
|
|
|
435
|
|
|
436 The problem is in the Sun shared C library, not in GNU ld.
|
|
|
437
|
|
|
438 The solution is to install Patch-ID# 100267-03 from Sun.
|
|
|
439
|
|
|
440 ** SunOS 4.1.2: undefined symbol _get_wmShellWidgetClass
|
|
|
441
|
|
|
442 Apparently the version of libXmu.so.a that Sun ships is hosed: it's missing
|
|
|
443 some stuff that is in libXmu.a (the static version). Sun has a patch for
|
|
|
444 this, but a workaround is to use the static version of libXmu, by changing
|
|
|
445 the link command from "-lXmu" to "-Bstatic -lXmu -Bdynamic". If you have
|
|
|
446 OpenWindows 3.0, ask Sun for these patches:
|
|
|
447 100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
|
|
|
448 100573-03 4.1.x OpenWindows 3.0 undefined symbols with shared libXmu
|
|
|
449
|
|
|
450 ** Random other SunOS 4.1.[12] link errors.
|
|
|
451
|
|
|
452 The X headers and libraries that Sun ships in /usr/{include,lib}/X11 are
|
|
|
453 broken. Use the ones in /usr/openwin/{include,lib} instead.
|
|
|
454
|
|
|
455 ** When using gcc, you get the error message "undefined symbol __fixunsdfsi".
|
|
|
456 ** When using gcc, you get the error message "undefined symbol __main".
|
|
|
457
|
|
|
458 This means that you need to link with the gcc library. It may be called
|
|
|
459 "gcc-gnulib" or "libgcc.a"; figure out where it is, and define LIB_GCC in
|
|
|
460 config.h to point to it.
|
|
|
461
|
|
|
462 It may also work to use the GCC version of `ld' instead of the standard one.
|
|
|
463
|
|
|
464 ** When compiling with X11, you get "undefined symbol _XtStrings".
|
|
|
465
|
|
|
466 This means that you are trying to link emacs against the X11r4 version of
|
|
|
467 libXt.a, but you have compiled either Emacs or the code in the lwlib
|
|
|
468 subdirectory with the X11r5 header files. That doesn't work.
|
|
|
469
|
|
|
470 Remember, you can't compile lwlib for r4 and emacs for r5, or vice versa.
|
|
|
471 They must be in sync.
|
|
|
472
|
|
136
|
473 ** Problems finding X11 libraries on Solaris with Openwindows
|
|
|
474
|
|
|
475 Some users have reported problems in this area. The reported solution
|
|
|
476 is to define the environment variable OPENWINHOME, even if you must set
|
|
|
477 it to `/usr/openwin'.
|
|
|
478
|
|
124
|
479 * Problems with running XEmacs
|
|
|
480
|
|
|
481 ** You type Control-H (Backspace) expecting to delete characters.
|
|
|
482
|
|
|
483 Emacs has traditionally used Control-H for help; unfortunately this
|
|
|
484 interferes with its use as Backspace on TTY's. One way to solve this
|
|
|
485 problem is to put this in your .emacs:
|
|
|
486
|
|
|
487 (keyboard-translate ?\C-h ?\C-?)
|
|
|
488 (global-set-key "\M-?" 'help-command)
|
|
|
489
|
|
|
490 This makes Control-H (Backspace) work sensibly, and moves help to
|
|
|
491 Meta-? (ESC ?).
|
|
|
492
|
|
|
493 Note that you can probably also access help using F1.
|
|
|
494
|
|
|
495 ** On Solaris, C-x doesn't get through to Emacs when you use the console.
|
|
|
496
|
|
|
497 This is a Solaris feature (at least on Intel x86 cpus). Type C-r
|
|
|
498 C-r C-t, to toggle whether C-x gets through to Emacs.
|
|
|
499
|
|
|
500 ** VM appears to hang in large folders
|
|
|
501
|
|
|
502 This is normal (trust us) when upgrading to VM-6.22 from earlier
|
|
|
503 versions. Let VM finish what it is doing and all will be well.
|
|
|
504
|
|
|
505 ** Changes made to .el files do not take effect.
|
|
0
|
506
|
|
|
507 You may have forgotten to recompile them into .elc files.
|
|
|
508 Then the old .elc files will be loaded, and your changes
|
|
|
509 will not be seen. To fix this, do M-x byte-recompile-directory
|
|
|
510 and specify the directory that contains the Lisp files.
|
|
|
511
|
|
|
512 Note that you may get a warning when loading a .elc file that
|
|
|
513 is older than the corresponding .el file.
|
|
|
514
|
|
124
|
515 ** Things which should be bold or italic (such as the initial copyright notice)
|
|
|
516 are not.
|
|
0
|
517
|
|
|
518 The fonts of the "bold" and "italic" faces are generated from the font of
|
|
|
519 the "default" face; in this way, your bold and italic fonts will have the
|
|
|
520 appropriate size and family. However, emacs can only be clever in this
|
|
|
521 way if you have specified the default font using the XLFD (X Logical Font
|
|
|
522 Description) format, which looks like
|
|
|
523
|
|
|
524 *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
|
|
|
525
|
|
|
526 if you use any of the other, less strict font name formats, some of which
|
|
|
527 look like
|
|
|
528 lucidasanstypewriter-12
|
|
|
529 and fixed
|
|
|
530 and 9x13
|
|
|
531
|
|
|
532 then emacs won't be able to guess the names of the "bold" and "italic"
|
|
|
533 versions. All X fonts can be referred to via XLFD-style names, so you
|
|
|
534 should use those forms. See the man pages for X(1), xlsfonts(1), and
|
|
|
535 xfontsel(1).
|
|
|
536
|
|
124
|
537 ** The dumped Emacs (XEmacs) crashes when run, trying to write pure data.
|
|
0
|
538
|
|
|
539 Two causes have been seen for such problems.
|
|
|
540
|
|
|
541 1) On a system where getpagesize is not a system call, it is defined
|
|
|
542 as a macro. If the definition (in both unexec.c and malloc.c) is wrong,
|
|
|
543 it can cause problems like this. You might be able to find the correct
|
|
|
544 value in the man page for a.out (5).
|
|
|
545
|
|
|
546 2) Some systems allocate variables declared static among the
|
|
|
547 initialized variables. Emacs makes all initialized variables in most
|
|
|
548 of its files pure after dumping, but the variables declared static and
|
|
|
549 not initialized are not supposed to be pure. On these systems you
|
|
|
550 may need to add "#define static" to the m- or the s- file.
|
|
|
551
|
|
124
|
552 ** Reading and writing files is very very slow.
|
|
0
|
553
|
|
|
554 Try evaluating the form (setq lock-directory nil) and see if that helps.
|
|
|
555 There is a problem with file-locking on some systems (possibly related
|
|
|
556 to NFS) that I don't understand. Please send mail to the address
|
|
|
557 xemacs@xemacs.org if you figure this one out.
|
|
|
558
|
|
124
|
559 ** The Emacs window disappears when you type M-q.
|
|
|
560
|
|
|
561 Some versions of the Open Look window manager interpret M-q as a quit
|
|
|
562 command for whatever window you are typing at. If you want to use
|
|
|
563 Emacs with that window manager, you should try to configure the window
|
|
|
564 manager to use some other command. You can disable the
|
|
|
565 shortcut keys entirely by adding this line to ~/.OWdefaults:
|
|
|
566
|
|
|
567 OpenWindows.WindowMenuAccelerators: False
|
|
|
568
|
|
|
569 ** The `Alt' key doesn't behave as `Meta' when running DECwindows.
|
|
|
570
|
|
|
571 The default DEC keyboard mapping has the Alt keys set up to generate the
|
|
|
572 keysym `Multi_key', which has a meaning to xemacs which is distinct from that
|
|
|
573 of the `Meta_L' and `Meta-R' keysyms. A second problem is that certain keys
|
|
|
574 have the Mod2 modifier attached to them for no adequately explored reason.
|
|
|
575 The correct fix is to pass this file to xmodmap upon starting X:
|
|
|
576
|
|
|
577 clear mod2
|
|
|
578 keysym Multi_key = Alt_L
|
|
|
579 add mod1 = Alt_L
|
|
|
580 add mod1 = Alt_R
|
|
|
581
|
|
|
582 ** The Compose key on a DEC keyboard does not work as Meta key.
|
|
|
583
|
|
|
584 This shell command should fix it:
|
|
|
585
|
|
|
586 xmodmap -e 'keycode 0xb1 = Meta_L'
|
|
|
587
|
|
|
588
|
|
|
589 ** When emacs starts up, I get lots of warnings about unknown keysyms.
|
|
|
590
|
|
|
591 If you are running the prebuilt binaries, the Motif library expects to find
|
|
|
592 certain thing in the XKeysymDB file. This file is normally in /usr/lib/X11/
|
|
|
593 or in /usr/openwin/lib/. If you keep yours in a different place, set the
|
|
|
594 environment variable $XKEYSYMDB to point to it before starting emacs. If
|
|
|
595 you still have the problem after doing that, perhaps your version of X is
|
|
|
596 too old. There is a copy of the MIT X11R5 XKeysymDB file in the emacs `etc'
|
|
|
597 directory. Try using that one.
|
|
|
598
|
|
|
599 ** My X resources used to work, and now some of them are being ignored.
|
|
0
|
600
|
|
124
|
601 Check the resources in .../etc/Emacs.ad (which is the same as the file
|
|
|
602 sample.Xdefaults). Perhaps some of the default resources built in to
|
|
|
603 emacs are now overriding your existing resources. Copy and edit the
|
|
|
604 resources in Emacs.ad as necessary.
|
|
|
605
|
|
|
606 ** I get complaints about the mapping of my HP keyboard at startup, but I
|
|
|
607 haven't changed anything.
|
|
|
608
|
|
|
609 The default HP keymap is set up to have Mod1 assigned to two different keys:
|
|
|
610 Meta_L and Mode_switch (even though there is not actually a Mode_switch key on
|
|
|
611 the keyboard -- it uses an "imaginary" keycode.) There actually is a reason
|
|
|
612 for this, but it's not a good one. The correct fix is to execute this command
|
|
|
613 upon starting X:
|
|
|
614
|
|
|
615 xmodmap -e 'remove mod1 = Mode_switch'
|
|
|
616
|
|
|
617 ** I have focus problems when I use `M-o' to switch to another screen without
|
|
|
618 using the mouse.
|
|
|
619
|
|
|
620 The focus issues with a program like XEmacs, which has multiple homogeneous
|
|
|
621 top-level windows, are very complicated, and as a result, most window managers
|
|
|
622 don't implement them correctly.
|
|
0
|
623
|
|
124
|
624 The R4/R5 version of twm (and all of its descendants) had buggy focus
|
|
|
625 handling; there is a patch in .../xemacs/etc/twm-patch which fixes this.
|
|
|
626 Sufficiently recent versions of tvtwm do not need this patch, but most other
|
|
|
627 versions of twm do. If you need to apply this patch, please try to get it
|
|
|
628 integrated by the maintainer of whichever version of twm you're using.
|
|
|
629
|
|
|
630 In addition, if you're using twm, make sure you have not specified
|
|
|
631 "NoTitleFocus" in your .tvtwmrc file. The very nature of this option makes
|
|
|
632 twm do some illegal focus tricks, even with the patch.
|
|
|
633
|
|
|
634 It is known that olwm and olvwm are buggy, and in different ways. If you're
|
|
|
635 using click-to-type mode, try using point-to-type, or vice versa.
|
|
|
636
|
|
|
637 In older versions of NCDwm, one could not even type at XEmacs windows. This
|
|
|
638 has been fixed in newer versions (2.4.3, and possibly earlier).
|
|
|
639
|
|
|
640 (Many people suggest that XEmacs should warp the mouse when focusing on
|
|
|
641 another screen in point-to-type mode. This is not ICCCM-compliant behavior.
|
|
|
642 Implementing such policy is the responsibility of the window manager itself,
|
|
|
643 it is not legal for a client to do this.)
|
|
|
644
|
|
|
645 ** Mail agents (VM, Gnus, rmail) cannot get new mail
|
|
0
|
646
|
|
|
647 rmail and VM get new mail from /usr/spool/mail/$USER using a program
|
|
120
|
648 called `movemail'. This program interlocks with /bin/mail using the
|
|
|
649 protocol defined by /bin/mail.
|
|
0
|
650
|
|
|
651 There are two different protocols in general use. One of them uses
|
|
|
652 the `flock' system call. The other involves creating a lock file;
|
|
|
653 `movemail' must be able to write in /usr/spool/mail in order to do
|
|
120
|
654 this. You control which one is used by defining, or not defining, the
|
|
|
655 macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes. IF
|
|
|
656 YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR SYSTEM,
|
|
|
657 YOU CAN LOSE MAIL!
|
|
0
|
658
|
|
|
659 If your system uses the lock file protocol, and fascist restrictions
|
|
|
660 prevent ordinary users from writing the lock files in /usr/spool/mail,
|
|
|
661 you may need to make `movemail' setgid to a suitable group such as
|
|
|
662 `mail'. You can use these commands (as root):
|
|
|
663
|
|
|
664 chgrp mail movemail
|
|
|
665 chmod 2755 movemail
|
|
|
666
|
|
|
667 If your system uses the lock file protocol, and fascist restrictions
|
|
|
668 prevent ordinary users from writing the lock files in /usr/spool/mail,
|
|
|
669 you may need to make `movemail' setgid to a suitable group such as
|
|
120
|
670 `mail'. To do this, use the following commands (as root) after doing
|
|
|
671 the make install.
|
|
0
|
672
|
|
|
673 chgrp mail movemail
|
|
|
674 chmod 2755 movemail
|
|
|
675
|
|
|
676 Installation normally copies movemail from the build directory to an
|
|
|
677 installation directory which is usually under /usr/local/lib. The
|
|
|
678 installed copy of movemail is usually in the directory
|
|
|
679 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and
|
|
|
680 mode of the installed copy; changing the group and mode of the build
|
|
|
681 directory copy is ineffective.
|
|
|
682
|
|
124
|
683 ** Emacs spontaneously displays "I-search: " at the bottom of the screen.
|
|
0
|
684
|
|
|
685 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
|
|
|
686 used. C-s/C-q flow control is bad for Emacs editors because it takes
|
|
|
687 away C-s and C-q as user commands. Since editors do not output long
|
|
|
688 streams of text without user commands, there is no need for a
|
|
|
689 user-issuable "stop output" command in an editor; therefore, a
|
|
|
690 properly designed flow control mechanism would transmit all possible
|
|
|
691 input characters without interference. Designing such a mechanism is
|
|
|
692 easy, for a person with at least half a brain.
|
|
|
693
|
|
|
694 There are three possible reasons why flow control could be taking place:
|
|
|
695
|
|
|
696 1) Terminal has not been told to disable flow control
|
|
|
697 2) Insufficient padding for the terminal in use
|
|
|
698 3) Some sort of terminal concentrator or line switch is responsible
|
|
|
699
|
|
|
700 First of all, many terminals have a set-up mode which controls whether
|
|
|
701 they generate XON/XOFF flow control characters. This must be set to
|
|
|
702 "no XON/XOFF" in order for Emacs to work. Sometimes there is an
|
|
|
703 escape sequence that the computer can send to turn flow control off
|
|
|
704 and on. If so, perhaps the termcap `ti' string should turn flow
|
|
|
705 control off, and the `te' string should turn it on.
|
|
|
706
|
|
|
707 Once the terminal has been told "no flow control", you may find it
|
|
|
708 needs more padding. The amount of padding Emacs sends is controlled
|
|
|
709 by the termcap entry for the terminal in use, and by the output baud
|
|
|
710 rate as known by the kernel. The shell command `stty' will print
|
|
|
711 your output baud rate; `stty' with suitable arguments will set it if
|
|
|
712 it is wrong. Setting to a higher speed causes increased padding. If
|
|
|
713 the results are wrong for the correct speed, there is probably a
|
|
|
714 problem in the termcap entry. You must speak to a local Unix wizard
|
|
|
715 to fix this. Perhaps you are just using the wrong terminal type.
|
|
|
716
|
|
|
717 For terminals that lack a "no flow control" mode, sometimes just
|
|
|
718 giving lots of padding will prevent actual generation of flow control
|
|
|
719 codes. You might as well try it.
|
|
|
720
|
|
|
721 If you are really unlucky, your terminal is connected to the computer
|
|
|
722 through a concentrator which sends XON/XOFF flow control to the
|
|
|
723 computer, or it insists on sending flow control itself no matter how
|
|
|
724 much padding you give it. Unless you can figure out how to turn flow
|
|
|
725 control off on this concentrator (again, refer to your local wizard),
|
|
|
726 you are screwed! You should have the terminal or concentrator
|
|
|
727 replaced with a properly designed one. In the mean time, some drastic
|
|
|
728 measures can make Emacs semi-work.
|
|
|
729
|
|
|
730 You can make Emacs ignore C-s and C-q and let the operating system
|
|
|
731 handle them. To do this on a per-session basis, just type M-x
|
|
|
732 enable-flow-control RET. You will see a message that C-\ and C-^ are
|
|
|
733 now translated to C-s and C-q. (Use the same command M-x
|
|
|
734 enable-flow-control to turn *off* this special mode. It toggles flow
|
|
|
735 control handling.)
|
|
|
736
|
|
|
737 If C-\ and C-^ are inconvenient for you (for example, if one of them
|
|
|
738 is the escape character of your terminal concentrator), you can choose
|
|
|
739 other characters by setting the variables flow-control-c-s-replacement
|
|
|
740 and flow-control-c-q-replacement. But choose carefully, since all
|
|
|
741 other control characters are already used by emacs.
|
|
|
742
|
|
|
743 IMPORTANT: if you type C-s by accident while flow control is enabled,
|
|
|
744 Emacs output will freeze, and you will have to remember to type C-q in
|
|
|
745 order to continue.
|
|
|
746
|
|
|
747 If you work in an environment where a majority of terminals of a
|
|
|
748 certain type are flow control hobbled, you can use the function
|
|
|
749 `enable-flow-control-on' to turn on this flow control avoidance scheme
|
|
|
750 automatically. Here is an example:
|
|
|
751
|
|
|
752 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
|
|
753
|
|
|
754 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
|
|
|
755 and good vt200 terminals), you can still run enable-flow-control
|
|
|
756 manually.
|
|
|
757
|
|
|
758 I have no intention of ever redesigning the Emacs command set for the
|
|
|
759 assumption that terminals use C-s/C-q flow control. XON/XOFF flow
|
|
|
760 control technique is a bad design, and terminals that need it are bad
|
|
|
761 merchandise and should not be purchased. Now that X is becoming
|
|
|
762 widespread, XON/XOFF seems to be on the way out. If you can get some
|
|
|
763 use out of GNU Emacs on inferior terminals, more power to you, but I
|
|
|
764 will not make Emacs worse for properly designed systems for the sake
|
|
|
765 of inferior systems.
|
|
|
766
|
|
124
|
767 ** Control-S and Control-Q commands are ignored completely.
|
|
0
|
768
|
|
|
769 For some reason, your system is using brain-damaged C-s/C-q flow
|
|
|
770 control despite Emacs's attempts to turn it off. Perhaps your
|
|
|
771 terminal is connected to the computer through a concentrator
|
|
|
772 that wants to use flow control.
|
|
|
773
|
|
|
774 You should first try to tell the concentrator not to use flow control.
|
|
|
775 If you succeed in this, try making the terminal work without
|
|
|
776 flow control, as described in the preceding section.
|
|
|
777
|
|
|
778 If that line of approach is not successful, map some other characters
|
|
|
779 into C-s and C-q using keyboard-translate-table. The example above
|
|
|
780 shows how to do this with C-^ and C-\.
|
|
|
781
|
|
124
|
782 ** Control-S and Control-Q commands are ignored completely on a net
|
|
|
783 connection.
|
|
0
|
784
|
|
|
785 Some versions of rlogin (and possibly telnet) do not pass flow
|
|
|
786 control characters to the remote system to which they connect.
|
|
|
787 On such systems, emacs on the remote system cannot disable flow
|
|
|
788 control on the local system.
|
|
|
789
|
|
|
790 One way to cure this is to disable flow control on the local host
|
|
|
791 (the one running rlogin, not the one running rlogind) using the
|
|
|
792 stty command, before starting the rlogin process. On many systems,
|
|
120
|
793 `stty start u stop u' will do this.
|
|
0
|
794
|
|
|
795 Some versions of tcsh will prevent even this from working. One way
|
|
|
796 around this is to start another shell before starting rlogin, and
|
|
|
797 issue the stty command to disable flow control from that shell.
|
|
|
798
|
|
|
799 If none of these methods work, the best solution is to type
|
|
120
|
800 `M-x enable-flow-control' at the beginning of your emacs session, or
|
|
0
|
801 if you expect the problem to continue, add a line such as the
|
|
|
802 following to your .emacs (on the host running rlogind):
|
|
|
803
|
|
|
804 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
|
|
805
|
|
|
806 See the entry about spontaneous display of I-search (above) for more
|
|
|
807 info.
|
|
|
808
|
|
124
|
809 ** Screen is updated wrong, but only on one kind of terminal.
|
|
0
|
810
|
|
120
|
811 This could mean that the termcap entry you are using for that terminal
|
|
|
812 is wrong, or it could mean that Emacs has a bug handing the
|
|
|
813 combination of features specified for that terminal.
|
|
0
|
814
|
|
|
815 The first step in tracking this down is to record what characters
|
|
|
816 Emacs is sending to the terminal. Execute the Lisp expression
|
|
120
|
817 (open-termscript "./emacs-script") to make Emacs write all terminal
|
|
|
818 output into the file ~/emacs-script as well; then do what makes the
|
|
|
819 screen update wrong, and look at the file and decode the characters
|
|
|
820 using the manual for the terminal. There are several possibilities:
|
|
0
|
821
|
|
|
822 1) The characters sent are correct, according to the terminal manual.
|
|
|
823
|
|
|
824 In this case, there is no obvious bug in Emacs, and most likely you
|
|
|
825 need more padding, or possibly the terminal manual is wrong.
|
|
|
826
|
|
120
|
827 2) The characters sent are incorrect, due to an obscure aspect of the
|
|
|
828 terminal behavior not described in an obvious way by termcap.
|
|
0
|
829
|
|
120
|
830 This case is hard. It will be necessary to think of a way for Emacs
|
|
|
831 to distinguish between terminals with this kind of behavior and other
|
|
|
832 terminals that behave subtly differently but are classified the same
|
|
|
833 by termcap; or else find an algorithm for Emacs to use that avoids the
|
|
|
834 difference. Such changes must be tested on many kinds of terminals.
|
|
0
|
835
|
|
|
836 3) The termcap entry is wrong.
|
|
|
837
|
|
120
|
838 See the file etc/TERMS for information on changes that are known to be
|
|
|
839 needed in commonly used termcap entries for certain terminals.
|
|
0
|
840
|
|
120
|
841 4) The characters sent are incorrect, and clearly cannot be right for
|
|
|
842 any terminal with the termcap entry you were using.
|
|
0
|
843
|
|
120
|
844 This is unambiguously an Emacs bug, and can probably be fixed in
|
|
|
845 termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.
|
|
0
|
846
|
|
124
|
847 ** Output from Control-V is slow.
|
|
0
|
848
|
|
|
849 On many bit-map terminals, scrolling operations are fairly slow.
|
|
|
850 Often the termcap entry for the type of terminal in use fails
|
|
|
851 to inform Emacs of this. The two lines at the bottom of the screen
|
|
|
852 before a Control-V command are supposed to appear at the top after
|
|
|
853 the Control-V command. If Emacs thinks scrolling the lines is fast,
|
|
|
854 it will scroll them to the top of the screen.
|
|
|
855
|
|
|
856 If scrolling is slow but Emacs thinks it is fast, the usual reason is
|
|
|
857 that the termcap entry for the terminal you are using does not
|
|
|
858 specify any padding time for the `al' and `dl' strings. Emacs
|
|
|
859 concludes that these operations take only as much time as it takes to
|
|
|
860 send the commands at whatever line speed you are using. You must
|
|
|
861 fix the termcap entry to specify, for the `al' and `dl', as much
|
|
|
862 time as the operations really take.
|
|
|
863
|
|
|
864 Currently Emacs thinks in terms of serial lines which send characters
|
|
|
865 at a fixed rate, so that any operation which takes time for the
|
|
|
866 terminal to execute must also be padded. With bit-map terminals
|
|
|
867 operated across networks, often the network provides some sort of
|
|
|
868 flow control so that padding is never needed no matter how slow
|
|
|
869 an operation is. You must still specify a padding time if you want
|
|
|
870 Emacs to realize that the operation takes a long time. This will
|
|
|
871 cause padding characters to be sent unnecessarily, but they do
|
|
|
872 not really cost much. They will be transmitted while the scrolling
|
|
|
873 is happening and then discarded quickly by the terminal.
|
|
|
874
|
|
|
875 Most bit-map terminals provide commands for inserting or deleting
|
|
|
876 multiple lines at once. Define the `AL' and `DL' strings in the
|
|
|
877 termcap entry to say how to do these things, and you will have
|
|
|
878 fast output without wasted padding characters. These strings should
|
|
|
879 each contain a single %-spec saying how to send the number of lines
|
|
|
880 to be scrolled. These %-specs are like those in the termcap
|
|
|
881 `cm' string.
|
|
|
882
|
|
|
883 You should also define the `IC' and `DC' strings if your terminal
|
|
|
884 has a command to insert or delete multiple characters. These
|
|
|
885 take the number of positions to insert or delete as an argument.
|
|
|
886
|
|
|
887 A `cs' string to set the scrolling region will reduce the amount
|
|
|
888 of motion you see on the screen when part of the screen is scrolled.
|
|
|
889
|
|
124
|
890 ** Your Delete key sends a Backspace to the terminal, using an AIXterm.
|
|
0
|
891
|
|
|
892 The solution is to include in your .Xdefaults the lines:
|
|
|
893
|
|
|
894 *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
|
|
|
895 aixterm*ttyModes: erase ^?
|
|
|
896
|
|
|
897 This makes your Backspace key send DEL (ASCII 127).
|
|
|
898
|
|
124
|
899 ** With certain fonts, when the cursor appears on a character, the
|
|
|
900 character doesn't appear--you get a solid box instead.
|
|
|
901
|
|
|
902 One user on a Linux system reported that this problem went away with
|
|
|
903 installation of a new X server. The failing server was XFree86 3.1.1.
|
|
|
904 XFree86 3.1.2 works.
|
|
|
905
|
|
|
906 ** On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
|
|
0
|
907
|
|
124
|
908 This happens if you configure Emacs specifying just `sparc-sun-sunos4'
|
|
|
909 on a system that is version 4.1.3. You must specify the precise
|
|
|
910 version number (or let configure figure out the configuration, which
|
|
|
911 it can do perfectly well for SunOS).
|
|
|
912
|
|
|
913 ** On Irix, I don't see the toolbar icons and I'm getting lots of
|
|
|
914 entries in the warnings buffer.
|
|
0
|
915
|
|
124
|
916 SGI ships a really old Xpm library in /usr/lib which does not work at
|
|
|
917 all well with XEmacs. The solution is to install your own copy of the
|
|
|
918 latest version of Xpm somewhere and then use the --site-includes and
|
|
|
919 --site-libraries flags to tell configure where to find it.
|
|
|
920
|
|
|
921 ** On HPUX, you get "poll: Interrupted system call" message in the window
|
|
|
922 where XEmacs was launched.
|
|
|
923
|
|
|
924 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
0
|
925
|
|
124
|
926 I get a very strange problem when linking libc.a
|
|
|
927 dynamically: every event (mouse, keyboard, expose...) results
|
|
|
928 in a "poll: Interrupted system call" message in the window
|
|
|
929 where XEmacs was launched. Forcing a static link of libc.a
|
|
|
930 alone by adding /usr/lib/libc.a at the end of the link line
|
|
|
931 solves this. Note that my 9.07 build of 19.14b17 and my (old)
|
|
|
932 build of 19.13 both exhibit the same behaviour. I've tried
|
|
|
933 various hpux patches to no avail. If this problem cannot be
|
|
|
934 solved before the release date, binary kits for HP *must* be
|
|
|
935 linked statically against libc, otherwise this problem will
|
|
|
936 show up. (This is directed at whoever will volunteer for this
|
|
|
937 kit, as I won't be available to do it, unless 19.14 gets
|
|
|
938 delayed until mid-june ;-). I think this problem will be an FAQ
|
|
|
939 soon after the release otherwise.
|
|
0
|
940
|
|
124
|
941 ** When Emacs tries to ring the bell, you get an error like
|
|
|
942
|
|
|
943 audio: sst_open: SETQSIZE" Invalid argument
|
|
|
944 audio: sst_close: SETREG MMR2, Invalid argument
|
|
|
945
|
|
|
946 you have probably compiled using an ANSI C compiler, but with non-ANSI include
|
|
|
947 files. In particular, on Suns, the file /usr/include/sun/audioio.h uses the
|
|
|
948 _IOW macro to define the constant AUDIOSETQSIZE. _IOW in turn uses a K&R
|
|
|
949 preprocessor feature that is now explicitly forbidden in ANSI preprocessors,
|
|
|
950 namely substitution inside character constants. All ANSI C compilers must
|
|
|
951 provide a workaround for this problem. Lucid's C compiler is shipped with a
|
|
|
952 new set of system include files. If you are using GCC, there is a script
|
|
|
953 called fixincludes that creates new versions of some system include files that
|
|
|
954 use this obsolete feature.
|
|
|
955
|
|
|
956 ** My buffers are full of \000 characters or otherwise corrupt.
|
|
0
|
957
|
|
124
|
958 Some compilers have trouble with gmalloc.c and ralloc.c; try recompiling
|
|
|
959 without optimization. If that doesn't work, try recompiling with
|
|
|
960 SYSTEM_MALLOC defined, and/or with REL_ALLOC undefined.
|
|
|
961
|
|
|
962 ** On AIX 4, some programs fail when run in a Shell buffer
|
|
|
963 with an error message like No terminfo entry for "unknown".
|
|
|
964
|
|
|
965 On AIX, many terminal type definitions are not installed by default.
|
|
|
966 `unknown' is one of them. Install the "Special Generic Terminal
|
|
|
967 Definitions" to make them defined.
|
|
|
968
|
|
|
969 ** Emacs exits with "X protocol error" when run with an X server for
|
|
|
970 Windows.
|
|
0
|
971
|
|
124
|
972 A certain X server for Windows had a bug which caused this.
|
|
|
973 Supposedly the newer 32-bit version of this server doesn't have the
|
|
|
974 problem.
|
|
|
975
|
|
|
976 ** A position you specified in .Xdefaults is ignored, using twm.
|
|
|
977
|
|
|
978 twm normally ignores "program-specified" positions.
|
|
|
979 You can tell it to obey them with this command in your `.twmrc' file:
|
|
0
|
980
|
|
124
|
981 UsePPosition "on" #allow clents to request a position
|
|
|
982
|
|
|
983 ** The right Alt key works wrong on German HP keyboards (and perhaps
|
|
|
984 other non-English HP keyboards too).
|
|
|
985
|
|
|
986 This is because HPUX defines the modifiers wrong in X. Here is a
|
|
|
987 shell script to fix the problem; be sure that it is run after VUE
|
|
|
988 configures the X server.
|
|
0
|
989
|
|
124
|
990 xmodmap 2> /dev/null - << EOF
|
|
|
991 keysym Alt_L = Meta_L
|
|
|
992 keysym Alt_R = Meta_R
|
|
|
993 EOF
|
|
|
994
|
|
|
995 xmodmap - << EOF
|
|
|
996 clear mod1
|
|
|
997 keysym Mode_switch = NoSymbol
|
|
|
998 add mod1 = Meta_L
|
|
|
999 keysym Meta_R = Mode_switch
|
|
|
1000 add mod2 = Mode_switch
|
|
|
1001 EOF
|
|
|
1002
|
|
|
1003 ** Emacs does not notice when you release the mouse.
|
|
0
|
1004
|
|
124
|
1005 There are reports that this happened with (some) Microsoft mice and
|
|
|
1006 that replacing the mouse made it stop.
|
|
|
1007
|
|
|
1008 ** Trouble using ptys on IRIX, or running out of ptys.
|
|
|
1009
|
|
|
1010 The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
|
|
|
1011 be set-UID to root, or non-root programs like Emacs will not be able
|
|
|
1012 to allocate ptys reliably.
|
|
|
1013
|
|
126
|
1014 ** Motif dialog boxes lose big time on Irix.
|
|
|
1015
|
|
|
1016 Larry Auton <lda@control.att.com> writes:
|
|
|
1017 Beware of not specifying
|
|
|
1018
|
|
|
1019 --with-dialogs=athena
|
|
|
1020
|
|
|
1021 if it builds with the motif dialogs [boom!] you're a dead man.
|
|
|
1022
|
|
|
1023 ** Beware of the default image & graphics library on Irix
|
|
|
1024
|
|
|
1025 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
|
1026 You *have* to compile your own jpeg lib. The one delivered with SGI
|
|
|
1027 systems is a C++ lib, which apparently XEmacs cannot cope with.
|
|
|
1028
|
|
138
|
1029 ** XEmacs won't build with the n32 environment on Irix 6.
|
|
|
1030
|
|
|
1031 Olivier Galibert <Olivier.Galibert@mines.u-nancy.fr> writes:
|
|
|
1032 While making the OS and the compiler able to work on 64b
|
|
|
1033 architectures, SGI designed another mode for using registers
|
|
|
1034 and passing parameters between functions, activated on the
|
|
|
1035 compiler by using -64. Since it was much more efficient ar
|
|
|
1036 using registers even for 32b architectures, they designed
|
|
|
1037 a version for 32b called n32. And it _is_ really better.
|
|
|
1038 This mode should always be used when not using gcc (which
|
|
|
1039 can only do o32 afaik).
|
|
|
1040
|
|
|
1041 Too bad xemacs can't do n32 out of the box. So here is what
|
|
|
1042 I had to do to compile it in this mode:
|
|
|
1043
|
|
|
1044 s/irix6-0.h:
|
|
|
1045 - #define LD_SWITCH_SYSTEM -32
|
|
|
1046 + #define LD_SWITCH_SYSTEM -n32 -G 0
|
|
|
1047
|
|
|
1048 m/iris4d.h:
|
|
|
1049 - #define LIBS_MACHINE -lmld
|
|
|
1050 + #define LIBS_MACHINE
|
|
|
1051
|
|
|
1052 - #define C_SWITCH_MACHINE -32
|
|
|
1053 + #define C_SWITCH_MACHINE -n32 -G 0
|
|
|
1054
|
|
|
1055 (the mld lib does not exist in n32 mode)
|
|
|
1056
|
|
|
1057 I also added a --cflags='-n32 -O2 -G 0 -s' to the configuration
|
|
|
1058 line but it seems that these flags are ignored for configure test
|
|
|
1059 and since o32 and n32 libraries are independant I had to revert
|
|
|
1060 to the CFLAGS env var.
|
|
|
1061
|
|
|
1062 Anyway, once done that the compile has gone succesfully, the dump
|
|
|
1063 was OK and I'm writing this in the resulting xemacs-20.2b1 ;-)
|
|
|
1064
|
|
124
|
1065 ** Slow startup on Linux.
|
|
|
1066
|
|
|
1067 People using systems based on the Linux kernel sometimes report that
|
|
|
1068 startup takes 10 to 15 seconds longer than `usual'.
|
|
|
1069
|
|
|
1070 This is because Emacs looks up the host name when it starts.
|
|
|
1071 Normally, this takes negligible time; the extra delay is due to
|
|
|
1072 improper system configuration. This problem can occur for both
|
|
|
1073 networked and non-networked machines.
|
|
0
|
1074
|
|
124
|
1075 Here is how to fix the configuration. It requires being root.
|
|
|
1076
|
|
|
1077 *** Networked Case
|
|
|
1078
|
|
|
1079 First, make sure the files `/etc/hosts' and `/etc/host.conf' both
|
|
|
1080 exist. The first line in the `/etc/hosts' file should look like this
|
|
|
1081 (replace HOSTNAME with your host name):
|
|
|
1082
|
|
|
1083 127.0.0.1 localhost HOSTNAME
|
|
|
1084
|
|
|
1085 Also make sure that the `/etc/host.conf' files contains the following
|
|
|
1086 lines:
|
|
|
1087
|
|
|
1088 order hosts, bind
|
|
|
1089 multi on
|
|
|
1090
|
|
|
1091 Any changes, permanent and temporary, to the host name should be
|
|
|
1092 indicated in the `/etc/hosts' file, since it acts a limited local
|
|
|
1093 database of addresses and names (e.g., some SLIP connections
|
|
|
1094 dynamically allocate ip addresses).
|
|
|
1095
|
|
|
1096 *** Non-Networked Case
|
|
|
1097
|
|
|
1098 The solution described in the networked case applies here as well.
|
|
|
1099 However, if you never intend to network your machine, you can use a
|
|
|
1100 simpler solution: create an empty `/etc/host.conf' file. The command
|
|
|
1101 `touch /etc/host.conf' suffices to create the file. The `/etc/hosts'
|
|
|
1102 file is not necessary with this approach.
|
|
|
1103
|
|
|
1104 ** On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs
|
|
|
1105 forever waiting for termination of a subprocess that is a zombie.
|
|
|
1106
|
|
|
1107 casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so
|
|
|
1108 after changing the file xc/config/cf/sunLib.tmpl. Change the lines
|
|
|
1109
|
|
|
1110 #if ThreadedX
|
|
|
1111 #define SharedX11Reqs -lthread
|
|
|
1112 #endif
|
|
|
1113
|
|
|
1114 to:
|
|
|
1115
|
|
|
1116 #if OSMinorVersion < 4
|
|
|
1117 #if ThreadedX
|
|
|
1118 #define SharedX11Reqs -lthread
|
|
|
1119 #endif
|
|
|
1120 #endif
|
|
|
1121
|
|
|
1122 Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
|
|
|
1123 (as it should be for Solaris 2.4). The file has three definitions for
|
|
|
1124 OSMinorVersion: the first is for x86, the second for SPARC under
|
|
|
1125 Solaris, and the third for SunOS 4. Make sure to update the
|
|
|
1126 definition for your type of machine and system.
|
|
|
1127
|
|
|
1128 Then do `make Everything' in the top directory of X11R6, to rebuild
|
|
|
1129 the makefiles and rebuild X. The X built this way work only on
|
|
|
1130 Solaris 2.4, not on 2.3.
|
|
|
1131
|
|
|
1132 For multithreaded X to work it necessary to install patch
|
|
|
1133 101925-02 to fix problems in header files [2.4]. You need
|
|
|
1134 to reinstall gcc or re-run just-fixinc after installing that
|
|
|
1135 patch.
|
|
0
|
1136
|
|
124
|
1137 However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
|
|
|
1138 he changed
|
|
|
1139 #define ThreadedX YES
|
|
|
1140 to
|
|
|
1141 #define ThreadedX NO
|
|
|
1142 in sun.cf and did `make World' to rebuild X11R6. Removing all
|
|
|
1143 `-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
|
|
|
1144 typing 'make install' in that directory also seemed to work.
|
|
|
1145
|
|
|
1146 ** With M-x enable-flow-control, you need to type C-\ twice to do
|
|
|
1147 incremental search--a single C-\ gets no response.
|
|
0
|
1148
|
|
124
|
1149 This has been traced to communicating with your machine via kermit,
|
|
|
1150 with C-\ as the kermit escape character. One solution is to use
|
|
|
1151 another escape character in kermit. One user did
|
|
|
1152
|
|
|
1153 set escape-character 17
|
|
|
1154
|
|
|
1155 in his .kermrc file, to make C-q the kermit escape character.
|
|
0
|
1156
|
|
124
|
1157 ** The Motif version of Emacs paints the screen a solid color.
|
|
|
1158
|
|
|
1159 This has been observed to result from the following X resource:
|
|
|
1160
|
|
|
1161 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
|
|
|
1162
|
|
|
1163 That the resource has this effect indicates a bug in something, but we
|
|
|
1164 do not yet know what. If it is an Emacs bug, we hope someone can
|
|
|
1165 explain what the bug is so we can fix it. In the mean time, removing
|
|
|
1166 the resource prevents the problem.
|
|
0
|
1167
|
|
124
|
1168 ** Regular expressions matching bugs on SCO systems.
|
|
|
1169
|
|
|
1170 On SCO, there are problems in regexp matching when Emacs is compiled
|
|
|
1171 with the system compiler. The compiler version is "Microsoft C
|
|
|
1172 version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
|
|
|
1173 C Compiler Version 1.00.46 (Beta). The solution is to compile with
|
|
|
1174 GCC.
|
|
|
1175
|
|
|
1176 ** In Shell mode, you get a ^M at the end of every line.
|
|
|
1177
|
|
|
1178 This happens to people who use tcsh, because it is trying to be too
|
|
|
1179 smart. It sees that the Shell uses terminal type `unknown' and turns
|
|
|
1180 on the flag to output ^M at the end of each line. You can fix the
|
|
|
1181 problem by adding this to your .cshrc file:
|
|
|
1182
|
|
|
1183 if ($?EMACS) then
|
|
|
1184 if ($EMACS == "t") then
|
|
|
1185 unset edit
|
|
|
1186 stty -icrnl -onlcr -echo susp ^Z
|
|
|
1187 endif
|
|
|
1188 endif
|
|
|
1189
|
|
|
1190 ** An error message such as `X protocol error: BadMatch (invalid
|
|
|
1191 parameter attributes) on protocol request 93'.
|
|
|
1192
|
|
|
1193 This comes from having an invalid X resource, such as
|
|
|
1194 emacs*Cursor: black
|
|
|
1195 (which is invalid because it specifies a color name for something
|
|
|
1196 that isn't a color.)
|
|
|
1197
|
|
|
1198 The fix is to correct your X resources.
|
|
|
1199
|
|
|
1200 ** Mail is lost when sent to local aliases.
|
|
0
|
1201
|
|
124
|
1202 Many emacs mail user agents (VM and rmail, for instance) use the
|
|
|
1203 sendmail.el library. This library can arrange for mail to be
|
|
|
1204 delivered by passing messages to the /usr/lib/sendmail (usually)
|
|
|
1205 program . In doing so, it passes the '-t' flag to sendmail, which
|
|
|
1206 means that the name of the recipient of the message is not on the
|
|
|
1207 command line and, therefore, that sendmail must parse the message to
|
|
|
1208 obtain the destination address.
|
|
|
1209
|
|
|
1210 There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
|
|
|
1211 In short, when given the -t flag, the SunOS sendmail won't recognize
|
|
|
1212 non-local (i.e. NIS) aliases. It has been reported that the Solaris
|
|
|
1213 2.x versions of sendmail do not have this bug. For those using SunOS
|
|
|
1214 4.1, the best fix is to install sendmail V8 or IDA sendmail (which
|
|
|
1215 have other advantages over the regular sendmail as well). At the time
|
|
|
1216 of this writing, these official versions are available:
|
|
|
1217
|
|
|
1218 Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
|
|
|
1219 sendmail.8.6.9.base.tar.Z (the base system source & documentation)
|
|
|
1220 sendmail.8.6.9.cf.tar.Z (configuration files)
|
|
|
1221 sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
|
|
|
1222 sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
|
|
|
1223
|
|
|
1224 IDA sendmail on vixen.cso.uiuc.edu in /pub:
|
|
|
1225 sendmail-5.67b+IDA-1.5.tar.gz
|
|
|
1226
|
|
|
1227 ** On AIX, you get this message when running Emacs:
|
|
0
|
1228
|
|
124
|
1229 Could not load program emacs
|
|
|
1230 Symbol smtcheckinit in csh is undefined
|
|
|
1231 Error was: Exec format error
|
|
|
1232
|
|
|
1233 or this one:
|
|
|
1234
|
|
|
1235 Could not load program .emacs
|
|
|
1236 Symbol _system_con in csh is undefined
|
|
|
1237 Symbol _fp_trapsta in csh is undefined
|
|
|
1238 Error was: Exec format error
|
|
|
1239
|
|
|
1240 These can happen when you try to run on AIX 3.2.5 a program that was
|
|
|
1241 compiled with 3.2.4. The fix is to recompile.
|
|
|
1242
|
|
|
1243 ** After running emacs once, subsequent invocations crash.
|
|
|
1244
|
|
|
1245 Some versions of SVR4 have a serious bug in the implementation of the
|
|
|
1246 mmap () system call in the kernel; this causes emacs to run correctly
|
|
|
1247 the first time, and then crash when run a second time.
|
|
|
1248
|
|
|
1249 Contact your vendor and ask for the mmap bug fix; in the mean time,
|
|
|
1250 you may be able to work around the problem by adding a line to your
|
|
|
1251 operating system description file (whose name is reported by the
|
|
|
1252 configure script) that reads:
|
|
|
1253 #define SYSTEM_MALLOC
|
|
|
1254 This makes Emacs use memory less efficiently, but seems to work around
|
|
|
1255 the kernel bug.
|
|
|
1256
|
|
|
1257 ** Inability to send an Alt-modified key, when Emacs is communicating
|
|
|
1258 directly with an X server.
|
|
0
|
1259
|
|
124
|
1260 If you have tried to bind an Alt-modified key as a command, and it
|
|
|
1261 does not work to type the command, the first thing you should check is
|
|
|
1262 whether the key is getting through to Emacs. To do this, type C-h c
|
|
|
1263 followed by the Alt-modified key. C-h c should say what kind of event
|
|
|
1264 it read. If it says it read an Alt-modified key, then make sure you
|
|
|
1265 have made the key binding correctly.
|
|
|
1266
|
|
|
1267 If C-h c reports an event that doesn't have the Alt modifier, it may
|
|
|
1268 be because your X server has no key for the Alt modifier. The X
|
|
|
1269 server that comes from MIT does not set up the Alt modifier by
|
|
|
1270 default.
|
|
|
1271
|
|
|
1272 If your keyboard has keys named Alt, you can enable them as follows:
|
|
0
|
1273
|
|
124
|
1274 xmodmap -e 'add mod2 = Alt_L'
|
|
|
1275 xmodmap -e 'add mod2 = Alt_R'
|
|
|
1276
|
|
|
1277 If the keyboard has just one key named Alt, then only one of those
|
|
|
1278 commands is needed. The modifier `mod2' is a reasonable choice if you
|
|
|
1279 are using an unmodified MIT version of X. Otherwise, choose any
|
|
|
1280 modifier bit not otherwise used.
|
|
0
|
1281
|
|
124
|
1282 If your keyboard does not have keys named Alt, you can use some other
|
|
|
1283 keys. Use the keysym command in xmodmap to turn a function key (or
|
|
|
1284 some other 'spare' key) into Alt_L or into Alt_R, and then use the
|
|
|
1285 commands show above to make them modifier keys.
|
|
|
1286
|
|
|
1287 Note that if you have Alt keys but no Meta keys, Emacs translates Alt
|
|
|
1288 into Meta. This is because of the great importance of Meta in Emacs.
|
|
|
1289
|
|
|
1290 ** `Pid xxx killed due to text modification or page I/O error'
|
|
0
|
1291
|
|
124
|
1292 On HP/UX, you can get that error when the Emacs executable is on an NFS
|
|
|
1293 file system. HP/UX responds this way if it tries to swap in a page and
|
|
|
1294 does not get a response from the server within a timeout whose default
|
|
|
1295 value is just ten seconds.
|
|
|
1296
|
|
|
1297 If this happens to you, extend the timeout period.
|
|
|
1298
|
|
|
1299 ** `expand-file-name' fails to work on any but the machine you dumped Emacs on.
|
|
|
1300
|
|
|
1301 On Ultrix, if you use any of the functions which look up information
|
|
|
1302 in the passwd database before dumping Emacs (say, by using
|
|
|
1303 expand-file-name in site-init.el), then those functions will not work
|
|
|
1304 in the dumped Emacs on any host but the one Emacs was dumped on.
|
|
|
1305
|
|
|
1306 The solution? Don't use expand-file-name in site-init.el, or in
|
|
|
1307 anything it loads. Yuck - some solution.
|
|
0
|
1308
|
|
124
|
1309 I'm not sure why this happens; if you can find out exactly what is
|
|
|
1310 going on, and perhaps find a fix or a workaround, please let us know.
|
|
|
1311 Perhaps the YP functions cache some information, the cache is included
|
|
|
1312 in the dumped Emacs, and is then inaccurate on any other host.
|
|
|
1313
|
|
|
1314 ** Emacs fails to understand most Internet host names, even though
|
|
|
1315 the names work properly with other programs on the same system.
|
|
|
1316 ** Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
|
|
|
1317 ** Gnus can't make contact with the specified host for nntp.
|
|
0
|
1318
|
|
124
|
1319 This typically happens on Suns and other systems that use shared
|
|
|
1320 libraries. The cause is that the site has installed a version of the
|
|
|
1321 shared library which uses a name server--but has not installed a
|
|
|
1322 similar version of the unshared library which Emacs uses.
|
|
0
|
1323
|
|
124
|
1324 The result is that most programs, using the shared library, work with
|
|
|
1325 the nameserver, but Emacs does not.
|
|
|
1326
|
|
|
1327 The fix is to install an unshared library that corresponds to what you
|
|
|
1328 installed in the shared library, and then relink Emacs.
|
|
0
|
1329
|
|
124
|
1330 On SunOS 4.1, simply define HAVE_RES_INIT.
|
|
|
1331
|
|
|
1332 If you have already installed the name resolver in the file libresolv.a,
|
|
|
1333 then you need to compile Emacs to use that library. The easiest way to
|
|
|
1334 do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
|
|
|
1335 or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro
|
|
|
1336 that is already in use in your configuration to supply some other libraries,
|
|
|
1337 be careful not to lose the others.
|
|
|
1338
|
|
|
1339 Thus, you could start by adding this to config.h:
|
|
|
1340
|
|
|
1341 #define LIBS_SYSTEM -lresolv
|
|
|
1342
|
|
|
1343 Then if this gives you an error for redefining a macro, and you see that
|
|
|
1344 the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
|
|
|
1345 again to say this:
|
|
|
1346
|
|
|
1347 #define LIBS_SYSTEM -lresolv -lfoo -lbar
|
|
|
1348
|
|
|
1349 ** Bus errors on startup when compiled with Sun's "acc" (in the routine
|
|
|
1350 make_string_internal() called from initialize_environment_alist())
|
|
|
1351
|
|
|
1352 The Sun ANSI compiler doesn't place uninitialized static variables in BSS
|
|
|
1353 space like other compilers do. This breaks emacs. If you want to use acc,
|
|
|
1354 you need to make the file "lastfile.o" be the *first* file in the link
|
|
|
1355 command. Better yet, use Lucid C or GCC.
|
|
|
1356
|
|
|
1357 ** Trouble using ptys on AIX.
|
|
0
|
1358
|
|
124
|
1359 People often install the pty devices on AIX incorrectly.
|
|
|
1360 Use `smit pty' to reinstall them properly.
|
|
|
1361
|
|
|
1362 ** Shell mode on HP/UX gives the message, "`tty`: Ambiguous".
|
|
|
1363
|
|
|
1364 christos@theory.tn.cornell.edu says:
|
|
|
1365
|
|
|
1366 The problem is that in your .cshrc you have something that tries to
|
|
|
1367 execute `tty`. If you are not running the shell on a real tty then
|
|
|
1368 tty will print "not a tty". Csh expects one word in some places,
|
|
|
1369 but tty is giving it back 3.
|
|
|
1370
|
|
|
1371 The solution is to add a pair of quotes around `tty` to make it a single
|
|
|
1372 word:
|
|
0
|
1373
|
|
124
|
1374 if (`tty` == "/dev/console")
|
|
|
1375
|
|
|
1376 should be changed to:
|
|
|
1377
|
|
|
1378 if ("`tty`" == "/dev/console")
|
|
|
1379
|
|
|
1380 Even better, move things that set up terminal sections out of .cshrc
|
|
|
1381 and into .login.
|
|
0
|
1382
|
|
124
|
1383 ** With process-connection-type set to t, each line of subprocess output is
|
|
|
1384 terminated with a ^M, making ange-ftp and GNUS not work.
|
|
0
|
1385
|
|
124
|
1386 On SunOS systems, this problem has been seen to be a result of an incomplete
|
|
|
1387 installation of gcc 2.2 which allowed some non-ANSI compatible include files
|
|
|
1388 into the compilation. In particular this affected virtually all ioctl() calls.
|
|
|
1389
|
|
|
1390 ** Once you pull down a menu from the menubar, it won't go away.
|
|
0
|
1391
|
|
124
|
1392 It has been claimed that this is caused by a bug in certain very old (1990?)
|
|
|
1393 versions of the twm window manager. It doesn't happen with recent vintages,
|
|
|
1394 or with other window managers.
|
|
|
1395
|
|
|
1396 ** Emacs ignores the "help" key when running OLWM.
|
|
88
|
1397
|
|
124
|
1398 OLWM grabs the help key, and retransmits it to the appropriate client using
|
|
|
1399 XSendEvent. Allowing emacs to react to synthetic events is a security hole,
|
|
|
1400 so this is turned off by default. You can enable it by setting the variable
|
|
|
1401 x-allow-sendevents to t. You can also cause fix this by telling OLWM to not
|
|
|
1402 grab the help key, with the null binding "OpenWindows.KeyboardCommand.Help:".
|
|
|
1403
|
|
|
1404 ** Programs running under terminal emulator do not recognize `emacs'
|
|
|
1405 terminal type.
|
|
88
|
1406
|
|
124
|
1407 The cause of this is a shell startup file that sets the TERMCAP
|
|
|
1408 environment variable. The terminal emulator uses that variable to
|
|
|
1409 provide the information on the special terminal type that Emacs
|
|
|
1410 emulates.
|
|
88
|
1411
|
|
124
|
1412 Rewrite your shell startup file so that it does not change TERMCAP
|
|
|
1413 in such a case. You could use the following conditional which sets
|
|
|
1414 it only if it is undefined.
|
|
|
1415
|
|
|
1416 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
|
|
|
1417
|
|
|
1418 Or you could set TERMCAP only when you set TERM--which should not
|
|
|
1419 happen in a non-login shell.
|
|
|
1420
|
|
|
1421 * Compatibility problems (with Emacs 18, GNU Emacs, or previous XEmacs/lemacs)
|
|
88
|
1422
|
|
124
|
1423 ** "Symbol's value as variable is void: unread-command-char".
|
|
|
1424 ** "Wrong type argument: arrayp, #<keymap 143 entries>"
|
|
|
1425 ** "Wrong type argument: stringp, [#<keypress-event return>]"
|
|
88
|
1426
|
|
124
|
1427 There are a few incompatible changes in XEmacs, and these are the
|
|
|
1428 symptoms. Some of the emacs-lisp code you are running needs to be
|
|
|
1429 updated to be compatible with XEmacs.
|
|
|
1430
|
|
|
1431 The code should not treat keymaps as arrays (use `define-key', etc.),
|
|
|
1432 should not use obsolete variables like `unread-command-char' (use
|
|
|
1433 `unread-command-event'). Many (most) of the new ways of doing things
|
|
|
1434 are compatible in GNU Emacs and XEmacs.
|
|
88
|
1435
|
|
124
|
1436 Modern Emacs packages (Gnus, VM, etc) are written to support GNU Emacs
|
|
|
1437 and XEmacs. We have provided modified versions of several popular
|
|
|
1438 emacs packages (dired, etc) which are compatible with this version of
|
|
|
1439 emacs. Check to make sure you have not set your load-path so that
|
|
|
1440 your private copies of these packages are being found before the
|
|
|
1441 versions in the lisp directory.
|
|
|
1442
|
|
|
1443 Make sure that your load-path and your $EMACSLOADPATH environment
|
|
|
1444 variable are not pointing at an Emacs18 lisp directory. This will
|
|
|
1445 cripple emacs.
|
|
88
|
1446
|
|
124
|
1447 ** Some packages that worked before now cause the error
|
|
|
1448 Wrong type argument: arrayp, #<face ... >
|
|
|
1449
|
|
|
1450 Code which uses the `face' accessor functions must be recompiled with xemacs
|
|
|
1451 19.9 or later. The functions whose callers must be recompiled are: face-font,
|
|
|
1452 face-foreground, face-background, face-background-pixmap, and face-underline-p.
|
|
|
1453 The .elc files generated by version 19.9 will work in 19.6 and 19.8, but older
|
|
|
1454 .elc files which contain calls to these functions will not work in 19.9.
|
|
|
1455
|
|
|
1456 ** Signaling: (error "Byte code stack underflow (byte compiler bug), pc 38")
|
|
88
|
1457
|
|
120
|
1458 This error is given when XEmacs 20 is compiled without MULE support
|
|
88
|
1459 but is attempting to load a .elc which requires MULE support. The fix
|
|
|
1460 is to rebytecompile the offending file.
|
|
|
1461
|
|
124
|
1462 ** Signaling: (wrong-type-argument ...) when loading mail-abbrevs
|
|
88
|
1463
|
|
|
1464 The is seen when installing the Big Brother Data Base (bbdb) which
|
|
|
1465 includes an outdated copy of mail-abbrevs.el. Remove the copy that
|
|
|
1466 comes with bbdb and use the one that comes with XEmacs.
|
|
144
|
1467
|
|
|
1468 * MULE issues
|
|
|
1469
|
|
|
1470 ** Internationalized (Asian) Isearch doesn't work
|
|
|
1471
|
|
|
1472 Currently, Isearch doesn't directly support any of the input methods
|
|
|
1473 that are not XIM based (like egg, canna and quail) (and there are
|
|
|
1474 potential problems with XIM version too...). This is something
|
|
|
1475 we are working on, but for the moment, if you're using egg there is a
|
|
|
1476 workaround. Hitting <RET> right after C-s to invoke Isearch will put
|
|
|
1477 Isearch in string mode, where a complete string can be typed into the
|
|
|
1478 minibuffer and then processed by Isearch afterwards. Since egg is now
|
|
|
1479 supported in the minibuffer using string mode you can now use egg to
|
|
|
1480 input your Japanese, Korean or Chinese string, then hit return to send
|
|
|
1481 that to Isearch and then use standard Isearch commands from there.
|
|
|
1482
|
|
|
1483 ** Using egg or canna and mousing around while in 'fence' mode screws
|
|
|
1484 up my buffer
|
|
|
1485
|
|
|
1486 Don't do this. The fence modes of egg and canna are currently very
|
|
|
1487 modal, and messing with where they expect point to be and what they
|
|
|
1488 think is the current buffer is just asking for trouble. If you're
|
|
|
1489 lucky they will realize that something is awry, and simply delete the
|
|
|
1490 fence, but worst case can trash other buffers too. We've tried to
|
|
|
1491 protect against this where we can, but there still are many ways to
|
|
|
1492 shoot yourself in the foot. So just finish what you are typing into
|
|
|
1493 the fence before reaching for the mouse.
|
