Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!cwjcc!tut.cis.ohio-state.edu!comp.vuw.ac.nz!nickson
From: nickson@comp.vuw.ac.nz (Ray Nickson)
Newsgroups: gnu.bash.bug
Subject: Re: key binding/stty character conflict
Message-ID: <8907132137.AA09074@comp.vuw.ac.nz>
Date: 13 Jul 89 21:36:11 GMT
References: <8907130427.AA01153@aurel.caltech.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 38


   Date: Wed, 12 Jul 89 21:27:20 PDT
   From: bfox@aurel.caltech.EDU
   
      Date: Thu, 13 Jul 89 10:36:45 +1200
      From: Ray Nickson <nickson@comp.vuw.ac.nz>
   
      ...
   
      BUG: there is a conflict between the shell's interpretation of certain
      keystrokes and the terminal driver's.  In my case, ^C, ^\, ^Z and ^Y are
      bound (by stty) to INTR, QUIT, SUSP and DSUSP, so these keys (^Y in
      particular) are not available for the shell.
   
   ERROR:
   	This is NOT a bug.  This is a design decision.  You are welcome
   	to explain why it is necessary to change the users mind about
   	what keys are special to the kernal.

I initially suspected this was a deliberate decision, and managed to
convince myself otherwise.  I regret (and apologize for) calling it a
bug.

Notwithstanding this, I still feel that most users would prefer `my'
semantics, and intend to communicate with Brian via private email to
discuss this.  I'll leave it up to Brian as to whether he thinks it's
enough of an issue to discuss on the list.

Once again, I really like bash, and hope my comments aren't perceived
as a critisicm of it.  I wouldn't be devoting time to it if I didn't
think it was good software; nothing short of desparation would tempt
me to hack tcsh source!!!  
The beauty of such well-written free software is that we can `agree to
disagree' if necessary and all easily maintain our `own' versions.

-rgn
--
nickson@comp.vuw.ac.nz       ...!uunet!vuwcomp!nickson      + 64 4 721000x8593