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