XEmacs 21.2-b1
authortomo <tomo>
Mon, 17 May 1999 09:41:31 +0000 (09:41 +0000)
committertomo <tomo>
Mon, 17 May 1999 09:41:31 +0000 (09:41 +0000)
1195 files changed:
BUGS [new file with mode: 0644]
COPYING [new file with mode: 0644]
GETTING.GNU.SOFTWARE [new file with mode: 0644]
INSTALL [new file with mode: 0644]
PROBLEMS [new file with mode: 0644]
README [new file with mode: 0644]
aclocal.m4 [new file with mode: 0644]
config.guess [new file with mode: 0755]
config.sub [new file with mode: 0755]
configure.usage [new file with mode: 0644]
dynodump/Makefile.in.in [new file with mode: 0644]
dynodump/README [new file with mode: 0644]
dynodump/_dynodump.h [new file with mode: 0644]
dynodump/dynodump.c [new file with mode: 0644]
dynodump/i386/_relocate.c [new file with mode: 0644]
dynodump/i386/machdep.h [new file with mode: 0644]
dynodump/i386/uninit.c [new file with mode: 0644]
dynodump/ppc/_relocate.c [new file with mode: 0644]
dynodump/ppc/machdep.h [new file with mode: 0644]
dynodump/ppc/uninit.c [new file with mode: 0644]
dynodump/sparc/_relocate.c [new file with mode: 0644]
dynodump/sparc/machdep.h [new file with mode: 0644]
dynodump/sparc/uninit.c [new file with mode: 0644]
dynodump/syms.c [new file with mode: 0644]
etc/BETA [new file with mode: 0644]
etc/CHARSETS [new file with mode: 0644]
etc/CODING-STANDARDS [new file with mode: 0644]
etc/CODINGS [new file with mode: 0644]
etc/COPYING [new file with mode: 0644]
etc/COPYING.LIB [new file with mode: 0644]
etc/DEBUG [new file with mode: 0644]
etc/DISTRIB [new file with mode: 0644]
etc/Emacs.ad [new file with mode: 0644]
etc/FTP [new file with mode: 0644]
etc/GNU [new file with mode: 0644]
etc/HELLO [new file with mode: 0644]
etc/InstallGuide [new file with mode: 0644]
etc/LPF [new file with mode: 0644]
etc/MACHINES [new file with mode: 0644]
etc/MAILINGLISTS [new file with mode: 0644]
etc/MORE.STUFF [new file with mode: 0644]
etc/MOTIVATION [new file with mode: 0644]
etc/NEWS [new file with mode: 0644]
etc/OONEWS [new file with mode: 0644]
etc/ORDERS [new file with mode: 0644]
etc/ORDERS.EUROPE [new file with mode: 0644]
etc/ORDERS.JAPAN [new file with mode: 0644]
etc/PACKAGES [new file with mode: 0644]
etc/README [new file with mode: 0644]
etc/README.HYPERBOLE [new file with mode: 0644]
etc/README.OO-BROWSER [new file with mode: 0644]
etc/SERVICE [new file with mode: 0644]
etc/TERMS [new file with mode: 0644]
etc/TUTORIAL [new file with mode: 0644]
etc/TUTORIAL.de [new file with mode: 0644]
etc/TUTORIAL.fr [new file with mode: 0644]
etc/TUTORIAL.hr [new file with mode: 0644]
etc/TUTORIAL.ja [new file with mode: 0644]
etc/TUTORIAL.ko [new file with mode: 0644]
etc/TUTORIAL.no [new file with mode: 0644]
etc/TUTORIAL.pl [new file with mode: 0644]
etc/TUTORIAL.ro [new file with mode: 0644]
etc/TUTORIAL.ru [new file with mode: 0644]
etc/TUTORIAL.th [new file with mode: 0644]
etc/XKeysymDB [new file with mode: 0644]
etc/aliases.ksh [new file with mode: 0755]
etc/cbx.png [new file with mode: 0644]
etc/check_cygwin_setup.sh [new file with mode: 0644]
etc/ctags.1 [new file with mode: 0644]
etc/custom/check0.xpm [new file with mode: 0644]
etc/custom/check1.xpm [new file with mode: 0644]
etc/custom/choose-down.png [new file with mode: 0644]
etc/custom/choose-up.png [new file with mode: 0644]
etc/custom/done-down.png [new file with mode: 0644]
etc/custom/done-up.png [new file with mode: 0644]
etc/custom/down-pushed.xpm [new file with mode: 0644]
etc/custom/down.xpm [new file with mode: 0644]
etc/custom/face.xpm [new file with mode: 0644]
etc/custom/folder.xpm [new file with mode: 0644]
etc/custom/open-down.png [new file with mode: 0644]
etc/custom/open-up.png [new file with mode: 0644]
etc/custom/option.xpm [new file with mode: 0644]
etc/custom/radio0.xpm [new file with mode: 0644]
etc/custom/radio1.xpm [new file with mode: 0644]
etc/custom/reset-down.png [new file with mode: 0644]
etc/custom/reset-up.png [new file with mode: 0644]
etc/custom/right-pushed.xpm [new file with mode: 0644]
etc/custom/right.xpm [new file with mode: 0644]
etc/custom/save-down.png [new file with mode: 0644]
etc/custom/save-up.png [new file with mode: 0644]
etc/custom/set-down.png [new file with mode: 0644]
etc/custom/set-up.png [new file with mode: 0644]
etc/custom/state-down.png [new file with mode: 0644]
etc/custom/state-up.png [new file with mode: 0644]
etc/custom/toggle-off-down.png [new file with mode: 0644]
etc/custom/toggle-off-up.png [new file with mode: 0644]
etc/custom/toggle-on-down.png [new file with mode: 0644]
etc/custom/toggle-on-up.png [new file with mode: 0644]
etc/editclient.sh [new file with mode: 0644]
etc/emacskeys.sco [new file with mode: 0644]
etc/emacsstrs.sco [new file with mode: 0644]
etc/eos/eos-build.xbm [new file with mode: 0644]
etc/eos/eos-clear-at.xbm [new file with mode: 0644]
etc/eos/eos-cont.xbm [new file with mode: 0644]
etc/eos/eos-dismiss.xbm [new file with mode: 0644]
etc/eos/eos-down.xbm [new file with mode: 0644]
etc/eos/eos-evaluate-star.xbm [new file with mode: 0644]
etc/eos/eos-evaluate.xbm [new file with mode: 0644]
etc/eos/eos-fix.xbm [new file with mode: 0644]
etc/eos/eos-intro.xbm [new file with mode: 0644]
etc/eos/eos-introB.xbm [new file with mode: 0644]
etc/eos/eos-introD.xbm [new file with mode: 0644]
etc/eos/eos-introDB.xbm [new file with mode: 0644]
etc/eos/eos-run.xbm [new file with mode: 0644]
etc/eos/eos-run2.xbm [new file with mode: 0644]
etc/eos/eos-step-into.xbm [new file with mode: 0644]
etc/eos/eos-step-over.xbm [new file with mode: 0644]
etc/eos/eos-stop-in.xbm [new file with mode: 0644]
etc/eos/eos-stop.xbm [new file with mode: 0644]
etc/eos/eos-type.xbm [new file with mode: 0644]
etc/eos/eos-up.xbm [new file with mode: 0644]
etc/etags.1 [new file with mode: 0644]
etc/gnu.xbm [new file with mode: 0644]
etc/gnu.xpm [new file with mode: 0644]
etc/gnuattach.1 [new file with mode: 0644]
etc/gnuclient.1 [new file with mode: 0644]
etc/gnudoit.1 [new file with mode: 0644]
etc/gnuserv.1 [new file with mode: 0644]
etc/gnuserv.README [new file with mode: 0644]
etc/gray1.xbm [new file with mode: 0644]
etc/idd/drop [new file with mode: 0644]
etc/idd/dropmsk [new file with mode: 0644]
etc/ms-kermit [new file with mode: 0644]
etc/ms-kermit-7bit [new file with mode: 0644]
etc/recycle.xpm [new file with mode: 0644]
etc/recycle2.xpm [new file with mode: 0644]
etc/refcard.ps.gz [new file with mode: 0644]
etc/refcard.tex [new file with mode: 0644]
etc/sample.Xdefaults [new file with mode: 0644]
etc/sink.xbm [new file with mode: 0644]
etc/sparcworks/SW.Editor.xpm [new file with mode: 0644]
etc/sparcworks/sunpro-mailcap [new file with mode: 0644]
etc/tests/external-widget/Makefile [new file with mode: 0644]
etc/tests/external-widget/test-ew-motif.c [new file with mode: 0644]
etc/tests/external-widget/test-ew-xlib.c [new file with mode: 0644]
etc/toolbar/compile-cap-up.xpm [new file with mode: 0644]
etc/toolbar/compile-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/compile-dn.xbm [new file with mode: 0644]
etc/toolbar/compile-up.xbm [new file with mode: 0644]
etc/toolbar/compile-up.xpm [new file with mode: 0644]
etc/toolbar/compile-xx.xbm [new file with mode: 0644]
etc/toolbar/compile-xx.xpm [new file with mode: 0644]
etc/toolbar/copy-cap-up.xpm [new file with mode: 0644]
etc/toolbar/copy-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/copy-dn.xbm [new file with mode: 0644]
etc/toolbar/copy-up.xbm [new file with mode: 0644]
etc/toolbar/copy-up.xpm [new file with mode: 0644]
etc/toolbar/copy-xx.xbm [new file with mode: 0644]
etc/toolbar/copy-xx.xpm [new file with mode: 0644]
etc/toolbar/cut-cap-up.xpm [new file with mode: 0644]
etc/toolbar/cut-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/cut-dn.xbm [new file with mode: 0644]
etc/toolbar/cut-up.xbm [new file with mode: 0644]
etc/toolbar/cut-up.xpm [new file with mode: 0644]
etc/toolbar/cut-xx.xbm [new file with mode: 0644]
etc/toolbar/cut-xx.xpm [new file with mode: 0644]
etc/toolbar/debug-cap-up.xpm [new file with mode: 0644]
etc/toolbar/debug-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/debug-dn.xbm [new file with mode: 0644]
etc/toolbar/debug-up.xbm [new file with mode: 0644]
etc/toolbar/debug-up.xpm [new file with mode: 0644]
etc/toolbar/debug-xx.xbm [new file with mode: 0644]
etc/toolbar/debug-xx.xpm [new file with mode: 0644]
etc/toolbar/disk-cap-up.xpm [new file with mode: 0644]
etc/toolbar/disk-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/disk-dn.xbm [new file with mode: 0644]
etc/toolbar/disk-up.xbm [new file with mode: 0644]
etc/toolbar/disk-up.xpm [new file with mode: 0644]
etc/toolbar/disk-xx.xbm [new file with mode: 0644]
etc/toolbar/disk-xx.xpm [new file with mode: 0644]
etc/toolbar/file-cap-up.xpm [new file with mode: 0644]
etc/toolbar/file-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/file-dn.xbm [new file with mode: 0644]
etc/toolbar/file-up.xbm [new file with mode: 0644]
etc/toolbar/file-up.xpm [new file with mode: 0644]
etc/toolbar/file-xx.xbm [new file with mode: 0644]
etc/toolbar/file-xx.xpm [new file with mode: 0644]
etc/toolbar/folder-cap-up.xpm [new file with mode: 0644]
etc/toolbar/folder-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/folder-dn.xbm [new file with mode: 0644]
etc/toolbar/folder-up.xbm [new file with mode: 0644]
etc/toolbar/folder-up.xpm [new file with mode: 0644]
etc/toolbar/folder-xx.xbm [new file with mode: 0644]
etc/toolbar/folder-xx.xpm [new file with mode: 0644]
etc/toolbar/info-def-cap-up.xpm [new file with mode: 0644]
etc/toolbar/info-def-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/info-def-dn.xbm [new file with mode: 0644]
etc/toolbar/info-def-up.xbm [new file with mode: 0644]
etc/toolbar/info-def-up.xpm [new file with mode: 0644]
etc/toolbar/info-def-xx.xbm [new file with mode: 0644]
etc/toolbar/info-def-xx.xpm [new file with mode: 0644]
etc/toolbar/info-exit-cap-up.xpm [new file with mode: 0644]
etc/toolbar/info-exit-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/info-exit-dn.xbm [new file with mode: 0644]
etc/toolbar/info-exit-up.xbm [new file with mode: 0644]
etc/toolbar/info-exit-up.xpm [new file with mode: 0644]
etc/toolbar/info-exit-xx.xbm [new file with mode: 0644]
etc/toolbar/info-exit-xx.xpm [new file with mode: 0644]
etc/toolbar/info-exit.xbm [new file with mode: 0644]
etc/toolbar/info-exit.xpm [new file with mode: 0644]
etc/toolbar/info-next-cap-up.xpm [new file with mode: 0644]
etc/toolbar/info-next-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/info-next-dn.xbm [new file with mode: 0644]
etc/toolbar/info-next-up.xbm [new file with mode: 0644]
etc/toolbar/info-next-up.xpm [new file with mode: 0644]
etc/toolbar/info-next-xx.xbm [new file with mode: 0644]
etc/toolbar/info-next-xx.xpm [new file with mode: 0644]
etc/toolbar/info-next.xbm [new file with mode: 0644]
etc/toolbar/info-next.xpm [new file with mode: 0644]
etc/toolbar/info-prev-cap-up.xpm [new file with mode: 0644]
etc/toolbar/info-prev-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/info-prev-dn.xbm [new file with mode: 0644]
etc/toolbar/info-prev-up.xbm [new file with mode: 0644]
etc/toolbar/info-prev-up.xpm [new file with mode: 0644]
etc/toolbar/info-prev-xx.xbm [new file with mode: 0644]
etc/toolbar/info-prev-xx.xpm [new file with mode: 0644]
etc/toolbar/info-prev.xbm [new file with mode: 0644]
etc/toolbar/info-prev.xpm [new file with mode: 0644]
etc/toolbar/info-up-cap-up.xpm [new file with mode: 0644]
etc/toolbar/info-up-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/info-up-dn.xbm [new file with mode: 0644]
etc/toolbar/info-up-up.xbm [new file with mode: 0644]
etc/toolbar/info-up-up.xpm [new file with mode: 0644]
etc/toolbar/info-up-xx.xbm [new file with mode: 0644]
etc/toolbar/info-up-xx.xpm [new file with mode: 0644]
etc/toolbar/info-up.xbm [new file with mode: 0644]
etc/toolbar/info-up.xpm [new file with mode: 0644]
etc/toolbar/last-win-cap-up.xpm [new file with mode: 0644]
etc/toolbar/last-win-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/last-win-dn.xbm [new file with mode: 0644]
etc/toolbar/last-win-up.xbm [new file with mode: 0644]
etc/toolbar/last-win-up.xpm [new file with mode: 0644]
etc/toolbar/last-win-xx.xbm [new file with mode: 0644]
etc/toolbar/last-win-xx.xpm [new file with mode: 0644]
etc/toolbar/mail-cap-up.xpm [new file with mode: 0644]
etc/toolbar/mail-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/mail-dn.xbm [new file with mode: 0644]
etc/toolbar/mail-up.xbm [new file with mode: 0644]
etc/toolbar/mail-up.xpm [new file with mode: 0644]
etc/toolbar/mail-xx.xbm [new file with mode: 0644]
etc/toolbar/mail-xx.xpm [new file with mode: 0644]
etc/toolbar/news-cap-up.xpm [new file with mode: 0644]
etc/toolbar/news-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/news-dn.xbm [new file with mode: 0644]
etc/toolbar/news-up.xbm [new file with mode: 0644]
etc/toolbar/news-up.xpm [new file with mode: 0644]
etc/toolbar/news-xx.xbm [new file with mode: 0644]
etc/toolbar/news-xx.xpm [new file with mode: 0644]
etc/toolbar/next-win-cap-up.xpm [new file with mode: 0644]
etc/toolbar/next-win-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/next-win-dn.xbm [new file with mode: 0644]
etc/toolbar/next-win-up.xbm [new file with mode: 0644]
etc/toolbar/next-win-up.xpm [new file with mode: 0644]
etc/toolbar/next-win-xx.xbm [new file with mode: 0644]
etc/toolbar/next-win-xx.xpm [new file with mode: 0644]
etc/toolbar/paste-cap-up.xpm [new file with mode: 0644]
etc/toolbar/paste-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/paste-dn.xbm [new file with mode: 0644]
etc/toolbar/paste-up.xbm [new file with mode: 0644]
etc/toolbar/paste-up.xpm [new file with mode: 0644]
etc/toolbar/paste-xx.xbm [new file with mode: 0644]
etc/toolbar/paste-xx.xpm [new file with mode: 0644]
etc/toolbar/printer-cap-up.xpm [new file with mode: 0644]
etc/toolbar/printer-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/printer-dn.xbm [new file with mode: 0644]
etc/toolbar/printer-up.xbm [new file with mode: 0644]
etc/toolbar/printer-up.xpm [new file with mode: 0644]
etc/toolbar/printer-xx.xbm [new file with mode: 0644]
etc/toolbar/printer-xx.xpm [new file with mode: 0644]
etc/toolbar/replace-cap-up.xpm [new file with mode: 0644]
etc/toolbar/replace-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/replace-dn.xbm [new file with mode: 0644]
etc/toolbar/replace-up.xbm [new file with mode: 0644]
etc/toolbar/replace-up.xpm [new file with mode: 0644]
etc/toolbar/replace-xx.xbm [new file with mode: 0644]
etc/toolbar/replace-xx.xpm [new file with mode: 0644]
etc/toolbar/spell-cap-up.xpm [new file with mode: 0644]
etc/toolbar/spell-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/spell-dn.xbm [new file with mode: 0644]
etc/toolbar/spell-up.xbm [new file with mode: 0644]
etc/toolbar/spell-up.xpm [new file with mode: 0644]
etc/toolbar/spell-xx.xbm [new file with mode: 0644]
etc/toolbar/spell-xx.xpm [new file with mode: 0644]
etc/toolbar/undo-cap-up.xpm [new file with mode: 0644]
etc/toolbar/undo-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/undo-dn.xbm [new file with mode: 0644]
etc/toolbar/undo-up.xbm [new file with mode: 0644]
etc/toolbar/undo-up.xpm [new file with mode: 0644]
etc/toolbar/undo-xx.xbm [new file with mode: 0644]
etc/toolbar/undo-xx.xpm [new file with mode: 0644]
etc/toolbar/workshop-cap-up.xpm [new file with mode: 0644]
etc/toolbar/workshop-cap-xx.xpm [new file with mode: 0644]
etc/toolbar/workshop-up.xpm [new file with mode: 0644]
etc/toolbar/workshop-xx.xpm [new file with mode: 0644]
etc/trash.xpm [new file with mode: 0644]
etc/xemacs-beta.xpm [new file with mode: 0644]
etc/xemacs-fe.sh [new file with mode: 0755]
etc/xemacs-icon.xpm [new file with mode: 0644]
etc/xemacs-icon2.xbm [new file with mode: 0644]
etc/xemacs-icon2.xpm [new file with mode: 0644]
etc/xemacs-icon3.xpm [new file with mode: 0644]
etc/xemacs-ja.1 [new file with mode: 0644]
etc/xemacs.1 [new file with mode: 0644]
etc/xemacs.xbm [new file with mode: 0644]
etc/xemacs.xpm [new file with mode: 0644]
info/dir [new file with mode: 0644]
install.sh [new file with mode: 0755]
lib-src/ChangeLog [new file with mode: 0644]
lib-src/Makefile.in.in [new file with mode: 0644]
lib-src/README [new file with mode: 0644]
lib-src/ad2c [new file with mode: 0755]
lib-src/add-big-package.sh [new file with mode: 0755]
lib-src/b2m.c [new file with mode: 0644]
lib-src/config.values.in [new file with mode: 0644]
lib-src/config.values.sh [new file with mode: 0644]
lib-src/cvtmail.c [new file with mode: 0644]
lib-src/digest-doc.c [new file with mode: 0644]
lib-src/emacs.csh [new file with mode: 0644]
lib-src/etags.c [new file with mode: 0644]
lib-src/fakemail.c [new file with mode: 0644]
lib-src/getopt.c [new file with mode: 0644]
lib-src/getopt.h [new file with mode: 0644]
lib-src/getopt1.c [new file with mode: 0644]
lib-src/gnuattach [new file with mode: 0755]
lib-src/gnuclient.c [new file with mode: 0644]
lib-src/gnudepend.pl [new file with mode: 0755]
lib-src/gnudoit [new file with mode: 0755]
lib-src/gnuserv.c [new file with mode: 0644]
lib-src/gnuserv.h [new file with mode: 0644]
lib-src/gnuslib.c [new file with mode: 0644]
lib-src/gzip-el.sh [new file with mode: 0755]
lib-src/hexl.c [new file with mode: 0644]
lib-src/installexe.sh [new file with mode: 0644]
lib-src/leditcfns.c [new file with mode: 0644]
lib-src/make-docfile.c [new file with mode: 0644]
lib-src/make-msgfile.c [new file with mode: 0644]
lib-src/make-msgfile.lex [new file with mode: 0644]
lib-src/make-path.c [new file with mode: 0644]
lib-src/make-po.c [new file with mode: 0644]
lib-src/mmencode.c [new file with mode: 0644]
lib-src/movemail.c [new file with mode: 0644]
lib-src/ootags.c [new file with mode: 0644]
lib-src/pop.c [new file with mode: 0644]
lib-src/pop.h [new file with mode: 0644]
lib-src/profile.c [new file with mode: 0644]
lib-src/qsort.c [new file with mode: 0644]
lib-src/rcs-checkin [new file with mode: 0755]
lib-src/rcs2log [new file with mode: 0755]
lib-src/sorted-doc.c [new file with mode: 0644]
lib-src/srcdir-symlink.stamp [new file with mode: 0644]
lib-src/tcp.c [new file with mode: 0644]
lib-src/update-autoloads.sh [new file with mode: 0644]
lib-src/update-custom.sh [new file with mode: 0755]
lib-src/vcdiff [new file with mode: 0755]
lib-src/wakeup.c [new file with mode: 0644]
lib-src/yow.c [new file with mode: 0644]
lisp/ChangeLog.1 [new file with mode: 0644]
lisp/README [new file with mode: 0644]
lisp/abbrev.el [new file with mode: 0644]
lisp/about.el [new file with mode: 0644]
lisp/alist.el [new file with mode: 0644]
lisp/apropos.el [new file with mode: 0644]
lisp/auto-save.el [new file with mode: 0644]
lisp/auto-show.el [new file with mode: 0644]
lisp/autoload.el [new file with mode: 0644]
lisp/backquote.el [new file with mode: 0644]
lisp/blessmail.el [new file with mode: 0644]
lisp/buff-menu.el [new file with mode: 0644]
lisp/buffer.el [new file with mode: 0644]
lisp/build-report.el [new file with mode: 0644]
lisp/byte-optimize.el [new file with mode: 0644]
lisp/bytecomp-runtime.el [new file with mode: 0644]
lisp/callers-of-rpt.el [new file with mode: 0644]
lisp/check-features.el [new file with mode: 0644]
lisp/cl-compat.el [new file with mode: 0644]
lisp/cl-extra.el [new file with mode: 0644]
lisp/cl-macs.el [new file with mode: 0644]
lisp/cl-seq.el [new file with mode: 0644]
lisp/cl.el [new file with mode: 0644]
lisp/cmdloop.el [new file with mode: 0644]
lisp/code-files.el [new file with mode: 0644]
lisp/code-process.el [new file with mode: 0644]
lisp/coding.el [new file with mode: 0644]
lisp/config.el [new file with mode: 0644]
lisp/console.el [new file with mode: 0644]
lisp/cus-dep.el [new file with mode: 0644]
lisp/cus-edit.el [new file with mode: 0644]
lisp/cus-face.el [new file with mode: 0644]
lisp/cus-load.el [new file with mode: 0644]
lisp/cus-start.el [new file with mode: 0644]
lisp/custom.el [new file with mode: 0644]
lisp/derived.el [new file with mode: 0644]
lisp/device.el [new file with mode: 0644]
lisp/dialog.el [new file with mode: 0644]
lisp/disass.el [new file with mode: 0644]
lisp/disp-table.el [new file with mode: 0644]
lisp/dragdrop.el [new file with mode: 0644]
lisp/easymenu.el [new file with mode: 0644]
lisp/etags.el [new file with mode: 0644]
lisp/events.el [new file with mode: 0644]
lisp/extents.el [new file with mode: 0644]
lisp/faces.el [new file with mode: 0644]
lisp/files-nomule.el [new file with mode: 0644]
lisp/fill.el [new file with mode: 0644]
lisp/find-paths.el [new file with mode: 0644]
lisp/finder.el [new file with mode: 0644]
lisp/float-sup.el [new file with mode: 0644]
lisp/font-lock.el [new file with mode: 0644]
lisp/font.el [new file with mode: 0644]
lisp/fontl-hooks.el [new file with mode: 0644]
lisp/frame.el [new file with mode: 0644]
lisp/glyphs.el [new file with mode: 0644]
lisp/gnuserv.el [new file with mode: 0644]
lisp/gui.el [new file with mode: 0644]
lisp/help-macro.el [new file with mode: 0644]
lisp/help-nomule.el [new file with mode: 0644]
lisp/help.el [new file with mode: 0644]
lisp/hyper-apropos.el [new file with mode: 0644]
lisp/indent.el [new file with mode: 0644]
lisp/info.el [new file with mode: 0644]
lisp/isearch-mode.el [new file with mode: 0644]
lisp/itimer-autosave.el [new file with mode: 0644]
lisp/itimer.el [new file with mode: 0644]
lisp/keydefs.el [new file with mode: 0644]
lisp/keymap.el [new file with mode: 0644]
lisp/ldap.el [new file with mode: 0644]
lisp/lib-complete.el [new file with mode: 0644]
lisp/lisp-mnt.el [new file with mode: 0644]
lisp/lisp-mode.el [new file with mode: 0644]
lisp/lisp.el [new file with mode: 0644]
lisp/list-mode.el [new file with mode: 0644]
lisp/loaddefs.el [new file with mode: 0644]
lisp/loadhist.el [new file with mode: 0644]
lisp/loadup-el.el [new file with mode: 0644]
lisp/loadup.el [new file with mode: 0644]
lisp/make-docfile.el [new file with mode: 0644]
lisp/map-ynp.el [new file with mode: 0644]
lisp/menubar-items.el [new file with mode: 0644]
lisp/menubar.el [new file with mode: 0644]
lisp/minibuf.el [new file with mode: 0644]
lisp/misc.el [new file with mode: 0644]
lisp/mode-motion.el [new file with mode: 0644]
lisp/modeline.el [new file with mode: 0644]
lisp/mouse.el [new file with mode: 0644]
lisp/msw-faces.el [new file with mode: 0644]
lisp/msw-glyphs.el [new file with mode: 0644]
lisp/msw-init.el [new file with mode: 0644]
lisp/msw-mouse.el [new file with mode: 0644]
lisp/msw-select.el [new file with mode: 0644]
lisp/multicast.el [new file with mode: 0644]
lisp/mwheel.el [new file with mode: 0644]
lisp/objects.el [new file with mode: 0644]
lisp/package-admin.el [new file with mode: 0644]
lisp/package-get.el [new file with mode: 0644]
lisp/package-info.el [new file with mode: 0644]
lisp/packages.el [new file with mode: 0644]
lisp/page.el [new file with mode: 0644]
lisp/paragraphs.el [new file with mode: 0644]
lisp/paths.el [new file with mode: 0644]
lisp/picture.el [new file with mode: 0644]
lisp/process.el [new file with mode: 0644]
lisp/rect.el [new file with mode: 0644]
lisp/register.el [new file with mode: 0644]
lisp/replace.el [new file with mode: 0644]
lisp/scrollbar.el [new file with mode: 0644]
lisp/select.el [new file with mode: 0644]
lisp/shadow.el [new file with mode: 0644]
lisp/simple.el [new file with mode: 0644]
lisp/site-load.el [new file with mode: 0644]
lisp/sound.el [new file with mode: 0644]
lisp/specifier.el [new file with mode: 0644]
lisp/subr.el [new file with mode: 0644]
lisp/symbol-syntax.el [new file with mode: 0644]
lisp/symbols.el [new file with mode: 0644]
lisp/syntax.el [new file with mode: 0644]
lisp/term/AT386.el [new file with mode: 0644]
lisp/term/README [new file with mode: 0644]
lisp/term/apollo.el [new file with mode: 0644]
lisp/term/bg-mouse.el [new file with mode: 0644]
lisp/term/bobcat.el [new file with mode: 0644]
lisp/term/internal.el [new file with mode: 0644]
lisp/term/keyswap.el [new file with mode: 0644]
lisp/term/linux.el [new file with mode: 0644]
lisp/term/lk201.el [new file with mode: 0644]
lisp/term/news.el [new file with mode: 0644]
lisp/term/pc-win.el [new file with mode: 0644]
lisp/term/scoansi.el [new file with mode: 0644]
lisp/term/sun-mouse.el [new file with mode: 0644]
lisp/term/sun.el [new file with mode: 0644]
lisp/term/sup-mouse.el [new file with mode: 0644]
lisp/term/tvi970.el [new file with mode: 0644]
lisp/term/vt-control.el [new file with mode: 0644]
lisp/term/vt100-led.el [new file with mode: 0644]
lisp/term/vt100.el [new file with mode: 0644]
lisp/term/vt102.el [new file with mode: 0644]
lisp/term/vt125.el [new file with mode: 0644]
lisp/term/vt200.el [new file with mode: 0644]
lisp/term/vt201.el [new file with mode: 0644]
lisp/term/vt220.el [new file with mode: 0644]
lisp/term/vt240.el [new file with mode: 0644]
lisp/term/vt300.el [new file with mode: 0644]
lisp/term/vt320.el [new file with mode: 0644]
lisp/term/vt400.el [new file with mode: 0644]
lisp/term/vt420.el [new file with mode: 0644]
lisp/term/win32-win.el [new file with mode: 0644]
lisp/term/wyse50.el [new file with mode: 0644]
lisp/term/xterm.el [new file with mode: 0644]
lisp/text-mode.el [new file with mode: 0644]
lisp/text-props.el [new file with mode: 0644]
lisp/toolbar-items.el [new file with mode: 0644]
lisp/toolbar.el [new file with mode: 0644]
lisp/tty-init.el [new file with mode: 0644]
lisp/undo-stack.el [new file with mode: 0644]
lisp/userlock.el [new file with mode: 0644]
lisp/very-early-lisp.el [new file with mode: 0644]
lisp/view-less.el [new file with mode: 0644]
lisp/wid-browse.el [new file with mode: 0644]
lisp/wid-edit.el [new file with mode: 0644]
lisp/widget.el [new file with mode: 0644]
lisp/window-xemacs.el [new file with mode: 0644]
lisp/window.el [new file with mode: 0644]
lisp/x-compose.el [new file with mode: 0644]
lisp/x-faces.el [new file with mode: 0644]
lisp/x-font-menu.el [new file with mode: 0644]
lisp/x-init.el [new file with mode: 0644]
lisp/x-iso8859-1.el [new file with mode: 0644]
lisp/x-misc.el [new file with mode: 0644]
lisp/x-mouse.el [new file with mode: 0644]
lisp/x-scrollbar.el [new file with mode: 0644]
lisp/x-select.el [new file with mode: 0644]
lisp/x-win-sun.el [new file with mode: 0644]
lisp/x-win-xfree86.el [new file with mode: 0644]
lwlib/Makefile.in.in [new file with mode: 0644]
lwlib/config.h.in [new file with mode: 0644]
lwlib/lwlib-Xaw.c [new file with mode: 0644]
lwlib/lwlib-Xaw.h [new file with mode: 0644]
lwlib/lwlib-Xlw.c [new file with mode: 0644]
lwlib/lwlib-Xlw.h [new file with mode: 0644]
lwlib/lwlib-Xm.c [new file with mode: 0644]
lwlib/lwlib-Xm.h [new file with mode: 0644]
lwlib/lwlib-config.c [new file with mode: 0644]
lwlib/lwlib-internal.h [new file with mode: 0644]
lwlib/lwlib-utils.c [new file with mode: 0644]
lwlib/lwlib-utils.h [new file with mode: 0644]
lwlib/lwlib.c [new file with mode: 0644]
lwlib/lwlib.h [new file with mode: 0644]
lwlib/xlwmenu.c [new file with mode: 0644]
lwlib/xlwmenu.h [new file with mode: 0644]
lwlib/xlwmenuP.h [new file with mode: 0644]
lwlib/xlwscrollbar.c [new file with mode: 0644]
lwlib/xlwscrollbar.h [new file with mode: 0644]
lwlib/xlwscrollbarP.h [new file with mode: 0644]
man/ChangeLog [new file with mode: 0644]
man/Makefile [new file with mode: 0644]
man/README [new file with mode: 0644]
man/cl.texi [new file with mode: 0644]
man/custom.texi [new file with mode: 0644]
man/external-widget.texi [new file with mode: 0644]
man/info.texi [new file with mode: 0644]
man/internals/internals.texi [new file with mode: 0644]
man/lispref/abbrevs.texi [new file with mode: 0644]
man/lispref/annotations.texi [new file with mode: 0644]
man/lispref/back.texi [new file with mode: 0644]
man/lispref/backups.texi [new file with mode: 0644]
man/lispref/buffers.texi [new file with mode: 0644]
man/lispref/building.texi [new file with mode: 0644]
man/lispref/commands.texi [new file with mode: 0644]
man/lispref/compile.texi [new file with mode: 0644]
man/lispref/consoles-devices.texi [new file with mode: 0644]
man/lispref/control.texi [new file with mode: 0644]
man/lispref/databases.texi [new file with mode: 0644]
man/lispref/debugging.texi [new file with mode: 0644]
man/lispref/dialog.texi [new file with mode: 0644]
man/lispref/display.texi [new file with mode: 0644]
man/lispref/dragndrop.texi [new file with mode: 0644]
man/lispref/edebug-inc.texi [new file with mode: 0644]
man/lispref/edebug.texi [new file with mode: 0644]
man/lispref/errors.texi [new file with mode: 0644]
man/lispref/eval.texi [new file with mode: 0644]
man/lispref/extents.texi [new file with mode: 0644]
man/lispref/faces.texi [new file with mode: 0644]
man/lispref/files.texi [new file with mode: 0644]
man/lispref/frames.texi [new file with mode: 0644]
man/lispref/functions.texi [new file with mode: 0644]
man/lispref/glyphs.texi [new file with mode: 0644]
man/lispref/hash-tables.texi [new file with mode: 0644]
man/lispref/help.texi [new file with mode: 0644]
man/lispref/hooks.texi [new file with mode: 0644]
man/lispref/internationalization.texi [new file with mode: 0644]
man/lispref/intro.texi [new file with mode: 0644]
man/lispref/keymaps.texi [new file with mode: 0644]
man/lispref/ldap.texi [new file with mode: 0644]
man/lispref/lispref.texi [new file with mode: 0644]
man/lispref/lists.texi [new file with mode: 0644]
man/lispref/loading.texi [new file with mode: 0644]
man/lispref/locals.texi [new file with mode: 0644]
man/lispref/macros.texi [new file with mode: 0644]
man/lispref/maps.texi [new file with mode: 0644]
man/lispref/markers.texi [new file with mode: 0644]
man/lispref/menus.texi [new file with mode: 0644]
man/lispref/minibuf.texi [new file with mode: 0644]
man/lispref/modes.texi [new file with mode: 0644]
man/lispref/mouse.texi [new file with mode: 0644]
man/lispref/mule.texi [new file with mode: 0644]
man/lispref/numbers.texi [new file with mode: 0644]
man/lispref/objects.texi [new file with mode: 0644]
man/lispref/os.texi [new file with mode: 0644]
man/lispref/positions.texi [new file with mode: 0644]
man/lispref/processes.texi [new file with mode: 0644]
man/lispref/range-tables.texi [new file with mode: 0644]
man/lispref/scrollbars.texi [new file with mode: 0644]
man/lispref/searching.texi [new file with mode: 0644]
man/lispref/sequences.texi [new file with mode: 0644]
man/lispref/specifiers.texi [new file with mode: 0644]
man/lispref/streams.texi [new file with mode: 0644]
man/lispref/strings.texi [new file with mode: 0644]
man/lispref/symbols.texi [new file with mode: 0644]
man/lispref/syntax.texi [new file with mode: 0644]
man/lispref/text.texi [new file with mode: 0644]
man/lispref/tips.texi [new file with mode: 0644]
man/lispref/toolbar.texi [new file with mode: 0644]
man/lispref/tooltalk.texi [new file with mode: 0644]
man/lispref/variables.texi [new file with mode: 0644]
man/lispref/windows.texi [new file with mode: 0644]
man/lispref/x-windows.texi [new file with mode: 0644]
man/make-stds.texi [new file with mode: 0644]
man/new-users-guide/custom1.texi [new file with mode: 0644]
man/new-users-guide/custom2.texi [new file with mode: 0644]
man/new-users-guide/edit.texi [new file with mode: 0644]
man/new-users-guide/enter.texi [new file with mode: 0644]
man/new-users-guide/files.texi [new file with mode: 0644]
man/new-users-guide/help.texi [new file with mode: 0644]
man/new-users-guide/modes.texi [new file with mode: 0644]
man/new-users-guide/new-users-guide.texi [new file with mode: 0644]
man/new-users-guide/region.texi [new file with mode: 0644]
man/new-users-guide/search.texi [new file with mode: 0644]
man/new-users-guide/xmenu.texi [new file with mode: 0644]
man/standards.texi [new file with mode: 0644]
man/term.texi [new file with mode: 0644]
man/termcap.texi [new file with mode: 0644]
man/texinfo.tex [new file with mode: 0644]
man/texinfo.texi [new file with mode: 0644]
man/widget.texi [new file with mode: 0644]
man/xemacs-faq.texi [new file with mode: 0644]
man/xemacs/abbrevs.texi [new file with mode: 0644]
man/xemacs/basic.texi [new file with mode: 0644]
man/xemacs/buffers.texi [new file with mode: 0644]
man/xemacs/building.texi [new file with mode: 0644]
man/xemacs/calendar.texi [new file with mode: 0644]
man/xemacs/cmdargs.texi [new file with mode: 0644]
man/xemacs/custom.texi [new file with mode: 0644]
man/xemacs/display.texi [new file with mode: 0644]
man/xemacs/entering.texi [new file with mode: 0644]
man/xemacs/files.texi [new file with mode: 0644]
man/xemacs/fixit.texi [new file with mode: 0644]
man/xemacs/frame.texi [new file with mode: 0644]
man/xemacs/glossary.texi [new file with mode: 0644]
man/xemacs/gnu.texi [new file with mode: 0644]
man/xemacs/help.texi [new file with mode: 0644]
man/xemacs/indent.texi [new file with mode: 0644]
man/xemacs/keystrokes.texi [new file with mode: 0644]
man/xemacs/killing.texi [new file with mode: 0644]
man/xemacs/m-x.texi [new file with mode: 0644]
man/xemacs/major.texi [new file with mode: 0644]
man/xemacs/mark.texi [new file with mode: 0644]
man/xemacs/menus.texi [new file with mode: 0644]
man/xemacs/mini.texi [new file with mode: 0644]
man/xemacs/misc.texi [new file with mode: 0644]
man/xemacs/mouse.texi [new file with mode: 0644]
man/xemacs/mule.texi [new file with mode: 0644]
man/xemacs/new.texi [new file with mode: 0644]
man/xemacs/packages.texi [new file with mode: 0644]
man/xemacs/picture.texi [new file with mode: 0644]
man/xemacs/programs.texi [new file with mode: 0644]
man/xemacs/reading.texi [new file with mode: 0644]
man/xemacs/regs.texi [new file with mode: 0644]
man/xemacs/search.texi [new file with mode: 0644]
man/xemacs/sending.texi [new file with mode: 0644]
man/xemacs/startup.texi [new file with mode: 0644]
man/xemacs/text.texi [new file with mode: 0644]
man/xemacs/trouble.texi [new file with mode: 0644]
man/xemacs/undo.texi [new file with mode: 0644]
man/xemacs/windows.texi [new file with mode: 0644]
man/xemacs/xemacs.texi [new file with mode: 0644]
modules/base64/base64.c [new file with mode: 0644]
modules/ldap/eldap.c [new file with mode: 0644]
modules/ldap/eldap.h [new file with mode: 0644]
modules/zlib/zlib.c [new file with mode: 0644]
move-if-change [new file with mode: 0755]
nt/ChangeLog [new file with mode: 0644]
nt/Emacs.ad.h [new file with mode: 0644]
nt/Installation.el [new file with mode: 0644]
nt/README [new file with mode: 0644]
nt/Win32.cf [new file with mode: 0644]
nt/ad2c.sed [new file with mode: 0644]
nt/config.h [new file with mode: 0644]
nt/file.ico [new file with mode: 0644]
nt/lisp.ico [new file with mode: 0644]
nt/paths.h [new file with mode: 0644]
nt/site.def [new file with mode: 0644]
nt/x11.patch [new file with mode: 0644]
nt/xemacs.ico [new file with mode: 0644]
nt/xemacs.mak [new file with mode: 0644]
nt/xemacs.rc [new file with mode: 0644]
nt/xpm.mak [new file with mode: 0644]
src/ChangeLog.1 [new file with mode: 0644]
src/EmacsFrame.c [new file with mode: 0644]
src/EmacsFrame.h [new file with mode: 0644]
src/EmacsFrameP.h [new file with mode: 0644]
src/EmacsManager.c [new file with mode: 0644]
src/EmacsManager.h [new file with mode: 0644]
src/EmacsManagerP.h [new file with mode: 0644]
src/EmacsShell-sub.c [new file with mode: 0644]
src/EmacsShell.c [new file with mode: 0644]
src/EmacsShell.h [new file with mode: 0644]
src/EmacsShellP.h [new file with mode: 0644]
src/ExternalClient-Xlib.c [new file with mode: 0644]
src/ExternalClient.c [new file with mode: 0644]
src/ExternalClient.h [new file with mode: 0644]
src/ExternalClientP.h [new file with mode: 0644]
src/ExternalShell.c [new file with mode: 0644]
src/ExternalShell.h [new file with mode: 0644]
src/ExternalShellP.h [new file with mode: 0644]
src/Makefile.in.in [new file with mode: 0644]
src/README [new file with mode: 0644]
src/alloca.c [new file with mode: 0644]
src/alloca.s [new file with mode: 0644]
src/backtrace.h [new file with mode: 0644]
src/balloon-x.c [new file with mode: 0644]
src/balloon_help.c [new file with mode: 0644]
src/balloon_help.h [new file with mode: 0644]
src/bitmaps.h [new file with mode: 0644]
src/blocktype.c [new file with mode: 0644]
src/blocktype.h [new file with mode: 0644]
src/broken-sun.h [new file with mode: 0644]
src/bytecode.c [new file with mode: 0644]
src/bytecode.h [new file with mode: 0644]
src/callint.c [new file with mode: 0644]
src/callproc.c [new file with mode: 0644]
src/cm.c [new file with mode: 0644]
src/cm.h [new file with mode: 0644]
src/cmdloop.c [new file with mode: 0644]
src/commands.h [new file with mode: 0644]
src/conslots.h [new file with mode: 0644]
src/console-msw.c [new file with mode: 0644]
src/console-msw.h [new file with mode: 0644]
src/console-stream.h [new file with mode: 0644]
src/console-tty.c [new file with mode: 0644]
src/console-tty.h [new file with mode: 0644]
src/console-x.c [new file with mode: 0644]
src/console.c [new file with mode: 0644]
src/debug.c [new file with mode: 0644]
src/debug.h [new file with mode: 0644]
src/device-msw.c [new file with mode: 0644]
src/device-tty.c [new file with mode: 0644]
src/device-x.c [new file with mode: 0644]
src/device.c [new file with mode: 0644]
src/device.h [new file with mode: 0644]
src/dialog-msw.c [new file with mode: 0644]
src/dialog-x.c [new file with mode: 0644]
src/dialog.c [new file with mode: 0644]
src/dired-msw.c [new file with mode: 0644]
src/dired.c [new file with mode: 0644]
src/doc.c [new file with mode: 0644]
src/dragdrop.c [new file with mode: 0644]
src/dragdrop.h [new file with mode: 0644]
src/dynarr.c [new file with mode: 0644]
src/ecrt0.c [new file with mode: 0644]
src/editfns.c [new file with mode: 0644]
src/eldap.c [new file with mode: 0644]
src/eldap.h [new file with mode: 0644]
src/elhash.c [new file with mode: 0644]
src/elhash.h [new file with mode: 0644]
src/eval.c [new file with mode: 0644]
src/event-Xt.c [new file with mode: 0644]
src/event-msw.c [new file with mode: 0644]
src/event-stream.c [new file with mode: 0644]
src/event-tty.c [new file with mode: 0644]
src/event-unixoid.c [new file with mode: 0644]
src/events-mod.h [new file with mode: 0644]
src/events.c [new file with mode: 0644]
src/events.h [new file with mode: 0644]
src/extents.c [new file with mode: 0644]
src/extents.h [new file with mode: 0644]
src/extw-Xlib.c [new file with mode: 0644]
src/extw-Xlib.h [new file with mode: 0644]
src/extw-Xt.c [new file with mode: 0644]
src/extw-Xt.h [new file with mode: 0644]
src/fileio.c [new file with mode: 0644]
src/filelock.c [new file with mode: 0644]
src/filemode.c [new file with mode: 0644]
src/floatfns.c [new file with mode: 0644]
src/frame-msw.c [new file with mode: 0644]
src/frame-tty.c [new file with mode: 0644]
src/frame-x.c [new file with mode: 0644]
src/frame.h [new file with mode: 0644]
src/frameslots.h [new file with mode: 0644]
src/free-hook.c [new file with mode: 0644]
src/general.c [new file with mode: 0644]
src/getloadavg.c [new file with mode: 0644]
src/getpagesize.h [new file with mode: 0644]
src/glyphs-msw.c [new file with mode: 0644]
src/glyphs-msw.h [new file with mode: 0644]
src/glyphs-x.c [new file with mode: 0644]
src/glyphs-x.h [new file with mode: 0644]
src/glyphs.h [new file with mode: 0644]
src/gmalloc.c [new file with mode: 0644]
src/gpmevent.c [new file with mode: 0644]
src/gpmevent.h [new file with mode: 0644]
src/gui-x.c [new file with mode: 0644]
src/gui-x.h [new file with mode: 0644]
src/gui.c [new file with mode: 0644]
src/gui.h [new file with mode: 0644]
src/hash.c [new file with mode: 0644]
src/hash.h [new file with mode: 0644]
src/hftctl.c [new file with mode: 0644]
src/hpplay.c [new file with mode: 0644]
src/imgproc.c [new file with mode: 0644]
src/imgproc.h [new file with mode: 0644]
src/inline.c [new file with mode: 0644]
src/input-method-motif.c [new file with mode: 0644]
src/input-method-xlib.c [new file with mode: 0644]
src/insdel.h [new file with mode: 0644]
src/intl.c [new file with mode: 0644]
src/iso-wide.h [new file with mode: 0644]
src/keymap.c [new file with mode: 0644]
src/keymap.h [new file with mode: 0644]
src/lastfile.c [new file with mode: 0644]
src/libsst.c [new file with mode: 0644]
src/libsst.h [new file with mode: 0644]
src/libst.h [new file with mode: 0644]
src/line-number.c [new file with mode: 0644]
src/line-number.h [new file with mode: 0644]
src/linuxplay.c [new file with mode: 0644]
src/lisp-union.h [new file with mode: 0644]
src/lstream.c [new file with mode: 0644]
src/m/7300.h [new file with mode: 0644]
src/m/README [new file with mode: 0644]
src/m/acorn.h [new file with mode: 0644]
src/m/alliant-2800.h [new file with mode: 0644]
src/m/alliant.h [new file with mode: 0644]
src/m/alliant1.h [new file with mode: 0644]
src/m/alliant4.h [new file with mode: 0644]
src/m/alpha.h [new file with mode: 0644]
src/m/altos.h [new file with mode: 0644]
src/m/amdahl.h [new file with mode: 0644]
src/m/apollo.h [new file with mode: 0644]
src/m/att3b.h [new file with mode: 0644]
src/m/aviion.h [new file with mode: 0644]
src/m/celerity.h [new file with mode: 0644]
src/m/clipper.h [new file with mode: 0644]
src/m/cnvrgnt.h [new file with mode: 0644]
src/m/convex.h [new file with mode: 0644]
src/m/cydra5.h [new file with mode: 0644]
src/m/delta.h [new file with mode: 0644]
src/m/delta88k.h [new file with mode: 0644]
src/m/dpx2.h [new file with mode: 0644]
src/m/dual.h [new file with mode: 0644]
src/m/elxsi.h [new file with mode: 0644]
src/m/ews4800r.h [new file with mode: 0644]
src/m/gec63.h [new file with mode: 0644]
src/m/gould-np1.h [new file with mode: 0644]
src/m/gould.h [new file with mode: 0644]
src/m/hp300bsd.h [new file with mode: 0644]
src/m/hp800.h [new file with mode: 0644]
src/m/hp9000s300.h [new file with mode: 0644]
src/m/i860.h [new file with mode: 0644]
src/m/ibm370aix.h [new file with mode: 0644]
src/m/ibmps2-aix.h [new file with mode: 0644]
src/m/ibmrs6000.h [new file with mode: 0644]
src/m/ibmrt-aix.h [new file with mode: 0644]
src/m/ibmrt.h [new file with mode: 0644]
src/m/intel386.h [new file with mode: 0644]
src/m/iris4d.h [new file with mode: 0644]
src/m/iris5d.h [new file with mode: 0644]
src/m/irist.h [new file with mode: 0644]
src/m/is386.h [new file with mode: 0644]
src/m/isi-ov.h [new file with mode: 0644]
src/m/luna88k.h [new file with mode: 0644]
src/m/m68k.h [new file with mode: 0644]
src/m/masscomp.h [new file with mode: 0644]
src/m/mega68.h [new file with mode: 0644]
src/m/mg1.h [new file with mode: 0644]
src/m/mips-siemens.h [new file with mode: 0644]
src/m/mips.h [new file with mode: 0644]
src/m/mips4.h [new file with mode: 0644]
src/m/ncr386.h [new file with mode: 0644]
src/m/news-risc.h [new file with mode: 0644]
src/m/news.h [new file with mode: 0644]
src/m/next.h [new file with mode: 0644]
src/m/nh3000.h [new file with mode: 0644]
src/m/nh4000.h [new file with mode: 0644]
src/m/ns16000.h [new file with mode: 0644]
src/m/ns32000.h [new file with mode: 0644]
src/m/nu.h [new file with mode: 0644]
src/m/orion.h [new file with mode: 0644]
src/m/orion105.h [new file with mode: 0644]
src/m/paragon.h [new file with mode: 0644]
src/m/pfa50.h [new file with mode: 0644]
src/m/plexus.h [new file with mode: 0644]
src/m/pmax.h [new file with mode: 0644]
src/m/powerpc.h [new file with mode: 0644]
src/m/pyramid.h [new file with mode: 0644]
src/m/pyrmips.h [new file with mode: 0644]
src/m/sequent-ptx.h [new file with mode: 0644]
src/m/sequent.h [new file with mode: 0644]
src/m/sgi-challenge.h [new file with mode: 0644]
src/m/sgi3000.h [new file with mode: 0644]
src/m/sparc.h [new file with mode: 0644]
src/m/sps7.h [new file with mode: 0644]
src/m/stride.h [new file with mode: 0644]
src/m/sun1.h [new file with mode: 0644]
src/m/sun2.h [new file with mode: 0644]
src/m/sun3-68881.h [new file with mode: 0644]
src/m/sun3-fpa.h [new file with mode: 0644]
src/m/sun3-soft.h [new file with mode: 0644]
src/m/sun3.h [new file with mode: 0644]
src/m/sun386.h [new file with mode: 0644]
src/m/symmetry.h [new file with mode: 0644]
src/m/tad68k.h [new file with mode: 0644]
src/m/tahoe.h [new file with mode: 0644]
src/m/tandem-s2.h [new file with mode: 0644]
src/m/targon31.h [new file with mode: 0644]
src/m/tek4300.h [new file with mode: 0644]
src/m/tekxd88.h [new file with mode: 0644]
src/m/template.h [new file with mode: 0644]
src/m/tower32.h [new file with mode: 0644]
src/m/tower32v3.h [new file with mode: 0644]
src/m/ustation.h [new file with mode: 0644]
src/m/vax.h [new file with mode: 0644]
src/m/wicat.h [new file with mode: 0644]
src/m/windowsnt.h [new file with mode: 0644]
src/m/xps100.h [new file with mode: 0644]
src/macros.c [new file with mode: 0644]
src/macros.h [new file with mode: 0644]
src/make-src-depend [new file with mode: 0644]
src/malloc.c [new file with mode: 0644]
src/marker.c [new file with mode: 0644]
src/md5.c [new file with mode: 0644]
src/mem-limits.h [new file with mode: 0644]
src/menubar-msw.c [new file with mode: 0644]
src/menubar-msw.h [new file with mode: 0644]
src/menubar-x.c [new file with mode: 0644]
src/menubar.c [new file with mode: 0644]
src/menubar.h [new file with mode: 0644]
src/minibuf.c [new file with mode: 0644]
src/mule-ccl.h [new file with mode: 0644]
src/nas.c [new file with mode: 0644]
src/ndir.h [new file with mode: 0644]
src/nsselect.m [new file with mode: 0644]
src/nt.c [new file with mode: 0644]
src/nt.h [new file with mode: 0644]
src/ntheap.c [new file with mode: 0644]
src/ntheap.h [new file with mode: 0644]
src/ntplay.c [new file with mode: 0644]
src/ntproc.c [new file with mode: 0644]
src/objects-msw.h [new file with mode: 0644]
src/objects-tty.h [new file with mode: 0644]
src/objects-x.c [new file with mode: 0644]
src/objects-x.h [new file with mode: 0644]
src/objects.c [new file with mode: 0644]
src/objects.h [new file with mode: 0644]
src/offix-cursors.h [new file with mode: 0644]
src/offix-types.h [new file with mode: 0644]
src/offix.c [new file with mode: 0644]
src/offix.h [new file with mode: 0644]
src/opaque.c [new file with mode: 0644]
src/opaque.h [new file with mode: 0644]
src/paths.h.in [new file with mode: 0644]
src/ppc.ldscript [new file with mode: 0644]
src/pre-crt0.c [new file with mode: 0644]
src/print.c [new file with mode: 0644]
src/process-nt.c [new file with mode: 0644]
src/process-unix.c [new file with mode: 0644]
src/process.c [new file with mode: 0644]
src/process.h [new file with mode: 0644]
src/procimpl.h [new file with mode: 0644]
src/profile.c [new file with mode: 0644]
src/ralloc.c [new file with mode: 0644]
src/rangetab.c [new file with mode: 0644]
src/rangetab.h [new file with mode: 0644]
src/realpath.c [new file with mode: 0644]
src/regex.h [new file with mode: 0644]
src/s/3700.h [new file with mode: 0644]
src/s/386-ix.h [new file with mode: 0644]
src/s/386bsd.h [new file with mode: 0644]
src/s/README [new file with mode: 0644]
src/s/aix3-1.h [new file with mode: 0644]
src/s/aix3-2-5.h [new file with mode: 0644]
src/s/aix3-2.h [new file with mode: 0644]
src/s/aix4-1.h [new file with mode: 0644]
src/s/aix4-2.h [new file with mode: 0644]
src/s/aix4.h [new file with mode: 0644]
src/s/alliant-2800.h [new file with mode: 0644]
src/s/alliant.h [new file with mode: 0644]
src/s/altos.h [new file with mode: 0644]
src/s/amdahl.h [new file with mode: 0644]
src/s/bsd386.h [new file with mode: 0644]
src/s/bsd4-1.h [new file with mode: 0644]
src/s/bsd4-2.h [new file with mode: 0644]
src/s/bsd4-3.h [new file with mode: 0644]
src/s/bsdos2-1.h [new file with mode: 0644]
src/s/bsdos2.h [new file with mode: 0644]
src/s/bsdos3.h [new file with mode: 0644]
src/s/cxux.h [new file with mode: 0644]
src/s/cxux7.h [new file with mode: 0644]
src/s/cygwin32.h [new file with mode: 0644]
src/s/decosf1-2.h [new file with mode: 0644]
src/s/decosf1-3.h [new file with mode: 0644]
src/s/decosf3-1.h [new file with mode: 0644]
src/s/decosf3-2.h [new file with mode: 0644]
src/s/decosf4-0.h [new file with mode: 0644]
src/s/dgux.h [new file with mode: 0644]
src/s/dgux5-4r2.h [new file with mode: 0644]
src/s/dgux5-4r3.h [new file with mode: 0644]
src/s/dgux5-4r4.h [new file with mode: 0644]
src/s/domain.h [new file with mode: 0644]
src/s/esix.h [new file with mode: 0644]
src/s/esix5r4.h [new file with mode: 0644]
src/s/ewsux5r4.h [new file with mode: 0644]
src/s/freebsd.h [new file with mode: 0644]
src/s/gnu.h [new file with mode: 0644]
src/s/hpux.h [new file with mode: 0644]
src/s/hpux10-shr.h [new file with mode: 0644]
src/s/hpux10.h [new file with mode: 0644]
src/s/hpux11-shr.h [new file with mode: 0644]
src/s/hpux11.h [new file with mode: 0644]
src/s/hpux8-shr.h [new file with mode: 0644]
src/s/hpux8.h [new file with mode: 0644]
src/s/hpux9-shr.h [new file with mode: 0644]
src/s/hpux9-x11r4.h [new file with mode: 0644]
src/s/hpux9.h [new file with mode: 0644]
src/s/hpux9shxr4.h [new file with mode: 0644]
src/s/iris3-5.h [new file with mode: 0644]
src/s/iris3-6.h [new file with mode: 0644]
src/s/irix3-3.h [new file with mode: 0644]
src/s/irix4-0.h [new file with mode: 0644]
src/s/irix5-0.h [new file with mode: 0644]
src/s/irix5-1.h [new file with mode: 0644]
src/s/irix5-2.h [new file with mode: 0644]
src/s/irix5-3.h [new file with mode: 0644]
src/s/irix6-0.h [new file with mode: 0644]
src/s/isc2-2.h [new file with mode: 0644]
src/s/isc3-0.h [new file with mode: 0644]
src/s/isc4-0.h [new file with mode: 0644]
src/s/isc4-1.h [new file with mode: 0644]
src/s/linux.h [new file with mode: 0644]
src/s/mach-bsd4-3.h [new file with mode: 0644]
src/s/netbsd.h [new file with mode: 0644]
src/s/newsos5.h [new file with mode: 0644]
src/s/nextstep.h [new file with mode: 0644]
src/s/openbsd.h [new file with mode: 0644]
src/s/osf1.h [new file with mode: 0644]
src/s/ptx.h [new file with mode: 0644]
src/s/riscix1-1.h [new file with mode: 0644]
src/s/riscix1-2.h [new file with mode: 0644]
src/s/riscos5.h [new file with mode: 0644]
src/s/rtu.h [new file with mode: 0644]
src/s/sco4.h [new file with mode: 0644]
src/s/sco5-shr.h [new file with mode: 0644]
src/s/sco5.h [new file with mode: 0644]
src/s/sol2.h [new file with mode: 0644]
src/s/sunos4-0-shr.h [new file with mode: 0644]
src/s/sunos4-0.h [new file with mode: 0644]
src/s/sunos4-1-1.h [new file with mode: 0644]
src/s/sunos4-1-2-shr.h [new file with mode: 0644]
src/s/sunos4-1-2.h [new file with mode: 0644]
src/s/sunos4-1-3-shr.h [new file with mode: 0644]
src/s/sunos4-1-3.h [new file with mode: 0644]
src/s/sunos4-1-4-shr.h [new file with mode: 0644]
src/s/sunos4-1-4.h [new file with mode: 0644]
src/s/sunos4-1-shr.h [new file with mode: 0644]
src/s/sunos4-1.h [new file with mode: 0644]
src/s/template.h [new file with mode: 0644]
src/s/ultrix.h [new file with mode: 0644]
src/s/ultrix4-3.h [new file with mode: 0644]
src/s/umax.h [new file with mode: 0644]
src/s/umips.h [new file with mode: 0644]
src/s/unipl5-0.h [new file with mode: 0644]
src/s/unipl5-2.h [new file with mode: 0644]
src/s/usg5-0.h [new file with mode: 0644]
src/s/usg5-2-2.h [new file with mode: 0644]
src/s/usg5-2.h [new file with mode: 0644]
src/s/usg5-3.h [new file with mode: 0644]
src/s/usg5-4-2.h [new file with mode: 0644]
src/s/usg5-4.h [new file with mode: 0644]
src/s/windowsnt.h [new file with mode: 0644]
src/s/xenix.h [new file with mode: 0644]
src/scrollbar-msw.c [new file with mode: 0644]
src/scrollbar-msw.h [new file with mode: 0644]
src/scrollbar-x.c [new file with mode: 0644]
src/scrollbar-x.h [new file with mode: 0644]
src/scrollbar.c [new file with mode: 0644]
src/scrollbar.h [new file with mode: 0644]
src/select-msw.c [new file with mode: 0644]
src/sgiplay.c [new file with mode: 0644]
src/sheap.c [new file with mode: 0644]
src/signal.c [new file with mode: 0644]
src/sound.c [new file with mode: 0644]
src/specifier.c [new file with mode: 0644]
src/specifier.h [new file with mode: 0644]
src/src-headers [new file with mode: 0644]
src/strcat.c [new file with mode: 0644]
src/strcmp.c [new file with mode: 0644]
src/strcpy.c [new file with mode: 0644]
src/strftime.c [new file with mode: 0644]
src/sunOS-fix.c [new file with mode: 0644]
src/sunplay.c [new file with mode: 0644]
src/sunpro.c [new file with mode: 0644]
src/symeval.h [new file with mode: 0644]
src/sysdep.c [new file with mode: 0644]
src/sysdep.h [new file with mode: 0644]
src/sysdir.h [new file with mode: 0644]
src/sysdll.c [new file with mode: 0644]
src/sysdll.h [new file with mode: 0644]
src/sysfile.h [new file with mode: 0644]
src/sysfloat.h [new file with mode: 0644]
src/sysproc.h [new file with mode: 0644]
src/syspwd.h [new file with mode: 0644]
src/syssignal.h [new file with mode: 0644]
src/systime.h [new file with mode: 0644]
src/systty.h [new file with mode: 0644]
src/syswait.h [new file with mode: 0644]
src/termcap.c [new file with mode: 0644]
src/terminfo.c [new file with mode: 0644]
src/toolbar-msw.c [new file with mode: 0644]
src/toolbar.c [new file with mode: 0644]
src/toolbar.h [new file with mode: 0644]
src/tooltalk.c [new file with mode: 0644]
src/tooltalk.doc [new file with mode: 0644]
src/tooltalk.h [new file with mode: 0644]
src/tparam.c [new file with mode: 0644]
src/undo.c [new file with mode: 0644]
src/unexaix.c [new file with mode: 0644]
src/unexalpha.c [new file with mode: 0644]
src/unexapollo.c [new file with mode: 0644]
src/unexconvex.c [new file with mode: 0644]
src/unexcw.c [new file with mode: 0644]
src/unexec.c [new file with mode: 0644]
src/unexelf.c [new file with mode: 0644]
src/unexelfsgi.c [new file with mode: 0644]
src/unexencap.c [new file with mode: 0644]
src/unexenix.c [new file with mode: 0644]
src/unexfreebsd.c [new file with mode: 0644]
src/unexfx2800.c [new file with mode: 0644]
src/unexhp9k3.c [new file with mode: 0644]
src/unexhp9k800.c [new file with mode: 0644]
src/unexmips.c [new file with mode: 0644]
src/unexnext.c [new file with mode: 0644]
src/unexnt.c [new file with mode: 0644]
src/unexsni.c [new file with mode: 0644]
src/unexsol2-6.c [new file with mode: 0644]
src/unexsol2.c [new file with mode: 0644]
src/unexsunos4.c [new file with mode: 0644]
src/universe.h [new file with mode: 0644]
src/vm-limit.c [new file with mode: 0644]
src/widget.c [new file with mode: 0644]
src/window.c [new file with mode: 0644]
src/window.h [new file with mode: 0644]
src/winslots.h [new file with mode: 0644]
src/xgccache.c [new file with mode: 0644]
src/xgccache.h [new file with mode: 0644]
src/xintrinsic.h [new file with mode: 0644]
src/xintrinsicp.h [new file with mode: 0644]
src/xmmanagerp.h [new file with mode: 0644]
src/xmprimitivep.h [new file with mode: 0644]
src/xmu.c [new file with mode: 0644]
src/xmu.h [new file with mode: 0644]
tests/DLL/dltest.c [new file with mode: 0644]
tests/Dnd/README [new file with mode: 0644]
tests/Dnd/README.OffiX [new file with mode: 0644]
tests/Dnd/dragtest.el [new file with mode: 0644]
tests/Dnd/droptest.el [new file with mode: 0644]
tests/Dnd/droptest.sh [new file with mode: 0644]
tests/auc-tex-test [new file with mode: 0644]
tests/frame.el [new file with mode: 0644]
tests/mule/match.el [new file with mode: 0644]
tests/reproduce-bugs.el [new file with mode: 0644]
tests/tooltalk/Makefile [new file with mode: 0644]
tests/tooltalk/beeps.el [new file with mode: 0644]
tests/tooltalk/emacs-eval.c [new file with mode: 0644]
tests/tooltalk/load-file.c [new file with mode: 0644]
tests/tooltalk/make-client-frame.c [new file with mode: 0644]
tests/tooltalk/simple.el [new file with mode: 0644]
version.sh [new file with mode: 0644]

