From xemacs-m  Fri Aug 15 09:00:05 1997
Received: from cs.sunysb.edu (sbcs.sunysb.edu [130.245.1.15])
	by xemacs.org (8.8.5/8.8.5) with SMTP id JAA22311
	for <xemacs-beta@xemacs.org>; Fri, 15 Aug 1997 09:00:04 -0500 (CDT)
Received: from sbkifer.cs.sunysb.edu (sbkifer.cs.sunysb.edu [130.245.1.35]) by cs.sunysb.edu (8.6.12/8.6.9) with SMTP id JAA04347; Fri, 15 Aug 1997 09:59:13 -0400
Message-Id: <199708151359.JAA04347@cs.sunysb.edu>
X-Authentication-Warning: sbcs.cs.sunysb.edu: Host sbkifer.cs.sunysb.edu didn't use HELO protocol
From: kifer@CS.SunySB.EDU (Michael Kifer)
To: Kyle Jones <kyle_jones@wonderworks.com>
cc: xemacs-beta@xemacs.org
Subject: Re: C-h, (control h), backspace breakage 
In-reply-to: "Kyle Jones" of Thu, 14 Aug 1997 19:42:58 EDT
             <QQdcpy13147.199708142342@crystal.WonderWorks.COM> 
Date: Fri, 15 Aug 1997 09:59:12 -0400
Sender: kifer@CS.SunySB.EDU

>>>>> "KJ" == Kyle Jones <of Thu, 14 Aug 1997 19:42:58 EDT> writes:

    KJ> Michael Kifer writes:
    >> But most weird and inconsistent is the fact that if I now evaluate:
    >> 
    >> (defun test2 ()
    >> (interactive)
    >> (message "bound-to-C-h")
    >> (sit-for 2))
    >> (define-key global-map "\C-h" 'test2)
    >> 
    >> Then BOTH the backspace key and Control-h become bound to test2!
    >> 
    >> I doubt that this is by design.

    KJ> Probably is by design.  If not, it still makes sense.

    KJ> "\C-h" is old syntax, hence old behavior.
    KJ> [(control h)] is (relatively) new syntax and hence new behavior is
    KJ> allowed. 

It does make sense. My question was: does it make GOOD sense?


	--michael  



