From xemacs-m  Sat May 17 06:13:07 1997
Received: from martigny.ai.mit.edu (martigny.ai.mit.edu [18.43.0.152])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA02376
	for <xemacs-beta@xemacs.org>; Sat, 17 May 1997 06:13:07 -0500 (CDT)
Received: from berne.ai.mit.edu by martigny.ai.mit.edu with SMTP
	(1.40.112.8/16.2) id AA214637587; Sat, 17 May 1997 07:13:07 -0400
From: Bill Dubuque <wgd@martigny.ai.mit.edu>
Message-Id: <199705171113.AA214637587@martigny.ai.mit.edu>
Received: by berne.ai.mit.edu
	(1.40.112.8/16.2) id AA159107586; Sat, 17 May 1997 07:13:06 -0400
Date: Sat, 17 May 1997 07:13:06 -0400
To: Gary.Foster@Corp.Sun.COM
Cc: xemacs-beta@xemacs.org
In-Reply-To: <bcienb72oyn.fsf@corp.Sun.COM> (Gary.Foster@Corp.Sun.COM)
Subject: Re: delbs.el

It seems to me that the logical way to do this is to have
virtual keys 'delete-forward' and 'delete-backward' and
for all modes to bind only these virtual keys. Then the user 
can bind whatevery physical keys he desires to these virtual 
keys, and no modes or any other code can end up getting the 
two confused.

I haven't looked at the key-translation stuff so I don't know
if it is general enought to implement this scheme.

Is this how your scheme will work?

-Bill