diff --git a/BUGS b/BUGS
new file mode 100644 (file)
index 0000000..5ec5508
--- /dev/null
+++ b/BUGS
@@ -0,0 +1,25 @@
+If you think you may have found a bug in XEmacs, please
+read the Bugs section of the XEmacs manual for advice on
+(1) how to tell when to report a bug, and
+(2) how to write a useful bug report and what information
+it needs to have.
+
+There are three ways to read the Bugs section.
+
+(1) In a printed copy of the XEmacs manual.
+
+(2) With Info.  Start XEmacs, do C-h i to enter Info,
+then m XEmacs RET to get to the Emacs manual, then m Bugs RET
+to get to the section on bugs.  Or use standalone Info in
+a like manner.  (Standalone Info is part of the Texinfo distribution,
+not part of the XEmacs distribution.)
+
+(3) By hand.  Do
+    cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"
+
+
+Part II of the XEmacs FAQ, available in a manner similar to the above,
+or via the world wide web, contains extensive information on how to
+track down and report bugs.
+
+       http://www.xemacs.org/faq/
diff --git a/COPYING b/COPYING
new file mode 100644 (file)
index 0000000..1942c43
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,341 @@
+                   GNU GENERAL PUBLIC LICENSE
+                      Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                          59 Temple Place - Suite 330
+                          Boston, MA 02111-1307, USA.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+\f
+                   GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+\f
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+\f
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+\f
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                           NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                    END OF TERMS AND CONDITIONS
+\f
+           How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; see the file COPYING.  If not, write to
+    the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+    Boston, MA 02111-1307, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/GETTING.GNU.SOFTWARE b/GETTING.GNU.SOFTWARE
new file mode 100644 (file)
index 0000000..27b5ca3
--- /dev/null
@@ -0,0 +1,120 @@
+-*- text -*-
+
+For information on getting XEmacs, see the files DISTRIB and
+MAILINGLISTS in the .../etc/ directory of the XEmacs distribution.
+
+
+                 Getting GNU Software, 14 May 94
+Copyright (C) 1986, 1987, 1988, 1989, 1990, 1992, 1993, 1994 Free Software Foundation, Inc.
+
+
+       Permission is granted to anyone to make or distribute verbatim
+       copies of this document provided that the copyright notice and
+       this permission notice are preserved, and that the distributor
+       grants the recipient permission for further redistribution as
+       permitted by this notice.
+
+
+* GNU and the Free Software Foundation
+
+Project GNU is organized as part of the Free Software Foundation, Inc.
+The Free Software Foundation has the following goals: 1) to create GNU
+as a full development/operating system.  2) to distribute GNU and
+other useful software with source code and permission to copy and
+redistribute.
+
+Further information on the rationale for GNU is in file
+`/pub/gnu/GNUinfo/GNU' (all files referred to are on the Internet host
+prep.ai.mit.edu).
+
+Information on GNU Internet mailing lists and gnUSENET newsgroups can
+be found in `/pub/gnu/GNUinfo/MAILINGLISTS'.
+
+* How To Get The Software
+
+The easiest way to get a copy of the distribution is from someone else
+who has it.  You need not ask for permission to do so, or tell any one
+else; just copy it.  The second easiest is to ftp it over the
+Internet.  The third easiest way is to uucp it.  Ftp and uucp
+information is in `/pub/gnu/GNUinfo/FTP'.
+
+If you cannot get a copy any of these ways, or if you would feel more
+confident getting copies straight from us, or if you would like to get
+some funds to us to help in our efforts, you can order one from the
+Free Software Foundation.  See `/pub/gnu/GNUinfo/DISTRIB' and
+`/pub/gnu/GNUinfo/ORDERS'.
+
+* What format are the *.gz files in?
+
+Because the unix `compress' utility is patented (by two separate
+patents, in fact), we cannot use it; it's not free software.
+
+Therefore, the GNU Project has chosen a new compression utility,
+`gzip', which is free of any known software patents and which tends to
+compress better anyway.  As of March 1993, all compressed files in the
+GNU anonymous FTP area, `prep.ai.mit.edu:/pub/gnu', have been
+converted to the new format.  Files compressed with this new
+compression program end in `.gz' (as opposed to `compress'-compressed
+files, which end in `.Z').
+
+Gzip can uncompress `compress'-compressed files and `pack'-compressed
+files (which end in `.z').  This is possible because the various
+decompression algorithms are not patented---only compression is.
+
+The gzip program is available from any GNU mirror site (see
+`/pub/gnu/GNUinfo/FTP' for a list of mirror sites) in shar, tar, or
+gzipped tar format (for those who already have a prior version of gzip
+and want faster data transmission).  It works on virtually every unix
+system, MSDOS, OS/2, and VMS.
+
+* Available Software
+
+** GNU Emacs
+
+The GNU Emacs distribution includes:   
+       - manual source in TeX format.
+       - an enhanced regex (regular expression) library.
+
+See files `/pub/gnu/GNUinfo/MACHINES*' for the status of porting Emacs
+to various machines and operating systems.
+
+** C Scheme - a block structured dialect of LISP.
+
+The Free Software Foundation distributes C Scheme for the MIT Scheme
+Project on its Scheme tapes.  The full ftp distribution can be gotten
+via anonymous FTP from altdorf.ai.mit.edu in directory /archive.
+
+Problems with the C Scheme distribution and its ftp distribution
+should be referred to: <bug-cscheme@martigny.ai.mit.edu>.  There are
+two general mailing lists: <info-cscheme@martigny.ai.mit.edu>and
+<scheme@mc.lcs.mit.edu>.  Send requests to join either list to:
+<info-cscheme-request@martigny.ai.mit.edu> or
+<scheme-request@mc.lcs.mit.edu>.
+
+** Other GNU Software
+
+A full list of available software are in `/pub/gnu/GNUinfo/ORDERS' and
+`/pub/gnu/DESCRIPTIONS'.
+
+* No Warranties
+
+We distribute software in the hope that it will be useful, but without
+any warranty.  No author or distributor of this software accepts
+responsibility to anyone for the consequences of using it or for
+whether it serves any particular purpose or works at all, unless he
+says so in writing.
+
+* If You Like The Software
+
+If you like the software developed and distributed by the Free
+Software Foundation, please express your satisfaction with a donation.
+Your donations will help to support the foundation and make our future
+efforts successful, including a complete development and operating
+system, called GNU (Gnu's Not Un*x), which will run Un*x user
+programs.  Please note that donations and funds raised by selling
+tapes, CD-ROMs, and floppy diskettes are the major source of funding
+for our work.
+
+For more information on GNU and the Foundation, contact us at Internet
+address <gnu@prep.ai.mit.edu> or the foundation's US Mail address
+found in file `/pub/gnu/GNUinfo/ORDERS'.
diff --git a/INSTALL b/INSTALL
new file mode 100644 (file)
index 0000000..50fba0b
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,766 @@
+XEmacs Installation Guide
+Copyright (c) 1994, 1995, 1996 Board of Trustees, University of Illinois
+Copyright (c) 1994 Free Software Foundation, Inc.
+
+Synched up with: FSF 19.30.
+
+   Permission is granted to anyone to make or distribute verbatim copies
+   of this document as received, in any medium, provided that the
+   copyright notice and permission notice are preserved,
+   and that the distributor grants the recipient permission
+   for further redistribution as permitted by this notice.
+
+   Permission is granted to distribute modified versions
+   of this document, or of portions of it,
+   under the above conditions, provided also that they
+   carry prominent notices stating who last changed them,
+   and that any new or changed statements about the activities
+   of the Free Software Foundation are approved by the Foundation.
+
+
+BUILDING AND INSTALLATION (Unix and Cygwin, see the file nt/README
+for instructions on building under Microsoft Windows):
+
+1) Make sure your system has enough swapping space allocated to handle
+   a program whose pure code is 900k bytes and whose data area is at
+   least 400k and can reach 8Mb or more.  If the swapping space is
+   insufficient, you will get an error in the command `temacs -batch
+   -l loadup dump', found in `./src/Makefile.in.in', or possibly when
+   running the final dumped XEmacs.
+
+Building XEmacs requires about 41 Mb of disk space (including the
+XEmacs sources).  Once installed, XEmacs occupies about 16 Mb in the
+file system where it is installed; this includes the executable files,
+Lisp libraries, miscellaneous data files, and on-line documentation.
+The amount of storage of the Lisp directories may be reduced by
+compressing the .el files. If the building and installation take place
+in different directories, then the installation procedure temporarily
+requires 41+16 Mb.  Adjust this value upwards depending upon what
+additional Lisp support is installed.
+
+XEmacs requires an ANSI C compiler, such as GCC.  If you wish to build
+the documentation yourself, you will need at least version 1.68 of
+makeinfo (GNU texinfo-3.11).
+
+
+2) Decide on what other software packages you would like to use with
+XEmacs, but are not yet available on your system.  On some systems,
+Motif and CDE are optional additions.  On Solaris, the SUNWaudmo
+package enables native sound support.  There are also a number of free
+software packages that XEmacs can use.  If these are not yet available
+on your system, obtain, build and install those external packages
+before building XEmacs.  The packages XEmacs can use are:
+
+   Xaw3d, XPM, JPEG, compface, PNG, zlib, GNU DBM, Berkeley DB, socks,
+   term, NAS, Canna, Kinput2, SJ3, Wnn.
+
+You can get (most of) them from the XEmacs ftp site at
+ftp://ftp.xemacs.org/pub/xemacs/aux
+
+If you want users on other systems to be able to use the XEmacs you
+have built, try to build those packages so that the generated
+libraries are statically linked.
+
+Use the --site-includes and --site-libraries options when building
+XEmacs to allow configure to find the external software packages.
+If you link with dynamic (``.so'') external package libraries, which
+is not recommended, you will also need to add the library directories
+to the --site-runtime-libraries option.
+
+
+3) Decide what Initial Lisp you need with XEmacs.  XEmacs is
+distributed separately from most of its runtime environment.  This is
+done to make it easier for administrators to tune an installation for
+what the local users need.  See the file etc/PACKAGES for an overview
+of what is available and which packages need to be installed prior to
+building XEmacs.  At this point you only need a minimum to get started
+at which point you may install what you wish without further changes
+to the XEmacs binary.  A sample minimum configuration for a Linux
+system using Mule and Wnn6 from OMRON corporation would be the
+packages `mule-base' and `egg-its'.  By default, packages will be
+searched for in the path
+
+~/.xemacs::$prefix/lib/xemacs-${version}/mule-packages:$prefix/lib/xemacs/mule-packages:$prefix/lib/xemacs-${version}/packages:$prefix/lib/xemacs/packages
+
+This may be changed by specifying a different value with the
+--package-path configuration option.
+
+4) In the top level directory of the XEmacs distribution, run the
+   program `configure' as follows:
+
+    ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
+
+Almost always, you should let `configure' (actually the shell script
+`config.guess') guess your host type, by omitting the
+CONFIGURATION-NAME argument.  If you like to experiment, specify a
+configuration name in the form MACHINE-VENDOR-OPSYS, for example:
+
+sparc-sun-solaris2.6
+
+See config.guess and configure.in for valid values for MACHINE,
+VENDOR, and OPSYS.  Also check `./etc/MACHINES' for advice on building
+on particular machines.
+
+If you don't want X support, specify `--without-x'.  If you omit this
+option, `configure' will try to autodetect whether your system has X,
+and arrange to use it if present.
+
+The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
+process where the compiler should look for the include files and
+object libraries used with the X Window System.  Normally, `configure'
+is able to find them; these options are necessary if you have your X
+Window System files installed in unusual places.
+
+The `--site-includes=DIR' and `--site-libraries=DIR' options allow you
+to specify additional places the compiler should look for include
+files and object libraries.  You may specify multiple DIR's by
+enclosing the list in quotes.  All the external packages you want to
+use with XEmacs (e.g. xpm, wnn, ...) described later should have their
+include and library directories defined using these options.
+
+The `--site-runtime-libraries=DIR' option specifies directories to
+search for shared libraries at run time.  This may be necessary if you
+link with dynamic libraries that are installed in non-standard
+directories, or if you expect some of the libraries used to build
+XEmacs to be in a different directory at run time than at build time.
+Usually this will add a `-R' to each directory specified and use that
+when linking XEmacs.  If you use this option, you must specify ALL of
+the directories containing shared libraries at run time, including
+system directories.
+
+Rationale: Some people think that directories in --site-libraries
+should be automatically used to update --site-runtime-libraries.
+Here's a real-life scenario that explains why this is not done: You
+build binaries for your company using static libs in
+/net/toy/hack/lib.  XEmacs adds /net/toy/hack/lib to the runpath of
+the executable you've built.  Since there are only static libs there,
+the system runtime loader will look in this dir, and ignore it,
+causing only a .01 second delay in starting XEmacs.  You leave the
+company for a job at a small Silicon Valley startup.  Time passes.
+The next guy who inherits your machine objects to working on a machine
+named `toy', and gets the sysadmin to rename the machine `godzilla'.
+The SA forgets to remove the old entry for `toy' from the hosts file.
+Now the system loader will still try to access /net/toy/, and the
+automounter will hang trying to access /net/toy.  XEmacs suddenly
+takes 30 seconds longer to start up, no one can figure out why, and
+everyone at your old company curses your name, thinking that you've
+put a time bomb into XEmacs.  And they're right!
+
+The `--with-gcc' option specifies that the build process should
+compile XEmacs using GCC.  The `--compiler' option allows you to
+specify some other compiler to be used to compile XEmacs.  If neither
+option is specified, the environment variable CC is used instead.
+Otherwise the compiler will then default to 'cc'.
+
+The `--cflags' option specifies the CFLAGS the build process should
+use when compiling XEmacs.  Otherwise the value of the environment
+variable CFLAGS is consulted.  If that is also undefined, CFLAGS
+defaults to "-g -O" for gcc and "-g" for all other compilers.
+
+The `--with-gnu-make' option specifies that Makefiles should be
+written to take advantage of special features of GNU Make.  GNU Make
+works fine on Makefiles even without this option.  This flag just
+allows for simultaneous in-place and --srcdir building.
+
+The `--dynamic' option specifies that configure should try to link
+emacs dynamically rather than statically.
+
+The `--const-is-losing' option is for use if you have trouble
+compiling due to the `const' storage class in C.  This is defined by
+default.  Most users should have no need to change this.
+
+You can build XEmacs for several different machine types from a single
+source directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  Make separate
+build directories for the different configuration types, and in each
+one, run the XEmacs `configure' script.  `configure' looks for the
+Emacs source code in the directory that `configure' is in.
+
+The `--prefix=PREFIXDIR' option specifies where the installation process
+should put XEmacs and its data files.  This defaults to `/usr/local'.
+- XEmacs (and the other utilities users run) go in PREFIXDIR/bin
+  (unless the `--exec-prefix' option says otherwise).
+- The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION
+  (where VERSION is the version number of XEmacs, like `21.0').
+- The architecture-dependent files go in
+  PREFIXDIR/lib/xemacs-VERSION/CONFIGURATION-NAME
+  (where CONFIGURATION-NAME is the host type, like mips-dec-ultrix4.2),
+  unless the `--exec-prefix' option says otherwise.
+
+The `--exec-prefix=EXECDIR' option allows you to specify a separate
+portion of the directory tree for installing architecture-specific
+files, like executables and utility programs.  If specified,
+- XEmacs (and the other utilities users run) go in EXECDIR/bin, and
+- The architecture-dependent files go in
+  EXECDIR/lib/xemacs-VERSION/CONFIGURATION-NAME.
+EXECDIR/bin should be a directory that is normally in users' PATHs.
+
+For example, the command
+
+    ./configure mips-dec-ultrix --with-x11=yes
+
+configures XEmacs to build for a DECstation running Ultrix, with
+support for the X11 window system.
+
+The `--with-menubars=TYPE' option allows you to specify which X
+toolkit you wish to use for the menubar.  The valid options are
+`lucid', `motif' and `no'.  The default is `lucid' which is a
+Motif-lookalike menubar.  We highly recommend its usage over the real
+Motif menubar. (In fact, the Motif menubar is currently broken.)  If
+`no' is specified then support for menubars will not be compiled in.
+
+The `--with-scrollbars=TYPE' option allows you to specify which X
+toolkit you wish to use for the scrollbars.  The valid options are
+`lucid', `motif', `athena', `athena3d', and `no'.  The default is
+`lucid' which is a Motif-lookalike scrollbar.  If `no' is specified
+then support for scrollbars will not be compiled in.
+
+The `--with-dialogs=TYPE' option allows you to specify which X toolkit
+you wish to use for the dialog boxes.  The valid options are `athena',
+`athena3d', `motif, and `no.  The `lucid' option is accepted and will
+result in the `athena' toolkit being used.  If the Motif toolkit can be
+found the default is `motif'.  Otherwise, the default is `athena'.  If
+`no' is specified then support for dialog boxes will not be compiled
+in.
+
+The `--with-toolbars' option allows you to enable or disable toolbar
+support.  The default is `yes' as long as support for a windowing
+system is included.
+
+The `--with-xpm' option specifies that XEmacs should support X11
+Pixmaps.  `configure' will attempt to detect if you have the Xpm
+libraries and define `--with-xpm' for you.
+
+The `--with-xface' option specifies that XEmacs should support
+X-Faces.  `configure' will attempt to detect if you have the compface
+library and define `--with-xface' for you.
+
+The `--with-database' option specifies that XEmacs should be built
+with additional database support.  The valid options are `no' or a
+comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'.
+`configure' will attempt to detect the necessary libraries and header
+files and define `--with-database' for you.
+
+The `--with-socks' option specifies that XEmacs should be built with
+SOCKS support.  This requires the libsocks library.
+
+The `--with-tooltalk' option specifies that XEmacs should be built
+with ToolTalk support for interconnecting with other applications.
+ToolTalk is not yet supported on all architectures.  If you use this
+option, you should have the tooltalk package (see etc/PACKAGES)
+installed prior to building XEmacs.
+
+The `--with-sparcworks' option specifies that XEmacs should be built
+with support for Sun Sparcworks 3.0.1 and up (including Sun WorkShop).
+This functionality is only of use on SunOS 4.1.x and Solaris 2.x
+systems.  If you use this option, you should have the Sun package (see
+etc/PACKAGES) installed prior to building XEmacs.
+
+The `--with-cde' option allows you to enable or disable CDE drag and
+drop support.  `configure' will attempt to detect this option and
+define `--with-cde' for you.
+
+The `--with-offix' option allows you to enable or disable OffiX drag
+and drop support.  This requires no external library support, so if
+X11 support is available, then this option defaults to `yes'.  OffiX
+support can be explicitly disabled via the `--with-offix=no' option.
+
+The `--external-widget' option specifies that XEmacs should be built
+with support for being used as a widget by other X11 applications.
+This functionality should be considered beta.
+
+The `--without-xmu' option can be used if your vendor doesn't ship
+the Xmu library.
+
+The `--puresize' option can be used to change the amount of purespace
+allocated for the dumped XEmacs.  As of XEmacs 20.1 usage of this
+parameter is deprecated and will be ignored.
+
+The `--with-sound=TYPE' option specifies that XEmacs should be built
+with sound support.  Native (`--with-sound=native') sound support is
+currently available only on Sun SparcStations, SGI's, HP9000s, and
+systems (such as Linux) with soundcard.h.  Network Audio Support (NAS)
+(`--with-sound=nas' or `--with-sound=both') is an extension to X that
+you may or may not have for your system.  For NAS, you will probably
+need to provide the paths to the nas include and library directories
+to configure.  If `--with-sound' is not specified, `configure' will
+attempt to determine if your configuration supports native sound and
+define --with-sound for you.  If your native sound library is not in a
+standard location you can specify it with the `--native-sound-lib=LIB'
+flag.  For Linux, `/dev/audio' is required for SunAudio files and
+`/dev/dsp' is required for raw data and WAVE format files.
+
+The `--rel-alloc' option can be used to either enable or disable use
+of the relocating allocator.  Turning on --rel-alloc will allow XEmacs
+to return unused memory to the operating system, thereby reducing its
+memory footprint.  However, it may make XEmacs runs more slowly,
+especially if your system's `mmap' implemntation is missing or
+inefficient.  Generally, it's best to go with the default
+configuration for your system.  You can tweak this based on how you
+use XEmacs, and the memory and cpu resources available on your system.
+
+The `--use-system-malloc' option can be use to either enable or
+disable use of the system malloc.  Generally, it's best to go with the
+default configuration for your system.  Note that on many systems
+using the system malloc disables the use of the relocating allocator.
+
+The `--use-debug-malloc' option can be used to link a special debugging
+version of malloc.  Debug Malloc is not included with XEmacs, is
+intended for use only by the developers and may be obtained from
+<URL:http://www.letters.com/dmalloc/>.
+
+The `--debug' and `--error-checking' options are intended for use only
+by the developers.  `--debug' adds code to be compiled in for
+performing various tests.  `--error-checking' adds additional tests to
+many of the commonly used macros.
+
+The `--verbose' and `--extra-verbose' options are intended for use
+only by the developers.  `--verbose' causes the results of all
+configure tests to be displayed.  `--extra-verbose' displays
+additional information, useful for debugging.  Another help for
+determining configure failures is the file `config.log', which
+contains the results of the compile and link tests used by configure.
+
+The `--with-mule' option enables (MUlti-Lingual Emacs) support, needed
+to suport non-Latin-1 (including Asian) languages.  The Mule support
+is not yet as stable or efficient as the `Latin1' support.   Enabling
+Mule support requires the mule-base package installed prior to
+building XEmacs.  The following options require Mule support:
+
+The `--with-xim' option enables use of the X11 XIM mechanism to allow
+an input method to input text into XEmacs.  The input method is shared
+among all the X applications sharing an X display and using the same
+language.  The XIM support comes in two flavors: `motif' and `xlib'.
+The Motif support (the XmIm* functions) is preferred when available.
+The xlib XIM support works reasonably well so long as the X11 libraries
+are recent enough.  It has been fairly well tested on Linux with glibc
+2.0.5 and 2.0.6 and Kinput2 as an XIM server.  In this configuration
+X11 must be recompiled with X_LOCALE defined because glibc is lacking
+localization for Japanese.  The XIM support defaults to `no' except
+when Motif is detected where it is stable with OSF libraries.  The XIM
+support in Lesstif (a Free Motif replacement) does not work as of
+v0.82.  If you enable this option, you will probably wish to install
+the `locale' package which contains localized Splash screens and
+Menubars.
+
+The `--with-xfs' option enables use of a multilingual Menubar.  At the
+present time, only Japanese and French locales are supported.  In
+order to use a multilingual Menubar you must have the `locale' package
+installed.  The `locale' package does not have to be installed when
+building XEmacs.
+
+The `--with-canna' option enables the use of the Canna Japanese input
+method.  This is stable code and fairly well tested.  In order to use
+it, you will have to have the Canna server installed and running.
+Canna versions 3.2pl2 and 3.5b2 are known to work.  Version 3.2pl2 is
+considered most stable than version 3.5b2.  If Canna is already
+installed, configure will autodetect it, so you never need to
+explicitly use this option unless your Canna libraries are somewhere
+strange.  Canna run time support is currently bundled with the
+`mule-base' package so there is nothing additional to install in order
+to use it.
+
+The `--with-wnn' and `--with-wnn6' options are for compiling with the Wnn
+multi-language input method.  `--with-wnn' is for compiling with Wnn-4.2,
+the Free version of WNN.  `--with-wnn6' is for compiling against WNN6,
+the commercial version of WNN available from OMRON Corporation.  This is
+stable code and fairly well tested.  In order to build with this
+option, you will need to have the `egg-its' lisp package already
+installed.
+
+Please note that it is safe to build with as many of the options
+`--with-xim', `--with-canna' and `--with-wnn' as your system
+supports.
+
+`configure' doesn't do any compilation or installation itself.  It
+just creates the files that influence those things: `./src/config.h',
+and all the Makefile's in the build tree.
+
+The `--with-pop', `--with-hesiod', and `--with-kerberos' options are used
+in conjunction with movemail.  As of XEmacs 20.1, movemail is identical
+to the one used in Emacs.
+
+When it is done, `configure' prints a description of what it did and
+creates a shell script `config.status' which, when run, recreates the
+same configuration.  If `configure' exits with an error after
+disturbing the status quo, it removes `config.status'.
+
+4) Look at `./lisp/paths.el'; if some of those values are not right
+for your system, set up the file `./lisp/site-init.el' with XEmacs
+Lisp code to override them; it is not a good idea to edit paths.el
+itself.  YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES,
+rather than `defvar', as used by `./lisp/paths.el'.  For example,
+
+     (setq news-inews-program "/usr/bin/inews")
+
+is how you would override the default value of the variable
+news-inews-program (which is "/usr/local/inews").
+
+Before you override a variable this way, *look at the value* that the
+variable gets by default!  Make sure you know what kind of value the
+variable should have.  If you don't pay attention to what you are
+doing, you'll make a mistake.
+
+Things may malfunction if the variable `directory-abbrev-alist' is not set
+up to translate "temporary" automounter mount points into the canonical
+form.  The default value of this variable contains the translation
+
+       ("^/tmp_mnt/" . "/")
+
+meaning translate "/tmp_mnt/net/FOO" into "/net/FOO", which is appropriate
+for the default configuration of the Sun automounter, but which may be
+inappropriate for different vendor's automounters, or if you have customized
+your mount-point names.
+
+5) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
+Lisp code you want XEmacs to load before it is dumped out.  Use
+site-load.el for additional libraries if you arrange for their
+documentation strings to be in the lib-src/DOC file (see
+src/Makefile.in.in if you wish to figure out how to do that).  For all
+else, use site-init.el.
+
+If you set load-path to a different value in site-init.el or
+site-load.el, XEmacs will use *precisely* that value when it starts up
+again.  If you do this, you are on your own!
+
+Note that, on some systems, the code you place in site-init.el must
+not use expand-file-name or any other function which may look
+something up in the system's password and user information database.
+See `./PROBLEMS' for more details on which systems this affects.
+
+The `site-*.el' files are nonexistent in the distribution.  You do not
+need to create them if you have nothing to put in them.
+
+6) Refer to the file `./etc/TERMS' for information on fields you may
+wish to add to various termcap entries.  The files `./etc/termcap.ucb'
+and `./etc/termcap.dat' may already contain appropriately-modified
+entries.
+
+7) Run `make' in the top directory of the XEmacs distribution to finish
+building XEmacs in the standard way.  The final executable file is
+named `src/emacs'.  You can execute this file "in place" without
+copying it, if you wish; then it automatically uses the sibling
+directories ../lisp, ../lib-src, ../info.
+
+Or you can "install" the executable and the other XEmacs into their
+installed locations, with `make install'.  By default, XEmacs's files
+are installed in the following directories:
+
+By default, XEmacs installs its files in the following directories:
+
+`/usr/local/bin' holds the executable programs users normally run -
+               `xemacs', `etags', `ctags', `b2m', `emacsclient',
+               `gnuclient', `gnudoit', `gnuattach', and `rcs-checkin'.
+
+`/usr/local/lib/xemacs-VERSION/lisp' holds the Emacs Lisp libraries;
+               `VERSION' stands for the number of the XEmacs version
+               you are installing, like `18.59' or `19.14'.  Since
+               the lisp libraries change from one version of XEmacs to
+               another, including the version number in the path
+               allows you to have several versions of XEmacs installed
+               at the same time; this means that you don't have to
+               make XEmacs unavailable while installing a new version.
+
+               XEmacs searches for its lisp files in these
+               directories, and then in
+               `/usr/local/lib/xemacs/site-lisp/*'.
+
+`/usr/local/lib/xemacs-VERSION/etc' holds the XEmacs tutorial, the
+               `yow' database, and other architecture-independent
+               files XEmacs might need while running.  VERSION is as
+               specified for `.../lisp'.
+
+`/usr/local/lib/xemacs/lock' contains files indicating who is
+               editing what, so XEmacs can detect editing clashes
+               between users.
+
+`/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME' contains executable
+               programs used by XEmacs that users are not expected to
+               run themselves, and the DOC file. `VERSION' is the
+               number of the XEmacs version you are installing, and
+               `CONFIGURATION-NAME' is the host type of your system.
+               Since these files are specific to the version of
+               XEmacs, operating system, and architecture in use,
+               including the configuration name in the path allows
+               you to have several versions of XEmacs for any mix of
+               machines and operating systems installed at the same
+               time; this is useful for sites at which different
+               kinds of machines share the file system XEmacs is
+               installed on.
+
+`/usr/local/lib/xemacs-VERSION/info' holds the on-line documentation
+               for XEmacs, known as "info files".
+
+`/usr/local/man/man1' holds the man pages for the programs installed
+               in `/usr/local/bin'.
+
+If these directories are not what you want, you can specify where to
+install XEmacs's libraries and data files or where XEmacs should search
+for its lisp files by giving values for `make' variables as part of
+the command.  See the section below called `MAKE VARIABLES' for more
+information on this.
+
+8) If your system uses lock files to interlock access to mailer inbox files,
+then you might need to make the movemail program setuid or setgid
+to enable it to write the lock files.  We believe this is safe.
+The setuid/setgid bits need not be set on any other XEmacs-related
+executables.
+
+9) You are done with the hard part!  You can remove executables and
+object files from the build directory by typing `make clean'.  To also
+remove the files that `configure' created (so you can compile XEmacs
+for a different configuration), type `make distclean'.
+
+10) You should now go to the XEmacs web page at http://www.xemacs.org/
+and decide what additional Lisp support you wish to have.
+
+MAKE VARIABLES
+
+You can change where the build process installs XEmacs and its data
+files by specifying values for `make' variables as part of the `make'
+command line.  For example, if you type
+
+    make install bindir=/usr/local/gnubin
+
+the `bindir=/usr/local/gnubin' argument indicates that the XEmacs
+executable files should go in `/usr/local/gnubin', not
+`/usr/local/bin'.
+
+Here is a complete list of the variables you may want to set.
+
+`bindir' indicates where to put executable programs that users can
+       run.  This defaults to /usr/local/bin.
+
+`datadir' indicates where to put the architecture-independent
+       read-only data files that XEmacs refers to while it runs; it
+       defaults to /usr/local/lib.  We create the following
+       subdirectories under `datadir':
+       - `xemacs-VERSION/lisp', containing the XEmacs lisp libraries, and
+
+       - `xemacs-VERSION/etc', containing the XEmacs tutorial and the
+               `yow' database.
+       `VERSION' is the number of the XEmacs version you are installing,
+       like `18.59' or `19.14'.  Since these files vary from one version
+       of XEmacs to another, including the version number in the path
+       allows you to have several versions of XEmacs installed at the
+       same time; this means that you don't have to make XEmacs
+       unavailable while installing a new version.
+
+`statedir' indicates where to put architecture-independent data files
+       that XEmacs modifies while it runs; it defaults to
+       /usr/local/lib as well.  We create the following
+       subdirectories under `statedir':
+       - `xemacs/lock', containing files indicating who is editing
+               what, so XEmacs can detect editing clashes between
+               users.
+
+`libdir' indicates where to put architecture-specific data files that
+       XEmacs refers to as it runs; it too defaults to `/usr/local/lib'.
+       We create the following subdirectories under `libdir':
+       - `xemacs-VERSION/CONFIGURATION-NAME', containing executable
+               programs used by XEmacs that users are not expected to run
+               themselves and the DOC file.
+       `VERSION' is the number of the XEmacs version you are installing,
+       and `CONFIGURATION-NAME' is the host type of your system.
+       Since these files are specific to the version of XEmacs,
+       operating system, and architecture in use, including the
+       configuration name in the path allows you to have several
+       versions of XEmacs for any mix of machines and operating
+       systems installed at the same time; this is useful for sites
+       at which different kinds of machines share the file system
+       XEmacs is installed on.
+
+`infodir' indicates where to put the info files distributed with
+       XEmacs; it defaults to `/usr/local/lib/xemacs-VERSION/info'.
+
+`mandir' indicates where to put the man pages for XEmacs and its
+       utilities (like `etags'); it defaults to
+       `/usr/local/man/man1'.
+
+`prefix' doesn't give a path for any specific part of XEmacs; instead,
+       its value is used to determine the defaults for all the
+       architecture-independent path variables - `datadir',
+       `statedir', `infodir', and `mandir'.  Its default value is
+       `/usr/local'; the other variables add on `lib' or `man' to it
+       by default.
+
+       For example, suppose your site generally places GNU software
+       under `/usr/users/software/gnusoft' instead of `/usr/local'.
+       By including
+           `prefix=/usr/users/software/gnusoft'
+       in the arguments to `make', you can instruct the build process
+       to place all of the XEmacs data files in the appropriate
+       directories under that path.
+
+`exec_prefix' serves the same purpose as `prefix', but instead
+       determines the default values for the architecture-dependent
+       path variables - `bindir' and `libdir'.
+
+The above variables serve analogous purposes in the makefiles for all
+GNU software; here are some variables specific to XEmacs.
+
+`lispdir' indicates where XEmacs installs and expects its lisp
+       libraries.  Its default value, based on `datadir' (see above),
+       is `/usr/local/lib/xemacs-VERSION/lisp' (where `VERSION' is as
+       described above).
+
+`sitelispdir' indicates where XEmacs should search for lisp libraries
+       specific to your site. XEmacs checks them in order before
+       checking `lispdir'.  Its default value, based on `datadir'
+       (see above), is `/usr/local/lib/xemacs/site-lisp'.
+
+`etcdir' indicates where XEmacs should install and expect the rest of
+       its architecture-independent data, like the tutorial and yow
+       database.  Its default value, based on `datadir'
+       (see above), is `/usr/local/lib/xemacs-VERSION/etc' (where
+       `VERSION' is as described above).
+
+`lockdir' indicates the directory where XEmacs keeps track of its
+       locking information.  Its default value, based on `statedir'
+       (see above), is `/usr/local/lib/xemacs/lock'.
+
+`archlibdir' indicates where XEmacs installs and expects the
+       executable files and other architecture-dependent data it uses
+       while running.  Its default value, based on `libdir' (see
+       above), is `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME'
+       (where VERSION and CONFIGURATION-NAME are as described above).
+
+Remember that you must specify any variable values you need each time
+you run `make' in the top directory.  If you run `make' once to build
+xemacs, test it, and then run `make' again to install the files, you
+must provide the same variable settings each time.  To make the
+settings persist, you can edit them into the `Makefile' in the top
+directory, but be aware that running the `configure' program erases
+`Makefile' and rebuilds it from `Makefile.in'.
+
+The top-level Makefile stores the variable settings it used in the
+Makefiles for the subdirectories, so you don't have to specify them
+when running make in the subdirectories.
+
+
+CONFIGURATION BY HAND
+
+Instead of running the `configure' program, you have to perform the
+following steps.
+
+1) Copy `./src/config.h.in' to `./src/config.h'.
+
+2) Consult `./etc/MACHINES' to see what configuration name you should
+use for your system.  Look at the code of the `configure' script to
+see which operating system and architecture description files from
+`src/s' and `src/m' should be used for that configuration name.  Edit
+`src/config.h', and change the two `#include' directives to include
+the appropriate system and architecture description files.
+
+2) Edit `./src/config.h' to set the right options for your system.  If
+you need to override any of the definitions in the s/*.h and m/*.h
+files for your system and machine, do so by editing config.h, not by
+changing the s/*.h and m/*.h files.  Occasionally you may need to
+redefine parameters used in `./lib-src/movemail.c'.
+
+3) If you're going to use the make utility to build XEmacs, you will
+still need to run `configure' first, giving the appropriate values for
+the variables in the sections entitled "Things `configure' Might Edit"
+and "Where To Install Things."  Note that you may only need to change
+the variables `prefix' and `exec_prefix', since the rest of the
+variables have reasonable defaults based on them.  For each Makefile
+variable of this type, there is a corresponding configure option; for
+example, to change the location of the lock directory, you might use
+
+        ./configure --lockdir=/nfs/xemacslock
+
+The `configure' script is built from `configure.in' by the `autoconf'
+program.  However, since XEmacs has configuration requirements that
+autoconf can't meet, `configure.in' uses a marriage of custom-baked
+configuration code and autoconf macros.  New versions of autoconf
+could very well break this arrangement, so it may be wise to avoid
+rebuilding `configure' from `configure.in' when possible.
+
+
+BUILDING XEMACS BY HAND
+
+Once XEmacs is configured, running `make' in the top directory performs
+the following steps.
+
+1) Run `make src/paths.h' in the top directory.  This produces
+`./src/paths.h' from the template file `./src/paths.h.in', changing
+the paths to the values specified in `./Makefile'.
+
+2) Cd to `./lib-src' and run `make'.  This creates executables named
+`ctags' and `etags' and `wakeup' and `make-docfile' and `digest-doc'
+and `test-distrib'.  And others.
+
+3) Cd to `./src' and Run `make'.  This refers to files in the `./lisp'
+and `./lib-src' subdirectories using names `../lisp' and
+`../lib-src'.
+
+This creates a file `./src/xemacs' which is the runnable XEmacs,
+assigning it a new build version number by incrementing the build
+version stored in `./lisp/version.el'.
+
+It also creates a file in `./lib-src' whose name is `DOC' followed by
+the current XEmacs version.  This file contains documentation strings
+for all the functions in XEmacs.  Each time you run make to make a new
+xemacs, a new DOC file with a new name is made.  You must keep the DOC
+file for an XEmacs version as long as you keep using that XEmacs
+version.
+
+
+INSTALLATION BY HAND
+
+The steps below are done by running `make install' in the main
+directory of the XEmacs distribution.
+
+1) Copy `./lisp' and its subdirectories, `./etc', and the executables
+in `./lib-src' to their final destinations, as selected in `./src/paths.h'.
+
+Strictly speaking, not all of the executables in `./lib-src' need be copied.
+- The programs `cvtmail', `emacsserver', `env', `fakemail', `hexl',
+    `movemail', `timer', `vcdiff', `wakeup', and `yow' are used by
+    XEmacs; they do need to be copied.
+- The programs `etags', `ctags', `emacsclient', `b2m', `rcs2log',
+    `gnuclient', `gnudoit', and `gnuattach' are intended to be run
+    by users; they are handled below.
+- The programs `make-docfile' and `test-distrib' were
+    used in building XEmacs, and are not needed any more.
+- The programs `digest-doc' and `sorted-doc' convert a `DOC' file into
+    a file for users to read.  There is no important reason to move them.
+
+2) Copy the files in `./info' to the place specified in
+`./lisp/site-init.el' or `./lisp/paths.el'.  Note that if the
+destination directory already contains a file named `dir', you
+probably don't want to replace it with the `dir' file in the XEmacs
+distribution.  Instead, you should make sure that the existing `dir'
+file contains an appropriate menu entry for the XEmacs info.
+
+3) Create a directory for XEmacs to use for clash detection, named as
+indicated by the PATH_LOCK macro in `./src/paths.h'.
+
+4) Copy `./src/xemacs' to `/usr/local/bin', or to some other directory
+in users' search paths.  `./src/xemacs' has an alternate name
+`./src/emacs-EMACSVERSION'; you may wish to make a symbolic link named
+`/usr/local/bin/xemacs' pointing to that alternate name, as an easy way
+of installing different versions.
+
+You can delete `./src/temacs'.
+
+5) Copy the programs `b2m', `emacsclient', `ctags', `etags', `rcs2log',
+`gnuclient', `gnudoit', and `gnuattach' from `./lib-src' to
+`/usr/local/bin'.  These programs are intended for users to run.
+
+6) Copy the man pages in `./etc' for xemacs, ctags, etags, and gnuserv
+into the appropriate man directories.
+
+7) The files in the `./src' subdirectory, except for `xemacs', are not
+used by XEmacs once it is built.  The source would be handy for
+debugging.
+
+
+PROBLEMS
+
+See the file PROBLEMS in this directory for a list of various
+problems sometimes encountered, and what to do about them.
+
+
+If all else fails, please see etc/InstallGuide courtesy
+of Jonathan Seth Hayward.
diff --git a/PROBLEMS b/PROBLEMS
new file mode 100644 (file)
index 0000000..072fc72
--- /dev/null
+++ b/PROBLEMS
@@ -0,0 +1,1475 @@
+                                                  -*- mode:outline -*-
+
+This file describes various problems that have been encountered
+in compiling, installing and running XEmacs.  It has been updated for
+XEmacs 21.2.
+
+This file is rather large, but we have tried to sort the entries by
+their respective relevance for XEmacs, but may have not succeeded
+completely in that task.  The file is divided into four parts:
+
+ - Problems with building XEmacs
+ - Problems with running XEmacs
+ - Compatibility problems
+ - Mule issues
+
+Use `C-c C-f' to move to the next equal level of outline, and
+`C-c C-b' to move to previous equal level.  `C-h m' will give more
+info about the Outline mode.
+
+Also, Try finding the things you need using one of the search commands
+XEmacs provides (e.g. `C-s').
+
+A general advice:
+    WATCH OUT for .emacs file!  ~/.emacs is your Emacs init file.  If
+    you observe strange problems, invoke XEmacs with the `-q' option
+    and see if you can repeat the problem.
+
+
+* Problems with building XEmacs
+===============================
+
+** Don't use -O2 with gcc 2.7.2 under Intel/XXX without also using
+`-fno-strength-reduce'.
+
+gcc will generate incorrect code otherwise.  This bug is present in at
+least 2.6.x and 2.7.[0-2].  This bug has been fixed in GCC 2.7.2.1 and
+later.  This bug is O/S independent, but is limited to x86 architectures.
+
+This problem is known to be fixed in egcs (or pgcc) 1.0 or later.
+
+** Don't use -O2 with gcc 2.7.2 under Intel architectures without also
+using `-fno-caller-saves'.
+
+gcc will generate incorrect code otherwise.  This bug is still
+present in gcc 2.7.2.3.  There have been no reports to indicate the
+bug is present in egcs 1.0 (or pgcc 1.0) or later.  This bug is O/S
+independent, but limited to x86 architectures.
+
+This problem is known to be fixed in egcs (or pgcc) 1.0 or later.
+
+** Excessive optimization with pgcc can break XEmacs
+
+It has been reported on some systems that compiling with -O6 can lead
+to XEmacs failures.  The workaround is to use a lower optimization
+level.  -O2 and -O4 have been tested extensively.
+
+All of this depends heavily on the version of pgcc and the version
+of libc.  Snapshots near the release of pgcc-1.0 have been tested
+extensively and no sign of breakage has been seen on systems using
+glibc-2.
+
+** `compress' and `uncompress' not found and XFree86
+
+XFree86 installs a very old version of libz.a by default ahead of where
+more modern version of libz might be installed.  This will cause problems
+when attempting to link against libMagick.  The fix is to remove the old
+libz.a in the X11 binary directory.
+
+** Excessive optimization on AIX 4.2 can lead to compiler failure.
+
+Valdis.Kletnieks@vt.edu writes:
+  At least at the b34 level, and the latest-and-greatest IBM xlc
+  (3.1.4.4), there are problems with -O3.  I haven't investigated
+  further.
+
+** Sed problems on Solaris 2.5
+
+There have been reports of Sun sed truncating very lines in the
+Makefile during configuration.  The workaround is to use GNU sed or,
+even better, think of a better way to generate Makefile, and send us a 
+patch. :-)
+
+** test-distrib says that the distribution has been clobbered
+or, temacs prints "Command key out of range 0-127"
+or, temacs runs and dumps xemacs, but xemacs totally fails to work.
+or, temacs gets errors dumping xemacs
+
+This can be because the .elc files have been garbled.  Do not be
+fooled by the fact that most of a .elc file is text: these are binary
+files and can contain all 256 byte values.
+
+In particular `shar' cannot be used for transmitting GNU Emacs.  It
+typically truncates "lines".  (this does not apply to GNU shar, which
+uses uuencode to encode binary files.)
+
+If you have a copy of Emacs that has been damaged in its nonprinting
+characters, you can fix them by running:
+
+ make all-elc
+
+This will rebuild all the needed .elc files.
+
+** `Error: No ExtNode to pop!' on Linux systems with Lesstif.
+
+This error message has been observed with lesstif-0.75a.  It does not
+appear to cause any harm.
+
+** Linking with -rpath on IRIX.
+
+Darrell Kindred <dkindred@cmu.edu> writes:
+There are a couple of problems [with use of -rpath with Irix ld], though:
+
+  1. The ld in IRIX 5.3 ignores all but the last -rpath
+     spec, so the patched configure spits out a warning
+     if --x-libraries or --site-runtime-libraries are
+     specified under irix 5.x, and it only adds -rpath 
+     entries for the --site-runtime-libraries.  This bug was
+     fixed sometime between 5.3 and 6.2.
+
+  2. IRIX gcc 2.7.2 doesn't accept -rpath directly, so
+     it would have to be prefixed by -Xlinker or "-Wl,".
+     This would be fine, except that configure compiles with
+        ${CC-cc} $CFLAGS $LDFLAGS ...
+     rather than quoting $LDFLAGS with prefix-args, like
+     src/Makefile does.  So if you specify --x-libraries
+     or --site-runtime-libraries, you must use --use-gcc=no,
+     or configure will fail.
+
+** On Irix 6.3, the SGI ld quits with segmentation fault when linking temacs
+
+This occurs if you use the SGI linker version 7.1.  Installing the
+patch SG0001872 fixes this problem.
+
+** xemacs: can't resolve symbol '__malloc_hook'
+
+This is a Linux problem where you've compiled the XEmacs binary on a libc
+5.4 with version higher than 5.4.19 and attempted to run the binary against
+an earlier version.  The solution is to upgrade your old library.
+
+** Compilation errors on VMS.
+
+Sorry, XEmacs does not work under VMS.  You might consider working on
+the port if you really want to have XEmacs work under VMS.
+
+** On Solaris 2 I get undefined symbols from libcurses.a.
+
+You probably have /usr/ucblib/ on your LD_LIBRARY_PATH.  Do the link with
+LD_LIBRARY_PATH unset.  Generally, avoid using any ucb* stuff when
+building XEmacs.
+
+** On Solaris 2 I cannot make alloc.o, glyphs.o or process.o.
+
+The SparcWorks C compiler may have difficulty building those modules
+with optimization level -xO4.  Try using only "-fast" optimization
+for just those modules.  (Or use gcc).
+
+** On Digital UNIX, the DEC C compiler might have a problem compiling
+some files.
+
+In particular, src/extents.c and src/faces.c might cause the DEC C
+compiler to abort.  When this happens: cd src, compile the files by
+hand, cd .., and redo the "make" command.  When recompiling the files by
+hand, use the old C compiler for the following versions of Digital UNIX:
+  - V3.n: Remove "-migrate" from the compile command.
+  - V4.n: Add "-oldc" to the compile command.
+
+A related compiler bug has been fixed by the DEC compiler team.  The
+new versions of the compiler should run fine.
+
+** On HPUX, the HP C compiler might have a problem compiling some files
+with optimization.
+
+Richard Cognot <cognot@ensg.u-nancy.fr> writes:
+
+  Had to drop once again to level 2 optimization, at least to
+  compile lstream.c. Otherwise, I get a "variable is void: \if"
+  problem while dumping (this is a problem I already reported
+  with vanilla hpux 10.01 and 9.07, which went away after
+  applying patches for the C compiler). Trouble is I still
+  haven't found the same patch for hpux 10.10, and I don't
+  remember the patch numbers. I think potential XEmacs builders
+  on HP should be warned about this.
+
+** I don't have `xmkmf' and `imake' on my HP.
+
+  You can get these standard X tools by anonymous FTP to
+  hpcvaaz.cv.hp.com.  Essentially all X programs need these.
+
+** On HP-UX, problems with make
+
+Marcus Thiessel <marcus_thiessel@hp.com>
+
+  Some releases of XEmacs (e.g. 20.4) require GNU make to build
+  successfully. You don't need GNU make when building 21.x.
+
+** On HP-UX 9.05 XEmacs won't compile or coredump during the build.
+
+Marcus Thiessel <marcus_thiessel@hp.com>
+
+  This might be a sed problem. For your own safety make sure to use
+  GNU sed while dumping XEmacs.
+
+** On HP-UX 11.0 XEmacs causes excessive X11 errors when running.
+
+Marcus Thiessel <marcus_thiessel@hp.com>
+
+  Unfortunately, XEmacs releases don't work with Motif2.1. It
+  will compile but you will get excessive X11 errors like
+
+  xemacs: X Error of failed request:  BadGC (invalid GC parameter)
+
+  and finally XEmacs gets killed. A workaround is to use the
+  Motif1.2_R6 libraries. You can the following line to your call to
+  configure:
+
+     --x-libraries="/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6"
+  Make sure /usr/lib/Motif1.2_R6/libXm.sl is a link to
+  /usr/lib/Motif1.2_R6/libXm.3.
+
+** Solaris 2.3 /bin/sh coredumps during configuration.
+
+This only occurs if you have LANG != C.  This is a known bug with
+/bin/sh fixed by installing Patch-ID# 101613-01.  Or, you can use
+bash, as a workaround.
+
+** On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
+
+A compiler bug inserts spaces into the string "unexelfsgi . o"
+in src/Makefile.  Edit src/Makefile, after configure is run,
+find that string, and take out the spaces.
+
+Compiler fixes in Irix 6.0.1 should eliminate this problem.
+
+** Coredumping in Irix 6.2
+
+Pete Forman <gsez020@compo.bedford.waii.com> writes:
+A problem noted by myself and others (I've lost the references) was
+that XEmacs coredumped when the cut or copy toolbar buttons were
+pressed.  This has been fixed by loading the SGI patchset (Feb 98)
+without having to recompile XEmacs.
+
+My versions are XEmacs 20.3 (problem first noted in 19.15) and IRIX
+6.2, compiled using -n32.  I'd guess that the relevant individual
+patch was "SG0002580: multiple fixes for X libraries".  SGI recommends
+that the complete patch set be installed rather than parts of it.
+
+** Native cc on SCO OpenServer 5 is now OK.  Icc may still throw you
+a curve.  Here is what Robert Lipe <robertl@arnet.com> says:
+
+Unlike XEmacs 19.13, building with the native cc on SCO OpenServer 5 
+now produces a functional binary.   I will typically build this
+configuration for COFF with:
+
+       /path_to_xemacs_source/configure --with-gcc=no \
+         --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
+         --with-xpm --with-xface --with-sound=nas
+
+This version now supports ELF builds.  I highly recommend this to 
+reduce the in-core footprint of XEmacs.  This is now how I compile 
+all my test releases.  Build it like this:
+
+       /path_to_XEmacs_source/configure --with-gcc=no \
+         --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
+         --with-xpm --with-xface --with-sound=nas --dynamic
+
+The compiler known as icc [ supplied with the OpenServer 5 Development 
+System ] generates a working binary, but it takes forever to generate
+XEmacs.  ICC also whines more about the code than /bin/cc does.  I do
+believe all its whining is legitimate, however.    Note that you do
+have to 'cd src ; make  LD=icc' to avoid linker errors.
+
+The way I handle the build procedure is:
+
+       /path_to_XEmacs_source/configure --with-gcc=no \
+         --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
+         --with-xpm --with-xface --with-sound=nas --dynamic --compiler="icc"
+
+NOTE I have the xpm, xface, and audio libraries and includes in 
+       /usr/local/lib, /usr/local/include.  If you don't have these,
+       don't include the "--with-*" arguments in any of my examples.
+
+In previous versions of XEmacs, you had to override the defaults while 
+compiling font-lock.o and extents.o when building with icc.  This seems
+to no longer be true, but I'm including this old information in case it
+resurfaces.  The process I used was:
+
+       make -k    
+       [ procure pizza, beer, repeat ] 
+       cd src
+       make CC="icc -W0,-mP1COPT_max_tree_size=3000" font-lock.o extents.o
+       make LD=icc
+
+If you want sound support, get the tls566 supplement from 
+ftp.sco.com:/TLS or any of its mirrors.  It works just groovy 
+with XEmacs.
+
+The M-x manual-entry is known not to work.  If you know Lisp and would
+like help in making it work, e-mail me at <robertl@dgii.com>.
+(UNCHECKED for 19.15 -- it might work).
+
+In earlier releases, gnuserv/gnuclient/gnudoit would open a frame 
+just fine, but the client would lock up and the server would
+terminate when you used C-x # to close the frame.   This is now 
+fixed in XEmacs.
+
+In etc/ there are two files of note. emacskeys.sco and emacsstrs.sco.
+The comments at the top of emacskeys.sco describe its function, and
+the emacstrs.sco is a suitable candidate for /usr/lib/keyboard/strings
+to take advantage of the keyboard map in emacskeys.sco.
+
+Note: Much of the above entry is probably not valid for XEmacs 21.2
+and later.
+
+** Under some versions of OSF XEmacs runs fine if built without
+optimization but will crash randomly if built with optimization.
+
+Using 'cc -g' is not sufficient to eliminate all optimization.  Try
+'cc -g -O0' instead.
+
+** On SunOS, you get linker errors
+    ld: Undefined symbol 
+       _get_wmShellWidgetClass
+       _get_applicationShellWidgetClass
+
+The fix to this is to install patch 100573 for OpenWindows 3.0
+or link libXmu statically.
+
+** On Sunos 4, you get the error ld: Undefined symbol __lib_version.
+
+This is the result of using cc or gcc with the shared library meant
+for acc (the Sunpro compiler).  Check your LD_LIBRARY_PATH and delete
+/usr/lang/SC2.0.1 or some similar directory.
+
+** On AIX 4.1.2, linker error messages such as
+   ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
+        of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
+
+This is a problem in libIM.a.  You can work around it by executing
+these shell commands in the src subdirectory of the directory where
+you build Emacs:
+
+    cp /usr/lib/libIM.a .
+    chmod 664 libIM.a
+    ranlib libIM.a
+
+Then change -lIM to ./libIM.a in the command to link temacs (in
+Makefile).
+
+** On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
+
+The file cmplrs/stsupport.h was included in the wrong file set in the
+Irix 5.2 distribution.  You can find it in the optional fileset
+compiler_dev, or copy it from some other Irix 5.2 system.  A kludgy
+workaround is to change unexelfsgi.c to include sym.h instead of
+syms.h.
+
+** Link failure when using acc on a Sun.
+
+To use acc, you need additional options just before the libraries, such as
+
+   /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
+
+and you need to add -lansi just before -lc.
+
+The precise file names depend on the compiler version, so we
+cannot easily arrange to supply them.
+
+** Link failure on IBM AIX 1.3 ptf 0013.
+
+There is a real duplicate definition of the function `_slibc_free' in
+the library /lib/libc_s.a (just do nm on it to verify).  The
+workaround/fix is:
+
+    cd /lib
+    ar xv libc_s.a NLtmtime.o
+    ar dv libc_s.a NLtmtime.o
+
+** Undefined symbols when linking on Sunos 4.1.
+
+If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
+_iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
+-lXaw in the command that links temacs.
+
+This problem seems to arise only when the international language
+extensions to X11R5 are installed.
+
+** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
+
+This can happen if configure uses GNU sed version 2.03.  That version
+had a bug.  GNU sed version 2.05 works properly.
+
+** On AIX, you get this compiler error message:
+
+    Processing include file ./XMenuInt.h
+        1501-106: (S) Include file X11/Xlib.h not found.
+
+This means your system was installed with only the X11 runtime i.d
+libraries.  You have to find your sipo (bootable tape) and install
+X11Dev... with smit.
+
+** C-z just refreshes the screen instead of suspending Emacs.
+
+You are probably using a shell that doesn't support job control, even
+though the system itself is capable of it.  Try using a different
+shell.
+
+** On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
+
+    /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment 
+
+The problem is in the Sun shared C library, not in GNU ld.
+
+The solution is to install Patch-ID# 100267-03 from Sun.
+
+** SunOS 4.1.2: undefined symbol _get_wmShellWidgetClass
+
+  Apparently the version of libXmu.so.a that Sun ships is hosed: it's missing
+  some stuff that is in libXmu.a (the static version).  Sun has a patch for 
+  this, but a workaround is to use the static version of libXmu, by changing
+  the link command from "-lXmu" to "-Bstatic -lXmu -Bdynamic".  If you have
+  OpenWindows 3.0, ask Sun for these patches:
+    100512-02       4.1.x OpenWindows 3.0 libXt Jumbo patch
+    100573-03       4.1.x OpenWindows 3.0 undefined symbols with shared libXmu
+
+** Random other SunOS 4.1.[12] link errors.
+
+  The X headers and libraries that Sun ships in /usr/{include,lib}/X11 are
+  broken.  Use the ones in /usr/openwin/{include,lib} instead.
+
+** When using gcc, you get the error message "undefined symbol __fixunsdfsi".
+When using gcc, you get the error message "undefined symbol __main".
+
+This means that you need to link with the gcc library.  It may be called
+"gcc-gnulib" or "libgcc.a"; figure out where it is, and define LIB_GCC in
+config.h to point to it.
+
+It may also work to use the GCC version of `ld' instead of the standard one.
+
+** When compiling with X11, you get "undefined symbol _XtStrings".
+
+This means that you are trying to link emacs against the X11r4 version of
+libXt.a, but you have compiled either Emacs or the code in the lwlib
+subdirectory with the X11r5 header files.  That doesn't work.
+
+Remember, you can't compile lwlib for r4 and emacs for r5, or vice versa.
+They must be in sync.
+
+** Problems finding X11 libraries on Solaris with Openwindows
+
+Some users have reported problems in this area.  The reported solution
+is to define the environment variable OPENWINHOME, even if you must set
+it to `/usr/openwin'.
+
+** Under Linux, you get "too many arguments to function `getpgrp'".
+
+You have probably installed LessTiff under `/usr/local' and `libXm.so'
+could not be found when linking `getpgrp()' test program, making XEmacs
+think that `getpgrp()' takes an argument. Try adding `/usr/local/lib'
+in `/etc/ld.so.conf' and run `ldconfig'. Then run XEmacs's `configure'
+again.  As with all problems of this type, reading the config.log file
+generated from configure and seeing the log of how the test failed can
+prove enlightening.
+
+
+* Problems with running XEmacs
+==============================
+** On Solaris 2.6, XEmacs dumps core when exiting.
+
+This happens if you're XEmacs is running on the same machine as the X
+server, and the optimized memory transport has been turned on by
+setting the environment variable XSUNTRANSPORT.  The crash occurs
+during the call to XCloseDisplay.
+
+If this describes your situation, you need to undefine the
+XSUNTRANSPORT environment variable.
+
+** `C-z', or `M-x suspend-emacs' hangs instead of suspending.
+
+If you build with `gpm' support on Linux, you cannot suspend XEmacs
+because gpm installs a buggy SIGTSTP handler.  Either compile with
+`--with-gpm=no', or don't suspend XEmacs on the Linux console until
+this bug is fixed.
+
+** You type Control-H (Backspace) expecting to delete characters.
+
+Emacs has traditionally used Control-H for help; unfortunately this
+interferes with its use as Backspace on TTY's.  One way to solve this
+problem is to put this in your .emacs:
+
+  (when (eq tty-erase-char ?\C-h)
+    (keyboard-translate ?\C-h ?\C-?)
+    (global-set-key "\M-?" 'help-command))
+
+This checks whether the TTY erase char is C-h, and if it is, makes
+Control-H (Backspace) work sensibly, and moves help to Meta-? (ESC ?).
+
+Note that you can probably also access help using F1.
+
+** Mail agents (VM, Gnus, rmail) cannot get new mail
+
+rmail and VM get new mail from /usr/spool/mail/$USER using a program
+called `movemail'.  This program interlocks with /bin/mail using the
+protocol defined by /bin/mail.
+
+There are two different protocols in general use.  One of them uses
+the `flock' system call.  The other involves creating a lock file;
+`movemail' must be able to write in /usr/spool/mail in order to do
+this.  You control which one is used by defining, or not defining, the
+macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes.  IF
+YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR SYSTEM,
+YOU CAN LOSE MAIL!
+
+If your system uses the lock file protocol, and fascist restrictions
+prevent ordinary users from writing the lock files in /usr/spool/mail,
+you may need to make `movemail' setgid to a suitable group such as
+`mail'.  To do this, use the following commands (as root) after doing
+the make install.
+
+       chgrp mail movemail
+       chmod 2755 movemail
+
+Installation normally copies movemail from the build directory to an
+installation directory which is usually under /usr/local/lib.  The
+installed copy of movemail is usually in the directory
+/usr/local/lib/emacs/VERSION/TARGET.  You must change the group and
+mode of the installed copy; changing the group and mode of the build
+directory copy is ineffective.
+
+** XEmacs crashes on Digital Unix within font-lock, or when dealing
+with large compilation buffers.
+
+The default stack size under Digital Unix is rather small (2M as
+opposed to Solaris 8M), hosing the regexp code, which uses alloca()
+extensively, overflowing the stack when complex regexps are used.
+Workarounds:
+
+1) Increase your stack size, using `ulimit -s 8192' or a (t)csh
+   equivalent;
+
+2) Recompile regex.c with REGEX_MALLOC defined.
+
+** On Solaris, C-x doesn't get through to Emacs when you use the console.
+
+This is a Solaris feature (at least on Intel x86 cpus).  Type C-r
+C-r C-t, to toggle whether C-x gets through to Emacs.
+
+** VM appears to hang in large folders.
+
+This is normal (trust us) when upgrading to VM-6.22 from earlier
+versions.  Let VM finish what it is doing and all will be well.
+
+** Changes made to .el files do not take effect.
+
+You may have forgotten to recompile them into .elc files.  Then the
+old .elc files will be loaded, and your changes will not be seen.  To
+fix this, do `M-x byte-recompile-directory' and specify the directory
+that contains the Lisp files.
+
+Note that you will get a warning when loading a .elc file that is
+older than the corresponding .el file.
+
+** Things which should be bold or italic (such as the initial
+copyright notice) are not.
+
+The fonts of the "bold" and "italic" faces are generated from the font
+of the "default" face; in this way, your bold and italic fonts will
+have the appropriate size and family.  However, emacs can only be
+clever in this way if you have specified the default font using the
+XLFD (X Logical Font Description) format, which looks like
+
+       *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
+
+if you use any of the other, less strict font name formats, some of
+which look like:
+
+               lucidasanstypewriter-12
+and            fixed
+and            9x13
+
+then emacs won't be able to guess the names of the "bold" and "italic"
+versions.  All X fonts can be referred to via XLFD-style names, so you
+should use those forms.  See the man pages for X(1), xlsfonts(1), and
+xfontsel(1).
+
+** The dumped Emacs crashes when run, trying to write pure data.
+
+Two causes have been seen for such problems.
+
+1) On a system where getpagesize is not a system call, it is defined
+as a macro.  If the definition (in both unexec.c and malloc.c) is wrong,
+it can cause problems like this.  You might be able to find the correct
+value in the man page for a.out (5).
+
+2) Some systems allocate variables declared static among the
+initialized variables.  Emacs makes all initialized variables in most
+of its files pure after dumping, but the variables declared static and
+not initialized are not supposed to be pure.  On these systems you
+may need to add "#define static" to the m- or the s- file.
+
+** Reading and writing files is very very slow.
+
+Try evaluating the form (setq lock-directory nil) and see if that helps.
+There is a problem with file-locking on some systems (possibly related
+to NFS) that I don't understand.  Please send mail to the address 
+xemacs@xemacs.org if you figure this one out.
+
+** The Emacs window disappears when you type M-q.
+
+Some versions of the Open Look window manager interpret M-q as a quit
+command for whatever window you are typing at.  If you want to use
+Emacs with that window manager, you should try to configure the window
+manager to use some other command.   You can disable the
+shortcut keys entirely by adding this line to ~/.OWdefaults:
+
+    OpenWindows.WindowMenuAccelerators: False
+
+** The `Alt' key doesn't behave as `Meta' when running DECwindows.
+
+The default DEC keyboard mapping has the Alt keys set up to generate the
+keysym `Multi_key', which has a meaning to xemacs which is distinct from that
+of the `Meta_L' and `Meta-R' keysyms.  A second problem is that certain keys
+have the Mod2 modifier attached to them for no adequately explored reason.
+The correct fix is to pass this file to xmodmap upon starting X:
+
+       clear mod2
+       keysym Multi_key = Alt_L
+       add mod1 = Alt_L
+       add mod1 = Alt_R
+
+** The Compose key on a DEC keyboard does not work as Meta key.
+
+This shell command should fix it:
+
+  xmodmap -e 'keycode 0xb1 = Meta_L'
+
+** When emacs starts up, I get lots of warnings about unknown keysyms.
+
+If you are running the prebuilt binaries, the Motif library expects to find
+certain thing in the XKeysymDB file.  This file is normally in /usr/lib/X11/
+or in /usr/openwin/lib/.  If you keep yours in a different place, set the
+environment variable $XKEYSYMDB to point to it before starting emacs.  If 
+you still have the problem after doing that, perhaps your version of X is 
+too old.  There is a copy of the MIT X11R5 XKeysymDB file in the emacs `etc'
+directory.  Try using that one.
+
+** My X resources used to work, and now some of them are being ignored.
+
+Check the resources in .../etc/Emacs.ad (which is the same as the file
+sample.Xdefaults).  Perhaps some of the default resources built in to 
+emacs are now overriding your existing resources.  Copy and edit the
+resources in Emacs.ad as necessary.
+
+** I get complaints about the mapping of my HP keyboard at startup,
+but I haven't changed anything.
+
+The default HP keymap is set up to have Mod1 assigned to two different keys:
+Meta_L and Mode_switch (even though there is not actually a Mode_switch key on
+the keyboard -- it uses an "imaginary" keycode.)  There actually is a reason
+for this, but it's not a good one.  The correct fix is to execute this command
+upon starting X:
+
+       xmodmap -e 'remove mod1 = Mode_switch'
+
+** I have focus problems when I use `M-o' to switch to another screen
+without using the mouse.
+
+The focus issues with a program like XEmacs, which has multiple
+homogeneous top-level windows, are very complicated, and as a result,
+most window managers don't implement them correctly.
+
+The R4/R5 version of twm (and all of its descendants) had buggy focus
+handling.  Sufficiently recent versions of tvtwm have been fixed.  In
+addition, if you're using twm, make sure you have not specified
+"NoTitleFocus" in your .tvtwmrc file.  The very nature of this option
+makes twm do some illegal focus tricks, even with the patch.
+
+It is known that olwm and olvwm are buggy, and in different ways.  If
+you're using click-to-type mode, try using point-to-type, or vice
+versa.
+
+In older versions of NCDwm, one could not even type at XEmacs windows.
+This has been fixed in newer versions (2.4.3, and possibly earlier).
+
+(Many people suggest that XEmacs should warp the mouse when focusing
+on another screen in point-to-type mode.  This is not ICCCM-compliant
+behavior.  Implementing such policy is the responsibility of the
+window manager itself, it is not legal for a client to do this.)
+
+** Emacs spontaneously displays "I-search: " at the bottom of the screen.
+
+This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
+used.  C-s/C-q flow control is bad for Emacs editors because it takes
+away C-s and C-q as user commands.  Since editors do not output long
+streams of text without user commands, there is no need for a
+user-issuable "stop output" command in an editor; therefore, a
+properly designed flow control mechanism would transmit all possible
+input characters without interference.  Designing such a mechanism is
+easy, for a person with at least half a brain.
+
+There are three possible reasons why flow control could be taking place:
+
+  1) Terminal has not been told to disable flow control
+  2) Insufficient padding for the terminal in use
+  3) Some sort of terminal concentrator or line switch is responsible
+
+First of all, many terminals have a set-up mode which controls whether
+they generate XON/XOFF flow control characters.  This must be set to
+"no XON/XOFF" in order for Emacs to work.  Sometimes there is an
+escape sequence that the computer can send to turn flow control off
+and on.  If so, perhaps the termcap `ti' string should turn flow
+control off, and the `te' string should turn it on.
+
+Once the terminal has been told "no flow control", you may find it
+needs more padding.  The amount of padding Emacs sends is controlled
+by the termcap entry for the terminal in use, and by the output baud
+rate as known by the kernel.  The shell command `stty' will print
+your output baud rate; `stty' with suitable arguments will set it if
+it is wrong.  Setting to a higher speed causes increased padding.  If
+the results are wrong for the correct speed, there is probably a
+problem in the termcap entry.  You must speak to a local Unix wizard
+to fix this.  Perhaps you are just using the wrong terminal type.
+
+For terminals that lack a "no flow control" mode, sometimes just
+giving lots of padding will prevent actual generation of flow control
+codes.  You might as well try it.
+
+If you are really unlucky, your terminal is connected to the computer
+through a concentrator which sends XON/XOFF flow control to the
+computer, or it insists on sending flow control itself no matter how
+much padding you give it.  Unless you can figure out how to turn flow
+control off on this concentrator (again, refer to your local wizard),
+you are screwed!  You should have the terminal or concentrator
+replaced with a properly designed one.  In the mean time, some drastic
+measures can make Emacs semi-work.
+
+You can make Emacs ignore C-s and C-q and let the operating system
+handle them.  To do this on a per-session basis, just type M-x
+enable-flow-control RET.  You will see a message that C-\ and C-^ are
+now translated to C-s and C-q.  (Use the same command M-x
+enable-flow-control to turn *off* this special mode.  It toggles flow
+control handling.)
+
+If C-\ and C-^ are inconvenient for you (for example, if one of them
+is the escape character of your terminal concentrator), you can choose
+other characters by setting the variables flow-control-c-s-replacement
+and flow-control-c-q-replacement.  But choose carefully, since all
+other control characters are already used by emacs.
+
+IMPORTANT: if you type C-s by accident while flow control is enabled,
+Emacs output will freeze, and you will have to remember to type C-q in
+order to continue.
+
+If you work in an environment where a majority of terminals of a
+certain type are flow control hobbled, you can use the function
+`enable-flow-control-on' to turn on this flow control avoidance scheme
+automatically.  Here is an example:
+
+(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
+
+If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
+and good vt200 terminals), you can still run enable-flow-control
+manually.
+
+I have no intention of ever redesigning the Emacs command set for the
+assumption that terminals use C-s/C-q flow control.  XON/XOFF flow
+control technique is a bad design, and terminals that need it are bad
+merchandise and should not be purchased.  Now that X is becoming
+widespread, XON/XOFF seems to be on the way out.  If you can get some
+use out of GNU Emacs on inferior terminals, more power to you, but I
+will not make Emacs worse for properly designed systems for the sake
+of inferior systems.
+
+** Control-S and Control-Q commands are ignored completely.
+
+For some reason, your system is using brain-damaged C-s/C-q flow
+control despite Emacs's attempts to turn it off.  Perhaps your
+terminal is connected to the computer through a concentrator
+that wants to use flow control.
+
+You should first try to tell the concentrator not to use flow control.
+If you succeed in this, try making the terminal work without
+flow control, as described in the preceding section.
+
+If that line of approach is not successful, map some other characters
+into C-s and C-q using keyboard-translate-table.  The example above
+shows how to do this with C-^ and C-\.
+
+** Control-S and Control-Q commands are ignored completely on a net
+connection.
+
+Some versions of rlogin (and possibly telnet) do not pass flow
+control characters to the remote system to which they connect.
+On such systems, emacs on the remote system cannot disable flow
+control on the local system.
+
+One way to cure this is to disable flow control on the local host
+(the one running rlogin, not the one running rlogind) using the
+stty command, before starting the rlogin process.  On many systems,
+`stty start u stop u' will do this.
+
+Some versions of tcsh will prevent even this from working.  One way
+around this is to start another shell before starting rlogin, and
+issue the stty command to disable flow control from that shell.
+
+If none of these methods work, the best solution is to type
+`M-x enable-flow-control' at the beginning of your emacs session, or
+if you expect the problem to continue, add a line such as the
+following to your .emacs (on the host running rlogind):
+
+(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
+
+See the entry about spontaneous display of I-search (above) for more
+info.
+
+** TTY redisplay is slow.
+
+XEmacs has fairly new TTY redisplay support (beginning from 19.12),
+which doesn't include some basic TTY optimizations -- like using
+scrolling regions to move around blocks of text.  This is why
+redisplay on the traditional terminals, or over slow lines can be very 
+slow.
+
+If you are interested in fixing this, please let us know at
+<xemacs@xemacs.org>.
+
+** Screen is updated wrong, but only on one kind of terminal.
+
+This could mean that the termcap entry you are using for that terminal
+is wrong, or it could mean that Emacs has a bug handing the
+combination of features specified for that terminal.
+
+The first step in tracking this down is to record what characters
+Emacs is sending to the terminal.  Execute the Lisp expression
+(open-termscript "./emacs-script") to make Emacs write all terminal
+output into the file ~/emacs-script as well; then do what makes the
+screen update wrong, and look at the file and decode the characters
+using the manual for the terminal.  There are several possibilities:
+
+1) The characters sent are correct, according to the terminal manual.
+
+In this case, there is no obvious bug in Emacs, and most likely you
+need more padding, or possibly the terminal manual is wrong.
+
+2) The characters sent are incorrect, due to an obscure aspect of the
+   terminal behavior not described in an obvious way by termcap.
+
+This case is hard.  It will be necessary to think of a way for Emacs
+to distinguish between terminals with this kind of behavior and other
+terminals that behave subtly differently but are classified the same
+by termcap; or else find an algorithm for Emacs to use that avoids the
+difference.  Such changes must be tested on many kinds of terminals.
+
+3) The termcap entry is wrong.
+
+See the file etc/TERMS for information on changes that are known to be
+needed in commonly used termcap entries for certain terminals.
+
+4) The characters sent are incorrect, and clearly cannot be right for
+   any terminal with the termcap entry you were using.
+
+This is unambiguously an Emacs bug, and can probably be fixed in
+termcap.c, terminfo.c, tparam.c, cm.c, redisplay-tty.c,
+redisplay-output.c, or redisplay.c.
+
+** Your Delete key sends a Backspace to the terminal, using an AIXterm.
+
+The solution is to include in your .Xdefaults the lines:
+
+   *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
+   aixterm*ttyModes: erase ^?
+
+This makes your Backspace key send DEL (ASCII 127).
+
+** With certain fonts, when the cursor appears on a character, the
+character doesn't appear--you get a solid box instead.
+
+One user on a Linux system reported that this problem went away with
+installation of a new X server.  The failing server was XFree86 3.1.1.
+XFree86 3.1.2 works.
+
+** On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
+
+This happens if you configure Emacs specifying just `sparc-sun-sunos4'
+on a system that is version 4.1.3.  You must specify the precise
+version number (or let configure figure out the configuration, which
+it can do perfectly well for SunOS).
+
+** On Irix, I don't see the toolbar icons and I'm getting lots of
+entries in the warnings buffer.
+
+SGI ships a really old Xpm library in /usr/lib which does not work at
+all well with XEmacs.  The solution is to install your own copy of the
+latest version of Xpm somewhere and then use the --site-includes and
+--site-libraries flags to tell configure where to find it.
+
+** On HPUX, you get "poll: Interrupted system call" message in the
+window where XEmacs was launched.
+
+Richard Cognot <cognot@ensg.u-nancy.fr> writes:
+
+  I get a very strange problem when linking libc.a dynamically: every
+  event (mouse, keyboard, expose...) results in a "poll: Interrupted
+  system call" message in the window where XEmacs was
+  launched. Forcing a static link of libc.a alone by adding
+  /usr/lib/libc.a at the end of the link line solves this. Note that
+  my 9.07 build of 19.14b17 and my (old) build of 19.13 both exhibit
+  the same behaviour. I've tried various hpux patches to no avail. If
+  this problem cannot be solved before the release date, binary kits
+  for HP *must* be linked statically against libc, otherwise this
+  problem will show up. (This is directed at whoever will volunteer
+  for this kit, as I won't be available to do it, unless 19.14 gets
+  delayed until mid-june ;-). I think this problem will be an FAQ soon
+  after the release otherwise.
+
+Note: The above entry is probably not valid for XEmacs 21.2 and
+later.
+
+** When Emacs tries to ring the bell, you get an error like
+
+       audio: sst_open: SETQSIZE" Invalid argument
+       audio: sst_close: SETREG MMR2, Invalid argument
+
+you have probably compiled using an ANSI C compiler, but with non-ANSI
+include files.  In particular, on Suns, the file
+/usr/include/sun/audioio.h uses the _IOW macro to define the constant
+AUDIOSETQSIZE.  _IOW in turn uses a K&R preprocessor feature that is
+now explicitly forbidden in ANSI preprocessors, namely substitution
+inside character constants.  All ANSI C compilers must provide a
+workaround for this problem.  Lucid's C compiler is shipped with a new
+set of system include files.  If you are using GCC, there is a script
+called fixincludes that creates new versions of some system include
+files that use this obsolete feature.
+
+** My buffers are full of \000 characters or otherwise corrupt.
+
+Some compilers have trouble with gmalloc.c and ralloc.c; try recompiling
+without optimization.  If that doesn't work, try recompiling with
+SYSTEM_MALLOC defined, and/or with REL_ALLOC undefined.
+
+** On AIX 4, some programs fail when run in a Shell buffer
+with an error message like No terminfo entry for "unknown".
+
+On AIX, many terminal type definitions are not installed by default.
+`unknown' is one of them.  Install the "Special Generic Terminal
+Definitions" to make them defined.
+
+** Emacs exits with "X protocol error" when run with an X server for
+Windows.
+
+A certain X server for Windows had a bug which caused this.
+Supposedly the newer 32-bit version of this server doesn't have the
+problem.
+
+** A position you specified in .Xdefaults is ignored, using twm.
+
+twm normally ignores "program-specified" positions.
+You can tell it to obey them with this command in your `.twmrc' file:
+
+  UsePPosition "on"            #allow clents to request a position
+
+** The right Alt key works wrong on German HP keyboards (and perhaps
+   other non-English HP keyboards too).
+
+This is because HPUX defines the modifiers wrong in X.  Here is a
+shell script to fix the problem; be sure that it is run after VUE
+configures the X server.
+
+    xmodmap 2> /dev/null - << EOF
+    keysym Alt_L = Meta_L
+    keysym Alt_R = Meta_R
+    EOF
+
+    xmodmap - << EOF
+    clear mod1
+    keysym Mode_switch = NoSymbol
+    add mod1 = Meta_L
+    keysym Meta_R = Mode_switch
+    add mod2 = Mode_switch
+    EOF
+
+** Trouble using ptys on IRIX, or running out of ptys.
+
+The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
+be set-UID to root, or non-root programs like Emacs will not be able
+to allocate ptys reliably.
+
+** Motif dialog boxes lose on Irix.
+
+Larry Auton <lda@control.att.com> writes:
+Beware of not specifying
+
+       --with-dialogs=athena
+
+if it builds with the motif dialogs [boom!] you're a dead man.
+
+** Beware of the default image & graphics library on Irix
+
+Richard Cognot <cognot@ensg.u-nancy.fr> writes:
+You *have* to compile your own jpeg lib. The one delivered with SGI
+systems is a C++ lib, which apparently XEmacs cannot cope with.
+
+** Slow startup on Linux.
+
+People using systems based on the Linux kernel sometimes report that
+startup takes 10 to 15 seconds longer than `usual'.
+
+This is because Emacs looks up the host name when it starts.
+Normally, this takes negligible time; the extra delay is due to
+improper system configuration.  This problem can occur for both
+networked and non-networked machines.
+
+Here is how to fix the configuration.  It requires being root.
+
+*** Networked Case
+
+First, make sure the files `/etc/hosts' and `/etc/host.conf' both
+exist.  The first line in the `/etc/hosts' file should look like this
+(replace HOSTNAME with your host name):
+
+    127.0.0.1      localhost HOSTNAME
+
+Also make sure that the `/etc/host.conf' files contains the following
+lines:
+
+    order hosts, bind 
+    multi on
+
+Any changes, permanent and temporary, to the host name should be
+indicated in the `/etc/hosts' file, since it acts a limited local
+database of addresses and names (e.g., some SLIP connections
+dynamically allocate ip addresses).
+
+*** Non-Networked Case
+
+The solution described in the networked case applies here as well.
+However, if you never intend to network your machine, you can use a
+simpler solution: create an empty `/etc/host.conf' file.  The command
+`touch /etc/host.conf' suffices to create the file.  The `/etc/hosts'
+file is not necessary with this approach.
+
+** On Solaris 2.4, Dired hangs and C-g does not work.  Or Emacs hangs
+forever waiting for termination of a subprocess that is a zombie.
+
+casper@fwi.uva.nl says the problem is in X11R6.  Rebuild libX11.so
+after changing the file xc/config/cf/sunLib.tmpl.  Change the lines
+
+    #if ThreadedX
+    #define SharedX11Reqs -lthread
+    #endif
+
+to:
+
+    #if OSMinorVersion < 4
+    #if ThreadedX
+    #define SharedX11Reqs -lthread
+    #endif
+    #endif
+
+Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
+(as it should be for Solaris 2.4).  The file has three definitions for
+OSMinorVersion: the first is for x86, the second for SPARC under
+Solaris, and the third for SunOS 4.  Make sure to update the
+definition for your type of machine and system.
+
+Then do `make Everything' in the top directory of X11R6, to rebuild
+the makefiles and rebuild X.  The X built this way work only on
+Solaris 2.4, not on 2.3.
+
+For multithreaded X to work it necessary to install patch
+101925-02 to fix problems in header files [2.4].  You need
+to reinstall gcc or re-run just-fixinc after installing that
+patch.
+
+However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
+he changed
+    #define ThreadedX          YES
+to
+    #define ThreadedX          NO
+in sun.cf and did `make World' to rebuild X11R6.  Removing all
+`-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
+typing 'make install' in that directory also seemed to work.
+
+** With M-x enable-flow-control, you need to type C-\ twice to do
+incremental search--a single C-\ gets no response.
+
+This has been traced to communicating with your machine via kermit,
+with C-\ as the kermit escape character.  One solution is to use
+another escape character in kermit.  One user did
+
+   set escape-character 17
+
+in his .kermrc file, to make C-q the kermit escape character.
+
+** The Motif version of Emacs paints the screen a solid color.
+
+This has been observed to result from the following X resource:
+
+   Emacs*default.attributeFont:        -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
+
+That the resource has this effect indicates a bug in something, but we
+do not yet know what.  If it is an Emacs bug, we hope someone can
+explain what the bug is so we can fix it.  In the mean time, removing
+the resource prevents the problem.
+
+** Regular expressions matching bugs on SCO systems.
+
+On SCO, there are problems in regexp matching when Emacs is compiled
+with the system compiler.  The compiler version is "Microsoft C
+version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
+C Compiler Version 1.00.46 (Beta).  The solution is to compile with
+GCC.
+
+** In Shell mode, you get a ^M at the end of every line.
+
+This happens to people who use tcsh, because it is trying to be too
+smart.  It sees that the Shell uses terminal type `unknown' and turns
+on the flag to output ^M at the end of each line.  You can fix the
+problem by adding this to your .cshrc file:
+
+    if ($?EMACS) then
+        if ($EMACS == "t") then
+            unset edit 
+            stty  -icrnl -onlcr -echo susp ^Z
+        endif
+    endif
+
+** An error message such as `X protocol error: BadMatch (invalid
+parameter attributes) on protocol request 93'.
+
+This comes from having an invalid X resource, such as
+   emacs*Cursor:   black
+(which is invalid because it specifies a color name for something
+that isn't a color.)
+
+The fix is to correct your X resources.
+
+** Mail is lost when sent to local aliases.
+
+Many emacs mail user agents (VM and rmail, for instance) use the
+sendmail.el library.  This library can arrange for mail to be
+delivered by passing messages to the /usr/lib/sendmail (usually)
+program .  In doing so, it passes the '-t' flag to sendmail, which
+means that the name of the recipient of the message is not on the
+command line and, therefore, that sendmail must parse the message to
+obtain the destination address.
+
+There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
+In short, when given the -t flag, the SunOS sendmail won't recognize
+non-local (i.e. NIS) aliases.  It has been reported that the Solaris
+2.x versions of sendmail do not have this bug.  For those using SunOS
+4.1, the best fix is to install sendmail V8 or IDA sendmail (which
+have other advantages over the regular sendmail as well).  At the time
+of this writing, these official versions are available:
+
+ Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
+   sendmail.8.6.9.base.tar.Z (the base system source & documentation)
+   sendmail.8.6.9.cf.tar.Z   (configuration files)
+   sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
+   sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
+
+ IDA sendmail on vixen.cso.uiuc.edu in /pub:
+   sendmail-5.67b+IDA-1.5.tar.gz
+
+** On AIX, you get this message when running Emacs:
+
+    Could not load program emacs
+    Symbol smtcheckinit in csh is undefined
+    Error was: Exec format error
+
+or this one:
+
+    Could not load program .emacs
+    Symbol _system_con in csh is undefined
+    Symbol _fp_trapsta in csh is undefined
+    Error was: Exec format error
+
+These can happen when you try to run on AIX 3.2.5 a program that was
+compiled with 3.2.4.  The fix is to recompile.
+
+** After running emacs once, subsequent invocations crash.
+
+Some versions of SVR4 have a serious bug in the implementation of the
+mmap () system call in the kernel; this causes emacs to run correctly
+the first time, and then crash when run a second time.
+
+Contact your vendor and ask for the mmap bug fix; in the mean time,
+you may be able to work around the problem by adding a line to your
+operating system description file (whose name is reported by the
+configure script) that reads:
+#define SYSTEM_MALLOC
+This makes Emacs use memory less efficiently, but seems to work around
+the kernel bug.
+
+** Inability to send an Alt-modified key, when Emacs is communicating
+directly with an X server.
+
+If you have tried to bind an Alt-modified key as a command, and it
+does not work to type the command, the first thing you should check is
+whether the key is getting through to Emacs.  To do this, type C-h c
+followed by the Alt-modified key.  C-h c should say what kind of event
+it read.  If it says it read an Alt-modified key, then make sure you
+have made the key binding correctly.
+
+If C-h c reports an event that doesn't have the Alt modifier, it may
+be because your X server has no key for the Alt modifier.  The X
+server that comes from MIT does not set up the Alt modifier by
+default.
+
+If your keyboard has keys named Alt, you can enable them as follows:
+
+    xmodmap -e 'add mod2 = Alt_L'
+    xmodmap -e 'add mod2 = Alt_R'
+
+If the keyboard has just one key named Alt, then only one of those
+commands is needed.  The modifier `mod2' is a reasonable choice if you
+are using an unmodified MIT version of X.  Otherwise, choose any
+modifier bit not otherwise used.
+
+If your keyboard does not have keys named Alt, you can use some other
+keys.  Use the keysym command in xmodmap to turn a function key (or
+some other 'spare' key) into Alt_L or into Alt_R, and then use the
+commands show above to make them modifier keys.
+
+Note that if you have Alt keys but no Meta keys, Emacs translates Alt
+into Meta.  This is because of the great importance of Meta in Emacs.
+
+** `Pid xxx killed due to text modification or page I/O error'
+
+On HP/UX, you can get that error when the Emacs executable is on an NFS
+file system.  HP/UX responds this way if it tries to swap in a page and
+does not get a response from the server within a timeout whose default
+value is just ten seconds.
+
+If this happens to you, extend the timeout period.
+
+** `expand-file-name' fails to work on any but the machine you dumped
+Emacs on.
+
+On Ultrix, if you use any of the functions which look up information
+in the passwd database before dumping Emacs (say, by using
+expand-file-name in site-init.el), then those functions will not work
+in the dumped Emacs on any host but the one Emacs was dumped on.
+
+The solution?  Don't use expand-file-name in site-init.el, or in
+anything it loads.  Yuck - some solution.
+
+I'm not sure why this happens; if you can find out exactly what is
+going on, and perhaps find a fix or a workaround, please let us know.
+Perhaps the YP functions cache some information, the cache is included
+in the dumped Emacs, and is then inaccurate on any other host.
+
+** Emacs fails to understand most Internet host names, even though
+the names work properly with other programs on the same system.
+  Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
+  Gnus can't make contact with the specified host for nntp.
+
+This typically happens on Suns and other systems that use shared
+libraries.  The cause is that the site has installed a version of the
+shared library which uses a name server--but has not installed a
+similar version of the unshared library which Emacs uses.
+
+The result is that most programs, using the shared library, work with
+the nameserver, but Emacs does not.
+
+The fix is to install an unshared library that corresponds to what you
+installed in the shared library, and then relink Emacs.
+
+On SunOS 4.1, simply define HAVE_RES_INIT.
+
+If you have already installed the name resolver in the file libresolv.a,
+then you need to compile Emacs to use that library.  The easiest way to
+do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
+or LIB_STANDARD which uses -lresolv.  Watch out!  If you redefine a macro
+that is already in use in your configuration to supply some other libraries,
+be careful not to lose the others.
+
+Thus, you could start by adding this to config.h:
+
+#define LIBS_SYSTEM -lresolv
+
+Then if this gives you an error for redefining a macro, and you see that
+the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
+again to say this:
+
+#define LIBS_SYSTEM -lresolv -lfoo -lbar
+
+** Trouble using ptys on AIX.
+
+People often install the pty devices on AIX incorrectly.
+Use `smit pty' to reinstall them properly.
+
+** Shell mode on HP/UX gives the message, "`tty`: Ambiguous".
+
+christos@theory.tn.cornell.edu says:
+
+The problem is that in your .cshrc you have something that tries to
+execute `tty`. If you are not running the shell on a real tty then tty
+will print "not a tty". Csh expects one word in some places, but tty
+is giving it back 3.
+
+The solution is to add a pair of quotes around `tty` to make it a
+single word:
+
+if (`tty` == "/dev/console") 
+
+should be changed to:
+
+if ("`tty`" == "/dev/console") 
+
+Even better, move things that set up terminal sections out of .cshrc
+and into .login.
+
+** With process-connection-type set to t, each line of subprocess
+output is terminated with a ^M, making ange-ftp and GNUS not work.
+
+On SunOS systems, this problem has been seen to be a result of an
+incomplete installation of gcc 2.2 which allowed some non-ANSI
+compatible include files into the compilation.  In particular this
+affected virtually all ioctl() calls.
+
+** Once you pull down a menu from the menubar, it won't go away.
+
+It has been claimed that this is caused by a bug in certain very old
+(1990?)  versions of the twm window manager.  It doesn't happen with
+recent vintages, or with other window managers.
+
+** Emacs ignores the "help" key when running OLWM.
+
+OLWM grabs the help key, and retransmits it to the appropriate client
+using XSendEvent.  Allowing emacs to react to synthetic events is a
+security hole, so this is turned off by default.  You can enable it by
+setting the variable x-allow-sendevents to t.  You can also cause fix
+this by telling OLWM to not grab the help key, with the null binding
+"OpenWindows.KeyboardCommand.Help:".
+
+** Programs running under terminal emulator do not recognize `emacs'
+terminal type.
+
+The cause of this is a shell startup file that sets the TERMCAP
+environment variable.  The terminal emulator uses that variable to
+provide the information on the special terminal type that Emacs
+emulates.
+
+Rewrite your shell startup file so that it does not change TERMCAP
+in such a case.  You could use the following conditional which sets
+it only if it is undefined.
+
+    if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
+
+Or you could set TERMCAP only when you set TERM--which should not
+happen in a non-login shell.
+
+
+* Compatibility problems (with Emacs 18, GNU Emacs, or previous XEmacs/lemacs)
+==============================================================================
+
+** "Symbol's value as variable is void: unread-command-char".
+ "Wrong type argument: arrayp, #<keymap 143 entries>"
+ "Wrong type argument: stringp, [#<keypress-event return>]"
+
+There are a few incompatible changes in XEmacs, and these are the
+symptoms.  Some of the emacs-lisp code you are running needs to be
+updated to be compatible with XEmacs.
+
+The code should not treat keymaps as arrays (use `define-key', etc.),
+should not use obsolete variables like `unread-command-char' (use
+`unread-command-events').  Many (most) of the new ways of doing things
+are compatible in GNU Emacs and XEmacs.
+
+Modern Emacs packages (Gnus, VM, W3, efs, etc) are written to support
+GNU Emacs and XEmacs.  We have provided modified versions of several
+popular emacs packages (dired, etc) which are compatible with this
+version of emacs.  Check to make sure you have not set your load-path
+so that your private copies of these packages are being found before
+the versions in the lisp directory.
+
+Make sure that your load-path and your $EMACSLOADPATH environment
+variable are not pointing at an Emacs18 lisp directory.  This will
+cripple emacs.
+
+** Some packages that worked before now cause the error
+Wrong type argument: arrayp, #<face ... >
+
+Code which uses the `face' accessor functions must be recompiled with
+xemacs 19.9 or later.  The functions whose callers must be recompiled
+are: face-font, face-foreground, face-background,
+face-background-pixmap, and face-underline-p.  The .elc files
+generated by version 19.9 will work in 19.6 and 19.8, but older .elc
+files which contain calls to these functions will not work in 19.9.
+
+** Signaling: (error "Byte code stack underflow (byte compiler bug), pc 38")
+
+This error is given when XEmacs 20 is compiled without MULE support
+but is attempting to load a .elc which requires MULE support.  The fix
+is to rebytecompile the offending file.
+
+** Signaling: (wrong-type-argument ...) when loading mail-abbrevs
+
+The is seen when installing the Insidious Big Brother Data Base (bbdb)
+which includes an outdated copy of mail-abbrevs.el.  Remove the copy
+that comes with bbdb and use the one that comes with XEmacs.
+
+
+* MULE issues
+=============
+
+** A reminder: XEmacs/Mule work does not currently receive *any*
+funding, and all work is done by volunteers.  If you think you can
+help, please contact the XEmacs maintainers.
+
+** XEmacs/Mule doesn't support TTY's satisfactorily.
+
+This is a major problem, which we plan to address in a future release
+of XEmacs.  Basically, XEmacs should have primitives to be told
+whether the terminal can handle international output, and which
+locale.  Also, it should be able to do approximations of characters to
+the nearest supported by the locale.
+
+** Internationalized (Asian) Isearch doesn't work.
+
+Currently, Isearch doesn't directly support any of the input methods
+that are not XIM based (like egg, canna and quail) (and there are
+potential problems with XIM version too...).  If you're using egg
+there is a workaround.  Hitting <RET> right after C-s to invoke
+Isearch will put Isearch in string mode, where a complete string can
+be typed into the minibuffer and then processed by Isearch afterwards.
+Since egg is now supported in the minibuffer using string mode you can
+now use egg to input your Japanese, Korean or Chinese string, then hit
+return to send that to Isearch and then use standard Isearch commands
+from there.
+
+** Using egg and mousing around while in 'fence' mode screws up my
+buffer.
+
+Don't do this. The fence modes of egg and canna are currently very
+modal, and messing with where they expect point to be and what they
+think is the current buffer is just asking for trouble. If you're
+lucky they will realize that something is awry, and simply delete the
+fence, but worst case can trash other buffers too. We've tried to
+protect against this where we can, but there still are many ways to
+shoot yourself in the foot. So just finish what you are typing into
+the fence before reaching for the mouse.
+
+** Not all langu