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