From xemacs-m  Tue Apr 29 16:49:36 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 QAA06241
	for <xemacs-beta@xemacs.org>; Tue, 29 Apr 1997 16:49:35 -0500 (CDT)
Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA04262; Tue, 29 Apr 1997 14:58:29 -0700
Received: from legba.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3)
	id OAA16218; Tue, 29 Apr 1997 14:48:49 -0700
Received: by legba.Corp.Sun.COM (SMI-8.6/SMI-SVR4)
	id OAA08744; Tue, 29 Apr 1997 14:48:41 -0700
To: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
Cc: xemacs-beta@xemacs.org
Subject: Re: keyboard mapping, delete-backspace and similar problems
References: <Pine.LNX.3.95.970429232600.7454C-100000@argon.roma2.infn.it>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Gary.Foster@Corp.Sun.COM (Gary D. Foster)
Date: 29 Apr 1997 14:48:33 -0700
In-Reply-To: "Lorenzo M. Catucci"'s message of Tue, 29 Apr 1997 23:38:46 +0200 (MET DST)
Message-ID: <bciyba1cxfy.fsf@corp.Sun.COM>
Lines: 20
X-Mailer: Gnus v5.4.46/XEmacs 20.2(beta3)

"Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it> writes:

> 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...)

Perhaps this could obviate the plea I made earlier for delbackspace
being fixed?  I'd help out here instead, if so. :)

-- Gary F.

