3 At the time of this release (SXEmacs 22.1.14), SXEmacs has the
4 following idiosyncrasies:
9 ** User init file (C-h v user-init-file)
11 SXEmacs searches for its init file in `~/.sxemacs/init.el'.
12 Symlinking your old ~/.xemacs directory should be enough to get you up
15 $ ln -s ~/.xemacs ~/.sxemacs RET
17 BTW, unlike XEmacs, SXEmacs doesn't attempt to "migrate" your old init
18 file or Gnu/Emacs .emacs file.
22 The default location that SXEmacs searches for packages is
23 `$prefix/share/sxemacs/'. The same as for the user-init-file, a
24 symlink is all you need to get up and running.
26 $ ln -s /usr/local/lib/xemacs /usr/local/share/sxemacs RET
34 *** FFI is not included with your distro
36 Sadly, some Linux distributions (hello Fedora) don't ship a libffi
37 package, and their GCC does NOT include libffi or FFI headers either.
38 In this instance you have 2 options...
40 1) Get the standalone package of libffi at
41 <http://sourceware.org/libffi/>.
43 2) Compile your own GCC from source, making sure you enable the java
44 compiler. Enabling java in your GCC build is the only way to get
47 Obviously, option #1 there is the easiest and quickest path to
48 FFI-enabled SXEmacsen, and it is the option that we recommend.
50 Oh, and please nag your distro to have FFI included by default.
52 *** FFI is included in your GCC but you see missing header errors
54 Often libffi headers aren't completely installed. If you are getting
55 errors in effi.c that seem to be hinged from something like...
57 /usr/include/ffi.h:63:23: ffitarget.h: No such file or directory
59 You need to find `ffitarget.h' and put it in the same directory as
60 your `ffi.h'. Your libffi came with GCC, so you'll find it within
63 $ dirname $(gcc -print-libgcc-file-name)
64 /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.1
66 Using that example, ffitarget.h would be in...
68 /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.1/libffi/
70 Just copy or symlink the ffitarget.h there to /usr/include
72 *** FFI on SELinux enabled machines
74 If you are running with SELinux enabled and configure fails with
75 messages like the following in `config.log'...
77 error while loading shared libraries: /usr/local/lib/libffi.so.1:
78 cannot restore segment prot after reloc: Permission denied
80 You need to correct the default security context for `libffi.so'.
82 $ chcon -t textrel_shlib_t /usr/local/lib/libffi.so
86 The autoconf tests for PostgreSQL support have changed. SXEmacs'
87 configure script now uses `pg_config' to determine whether or not to
88 enable PostgreSQL. Because of this you may have to set you $PATH
89 environment to include the pgsql bin directory. It is normally
90 `/usr/local/pgsql/bin/'. Another popular directory on Solaris 9 is
91 `/opt/crw/postgresql/bin/'. Check with your site administrator.
93 Bash users can do it like this...
95 export PATH=/usr/local/pgsql/bin:$PATH
97 *** Solaris 9 with 64-bit PostgreSQL
99 There has also been a report that on Solaris 9 you may also need to
100 configure with `--with-cflags='-mcpu=ultrasparc -m64''. Apparently
101 GCC on Solaris 9 defaults to building 32-bit, so you lose if you have
104 ** 64-bit test suite failure
106 We have had a couple of reports of the test suite failing on 64-bit
107 systems. The error is like this (or similar)...
109 Testing /usr/src/sxemacs/modules/ase/ase-heap-tests.el...
110 Loading ase_heap v0.0.0 (SXEmacs module: ase-heap)
111 Loaded module ase_heap v0.0.0 (SXEmacs module: ase-heap)Fatal error: assertion failed, file alloc.c, line 298, block != (void*)0xCAFEBABEDEADBEEF
112 make[3]: *** [check-am] Aborted
114 At this point we are not too sure exactly what the issue is. It looks
115 like it might be a bug in the malloc or free code of the libc. We do
116 know that not all 64-bit systems are affected, so far, only Fedora
117 Core 7, and Gentoo on x86_64.
119 One user has reported that using `-O1' in CFLAGS prevents it.
121 But even with this test failure, SXEmacs still runs and opperates
122 without incident. In fact, the failure can't be reproduced when
123 running the test suite interactively. With that in mind, it should be
124 safe to install if you see this failure.
126 We'll endeavour to get to the bottom of this one ASAP, if you think
127 you can help, let us know.
129 ** m4, libtool, autoconf, automake, and whatnot
131 SXEmacs tries to cope with any combination of versions of the above
132 programs. However, there is one lower bound, autoconf 2.60, and
133 unfortunately this has an impact on the other parts of the build
136 To cut it really short, here is the minimum known-to-work combination:
137 - autoconf 2.62, automake 1.9.6, libtool 1.5.22, m4 1.4.6
139 In general we support (as of April, 2010):
140 - autoconf >= 2.62, including current git versions
141 - automake 1.9.6, 1.10, 1.10a, 1.11.1, and current git versions
142 - libtool 1.5.N with N >= 22, libtool >= 2.1a (current CVS version)
143 - m4 1.4.M with M >= 6 plus current git versions
145 Note that many libtool packages shipped with the distros (OpenSuSE,
146 Debian, just to name two) are _broken_. Make sure you compile
147 your own libtool in case you want to rerun autogen.sh or bootstrap
148 the build chain, and double check that you use --enable-ltdl-install
151 If you are on a platform that has its own _non_gnu libtool (like OS/X
152 Leopard) add --program-prefix=g to your gnu libtool configure so it
153 installs as glibtool and doesn't clobber your other one.
155 Sometimes it helps just to copy over the libtool script manually:
156 cp -a $(type -p libtool) ${top_builddir}
158 *** ylwrap fails with sed errors
160 Some versions of the ylwrap script provided by autotools uses commas
161 as separators in sed commands. As such if your build path uses commas
162 the ylwrap will fail.
164 Sample message (where the build path was /Users/njsf/Projects/SXEmacs/nsx-up/,,mac):
166 /Users/njsf/Projects/SXEmacs/nsx-up/,,mac/lib-src/make-docfile --modname cl-loop -E cl-loop.doc.c ../../../modules/cl/cl-loop.c
167 /bin/sh ../../../ylwrap ../../../modules/cl/cl-loop-parser.y y.tab.c cl-loop-parser.c y.tab.h cl-loop-parser.h y.output
168 cl-loop-parser.output -- bison -y -d
169 sed: 1: "s,/Users/njsf/Projects/ ...": bad flag in substitute command: 'm'
170 sed: 1: "s,/Users/njsf/Projects/ ...": bad flag in substitute command: 'm'
172 The workaround is to use a path without commas in it.
175 *** Missing libltdl.la (Solaris 2.8)
177 We've had a report that missing libtool on Solaris 2.8 isn't detected
178 and so the included libtool still isn't used. If you see an error
179 about a missing libltdl.la all you need to do is configure SXEmacs
186 *** configure on FreeBSD, NetBSD, OpenBSD, etc.
188 Building SXEmacs on *BSD as far as we know requires the GNU Bourne
189 Again SHell (bash) versions 3 or 4.
191 bash is available for all tier 1 architectures as a binary package and
192 and for tier 2/3 as a port.
194 To run configure successfully...
196 CONFIG_SHELL=/path/to/bash $CONFIG_SHELL configure [option, ...]
198 ** bdwgc and gcc and code optimisation
200 There are some weird optimisation issues with the Boehm-Demers-Weiser
201 garbage collector (hereafter BDWGC) and the GCC C compilers of the 2 and
202 3 series. The build will crash like this:
204 Loading build-autoloads.el...
205 Loading loadup-el.el...
206 Loading loadup.el...make[3]: *** [auto-autoloads.el] Segmentation fault
208 make[3]: Leaving directory
210 The C backtrace will look like:
212 #0 0xbff9a2f0 in ?? ()
213 #1 0xb7eaf7d6 in GC_invoke_finalizers () at finalize.c:787
214 #2 0xb7eaf8ed in GC_notify_or_invoke_finalizers () at finalize.c:844
215 #3 0xb7eb2c8c in GC_generic_malloc (lb=32, k=0) at malloc.c:190
217 If this is true for you, you may want to try another optimisation level:
219 ./configure CFLAGS="-g -O2"
221 If this still does not work out either dispense with BDWGC support or
222 use a recent C compiler. ATTOW, all GCC 4.x compilers (including SVN)
227 ENT is basically a conglomerate of internally and externally implemented
228 arithmetics. Hence it supports a number of libraries, some of which
229 overlap in their functionality, some others do not but then break at the
232 One of the most likely problems is the GMP vs. MPFR issue. In past
233 times, mpfr (a multiprecision library for floats with exact rounding
234 facilities) has been a part of the GMP distribution. Later on, mpfr got
235 separated from it and has been developed independently while the version
236 of mpfr which ships with GMP stayed the same. Now that scenario is
239 Inattentive distributions (like Fedora) still deliver packages of GMP
240 with the old'n'incompatible mpfr library. SXEmacs will disable the MPFR
241 support on such systems by default (at configure time). However, if you
242 install a supported version of mpfr in parallel to the packaged ones on
243 such a system SXEmacs autodetection correctly reports that a sane
244 version of mpfr is available and enables it. Nonetheless, the according
245 build may fail (or the build may even succeed but calling the binary may
248 number-mpfr.o: In function `ent_lt_BIGFR_T':
249 /home/martin/src/edit/sxemacs-main/src/number-mpfr.c:661: undefined
250 reference to `mpfr_less_p'
251 number-mpfr.o: In function `ent_gt_BIGFR_T':
252 /home/martin/src/edit/sxemacs-main/src/number-mpfr.c:671: undefined
253 reference to `mpfr_greater_p'
256 Especially note that we _only_ support the standalone version of MPFR,
257 and not the one distributed with GMP.
262 Badger your distributor and demand separate packages for GMP and
265 Remove the GMP package and install your own build -- available at
266 http://swox.com/gmp -- afterwards install your own build of mpfr (the
267 one from http://www.mpfr.org)
269 Reconfigure and rebuild SXEmacs afterwards.
272 ** Build fails because of missing makeinfo
274 Install the GNU texinfo package on your system. You'll need at least
278 ** MacOS X warns of a crash during configure
280 This is normal, as one of the tests made during configure (for the
281 realpath call correctness) induces as crash.
283 If you are developing SXEmacs and will do lots of runs of configure
284 and that dialog annoys you, consider issuing:
286 # Disable crash reporting
287 sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
288 # Redo last configure
289 ./config.status --recheck
290 # Enable crash reporting
291 sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
293 Another alternative (not recommended) is to launch
295 /Developer/Applications/Utilities/CrashReporterPrefs
297 and configure the mode to server, but you will loose notifications of
298 crashes on all applications.
300 In order to give SXEmacs developers with good diagnosis information it
301 is recommended the mode be Developer.
305 SXEmacs does build and run on OpenIndiana (151a) but you will need to
306 install a few files/packages beforehand. Namely...
308 Common Name OpenIndiana Package Name
312 automake automake-110
314 libtool libtool (also install libltdl)
321 Yes, you read that right... to get pkg-config you must install the
322 "gettext" package. :-)
324 In that list, `bison', `gmp', and `mpfr' are not critical, but you
325 will get extra functionality in your SXEmacs if you have them.
327 *** automake additional instructions for OpenIndiana
329 When you install the automake-110 OpenIndiana package it won't set up
330 the symlinks to /usr/bin/automake or /usr/bin/aclocal. Fix that
333 sudo ln -sv automake-1.10 /usr/bin/automake
334 sudo ln -sv aclocal-1.10 /usr/bin/aclocal
336 *** Running SXEmacs configure on OpenIndiana
338 There's one more quirk with OpenIndiana when you try to run SXEmacs'
339 configure... you MUST set $CONFIG_SHELL
341 CONFIG_SHELL=/bin/bash ../configure [opts]
346 We have identified 2 packages so far that don't work "out of the box"
347 with SXEmacs. In both of these the problem is with parsing version
348 information. Patches have been sent to the appropriate maintainer to
349 fix the problem and are included here in case the packages haven't
350 been updated by the time you install SXEmacs.
352 Update: The EFS, and Dired XEmacs packages that are currently
353 available from the "Pre-Releases" area of XEmacs package mirrors are
354 both now compatible with SXEmacs and do not need the patches mentioned
359 Here is the patch to make EFS work with SXEmacs:
361 (Note: the current EFS package that XEmacs distributes has this
365 ===================================================================
366 RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/efs/ChangeLog,v
367 retrieving revision 1.41
368 diff -u -U0 -r1.41 ChangeLog
369 --- ChangeLog 4 Oct 2004 08:54:56 -0000 1.41
370 +++ ChangeLog 14 Jan 2005 02:43:10 -0000
372 +2005-01-14 Steve Youngs <steve@sxemacs.org>
374 + * efs-fnh.el (efs-handle-emacs-version): Use `emacs-*-version'
375 + variables for version info instead of string-matching through
379 ===================================================================
380 RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/efs/efs-fnh.el,v
381 retrieving revision 1.13
382 diff -u -u -r1.13 efs-fnh.el
383 --- efs-fnh.el 2 Oct 2004 14:06:00 -0000 1.13
384 +++ efs-fnh.el 14 Jan 2005 02:42:59 -0000
386 (let ((ehev-match-data (match-data)))
388 (let ((xemacsp (string-match "XEmacs" emacs-version))
390 - (or (string-match "^\\([0-9]+\\)\\.\\([0-9]+\\)" emacs-version)
391 - (error "efs does not work with emacs version %s" emacs-version))
392 - (setq ver (string-to-int (substring emacs-version
393 - (match-beginning 1)
395 - subver (string-to-int (substring emacs-version
396 - (match-beginning 2)
398 + (ver emacs-major-version)
399 + (subver emacs-minor-version))
401 + (or (string-match "^\\([0-9]+\\)\\.\\([0-9]+\\)" emacs-version)
402 + (error "efs does not work with emacs version %s" emacs-version))
403 + (setq ver (string-to-int (substring emacs-version
404 + (match-beginning 1)
406 + subver (string-to-int (substring emacs-version
407 + (match-beginning 2)
411 ;; XEmacs (emacs-version looks like \"19.xx XEmacs\")
415 Here is the patch to make Dired work with SXEmacs:
417 (Note: the current Dired package that XEmacs distributes has this
421 ===================================================================
422 RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/dired/ChangeLog,v
423 retrieving revision 1.19
424 diff -u -U0 -r1.19 ChangeLog
425 --- ChangeLog 4 Oct 2004 08:54:24 -0000 1.19
426 +++ ChangeLog 14 Jan 2005 02:37:37 -0000
428 +2005-01-14 Steve Youngs <steve@sxemacs.org>
430 + * dired.el: Use `emacs-*-version' variables for finding version
431 + information instead of string-matching through `emacs-version'.
433 + * diff.el (diff-emacs-19-p): Ditto.
436 ===================================================================
437 RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/dired/diff.el,v
438 retrieving revision 1.4
439 diff -u -u -r1.4 diff.el
440 --- diff.el 2 Oct 2004 14:06:17 -0000 1.4
441 +++ diff.el 14 Jan 2005 02:37:23 -0000
443 ;;; Internal variables
445 (defconst diff-emacs-19-p
446 - (let ((ver (string-to-int (substring emacs-version 0 2))))
447 + (let ((ver emacs-major-version))
450 (or diff-emacs-19-p (require 'emacs-19))
452 ===================================================================
453 RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/dired/dired.el,v
454 retrieving revision 1.7
455 diff -u -u -r1.7 dired.el
456 --- dired.el 2 Oct 2004 14:06:19 -0000 1.7
457 +++ dired.el 14 Jan 2005 02:37:25 -0000
459 ;; Testing against the string `Lucid' breaks InfoDock. How many years has
460 ;; it been since Lucid went away?
461 (let ((lucid-p (string-match "XEmacs" emacs-version))
463 - (or (string-match "^\\([0-9]+\\)\\.\\([0-9]+\\)" emacs-version)
464 - (error "dired does not work with emacs version %s" emacs-version))
465 - (setq ver (string-to-int (substring emacs-version (match-beginning 1)
467 - subver (string-to-int (substring emacs-version (match-beginning 2)
469 + (ver emacs-major-version)
470 + (subver emacs-minor-version))
472 + (or (string-match "^\\([0-9]+\\)\\.\\([0-9]+\\)" emacs-version)
473 + (error "dired does not work with emacs version %s" emacs-version))
474 + (setq ver (string-to-int (substring emacs-version (match-beginning 1)
476 + subver (string-to-int (substring emacs-version (match-beginning 2)
481 @@ -6616,11 +6618,12 @@
482 ;;;; --------------------------------------------------------------
484 (let ((lucid-p (string-match "XEmacs" emacs-version))
486 - (or (string-match "^\\([0-9]+\\)\\." emacs-version)
487 - (error "Weird emacs version %s" emacs-version))
488 - (setq ver (string-to-int (substring emacs-version (match-beginning 1)
490 + (ver emacs-major-version))
492 + (or (string-match "^\\([0-9]+\\)\\." emacs-version)
493 + (error "Weird emacs version %s" emacs-version))
494 + (setq ver (string-to-int (substring emacs-version (match-beginning 1)
497 ;; Reading with history.
501 * Problems with running SXEmacs
502 ===============================
506 *** ffi-wand.el refuses to load.
508 Can't load library `libMagickWand': libgomp.so.1: shared object cannot be
511 If you get that error when trying to load ffi-wand, it is because you
512 have a ImageMagick that is using OpenMP (currently only svn HEAD). To
513 fix this you will need to rebuild ImageMagick, making sure that you
514 configure it using --disable-openmp.
516 See: <http://issues.sxemacs.org/show_bug.cgi?id=104>
518 ** Multimedia Goodness
520 *** SXEmacs hangs or crashes during (init-asynchronousity).
522 This is most likely a known effect (we do not want to call it bug,
523 since there is no definite location) with certain (g)libc and kernel
524 combinations under Linux. If it crashes analyse the core file, it
525 should look like this:
527 #0 0x4014ebc4 in __sigsuspend (set=0xbffffbb4) at
528 ../sysdeps/unix/sysv/linux/sigsuspend.c:48
529 #1 0x40101b34 in __pthread_wait_for_restart_signal (self=0x401116e0) at
531 #2 0x40101138 in __pthread_create_2_1 (thread=0x206f8dc, attr=0xbffffc58,
532 start_routine=0x20043ac <console>, arg=0xbffffd88) at restart.h:26
534 A definite fault-prone setup is using kernel 2.6.x in conjunction with
537 *** SXEmacs hangs or crashes before it ought to playback sound.
539 As before, this is most likely a suspicious (g)libc/kernel
542 *** SXEmacs dumps core when using the ALSA audio device
544 This has been reported to happen with old ALSA libraries (1.0.3 to be
545 precise). At the moment it is uncertain at which version these
546 problems disappear (no developer wants to downgrade to a non-working
547 ALSA :D). We highly suggest to use the version 1.0.10 and above, or
550 *** SXEmacs in async mode does not play simultaneous sounds with ALSA
552 This is due to missing (hardware-)mixing capabilities of your
553 soundcard. There is a user-space plugin called dmix, which can
554 effectively circumvent this issue.
556 *** SXEmacs dumps core when using the aRts audio device
558 Does it? Please report details (version number of aRts, backtrace,
561 *** SXEmacs crashes when using state sentinels with asynchronous sounds
563 This is a known bug (#13 in our bug database). At the moment the only
564 advise we can give is: do not use sentinels before 22.1.7.
565 Also see our bug database at http://issues.sxemacs.org
567 *** make-media-stream seems to recognise any file as valid audio
569 This is a known issue with fully-featured ffmpeg builds. The current
570 code in SXEmacs blindly relies on FFmpeg when it reports a file or
571 string as valid audio. There is no way to double-check that at the
572 moment. However, you can perform the additional check yourself if
573 you have taglib installed. Use the included ffi-taglib.el.
576 * Original XEmacs PROBLEMS File
577 ===============================
578 From here down is a reproduction of the original XEmacs PROBLEMS
579 file. Much of it is already fixed in SXEmacs (and in XEmacs too).
580 We're keeping it here for prosperity, or until somebody finds the time
581 to go through it all and remove the irrelevant stuff. :-)
583 Note: Some irrelevant stuff purged (mostly windows rubbish) 2010-04-01
585 This file describes various problems that have been encountered
586 in compiling, installing and running XEmacs. It has been updated for
589 This file is rather large, but we have tried to sort the entries by
590 their respective relevance for XEmacs, but may have not succeeded
591 completely in that task. The file is divided into four parts:
593 - Problems with building XEmacs
594 - Problems with running XEmacs
595 - Compatibility problems
598 Use `C-c C-f' to move to the next equal level of outline, and
599 `C-c C-b' to move to previous equal level. `C-h m' will give more
600 info about the Outline mode.
602 Also, Try finding the things you need using one of the search commands
603 XEmacs provides (e.g. `C-s').
607 WATCH OUT for your init file! (~/.xemacs/init.el or ~/.emacs) If
608 you observe strange problems, invoke XEmacs with the `-vanilla'
609 option and see if you can repeat the problem.
611 Note that most of the problems described here manifest at RUN
612 time, even those described as BUILD problems. It is quite unusual
613 for a released XEmacs to fail to build. So a "build problem"
614 requires you to tweak the build environment, then rebuild XEmacs.
615 A "runtime problem" is one that can be fixed by proper
616 configuration of the existing build. Compatibility problems and
617 Mule issues are generally runtime problems, but are treated
618 separately for convenience.
621 * Problems with building XEmacs
622 ===============================
626 Much general information is in INSTALL. If it's covered in
627 INSTALL, we don't repeat it here.
629 *** How do I configure to get the buffer tabs/progress bars?
631 These features depend on support for "native widgets". Use the
632 --with-widgets option to configure. Configuration of widgets is
633 automatic for "modern" toolkits (MS Windows, GTK, and Motif), but if
634 you are using Xt and the Athena widgets, you will probably want to
635 specify a "3d" widget set. See configure --usage, and don't forget to
636 install the corresponding development libraries.
638 *** I know I have libfoo installed, but configure doesn't find it.
640 Typical of Linux systems with package managers. To link with a shared
641 library, you only need the shared library. To compile objects that
642 link with it, you need the headers---and distros don't provide them with
643 the libraries. You need the additional "development" package, too.
645 *** When using gcc, you get the error message "undefined symbol __fixunsdfsi".
646 When using gcc, you get the error message "undefined symbol __main".
648 This means that you need to link with the gcc library. It may be called
649 "gcc-gnulib" or "libgcc.a"; figure out where it is, and define LIB_GCC in
650 config.h to point to it.
652 It may also work to use the GCC version of `ld' instead of the standard one.
654 *** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
656 This can happen if configure uses GNU sed version 2.03. That version
657 had a bug. GNU sed version 2.05 works properly.
661 Motif is the X11 version of the Gnus torture test: if there's a way to
662 crash, Motif will find it. With the open source release of Motif, it
663 seems like a good idea to collect all Motif-related issues in one
666 You should also look in your OS's section, as it may not be Motif's
669 *** XEmacs visibly repaints itty-bitty rectangles very slowly.
671 This should only be visible on a slow X connection (ISDN, maybe T1).
673 At least some versions of Motif apparently do not implement
674 XtExposeCompressMaximal properly, so it is disabled. If you wish to
675 experiment, you can remove the #ifdef LWLIB_NEEDS_MOTIF at line 238
676 (or so) of src/EmacsFrame.c, leaving only the line
678 /* compress_exposure */ XtExposeCompressMaximal | XtExposeNoRegion,
680 and recompile. This enables exposure compression, giving a 10:1 or
681 better speedup for some users. However, on some Motif platforms (Red
682 Hat Linux 9.0 and Solaris 2.8, at least), this causes XEmacs to hang
683 while displaying the progress bar (eg, in font-lock). A workaround
684 for that problem is to setq `progress-feedback-use-echo-area' to `t'.
686 *** XEmacs crashes on exit (#1).
688 The backtrace is something like:
691 #0 0xfeb9a480 in _libc_kill () from /usr/lib/libc.so.1
692 #1 0x000b0388 in fatal_error_signal ()
693 #2 <signal handler called>
694 #3 YowIter (ht=0xb, id=0x0, v=0x74682074, client=0x47e3c0)
696 #4 0xff26cc5c in _LTHashTableForEachItem (ht=0x4725e8,
697 iter=0xff26dda0 <YowIter>, ClientData=0x47e3c0) at Hash.c:671
698 #5 0xff2a4664 in destroy (w=0x496550) at Screen.c:352
699 #6 0xfef92118 in Phase2Destroy () from /usr/openwin/lib/libXt.so.4
700 #7 0xfef91940 in Recursive () from /usr/openwin/lib/libXt.so.4
701 #8 0xfef91e44 in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
702 #9 0xfef91ae8 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
703 #10 0xfef918cc in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
704 #11 0xfef91438 in CloseDisplay () from /usr/openwin/lib/libXt.so.4
705 #12 0xfef91394 in XtCloseDisplay () from /usr/openwin/lib/libXt.so.4
706 #13 0x0025b8b0 in x_delete_device ()
707 #14 0x000940b0 in delete_device_internal ()
708 #15 0x000806a0 in delete_console_internal ()
710 This is known to happen with Lesstif version 0.93.36. Similar
711 backtraces have also been observed on HP/UX and Solaris. There is a
712 patch for Lesstif. (This is not a solution; it just stops the crash.
713 It may or may not be harmless, but "it works for the author".)
715 Note that this backtrace looks a lot like the one in the next item.
716 However, this one is invulnerable to the Solaris patches mentioned there.
718 Frank McIngvale <frankm@hiwaay.net> says:
720 Ok, 0.93.34 works, and I tracked down the crash to a section
721 marked "experimental" in 0.93.36. Patch attached, "works for me".
723 diff -u -r lesstif-0.93.36/lib/Xm/ImageCache.c lesstif-0.93.36-mod/lib/Xm/ImageCache.c
724 --- lesstif-0.93.36/lib/Xm/ImageCache.c 2002-08-05 14:53:24.000000000 -0500
725 +++ lesstif-0.93.36-mod/lib/Xm/ImageCache.c 2002-11-11 11:13:12.000000000 -0600
726 @@ -1166,5 +1166,4 @@
727 DEBUGOUT(_LtDebug0(__FILE__, NULL, "_LtImageCacheScreenDestroy (XmGetPixmapByDepth) %p\n",
730 - (void) _LTHashTableForEachItem(PixmapCache, YowIter, (XtPointer)s);
733 *** XEmacs crashes on exit (#2)
735 Especially frequent with multiple frames. Crashes that produce C
736 backtraces like this:
738 #0 0xfec9a118 in _libc_kill () from /usr/lib/libc.so.1
739 #1 0x77f48 in fatal_error_signal (sig=11)
740 at /codes/rpluim/xemacs-21.4/src/emacs.c:539
741 #2 <signal handler called>
742 #3 0xfee929f4 in XFindContext () from /usr/openwin/lib/libX11.so.4
743 #4 0xfee92930 in XFindContext () from /usr/openwin/lib/libX11.so.4
744 #5 0xff297e54 in DisplayDestroy () from /usr/dt/lib/libXm.so.4
745 #6 0xfefbece0 in XtCallCallbackList () from /usr/openwin/lib/libXt.so.4
746 #7 0xfefc486c in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
747 #8 0xfefc45d0 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
748 #9 0xfefc43b4 in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
749 #10 0x15cf9c in x_delete_device (d=0x523f00)
751 are caused by buggy Motif libraries. Installing the following patches
752 has been reported to solve the problem on Solaris 2.7:
756 For information (although they have not been confirmed to work), the
757 equivalent patches for Solaris 2.8 are:
761 *** On HP-UX 11.0 XEmacs causes excessive X11 errors when running.
762 (also appears on AIX as reported in comp.emacs.xemacs)
764 Marcus Thiessel <marcus@xemacs.org>
766 Unfortunately, XEmacs releases prior to 21.0 don't work with
767 Motif2.1. It will compile but you will get excessive X11 errors like
769 xemacs: X Error of failed request: BadGC (invalid GC parameter)
771 and finally XEmacs gets killed. A workaround is to use the
772 Motif1.2_R6 libraries. You can the following line to your call to
775 --x-libraries="/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6"
777 Make sure /usr/lib/Motif1.2_R6/libXm.sl is a link to
778 /usr/lib/Motif1.2_R6/libXm.3.
780 *** On HP-UX 11.0: Object "" does not have windowed ancestor
782 Marcus Thiessel <marcus@xemacs.org>
784 XEmacs dies without core file and reports:
786 Error: Object "" does not have windowed ancestor.
788 This is a bug. Please apply the patch PHSS_19964 (check if
789 superseded). The other alternative is to link with Motif1.2_R6 (see
792 *** Motif dialog boxes lose on Irix.
794 Larry Auton <lda@control.att.com> writes:
795 Beware of not specifying
797 --with-dialogs=athena
799 if it builds with the motif dialogs [boom!] you're a dead man.
803 *** IBM compiler fails: "The character # is not a valid C source character."
805 Most recently observed in 21.5.9, due to USE_KKCC ifdefs (they just
806 happen to tickle the implementation).
808 Valdis Kletnieks says:
810 The problem is that IBM defines a *MACRO* called 'memcpy', and we
811 have stuck a #ifdef/#endif inside the macro call. As a workaround,
812 try adding '-U__STR__' to your CFLAGS - this will cause string.h to
813 not do a #define for strcpy() to __strcpy() - it uses this for
814 automatic inlining support.
816 (For the record, the same issue affects a number of other functions
817 defined in string.h - basically anything the compiler knows how to
820 *** On AIX 4.3, you must specify --with-dialogs=athena with configure
822 *** The libXt shipped with AIX 4.3 up to 4.3.2 is broken. This causes
823 xemacs -nw to fail in various ways. The official APAR is this:
825 APAR NUMBER: <IX89470> RESOLVED AS: PROGRAM ERROR
828 <IX89470>: LIBXT.A INCORRECT HANDLING OF EXCEPTIONS IN XTAPPADDINPUT
830 The solution is to install X11.base.lib at version >=4.3.2.5.
832 *** On AIX, you get this compiler error message:
834 Processing include file ./XMenuInt.h
835 1501-106: (S) Include file X11/Xlib.h not found.
837 This means your system was installed with only the X11 runtime i.d
838 libraries. You have to find your sipo (bootable tape) and install
841 *** On AIX 4.1.2, linker error messages such as
842 ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
843 of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
845 This is a problem in libIM.a. You can work around it by executing
846 these shell commands in the src subdirectory of the directory where
849 cp /usr/lib/libIM.a .
853 Then change -lIM to ./libIM.a in the command to link temacs (in
856 *** Excessive optimization on AIX 4.2 can lead to compiler failure.
858 Valdis.Kletnieks@vt.edu writes:
859 At least at the b34 level, and the latest-and-greatest IBM xlc
860 (3.1.4.4), there are problems with -O3. I haven't investigated
865 *** Dumping error when using GNU binutils / GNU ld on a Sun.
867 Errors similar to the following:
869 Dumping under the name xemacs unexec():
870 dldump(/space/rpluim/xemacs-obj/src/xemacs): ld.so.1: ./temacs:
871 fatal: /space/rpluim/xemacs-obj/src/xemacs: unknown dynamic entry:
874 are caused by using GNU ld. There are several workarounds available:
876 In XEmacs 21.2 or later, configure using the new portable dumper
879 Alternatively, you can link using the Sun version of ld, which is
880 normally held in /usr/ccs/bin. This can be done by one of:
882 - building gcc with these configure flags:
883 configure --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as
885 - adding -B/usr/ccs/bin/ to CFLAGS used to configure XEmacs
886 (Note: The trailing '/' there is significant.)
888 - uninstalling GNU ld.
890 The Solaris2 FAQ claims:
892 When you install gcc, don't make the mistake of installing
893 GNU binutils or GNU libc, they are not as capable as their
894 counterparts you get with Solaris 2.x.
896 *** Link failure when using acc on a Sun.
898 To use acc, you need additional options just before the libraries, such as
900 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
902 and you need to add -lansi just before -lc.
904 The precise file names depend on the compiler version, so we
905 cannot easily arrange to supply them.
907 *** Problems finding X11 libraries on Solaris with Openwindows
909 Some users have reported problems in this area. The reported solution
910 is to define the environment variable OPENWINHOME, even if you must set
911 it to `/usr/openwin'.
913 *** Sed problems on Solaris 2.5
915 There have been reports of Sun sed truncating very lines in the
916 Makefile during configuration. The workaround is to use GNU sed or,
917 even better, think of a better way to generate Makefile, and send us a
920 *** On Solaris 2 I get undefined symbols from libcurses.a.
922 You probably have /usr/ucblib/ on your LD_LIBRARY_PATH. Do the link with
923 LD_LIBRARY_PATH unset. Generally, avoid using any ucb* stuff when
926 *** On Solaris 2 I cannot make alloc.o, glyphs.o or process.o.
928 The SparcWorks C compiler may have difficulty building those modules
929 with optimization level -xO4. Try using only "-fast" optimization
930 for just those modules. (Or use gcc).
932 *** Solaris 2.3 /bin/sh coredumps during configuration.
934 This only occurs if you have LANG != C. This is a known bug with
935 /bin/sh fixed by installing Patch-ID# 101613-01. Or, you can use
936 bash by setting the environment variable CONFIG_SHELL to /bin/bash
938 *** Solaris 2.x configure/Makefile syntax "errors"
940 This is a known bug with /bin/sh and /bin/test, i.e. they do not
941 support the XPG4 standard. You can use bash as a workaround or an
942 XPG4-compliant Bourne shell such as the Sun-supplied /usr/xpg4/bin/sh
943 by setting the environment variable CONFIG_SHELL to /usr/xpg4/bin/sh
945 *** On SunOS, you get linker errors
947 _get_wmShellWidgetClass
948 _get_applicationShellWidgetClass
950 The fix to this is to install patch 100573 for OpenWindows 3.0
951 or link libXmu statically.
953 *** On Sunos 4, you get the error ld: Undefined symbol __lib_version.
955 This is the result of using cc or gcc with the shared library meant
956 for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete
957 /usr/lang/SC2.0.1 or some similar directory.
959 *** Undefined symbols when linking on Sunos 4.1.
961 If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
962 _iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
963 -lXaw in the command that links temacs.
965 This problem seems to arise only when the international language
966 extensions to X11R5 are installed.
968 *** On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
970 /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
972 The problem is in the Sun shared C library, not in GNU ld.
974 The solution is to install Patch-ID# 100267-03 from Sun.
976 *** SunOS 4.1.2: undefined symbol _get_wmShellWidgetClass
978 Apparently the version of libXmu.so.a that Sun ships is hosed: it's missing
979 some stuff that is in libXmu.a (the static version). Sun has a patch for
980 this, but a workaround is to use the static version of libXmu, by changing
981 the link command from "-lXmu" to "-Bstatic -lXmu -Bdynamic". If you have
982 OpenWindows 3.0, ask Sun for these patches:
983 100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
984 100573-03 4.1.x OpenWindows 3.0 undefined symbols with shared libXmu
986 *** Random other SunOS 4.1.[12] link errors.
988 The X headers and libraries that Sun ships in /usr/{include,lib}/X11 are
989 broken. Use the ones in /usr/openwin/{include,lib} instead.
993 See also Intel Architecture General, above.
995 *** Under Linux, you get "too many arguments to function `getpgrp'".
997 You have probably installed LessTiff under `/usr/local' and `libXm.so'
998 could not be found when linking `getpgrp()' test program, making XEmacs
999 think that `getpgrp()' takes an argument. Try adding `/usr/local/lib'
1000 in `/etc/ld.so.conf' and run `ldconfig'. Then run XEmacs's `configure'
1001 again. As with all problems of this type, reading the config.log file
1002 generated from configure and seeing the log of how the test failed can
1005 *** `Error: No ExtNode to pop!' on Linux systems with Lesstif.
1007 This error message has been observed with lesstif-0.75a. It does not
1008 appear to cause any harm.
1012 *** More coredumping in Irix (6.5 known to be vulnerable)
1014 No fix is known yet. Here's the best information we have:
1016 Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
1018 Were xemacs and [any 3rd party, locally-compiled] libraries [you use]
1019 all compiled with the same ABI ( -o32, -n32, -64) and
1020 mips2/mips3/mips4 flags, and are they appropriate for the machine in
1021 question? I know the IP30 implies an Octane, so it should be an R10K
1022 chipset and above such nonsense, but I've seen the most astoundingly
1023 bizzare crashes when somebody managed to compile with -mips4 and get
1024 it to run on an R4400 or R5K system. ;)
1026 Also, since you're using gcc, try re-running fixincludes and *then*
1027 rebuilding xemacs and [any] libraries - mismatched headers can do that
1028 sort of thing to you with little or no clue what's wrong (often you
1029 get screwed when one routine does an malloc(sizeof(foo_struct)) and
1030 passes the result to something that things foo_struct is a bit bigger,
1033 Here's typical crash backtrace. With --pdump, this occurs usually at
1034 startup under X windows and xemacs -nw at least starts, while without
1035 --pdump a similar crash is observed during build.
1037 #0 0x0fa460b8 in kill () at regcomp.c:637
1038 637 regcomp.c: No such file or directory.
1041 #0 0x0fa460b8 in kill () at regcomp.c:637
1042 #1 0x10087f34 in fatal_error_signal ()
1045 This is confusing because there is no such file in the XEmacs
1046 distribution. This is seen on (at least) the following configurations:
1048 uname -a: IRIX64 oct202 6.5 01091821 IP30
1049 XEmacs 21.4.9 "Informed Management" configured for `mips-sgi-irix6.5'.
1050 XEmacs 21.5-b9 "brussels sprouts" configured for `mips-sgi-irix6.5'.
1052 *** On Irix 6.5, the MIPSpro compiler gets an internal compiler error
1054 The MIPSpro Compiler (at least version 7.2.1) can't seem to handle the
1055 union type properly, and fails to compile src/glyphs.c. To avoid this
1056 problem, always build ---use-union-type=no (but that's the default, so
1057 you should only see this problem if you're an XEmacs maintainer).
1059 *** Linking with -rpath on IRIX.
1061 Darrell Kindred <dkindred@cmu.edu> writes:
1062 There are a couple of problems [with use of -rpath with Irix ld], though:
1064 1. The ld in IRIX 5.3 ignores all but the last -rpath
1065 spec, so the patched configure spits out a warning
1066 if --x-libraries or --site-runtime-libraries are
1067 specified under irix 5.x, and it only adds -rpath
1068 entries for the --site-runtime-libraries. This bug was
1069 fixed sometime between 5.3 and 6.2.
1071 2. IRIX gcc 2.7.2 doesn't accept -rpath directly, so
1072 it would have to be prefixed by -Xlinker or "-Wl,".
1073 This would be fine, except that configure compiles with
1074 ${CC-cc} $CFLAGS $LDFLAGS ...
1075 rather than quoting $LDFLAGS with prefix-args, like
1076 src/Makefile does. So if you specify --x-libraries
1077 or --site-runtime-libraries, you must use --use-gcc=no,
1078 or configure will fail.
1080 *** On Irix 6.3, the SGI ld quits with segmentation fault when linking temacs
1082 This occurs if you use the SGI linker version 7.1. Installing the
1083 patch SG0001872 fixes this problem.
1085 *** On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
1087 A compiler bug inserts spaces into the string "unexelfsgi . o"
1088 in src/Makefile. Edit src/Makefile, after configure is run,
1089 find that string, and take out the spaces.
1091 Compiler fixes in Irix 6.0.1 should eliminate this problem.
1093 *** On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
1095 The file cmplrs/stsupport.h was included in the wrong file set in the
1096 Irix 5.2 distribution. You can find it in the optional fileset
1097 compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
1098 workaround is to change unexelfsgi.c to include sym.h instead of
1101 *** Coredumping in Irix 6.2
1103 Pete Forman <gsez020@compo.bedford.waii.com> writes:
1104 A problem noted by myself and others (I've lost the references) was
1105 that XEmacs coredumped when the cut or copy toolbar buttons were
1106 pressed. This has been fixed by loading the SGI patchset (Feb 98)
1107 without having to recompile XEmacs.
1109 My versions are XEmacs 20.3 (problem first noted in 19.15) and IRIX
1110 6.2, compiled using -n32. I'd guess that the relevant individual
1111 patch was "SG0002580: multiple fixes for X libraries". SGI recommends
1112 that the complete patch set be installed rather than parts of it.
1114 ** Digital UNIX/OSF/VMS
1115 *** On Digital UNIX, the DEC C compiler might have a problem compiling
1118 In particular, src/extents.c and src/faces.c might cause the DEC C
1119 compiler to abort. When this happens: cd src, compile the files by
1120 hand, cd .., and redo the "make" command. When recompiling the files by
1121 hand, use the old C compiler for the following versions of Digital UNIX:
1122 - V3.n: Remove "-migrate" from the compile command.
1123 - V4.n: Add "-oldc" to the compile command.
1125 A related compiler bug has been fixed by the DEC compiler team. The
1126 new versions of the compiler should run fine.
1128 *** Under some versions of OSF XEmacs runs fine if built without
1129 optimization but will crash randomly if built with optimization.
1131 Using 'cc -g' is not sufficient to eliminate all optimization. Try
1132 'cc -g -O0' instead.
1134 *** Compilation errors on VMS.
1136 Sorry, XEmacs does not work under VMS. You might consider working on
1137 the port if you really want to have XEmacs work under VMS.
1140 *** On HPUX, the HP C compiler might have a problem compiling some files
1143 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
1145 Had to drop once again to level 2 optimization, at least to
1146 compile lstream.c. Otherwise, I get a "variable is void: \if"
1147 problem while dumping (this is a problem I already reported
1148 with vanilla hpux 10.01 and 9.07, which went away after
1149 applying patches for the C compiler). Trouble is I still
1150 haven't found the same patch for hpux 10.10, and I don't
1151 remember the patch numbers. I think potential XEmacs builders
1152 on HP should be warned about this.
1154 *** I don't have `xmkmf' and `imake' on my HP.
1156 You can get these standard X tools by anonymous FTP to
1157 hpcvaaz.cv.hp.com. Essentially all X programs need these.
1159 *** On HP-UX, problems with make
1161 Marcus Thiessel <marcus@xemacs.org>
1163 Some releases of XEmacs (e.g. 20.4) require GNU make to build
1164 successfully. You don't need GNU make when building 21.x.
1166 *** On HP-UX 9.05 XEmacs won't compile or coredump during the build.
1168 Marcus Thiessel <marcus@xemacs.org>
1170 This might be a sed problem. For your own safety make sure to use
1171 GNU sed while dumping XEmacs.
1175 *** Native cc on SCO OpenServer 5 is now OK. Icc may still throw you
1176 a curve. Here is what Robert Lipe <robertl@arnet.com> says:
1178 Unlike XEmacs 19.13, building with the native cc on SCO OpenServer 5
1179 now produces a functional binary. I will typically build this
1180 configuration for COFF with:
1182 /path_to_xemacs_source/configure --with-gcc=no \
1183 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
1184 --with-xpm --with-xface --with-sound=nas
1186 This version now supports ELF builds. I highly recommend this to
1187 reduce the in-core footprint of XEmacs. This is now how I compile
1188 all my test releases. Build it like this:
1190 /path_to_XEmacs_source/configure --with-gcc=no \
1191 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
1192 --with-xpm --with-xface --with-sound=nas --dynamic
1194 The compiler known as icc [ supplied with the OpenServer 5 Development
1195 System ] generates a working binary, but it takes forever to generate
1196 XEmacs. ICC also whines more about the code than /bin/cc does. I do
1197 believe all its whining is legitimate, however. Note that you do
1198 have to 'cd src ; make LD=icc' to avoid linker errors.
1200 The way I handle the build procedure is:
1202 /path_to_XEmacs_source/configure --with-gcc=no \
1203 --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
1204 --with-xpm --with-xface --with-sound=nas --dynamic --compiler="icc"
1206 NOTE I have the xpm, xface, and audio libraries and includes in
1207 /usr/local/lib, /usr/local/include. If you don't have these,
1208 don't include the "--with-*" arguments in any of my examples.
1210 In previous versions of XEmacs, you had to override the defaults while
1211 compiling font-lock.o and extents.o when building with icc. This seems
1212 to no longer be true, but I'm including this old information in case it
1213 resurfaces. The process I used was:
1216 [ procure pizza, beer, repeat ]
1218 make CC="icc -W0,-mP1COPT_max_tree_size=3000" font-lock.o extents.o
1221 If you want sound support, get the tls566 supplement from
1222 ftp.sco.com:/TLS or any of its mirrors. It works just groovy
1225 The M-x manual-entry is known not to work. If you know Lisp and would
1226 like help in making it work, e-mail me at <robertl@dgii.com>.
1227 (UNCHECKED for 19.15 -- it might work).
1229 In earlier releases, gnuserv/gnuclient/gnudoit would open a frame
1230 just fine, but the client would lock up and the server would
1231 terminate when you used C-x # to close the frame. This is now
1234 In etc/ there are two files of note. emacskeys.sco and emacsstrs.sco.
1235 The comments at the top of emacskeys.sco describe its function, and
1236 the emacstrs.sco is a suitable candidate for /usr/lib/keyboard/strings
1237 to take advantage of the keyboard map in emacskeys.sco.
1239 Note: Much of the above entry is probably not valid for XEmacs 21.0
1242 * Problems with running XEmacs
1243 ==============================
1246 *** XEmacs consistently crashes in a particular strange place.
1248 One known case is on Red Hat Linux, compiled with GCC, attempting to
1249 render PNG images. The problem is that XEmacs code is not compliant
1250 with ANSI rules about aliasing. Adding -fno-strict-aliasing to CFLAGS
1251 may help (or the equivalent for your compiler). (Some versions of
1252 XEmacs may already do this automatically, but if you specify CFLAGS or
1253 --cflags yourself, you will have to add this flag by hand.)
1255 If you diagnose this bug for some other symptoms or systems, please
1256 let us know (if you can send mail from the affected system, use M-x
1257 report-xemacs-bug) so we can update this entry.
1259 *** Changes made to .el files do not take effect.
1261 You may have forgotten to recompile them into .elc files. Then the
1262 old .elc files will be loaded, and your changes will not be seen. To
1263 fix this, do `M-x byte-recompile-directory' and specify the directory
1264 that contains the Lisp files.
1266 Note that you will get a warning when loading a .elc file that is
1267 older than the corresponding .el file.
1269 *** VM appears to hang in large folders.
1271 This is normal (trust us) when upgrading to VM-6.22 from earlier
1272 versions. Let VM finish what it is doing and all will be well.
1274 *** Starting with 21.4.x, killing text is absurdly slow.
1276 See FAQ Q3.10.6. Should be available on the web near
1277 http://www.xemacs.org/faq/xemacs-faq.html#SEC160.
1279 *** Whenever I try to retrieve a remote file, I have problems.
1281 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
1282 Thanks to giacomo boffi <giacomo.boffi@polimi.it> on comp.emacs.xemacs:
1284 tell your ftp client to not attempt AUTH authentication (or do not
1285 use FTP servers that don't understand AUTH)
1287 and notes that you need to add an element (often "-u") to
1288 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
1289 needed flag with `man ftp' or other local documentation.
1291 *** gnuserv is running, some clients can connect, but others cannot.
1293 The code in gnuslib.c respects the value of TMPDIR. If the server and
1294 the client have different values in their environment, you lose.
1295 One program known to set TMPDIR and manifest this problem is exmh.
1296 You can defeat the use of TMPDIR by unsetting USE_TMPDIR at the top of
1297 gnuserv.h at build time.
1301 *** You type Control-H (Backspace) expecting to delete characters.
1303 Emacs has traditionally used Control-H for help; unfortunately this
1304 interferes with its use as Backspace on TTY's. As of XEmacs 21,
1305 XEmacs looks at the "erase" setting of TTY structures and maps C-h to
1306 backspace when erase is set to C-h. This is sort of a special hack,
1307 but it makes it possible for you to use the standard:
1311 to get your backspace key to erase characters. The erase setting is
1312 recorded in the Lisp variable `tty-erase-char', which you can use to
1313 tune the settings in your .emacs.
1315 A major drawback of this is that when C-h becomes backspace, it no
1316 longer invokes help. In that case, you need to use f1 for help, or
1317 bind another key. An example of the latter is the following code,
1318 which moves help to Meta-? (ESC ?):
1320 (global-set-key "\M-?" 'help-command)
1322 *** At startup I get a warning on stderr about missing charsets:
1324 Warning: Missing charsets in String to FontSet conversion
1326 You need to specify appropriate charsets for your locale (usually the
1327 value of the LANG environment variable) in .Xresources. See
1328 etc/Emacs.ad for the relevant resources (mostly menubar fonts and
1329 fontsets). Do not edit this file, it's purely informative.
1331 If you have no satisfactory fonts for iso-8859-1, XEmacs will crash.
1333 It looks like XFree86 4.x (the usual server on Linux and *BSD) has
1334 some braindamage where .UTF-8 locales will always generate this
1335 message, because the XFree86 (font)server doesn't know that UTF-8 will
1336 use the ISO10646-1 font registry (or a Cmap or something).
1338 If you are not using a .UTF-8 locale and see this warning for a
1339 character set not listed in the default in Emacs.ad, please let
1340 xemacs-beta@xemacs.org know about it, so we can add fonts to the
1341 appropriate fontsets and stifle this warning. (Unfortunately it's
1342 buried in Xlib, so we can't easily get rid of it otherwise.)
1344 *** Mail agents (VM, Gnus, rmail) cannot get new mail
1346 rmail and VM get new mail from /usr/spool/mail/$USER using a program
1347 called `movemail'. This program interlocks with /bin/mail using the
1348 protocol defined by /bin/mail.
1350 There are two different protocols in general use. One of them uses
1351 the `flock' system call. The other involves creating a lock file;
1352 `movemail' must be able to write in /usr/spool/mail in order to do
1353 this. You control which one is used by defining, or not defining, the
1354 macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes. IF
1355 YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR SYSTEM,
1358 If your system uses the lock file protocol, and fascist restrictions
1359 prevent ordinary users from writing the lock files in /usr/spool/mail,
1360 you may need to make `movemail' setgid to a suitable group such as
1361 `mail'. To do this, use the following commands (as root) after doing
1367 Installation normally copies movemail from the build directory to an
1368 installation directory which is usually under /usr/local/lib. The
1369 installed copy of movemail is usually in the directory
1370 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and
1371 mode of the installed copy; changing the group and mode of the build
1372 directory copy is ineffective.
1374 *** Things which should be bold or italic (such as the initial
1375 copyright notice) are not.
1377 The fonts of the "bold" and "italic" faces are generated from the font
1378 of the "default" face; in this way, your bold and italic fonts will
1379 have the appropriate size and family. However, emacs can only be
1380 clever in this way if you have specified the default font using the
1381 XLFD (X Logical Font Description) format, which looks like
1383 *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
1385 if you use any of the other, less strict font name formats, some of
1388 lucidasanstypewriter-12
1392 then emacs won't be able to guess the names of the "bold" and "italic"
1393 versions. All X fonts can be referred to via XLFD-style names, so you
1394 should use those forms. See the man pages for X(1), xlsfonts(1), and
1397 *** The dumped Emacs crashes when run, trying to write pure data.
1399 Two causes have been seen for such problems.
1401 1) On a system where getpagesize is not a system call, it is defined
1402 as a macro. If the definition (in both unexec.c and malloc.c) is wrong,
1403 it can cause problems like this. You might be able to find the correct
1404 value in the man page for a.out (5).
1406 2) Some systems allocate variables declared static among the
1407 initialized variables. Emacs makes all initialized variables in most
1408 of its files pure after dumping, but the variables declared static and
1409 not initialized are not supposed to be pure. On these systems you
1410 may need to add "#define static" to the m- or the s- file.
1412 *** Reading and writing files is very very slow.
1414 Try evaluating the form (setq lock-directory nil) and see if that helps.
1415 There is a problem with file-locking on some systems (possibly related
1416 to NFS) that I don't understand. Please send mail to the address
1417 xemacs-beta@xemacs.org if you figure this one out.
1419 *** When emacs starts up, I get lots of warnings about unknown keysyms.
1421 If you are running the prebuilt binaries, the Motif library expects to find
1422 certain thing in the XKeysymDB file. This file is normally in /usr/lib/X11/
1423 or in /usr/openwin/lib/. If you keep yours in a different place, set the
1424 environment variable $XKEYSYMDB to point to it before starting emacs. If
1425 you still have the problem after doing that, perhaps your version of X is
1426 too old. There is a copy of the MIT X11R5 XKeysymDB file in the emacs `etc'
1427 directory. Try using that one.
1429 *** My X resources used to work, and now some of them are being ignored.
1431 Check the resources in .../etc/Emacs.ad (which is the same as the file
1432 sample.Xresources). Perhaps some of the default resources built in to
1433 emacs are now overriding your existing resources. Copy and edit the
1434 resources in Emacs.ad as necessary.
1436 *** I have focus problems when I use `M-o' to switch to another screen
1437 without using the mouse.
1439 The focus issues with a program like XEmacs, which has multiple
1440 homogeneous top-level windows, are very complicated, and as a result,
1441 most window managers don't implement them correctly.
1443 The R4/R5 version of twm (and all of its descendants) had buggy focus
1444 handling. Sufficiently recent versions of tvtwm have been fixed. In
1445 addition, if you're using twm, make sure you have not specified
1446 "NoTitleFocus" in your .tvtwmrc file. The very nature of this option
1447 makes twm do some illegal focus tricks, even with the patch.
1449 It is known that olwm and olvwm are buggy, and in different ways. If
1450 you're using click-to-type mode, try using point-to-type, or vice
1453 In older versions of NCDwm, one could not even type at XEmacs windows.
1454 This has been fixed in newer versions (2.4.3, and possibly earlier).
1456 (Many people suggest that XEmacs should warp the mouse when focusing
1457 on another screen in point-to-type mode. This is not ICCCM-compliant
1458 behavior. Implementing such policy is the responsibility of the
1459 window manager itself, it is not legal for a client to do this.)
1461 *** Emacs spontaneously displays "I-search: " at the bottom of the screen.
1463 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
1464 used. C-s/C-q flow control is bad for Emacs editors because it takes
1465 away C-s and C-q as user commands. Since editors do not output long
1466 streams of text without user commands, there is no need for a
1467 user-issuable "stop output" command in an editor; therefore, a
1468 properly designed flow control mechanism would transmit all possible
1469 input characters without interference. Designing such a mechanism is
1470 easy, for a person with at least half a brain.
1472 There are three possible reasons why flow control could be taking place:
1474 1) Terminal has not been told to disable flow control
1475 2) Insufficient padding for the terminal in use
1476 3) Some sort of terminal concentrator or line switch is responsible
1478 First of all, many terminals have a set-up mode which controls whether
1479 they generate XON/XOFF flow control characters. This must be set to
1480 "no XON/XOFF" in order for Emacs to work. Sometimes there is an
1481 escape sequence that the computer can send to turn flow control off
1482 and on. If so, perhaps the termcap `ti' string should turn flow
1483 control off, and the `te' string should turn it on.
1485 Once the terminal has been told "no flow control", you may find it
1486 needs more padding. The amount of padding Emacs sends is controlled
1487 by the termcap entry for the terminal in use, and by the output baud
1488 rate as known by the kernel. The shell command `stty' will print
1489 your output baud rate; `stty' with suitable arguments will set it if
1490 it is wrong. Setting to a higher speed causes increased padding. If
1491 the results are wrong for the correct speed, there is probably a
1492 problem in the termcap entry. You must speak to a local Unix wizard
1493 to fix this. Perhaps you are just using the wrong terminal type.
1495 For terminals that lack a "no flow control" mode, sometimes just
1496 giving lots of padding will prevent actual generation of flow control
1497 codes. You might as well try it.
1499 If you are really unlucky, your terminal is connected to the computer
1500 through a concentrator which sends XON/XOFF flow control to the
1501 computer, or it insists on sending flow control itself no matter how
1502 much padding you give it. Unless you can figure out how to turn flow
1503 control off on this concentrator (again, refer to your local wizard),
1504 you are screwed! You should have the terminal or concentrator
1505 replaced with a properly designed one. In the mean time, some drastic
1506 measures can make Emacs semi-work.
1508 You can make Emacs ignore C-s and C-q and let the operating system
1509 handle them. To do this on a per-session basis, just type M-x
1510 enable-flow-control RET. You will see a message that C-\ and C-^ are
1511 now translated to C-s and C-q. (Use the same command M-x
1512 enable-flow-control to turn *off* this special mode. It toggles flow
1515 If C-\ and C-^ are inconvenient for you (for example, if one of them
1516 is the escape character of your terminal concentrator), you can choose
1517 other characters by setting the variables flow-control-c-s-replacement
1518 and flow-control-c-q-replacement. But choose carefully, since all
1519 other control characters are already used by emacs.
1521 IMPORTANT: if you type C-s by accident while flow control is enabled,
1522 Emacs output will freeze, and you will have to remember to type C-q in
1525 If you work in an environment where a majority of terminals of a
1526 certain type are flow control hobbled, you can use the function
1527 `enable-flow-control-on' to turn on this flow control avoidance scheme
1528 automatically. Here is an example:
1530 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
1532 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
1533 and good vt200 terminals), you can still run enable-flow-control
1536 I have no intention of ever redesigning the Emacs command set for the
1537 assumption that terminals use C-s/C-q flow control. XON/XOFF flow
1538 control technique is a bad design, and terminals that need it are bad
1539 merchandise and should not be purchased. Now that X is becoming
1540 widespread, XON/XOFF seems to be on the way out. If you can get some
1541 use out of GNU Emacs on inferior terminals, more power to you, but I
1542 will not make Emacs worse for properly designed systems for the sake
1543 of inferior systems.
1545 *** Control-S and Control-Q commands are ignored completely.
1547 For some reason, your system is using brain-damaged C-s/C-q flow
1548 control despite Emacs's attempts to turn it off. Perhaps your
1549 terminal is connected to the computer through a concentrator
1550 that wants to use flow control.
1552 You should first try to tell the concentrator not to use flow control.
1553 If you succeed in this, try making the terminal work without
1554 flow control, as described in the preceding section.
1556 If that line of approach is not successful, map some other characters
1557 into C-s and C-q using keyboard-translate-table. The example above
1558 shows how to do this with C-^ and C-\.
1560 *** Control-S and Control-Q commands are ignored completely on a net
1563 Some versions of rlogin (and possibly telnet) do not pass flow
1564 control characters to the remote system to which they connect.
1565 On such systems, emacs on the remote system cannot disable flow
1566 control on the local system.
1568 One way to cure this is to disable flow control on the local host
1569 (the one running rlogin, not the one running rlogind) using the
1570 stty command, before starting the rlogin process. On many systems,
1571 `stty start u stop u' will do this.
1573 Some versions of tcsh will prevent even this from working. One way
1574 around this is to start another shell before starting rlogin, and
1575 issue the stty command to disable flow control from that shell.
1577 If none of these methods work, the best solution is to type
1578 `M-x enable-flow-control' at the beginning of your emacs session, or
1579 if you expect the problem to continue, add a line such as the
1580 following to your .emacs (on the host running rlogind):
1582 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
1584 See the entry about spontaneous display of I-search (above) for more
1587 *** TTY redisplay is slow.
1589 XEmacs has fairly new TTY redisplay support (beginning from 19.12),
1590 which doesn't include some basic TTY optimizations -- like using
1591 scrolling regions to move around blocks of text. This is why
1592 redisplay on the traditional terminals, or over slow lines can be very
1595 If you are interested in fixing this, please let us know at
1596 <xemacs-beta@xemacs.org>.
1598 *** Screen is updated wrong, but only on one kind of terminal.
1600 This could mean that the termcap entry you are using for that terminal
1601 is wrong, or it could mean that Emacs has a bug handing the
1602 combination of features specified for that terminal.
1604 The first step in tracking this down is to record what characters
1605 Emacs is sending to the terminal. Execute the Lisp expression
1606 (open-termscript "./emacs-script") to make Emacs write all terminal
1607 output into the file ~/emacs-script as well; then do what makes the
1608 screen update wrong, and look at the file and decode the characters
1609 using the manual for the terminal. There are several possibilities:
1611 1) The characters sent are correct, according to the terminal manual.
1613 In this case, there is no obvious bug in Emacs, and most likely you
1614 need more padding, or possibly the terminal manual is wrong.
1616 2) The characters sent are incorrect, due to an obscure aspect of the
1617 terminal behavior not described in an obvious way by termcap.
1619 This case is hard. It will be necessary to think of a way for Emacs
1620 to distinguish between terminals with this kind of behavior and other
1621 terminals that behave subtly differently but are classified the same
1622 by termcap; or else find an algorithm for Emacs to use that avoids the
1623 difference. Such changes must be tested on many kinds of terminals.
1625 3) The termcap entry is wrong.
1627 See the file etc/TERMS for information on changes that are known to be
1628 needed in commonly used termcap entries for certain terminals.
1630 4) The characters sent are incorrect, and clearly cannot be right for
1631 any terminal with the termcap entry you were using.
1633 This is unambiguously an Emacs bug, and can probably be fixed in
1634 termcap.c, terminfo.c, tparam.c, cm.c, redisplay-tty.c,
1635 redisplay-output.c, or redisplay.c.
1637 *** My buffers are full of \000 characters or otherwise corrupt.
1639 Some compilers have trouble with gmalloc.c and ralloc.c; try recompiling
1640 without optimization. If that doesn't work, try recompiling with
1641 SYSTEM_MALLOC defined, and/or with REL_ALLOC undefined.
1643 *** A position you specified in .Xresources is ignored, using twm.
1645 twm normally ignores "program-specified" positions.
1646 You can tell it to obey them with this command in your `.twmrc' file:
1648 UsePPosition "on" #allow clents to request a position
1650 *** With M-x enable-flow-control, you need to type C-\ twice to do
1651 incremental search--a single C-\ gets no response.
1653 This has been traced to communicating with your machine via kermit,
1654 with C-\ as the kermit escape character. One solution is to use
1655 another escape character in kermit. One user did
1657 set escape-character 17
1659 in his .kermrc file, to make C-q the kermit escape character.
1661 *** The Motif version of Emacs paints the screen a solid color.
1663 This has been observed to result from the following X resource:
1665 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
1667 That the resource has this effect indicates a bug in something, but we
1668 do not yet know what. If it is an Emacs bug, we hope someone can
1669 explain what the bug is so we can fix it. In the mean time, removing
1670 the resource prevents the problem.
1672 *** After running emacs once, subsequent invocations crash.
1674 Some versions of SVR4 have a serious bug in the implementation of the
1675 mmap () system call in the kernel; this causes emacs to run correctly
1676 the first time, and then crash when run a second time.
1678 Contact your vendor and ask for the mmap bug fix; in the mean time,
1679 you may be able to work around the problem by adding a line to your
1680 operating system description file (whose name is reported by the
1681 configure script) that reads:
1682 #define SYSTEM_MALLOC
1683 This makes Emacs use memory less efficiently, but seems to work around
1686 *** Inability to send an Alt-modified key, when Emacs is communicating
1687 directly with an X server.
1689 If you have tried to bind an Alt-modified key as a command, and it
1690 does not work to type the command, the first thing you should check is
1691 whether the key is getting through to Emacs. To do this, type C-h c
1692 followed by the Alt-modified key. C-h c should say what kind of event
1693 it read. If it says it read an Alt-modified key, then make sure you
1694 have made the key binding correctly.
1696 If C-h c reports an event that doesn't have the Alt modifier, it may
1697 be because your X server has no key for the Alt modifier. The X
1698 server that comes from MIT does not set up the Alt modifier by
1701 If your keyboard has keys named Alt, you can enable them as follows:
1703 xmodmap -e 'add mod2 = Alt_L'
1704 xmodmap -e 'add mod2 = Alt_R'
1706 If the keyboard has just one key named Alt, then only one of those
1707 commands is needed. The modifier `mod2' is a reasonable choice if you
1708 are using an unmodified MIT version of X. Otherwise, choose any
1709 modifier bit not otherwise used.
1711 If your keyboard does not have keys named Alt, you can use some other
1712 keys. Use the keysym command in xmodmap to turn a function key (or
1713 some other 'spare' key) into Alt_L or into Alt_R, and then use the
1714 commands show above to make them modifier keys.
1716 Note that if you have Alt keys but no Meta keys, Emacs translates Alt
1717 into Meta. This is because of the great importance of Meta in Emacs.
1719 *** In Shell mode, you get a ^M at the end of every line.
1721 This happens to people who use tcsh, because it is trying to be too
1722 smart. It sees that the Shell uses terminal type `unknown' and turns
1723 on the flag to output ^M at the end of each line. You can fix the
1724 problem by adding this to your .cshrc file:
1727 if ($EMACS == "t") then
1729 stty -icrnl -onlcr -echo susp ^Z
1733 *** An error message such as `X protocol error: BadMatch (invalid
1734 parameter attributes) on protocol request 93'.
1736 This comes from having an invalid X resource, such as
1738 (which is invalid because it specifies a color name for something
1739 that isn't a color.)
1741 The fix is to correct your X resources.
1743 *** Once you pull down a menu from the menubar, it won't go away.
1745 It has been claimed that this is caused by a bug in certain very old
1746 (1990?) versions of the twm window manager. It doesn't happen with
1747 recent vintages, or with other window managers.
1749 *** Emacs ignores the "help" key when running OLWM.
1751 OLWM grabs the help key, and retransmits it to the appropriate client
1752 using XSendEvent. Allowing emacs to react to synthetic events is a
1753 security hole, so this is turned off by default. You can enable it by
1754 setting the variable x-allow-sendevents to t. You can also cause fix
1755 this by telling OLWM to not grab the help key, with the null binding
1756 "OpenWindows.KeyboardCommand.Help:".
1758 *** Programs running under terminal emulator do not recognize `emacs'
1761 The cause of this is a shell startup file that sets the TERMCAP
1762 environment variable. The terminal emulator uses that variable to
1763 provide the information on the special terminal type that Emacs
1766 Rewrite your shell startup file so that it does not change TERMCAP
1767 in such a case. You could use the following conditional which sets
1768 it only if it is undefined.
1770 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
1772 Or you could set TERMCAP only when you set TERM--which should not
1773 happen in a non-login shell.
1775 *** The popup menu appears at the bottom/right of my screen.
1777 You probably have something like the following in your ~/.Xresources
1779 Emacs.geometry: 81x56--9--1
1781 Use the following instead
1783 Emacs*EmacsFrame.geometry: 81x56--9--1
1785 *** When I try to use the PostgreSQL functions, I get a message about
1788 The only known case in which this happens is if you are using gcc, you
1789 configured with --error-checking=all and --with-modules, and you
1790 compiled with no optimization. If you encounter this problem in any
1791 other situation, please inform xemacs-beta@xemacs.org.
1793 This problem stems from a gcc bug. With no optimization, functions
1794 declared `extern inline' sometimes are not completely compiled away. An
1795 undefined symbol with the function's name is put into the resulting
1796 object file. In this case, when the postgresql module is loaded, the
1797 linker is unable to resolve that symbol, so the module load fails. The
1798 workaround is to recompile the module with optimization turned on. Any
1799 optimization level, including -Os, appears to work.
1801 *** C-z just refreshes the screen instead of suspending Emacs.
1803 You are probably using a shell that doesn't support job control, even
1804 though the system itself is capable of it. Try using a different
1808 *** XEmacs crashes on MacOS within font-lock, or when dealing
1809 with large compilation buffers, or in other regex applications.
1811 The default stack size under MacOS/X is rather small (512k as opposed
1812 to Solaris 8M), hosing the regexp code, which uses alloca()
1813 extensively, overflowing the stack when complex regexps are used.
1816 1) Increase your stack size, using `ulimit -s 8192' or a (t)csh
1819 2) Recompile regex.c with REGEX_MALLOC defined.
1822 *** Your Delete key sends a Backspace to the terminal, using an AIXterm.
1824 The solution is to include in your .Xresources the lines:
1826 *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
1827 aixterm*ttyModes: erase ^?
1829 This makes your Backspace key send DEL (ASCII 127).
1831 *** On AIX 4, some programs fail when run in a Shell buffer
1832 with an error message like No terminfo entry for "unknown".
1834 On AIX, many terminal type definitions are not installed by default.
1835 `unknown' is one of them. Install the "Special Generic Terminal
1836 Definitions" to make them defined.
1838 *** On AIX, you get this message when running Emacs:
1840 Could not load program emacs
1841 Symbol smtcheckinit in csh is undefined
1842 Error was: Exec format error
1846 Could not load program .emacs
1847 Symbol _system_con in csh is undefined
1848 Symbol _fp_trapsta in csh is undefined
1849 Error was: Exec format error
1851 These can happen when you try to run on AIX 3.2.5 a program that was
1852 compiled with 3.2.4. The fix is to recompile.
1854 *** Trouble using ptys on AIX.
1856 People often install the pty devices on AIX incorrectly.
1857 Use `smit pty' to reinstall them properly.
1861 *** The Emacs window disappears when you type M-q.
1863 Some versions of the Open Look window manager interpret M-q as a quit
1864 command for whatever window you are typing at. If you want to use
1865 Emacs with that window manager, you should try to configure the window
1866 manager to use some other command. You can disable the
1867 shortcut keys entirely by adding this line to ~/.OWdefaults:
1869 OpenWindows.WindowMenuAccelerators: False
1871 *** When Emacs tries to ring the bell, you get an error like
1873 audio: sst_open: SETQSIZE" Invalid argument
1874 audio: sst_close: SETREG MMR2, Invalid argument
1876 you have probably compiled using an ANSI C compiler, but with non-ANSI
1877 include files. In particular, on Suns, the file
1878 /usr/include/sun/audioio.h uses the _IOW macro to define the constant
1879 AUDIOSETQSIZE. _IOW in turn uses a K&R preprocessor feature that is
1880 now explicitly forbidden in ANSI preprocessors, namely substitution
1881 inside character constants. All ANSI C compilers must provide a
1882 workaround for this problem. Lucid's C compiler is shipped with a new
1883 set of system include files. If you are using GCC, there is a script
1884 called fixincludes that creates new versions of some system include
1885 files that use this obsolete feature.
1887 *** On Solaris 2.6, XEmacs dumps core when exiting.
1889 This happens if you're XEmacs is running on the same machine as the X
1890 server, and the optimized memory transport has been turned on by
1891 setting the environment variable XSUNTRANSPORT. The crash occurs
1892 during the call to XCloseDisplay.
1894 If this describes your situation, you need to undefine the
1895 XSUNTRANSPORT environment variable.
1897 *** On Solaris, C-x doesn't get through to Emacs when you use the console.
1899 This is a Solaris feature (at least on Intel x86 cpus). Type C-r
1900 C-r C-t, to toggle whether C-x gets through to Emacs.
1902 *** On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs
1903 forever waiting for termination of a subprocess that is a zombie.
1905 casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so
1906 after changing the file xc/config/cf/sunLib.tmpl. Change the lines
1909 #define SharedX11Reqs -lthread
1914 #if OSMinorVersion < 4
1916 #define SharedX11Reqs -lthread
1920 Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
1921 (as it should be for Solaris 2.4). The file has three definitions for
1922 OSMinorVersion: the first is for x86, the second for SPARC under
1923 Solaris, and the third for SunOS 4. Make sure to update the
1924 definition for your type of machine and system.
1926 Then do `make Everything' in the top directory of X11R6, to rebuild
1927 the makefiles and rebuild X. The X built this way work only on
1928 Solaris 2.4, not on 2.3.
1930 For multithreaded X to work it necessary to install patch
1931 101925-02 to fix problems in header files [2.4]. You need
1932 to reinstall gcc or re-run just-fixinc after installing that
1935 However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
1937 #define ThreadedX YES
1939 #define ThreadedX NO
1940 in sun.cf and did `make World' to rebuild X11R6. Removing all
1941 `-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
1942 typing 'make install' in that directory also seemed to work.
1944 *** On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
1946 This happens if you configure Emacs specifying just `sparc-sun-sunos4'
1947 on a system that is version 4.1.3. You must specify the precise
1948 version number (or let configure figure out the configuration, which
1949 it can do perfectly well for SunOS).
1951 *** Mail is lost when sent to local aliases.
1953 Many emacs mail user agents (VM and rmail, for instance) use the
1954 sendmail.el library. This library can arrange for mail to be
1955 delivered by passing messages to the /usr/lib/sendmail (usually)
1956 program . In doing so, it passes the '-t' flag to sendmail, which
1957 means that the name of the recipient of the message is not on the
1958 command line and, therefore, that sendmail must parse the message to
1959 obtain the destination address.
1961 There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
1962 In short, when given the -t flag, the SunOS sendmail won't recognize
1963 non-local (i.e. NIS) aliases. It has been reported that the Solaris
1964 2.x versions of sendmail do not have this bug. For those using SunOS
1965 4.1, the best fix is to install sendmail V8 or IDA sendmail (which
1966 have other advantages over the regular sendmail as well). At the time
1967 of this writing, these official versions are available:
1969 Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
1970 sendmail.8.6.9.base.tar.Z (the base system source & documentation)
1971 sendmail.8.6.9.cf.tar.Z (configuration files)
1972 sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
1973 sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
1975 IDA sendmail on vixen.cso.uiuc.edu in /pub:
1976 sendmail-5.67b+IDA-1.5.tar.gz
1978 *** Emacs fails to understand most Internet host names, even though
1979 the names work properly with other programs on the same system.
1980 Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
1981 Gnus can't make contact with the specified host for nntp.
1983 This typically happens on Suns and other systems that use shared
1984 libraries. The cause is that the site has installed a version of the
1985 shared library which uses a name server--but has not installed a
1986 similar version of the unshared library which Emacs uses.
1988 The result is that most programs, using the shared library, work with
1989 the nameserver, but Emacs does not.
1991 The fix is to install an unshared library that corresponds to what you
1992 installed in the shared library, and then relink Emacs.
1994 On SunOS 4.1, simply define HAVE_RES_INIT.
1996 If you have already installed the name resolver in the file libresolv.a,
1997 then you need to compile Emacs to use that library. The easiest way to
1998 do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
1999 or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro
2000 that is already in use in your configuration to supply some other libraries,
2001 be careful not to lose the others.
2003 Thus, you could start by adding this to config.h:
2005 #define LIBS_SYSTEM -lresolv
2007 Then if this gives you an error for redefining a macro, and you see that
2008 the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
2011 #define LIBS_SYSTEM -lresolv -lfoo -lbar
2013 *** With process-connection-type set to t, each line of subprocess
2014 output is terminated with a ^M, making ange-ftp and GNUS not work.
2016 On SunOS systems, this problem has been seen to be a result of an
2017 incomplete installation of gcc 2.2 which allowed some non-ANSI
2018 compatible include files into the compilation. In particular this
2019 affected virtually all ioctl() calls.
2023 *** XEmacs crashes on startup, in make-frame.
2025 Typically the Lisp backtrace includes
2027 make-frame(nil #<x-device on ":0.0" 0x2558>)
2029 somewhere near the top. The problem is due to an improvement in GNU
2030 ld that sorts the ELF reloc sections in the executable, giving
2031 dramatic speedups in startup for large executables. It also confuses
2032 the traditional unexec code in XEmacs, leading to the core dump. The
2033 solution is to use the --pdump or --ldflags='-z nocombreloc' options
2034 to configure. Recent 21.4 and 12.5 autodetect this in configure.
2036 Red Hat and SuSE (at least) distributed a prerelease version of ld
2037 (versions around 2.11.90.x.y) where autodetection is impossible. The
2038 recommended procedure is to upgrade to binutils >= 2.12 and rerun
2039 configure. Otherwise you must apply the flags by hand. --pdump is
2042 *** I want XEmacs to use the Alt key, not the XXX key, for Meta commands
2044 For historical reasons, XEmacs looks for a Meta key, then an Alt key.
2045 It binds Meta commands to the X11 modifier bit attached to the first
2046 of these it finds. On PCs, the Windows key is often assigned the Meta
2047 bit, but many desktop environments go to great lengths to get all apps
2048 to use the Alt key, and reserve the Windows key to (sensibly enough)
2051 One correct way to implement this was suggested on comp.emacs.xemacs
2052 (by Kilian Foth and in more detail by Michael Piotrowski): unmap the
2053 Meta modifier using xmodmap or xkb, and then map the Meta/Windows key
2054 to the Super or Hyper keysym and an appropriate mod bit. XEmacs will
2055 not find the Meta keysym, and default to using the Alt key for Meta
2056 keybindings. Typically few applications use the (X11) Meta modifier;
2057 it is tedious but not too much so to teach the ones you need to use
2058 Super instead of Meta. There may be further useful hints in the
2059 discussion of keymapping on non-Linux platforms.
2061 *** The color-gcc wrapper
2063 This wrapper colorizes the error messages from gcc. By default XEmacs
2064 does not interpret the escape sequences used to generate colors,
2065 resulting in a cluttered, hard-to-read buffer. You can remove the
2066 wrapper, or defeat the wrapper colorization in Emacs process buffers
2067 by editing the "nocolor" attribute in /etc/colorgccrc:
2069 $ diff -u /etc/colorgccrc.old /etc/colorgccrc
2070 --- /etc/colorgccrc.old Tue Dec 26 02:17:46 2000
2071 +++ /etc/colorgccrc Tue Dec 26 02:15:48 2000
2074 +nocolor: dumb emacs
2076 If you want colorization in your Emacs buffers, you may get good
2077 results from the ansi-color.el library:
2079 http://www.geocities.com/kensanata/color-emacs.html#ansicolors
2081 This is written for the mainline GNU Emacs but the author has made
2082 efforts to adapt it to XEmacs. YMMV.
2084 *** Slow startup on Linux.
2086 People using systems based on the Linux kernel sometimes report that
2087 startup takes 10 to 15 seconds longer than `usual'. There are two
2088 problems, one older, one newer.
2090 **** Old problem: IPv4 host lookup
2092 On older systems, this is because Emacs looks up the host name when it
2093 starts. Normally, this takes negligible time; the extra delay is due
2094 to improper system configuration. (Recent Linux distros usually have
2095 this configuration correct "out of the box".) This problem can occur
2096 for both networked and non-networked machines.
2098 Here is how to fix the configuration. It requires being root.
2100 ***** Networked Case
2102 First, make sure the files `/etc/hosts' and `/etc/host.conf' both
2103 exist. The first line in the `/etc/hosts' file should look like this
2104 (replace HOSTNAME with your host name):
2106 127.0.0.1 localhost HOSTNAME
2108 Also make sure that the `/etc/host.conf' files contains the following
2114 Any changes, permanent and temporary, to the host name should be
2115 indicated in the `/etc/hosts' file, since it acts a limited local
2116 database of addresses and names (e.g., some SLIP connections
2117 dynamically allocate ip addresses).
2119 ***** Non-Networked Case
2121 The solution described in the networked case applies here as well.
2122 However, if you never intend to network your machine, you can use a
2123 simpler solution: create an empty `/etc/host.conf' file. The command
2124 `touch /etc/host.conf' suffices to create the file. The `/etc/hosts'
2125 file is not necessary with this approach.
2127 **** New problem: IPv6 CNAME lookup
2129 A newer problem is due to XEmacs changing to use the modern
2130 getaddrinfo() interface from the older gethostbyname() interface. The
2131 solution above is insufficient, because getaddrinfo() by default tries
2132 to get IPv6 information for localhost. This always involves a dns
2133 lookup to get the CNAME, and the strategies above don't work. It then
2134 falls back to IPv4 behavior. This is good[tm] according the people at
2135 WIDE who know about IPv6.
2137 ***** Robust network case
2139 Configure your network so that there are no nameservers configured
2140 until the network is actually running. getaddrinfo() will not try to
2141 access a nameserver that isn't configured.
2143 ***** Flaky network case
2145 If you have a flaky modem or DSL connection that can be relied on only
2146 to go down whenever you want to bring XEmacs up, you need to force
2147 IPv4 behavior. Explicitly setting DISPLAY=127.0.0.1:0.0 (or whatever
2148 is appropriate) works in most cases.
2150 If you cannot or do not want to do that, you can hard code IPv4
2151 behavior in src/process-unix.c. This is bad[tm], on your own head be
2152 it. Use the configure option `--with-ipv6-cname=no'.
2156 The Mandrake Linux distribution is attempting to comprehensively
2157 update the user interface, and make it consistent across
2158 applications. This is very difficult, and will occasionally cause
2159 conflicts with applications like Emacs with their own long-established
2160 interfaces. Known issues specific to Mandrake or especially common:
2162 Some versions of XEmacs (21.1.9 is known) distributed with Mandrake
2163 were patched to make the Meta and Alt keysyms synonymous. These
2164 normally work as expected in the Mandrake environment. However,
2165 custom-built XEmacsen (including all 21.2 betas) will "inexplicably"
2166 not respect the "Alt-invokes-Meta-commands" convention. See "I want
2167 XEmacs to use the Alt key" below.
2169 The color-gcc wrapper (see below) is in common use on the Mandrake
2172 *** You get crashes in a non-C locale with Linux GNU Libc 2.0.
2174 Internationalization was not the top priority for GNU Libc 2.0.
2175 As of this writing (1998-12-28) you may get crashes while running
2176 XEmacs in a non-C locale. For example, `LC_ALL=en_US xemacs' crashes
2177 while `LC_ALL=C xemacs' runs fine. This happens for example with GNU
2178 libc 2.0.7. Installing libintl.a and libintl.h built from gettext
2179 0.10.35 and re-building XEmacs solves the crashes. Presumably soon
2180 everyone will upgrade to GNU Libc 2.1 and this problem will go away.
2182 *** `C-z', or `M-x suspend-emacs' hangs instead of suspending.
2184 If you build with `gpm' support on Linux, you cannot suspend XEmacs
2185 because gpm installs a buggy SIGTSTP handler. Either compile with
2186 `--with-gpm=no', or don't suspend XEmacs on the Linux console until
2189 *** With certain fonts, when the cursor appears on a character, the
2190 character doesn't appear--you get a solid box instead.
2192 One user on a Linux system reported that this problem went away with
2193 installation of a new X server. The failing server was XFree86 3.1.1.
2194 XFree86 3.1.2 works.
2197 *** On Irix, I don't see the toolbar icons and I'm getting lots of
2198 entries in the warnings buffer.
2200 SGI ships a really old Xpm library in /usr/lib which does not work at
2201 all well with XEmacs. The solution is to install your own copy of the
2202 latest version of Xpm somewhere and then use the --site-includes and
2203 --site-libraries flags to tell configure where to find it.
2205 *** Trouble using ptys on IRIX, or running out of ptys.
2207 The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
2208 be set-UID to root, or non-root programs like Emacs will not be able
2209 to allocate ptys reliably.
2211 *** Beware of the default image & graphics library on Irix
2213 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
2215 You *have* to compile your own jpeg lib. The one delivered with SGI
2216 systems is a C++ lib, which apparently XEmacs cannot cope with.
2219 ** Digital UNIX/OSF/VMS/Ultrix
2220 *** XEmacs crashes on Digital Unix within font-lock, or when dealing
2221 with large compilation buffers, or in other regex applications.
2223 The default stack size under Digital Unix is rather small (2M as
2224 opposed to Solaris 8M), hosing the regexp code, which uses alloca()
2225 extensively, overflowing the stack when complex regexps are used.
2228 1) Increase your stack size, using `ulimit -s 8192' or a (t)csh
2231 2) Recompile regex.c with REGEX_MALLOC defined.
2233 *** The `Alt' key doesn't behave as `Meta' when running DECwindows.
2235 The default DEC keyboard mapping has the Alt keys set up to generate the
2236 keysym `Multi_key', which has a meaning to xemacs which is distinct from that
2237 of the `Meta_L' and `Meta-R' keysyms. A second problem is that certain keys
2238 have the Mod2 modifier attached to them for no adequately explored reason.
2239 The correct fix is to pass this file to xmodmap upon starting X:
2242 keysym Multi_key = Alt_L
2246 *** The Compose key on a DEC keyboard does not work as Meta key.
2248 This shell command should fix it:
2250 xmodmap -e 'keycode 0xb1 = Meta_L'
2252 *** `expand-file-name' fails to work on any but the machine you dumped
2255 On Ultrix, if you use any of the functions which look up information
2256 in the passwd database before dumping Emacs (say, by using
2257 expand-file-name in site-init.el), then those functions will not work
2258 in the dumped Emacs on any host but the one Emacs was dumped on.
2260 The solution? Don't use expand-file-name in site-init.el, or in
2261 anything it loads. Yuck - some solution.
2263 I'm not sure why this happens; if you can find out exactly what is
2264 going on, and perhaps find a fix or a workaround, please let us know.
2265 Perhaps the YP functions cache some information, the cache is included
2266 in the dumped Emacs, and is then inaccurate on any other host.
2270 *** I get complaints about the mapping of my HP keyboard at startup,
2271 but I haven't changed anything.
2273 The default HP keymap is set up to have Mod1 assigned to two different keys:
2274 Meta_L and Mode_switch (even though there is not actually a Mode_switch key on
2275 the keyboard -- it uses an "imaginary" keycode.) There actually is a reason
2276 for this, but it's not a good one. The correct fix is to execute this command
2279 xmodmap -e 'remove mod1 = Mode_switch'
2281 *** On HP-UX, you get "poll: Interrupted system call" message in the
2282 window where XEmacs was launched.
2284 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
2286 I get a very strange problem when linking libc.a dynamically: every
2287 event (mouse, keyboard, expose...) results in a "poll: Interrupted
2288 system call" message in the window where XEmacs was
2289 launched. Forcing a static link of libc.a alone by adding
2290 /usr/lib/libc.a at the end of the link line solves this. Note that
2291 my 9.07 build of 19.14b17 and my (old) build of 19.13 both exhibit
2292 the same behavior. I've tried various hpux patches to no avail. If
2293 this problem cannot be solved before the release date, binary kits
2294 for HP *must* be linked statically against libc, otherwise this
2295 problem will show up. (This is directed at whoever will volunteer
2296 for this kit, as I won't be available to do it, unless 19.14 gets
2297 delayed until mid-june ;-). I think this problem will be an FAQ soon
2298 after the release otherwise.
2300 Note: The above entry is probably not valid for XEmacs 21.0 and
2303 *** The right Alt key works wrong on German HP keyboards (and perhaps
2304 other non-English HP keyboards too).
2306 This is because HP-UX defines the modifiers wrong in X. Here is a
2307 shell script to fix the problem; be sure that it is run after VUE
2308 configures the X server.
2310 xmodmap 2> /dev/null - << EOF
2311 keysym Alt_L = Meta_L
2312 keysym Alt_R = Meta_R
2317 keysym Mode_switch = NoSymbol
2319 keysym Meta_R = Mode_switch
2320 add mod2 = Mode_switch
2324 *** XEmacs dumps core at startup when native audio is used. Native
2325 audio does not work with recent versions of HP-UX.
2327 Under HP-UX 10.20 and later (e.g., HP-UX 11.XX), with native audio
2328 enabled, the dumped XEmacs binary ("xemacs") core dumps at startup if
2329 recent versions of the libAlib.sl audio shared library is used. Note
2330 that "temacs" will run, but "xemacs" will dump core. This, of course,
2331 causes the XEmacs build to fail. If GNU malloc is enabled, a stack
2332 trace will show XEmacs to have crashed in the "first" call to malloc().
2334 This bug currently exists in all versions of XEmacs, when the undump
2335 mechanism is used. It is not known if using the experimental portable
2336 dumper will allow native audio to work.
2340 Recent versions of the HP-UX 10.20 (and later) audio shared library (in
2341 /opt/audio/lib), pulls in the libdce shared library, which pulls in a
2342 thread (libcma) library. This prevents the HP-UX undump() routine (in
2343 unexhp9k800.c) from properly working. What's happening is that some
2344 initialization routines are being called in the libcma library, *BEFORE*
2345 main() is called, and these initialization routines are calling
2346 malloc(). Unfortunately, in order for the undumper to work, XEmacs must
2347 adjust (move upwards) the sbrk() value *BEFORE* the first call to
2348 malloc(); if malloc() is called before XEmacs has properly adjusted sbrk
2349 (which is what is happening), dumped memory that is being used by
2350 XEmacs, is improperly re-allocated for use by malloc() and the dumped
2351 memory is corrupted. This causes XEmacs to die an horrible death.
2353 It is believed that versions of the audio library past December 1998
2354 will trigger this problem. Under HP-UX 10.20, you probably have to
2355 install audio library patches to encounter this. It's probable that
2356 recent "fresh, out-of-the-box" HP-UX 11.XX workstations also have this
2357 problem. For HP-UX 10.20, it's believed that audio patch PHSS_17121 (or
2358 a superceeding one, like PHSS_17554, PHSS_17971, PHSS_18777, PHSS_21481,
2359 or PHSS_21662, etc.) will trigger this.
2361 To check if your audio library will cause problems for XEmacs, run
2362 "chatr /opt/audio/lib/libAlib.sl". If "libdce" appears in the displayed
2363 shared library list, XEmacs will probably encounter problems if audio is
2368 Don't enable native audio. Re-run configure without native audio
2371 If your site supports it, try using NAS (Network Audio Support).
2373 Try using the experimental portable dumper. It may work, or it may
2377 *** `Pid xxx killed due to text modification or page I/O error'
2379 On HP-UX, you can get that error when the Emacs executable is on an NFS
2380 file system. HP-UX responds this way if it tries to swap in a page and
2381 does not get a response from the server within a timeout whose default
2382 value is just ten seconds.
2384 If this happens to you, extend the timeout period.
2386 *** Shell mode on HP-UX gives the message, "`tty`: Ambiguous".
2388 christos@theory.tn.cornell.edu says:
2390 The problem is that in your .cshrc you have something that tries to
2391 execute `tty`. If you are not running the shell on a real tty then tty
2392 will print "not a tty". Csh expects one word in some places, but tty
2393 is giving it back 3.
2395 The solution is to add a pair of quotes around `tty` to make it a
2398 if (`tty` == "/dev/console")
2400 should be changed to:
2402 if ("`tty`" == "/dev/console")
2404 Even better, move things that set up terminal sections out of .cshrc
2409 *** Regular expressions matching bugs on SCO systems.
2411 On SCO, there are problems in regexp matching when Emacs is compiled
2412 with the system compiler. The compiler version is "Microsoft C
2413 version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
2414 C Compiler Version 1.00.46 (Beta). The solution is to compile with
2418 * Compatibility problems (with Emacs 18, GNU Emacs, or previous XEmacs/lemacs)
2419 ==============================================================================
2421 *** "Symbol's value as variable is void: unread-command-char".
2422 "Wrong type argument: arrayp, #<keymap 143 entries>"
2423 "Wrong type argument: stringp, [#<keypress-event return>]"
2425 There are a few incompatible changes in XEmacs, and these are the
2426 symptoms. Some of the emacs-lisp code you are running needs to be
2427 updated to be compatible with XEmacs.
2429 The code should not treat keymaps as arrays (use `define-key', etc.),
2430 should not use obsolete variables like `unread-command-char' (use
2431 `unread-command-events'). Many (most) of the new ways of doing things
2432 are compatible in GNU Emacs and XEmacs.
2434 Modern Emacs packages (Gnus, VM, W3, efs, etc) are written to support
2435 GNU Emacs and XEmacs. We have provided modified versions of several
2436 popular emacs packages (dired, etc) which are compatible with this
2437 version of emacs. Check to make sure you have not set your load-path
2438 so that your private copies of these packages are being found before
2439 the versions in the lisp directory.
2441 Make sure that your load-path and your $EMACSLOADPATH environment
2442 variable are not pointing at an Emacs18 lisp directory. This will
2445 ** Some packages that worked before now cause the error
2446 Wrong type argument: arrayp, #<face ... >
2448 Code which uses the `face' accessor functions must be recompiled with
2449 xemacs 19.9 or later. The functions whose callers must be recompiled
2450 are: face-font, face-foreground, face-background,
2451 face-background-pixmap, and face-underline-p. The .elc files
2452 generated by version 19.9 will work in 19.6 and 19.8, but older .elc
2453 files which contain calls to these functions will not work in 19.9.
2455 ** Signaling: (error "Byte code stack underflow (byte compiler bug), pc 38")
2457 This error is given when XEmacs 20 is compiled without MULE support
2458 but is attempting to load a .elc which requires MULE support. The fix
2459 is to rebytecompile the offending file.
2461 ** Signaling: (wrong-type-argument ...) when loading mail-abbrevs
2463 The is seen when installing the Insidious Big Brother Data Base (bbdb)
2464 which includes an outdated copy of mail-abbrevs.el. Remove the copy
2465 that comes with bbdb and use the one that comes with XEmacs.
2471 ** A reminder: XEmacs/Mule work does not currently receive *any*
2472 funding, and all work is done by volunteers. If you think you can
2473 help, please contact the XEmacs maintainers.
2475 ** XEmacs/Mule doesn't support TTY's satisfactorily.
2477 This is a major problem, which we plan to address in a future release
2478 of XEmacs. Basically, XEmacs should have primitives to be told
2479 whether the terminal can handle international output, and which
2480 locale. Also, it should be able to do approximations of characters to
2481 the nearest supported by the locale.
2483 ** Internationalized (Asian) Isearch doesn't work.
2485 Currently, Isearch doesn't directly support any of the input methods
2486 that are not XIM based (like egg, canna and quail) (and there are
2487 potential problems with XIM version too...). If you're using egg
2488 there is a workaround. Hitting <RET> right after C-s to invoke
2489 Isearch will put Isearch in string mode, where a complete string can
2490 be typed into the minibuffer and then processed by Isearch afterwards.
2491 Since egg is now supported in the minibuffer using string mode you can
2492 now use egg to input your Japanese, Korean or Chinese string, then hit
2493 return to send that to Isearch and then use standard Isearch commands
2496 ** Using egg and mousing around while in 'fence' mode screws up my
2499 Don't do this. The fence modes of egg and canna are currently very
2500 modal, and messing with where they expect point to be and what they
2501 think is the current buffer is just asking for trouble. If you're
2502 lucky they will realize that something is awry, and simply delete the
2503 fence, but worst case can trash other buffers too. We've tried to
2504 protect against this where we can, but there still are many ways to
2505 shoot yourself in the foot. So just finish what you are typing into
2506 the fence before reaching for the mouse.
2508 ** Not all languages in Quail are supported like Devanagari and Indian
2509 languages, Lao and Tibetan.
2511 Quail requires more work and testing. Although it has been ported to
2512 XEmacs, it works really well for Japanese and for the European
2515 ** Right-to-left mode is not yet implemented, so languages like
2516 Arabic, Hebrew and Thai don't work.
2518 Getting this right requires more work. It may be implemented in a
2519 future XEmacs version, but don't hold your breath. If you know
2520 someone who is ready to implement this, please let us know.
2522 ** We need more developers and native language testers. It's extremely
2523 difficult (and not particularly productive) to address languages that
2524 nobody is using and testing.
2526 ** The kWnn and cWnn support for Chinese and Korean needs developers
2527 and testers. It probably doesn't work.
2529 ** There are no `native XEmacs' TUTORIALs for any Asian languages,
2530 including Japanese. FSF Emacs and XEmacs tutorials are quite similar,
2531 so it should be sufficient to skim through the differences and apply
2532 them to the Japanese version.
2534 ** We only have localized menus translated for Japanese, and the
2535 Japanese menus are developing bitrot (the Mule menu appears in
2538 ** XIM is untested for any language other than Japanese.