Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!ux1.cso.uiuc.edu!mrcnext.cso.uiuc.edu!carlson From: carlson@mrcnext.cso.uiuc.edu Newsgroups: comp.sys.next Subject: kill char in csh Message-ID: <800034@mrcnext.cso.uiuc.edu> Date: 24 Feb 90 15:49:25 GMT Lines: 31 Nf-ID: #N:mrcnext.cso.uiuc.edu:800034:000:1602 Nf-From: mrcnext.cso.uiuc.edu!carlson Feb 23 23:23:00 1990 --- Copy of a letter to the mrcnext sys adm (ME) --- From: A disgruntled user... ....When you set stty kill to a certain anything it remembers all previous settings. Example, I presently have it set to control-u but want it to be control-? the delete key. I can change it to it but it remembers the control u which just happens to be the right arrow key on my computer which happens to be right next to the back arrow key, and being the terrible typist that I am I often hit the right arrow instead of the left and I then lose the whole line. It only fouls up when trying to change the kill -- all the others work fine. Any suggestions? --- My response (I myself like ^U just fine) --- Hmmm, I saw a similar problem with erase in 0.8, but I though they fixed it. The problem has nothing to do with stty, it is a bug/feature in csh. To implement some fancy tricks, the csh shell does some input editing (like ^H) itself (see CBREAK mode in tty(4)). Thus csh has its own idea of erase and kill chars, separate from the tty driver. In the new OS, csh was able to keep in sync with the effects of "stty erase" commands, but I guess they missed fixing the kill char. Basically, csh will remember the OLD setting for kill. Thus both the old and new kill char will work. (I tested this.) The work-around for this ain't easy. Basically, you have to change the kill setting, and then RELOAD the shell (exec csh). Not a pretty sight. -------------------- Brad Carlson or University of Illinois--Micro Resource Center--NeXT guru