From xemacs-m  Mon Aug 25 04:21:19 1997
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id EAA11652
	for <xemacs-beta@xemacs.org>; Mon, 25 Aug 1997 04:21:18 -0500 (CDT)
Received: from Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id CAA29685; Mon, 25 Aug 1997 02:20:49 -0700
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id CAA25335; Mon, 25 Aug 1997 02:20:47 -0700
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id CAA12384; Mon, 25 Aug 1997 02:20:46 -0700
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id CAA17238; Mon, 25 Aug 1997 02:20:44 -0700
Date: Mon, 25 Aug 1997 02:20:44 -0700
Message-Id: <199708250920.CAA17238@xemacs.eng.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: Jan Vroonhof <vroonhof@math.ethz.ch>
Cc: XEmacs Beta Test <xemacs-beta@xemacs.org>
Subject: x-compose.el in 19.16
X-Mailer: VM 6.33 under 20.3 "Vienna" XEmacs  Lucid (beta14)
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>

Here's a change I would like to see in 19.16:

This is a compromise.  Chances are that only those with a Multi_key
will want compose processing, and this will avoid a penalty for those
users who are not going to benefit.

Martin

(mrb@zebu) /set/ipe/sb2/xemacs-19.16-b90/lisp/x11 $ gnudiff -U3 x-init.el.orig x-init.el
--- x-init.el.orig	Wed Aug 20 23:24:18 1997
+++ x-init.el	Mon Aug 25 02:04:42 1997
@@ -83,7 +83,8 @@
 
 (defun x-initialize-compose ()
   "Enable compose processing"
-  (require 'x-compose))
+  (when (x-keysym-on-keyboard-p "Multi_key")
+    (require 'x-compose)))
 
 ;;; Load X-server specific code.
 ;;; Specifically, load some code to repair the grievous damage that MIT and

