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