From xemacs-m  Tue Apr 29 16:37:02 1997
Received: from argon.roma2.infn.it (lorenzo@ARGON.ROMA2.INFN.IT [141.108.16.147])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA06162
	for <xemacs-beta@xemacs.org>; Tue, 29 Apr 1997 16:37:01 -0500 (CDT)
Received: from localhost (lorenzo@localhost)
	by argon.roma2.infn.it (8.8.5/8.8.5) with SMTP id XAA07519
	for <xemacs-beta@xemacs.org>; Tue, 29 Apr 1997 23:38:46 +0200
Date: Tue, 29 Apr 1997 23:38:46 +0200 (MET DST)
From: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
To: xemacs-beta@xemacs.org
Subject: keyboard mapping, delete-backspace and similar problems
Message-ID: <Pine.LNX.3.95.970429232600.7454C-100000@argon.roma2.infn.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I just compiled xemacs under solaris 2.5.1, and have seen it running. 
I think there is still a small, but ugly problem: both under solaris, and
under linux, I have a key defined as a 'compose' key. The behavior
changes, since, under linux (xfree 3.2), whenever I push multi, I get only

Signaling: (undefined-keystroke-sequence [#<keypress-event multi-key>])

And no character composition.

If I try doing the same under CDE on solaris, I get the same error, but
now I get on my screen both the first typed character and the right
composed one. Something is messy, here...

Still another comment on delete-backspace mapping: I tried some week ago
to ask if there was anybody considering putting FSF's pc-select.el to work
under xemacs. I try another time... to put my case, that way, we could
gain two betterings (sorry for my english!) 
1. delete-backspace 'sensible' mapping
2. an handful of good mappings compliant with any other motif, cde, (say
cua) program, and to some way consistent with the standard mapping on
personal OS's (MacOS, win[39][1-5].) If you have had to try train some
pc-user to use emacs, you should know which kind of troubles does this
mapping save... And, still, this is the only good thing which came from
microsquish in these years... (even though I think it did really come from
PARC and, to a lesser extent, from Apple and IBM, but I'm not sure of my
own memory...)

Yours,


lorenzo

