From xemacs-m  Wed Mar 26 04:35:52 1997
Received: from argon.roma2.infn.it (ARGON.ROMA2.INFN.IT [141.108.16.147])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id EAA25485
	for <xemacs-beta@xemacs.org>; Wed, 26 Mar 1997 04:35:39 -0600 (CST)
Received: from localhost (lorenzo@localhost)
	by argon.roma2.infn.it (8.8.5/8.8.5) with SMTP id LAA23582
	for <xemacs-beta@xemacs.org>; Wed, 26 Mar 1997 11:35:29 +0100
Date: Wed, 26 Mar 1997 11:35:29 +0100 (MET)
From: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
To: xemacs-beta@xemacs.org
Subject: The 'Compose' (read 'Multi_key') key handling
Message-ID: <Pine.LNX.3.95.970326112928.23554A-100000@argon.roma2.infn.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dear readers,
	I have just seen the announce for the final release of
Xemacs-19.15, and therefore I'm sure pc-select didn't get in. Sad to
know... I forgot, in my last mailing, to report a small problem in X
keyboard handling: while the last stable version honored the Compose key I
have defined in my own keymap, which is useful if you have to write in
foreign languages (I use an italian keyboard, but sometimes I write about
german people, like Schr\"o dinger, and the direct composition is nicer). 

A second problem releated to the X11 keyboard handling comes from getting
something very near to raw keys, which broke my global
'Shift-Return'->'Linefeed' mapping. Is there some way to get back to the
previous behavior?

Yours


lorenzo m catucci

