From owner-freebsd-current Sat Mar 4 10:34:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA05791 for current-outgoing; Sat, 4 Mar 1995 10:34:41 -0800 Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.33.168]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA05781 for ; Sat, 4 Mar 1995 10:34:39 -0800 Received: from localhost (localhost [127.0.0.1]) by gilmore.nas.nasa.gov (8.6.10/8.3) with ESMTP id KAA03581; Sat, 4 Mar 1995 10:35:13 -0800 Message-Id: <199503041835.KAA03581@gilmore.nas.nasa.gov> Reply-To: Dave Tweten To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: backspace now broken Date: Sat, 04 Mar 1995 10:35:12 -0800 From: Dave Tweten Sender: current-owner@FreeBSD.org Precedence: bulk Joerg Wunsch writes: >... people mostly don't expect that key to generate any particular >code (why should they bother with any numerical codes?), they simply >expect it to delete something (instead of printing ^H when pressing >it). On the contrary, since the original IBM PC keyboard, I have never used one that doesn't have both "<--" and either "Backspace" or "Back Space" printed on it. >SysV's tend to use erase=^H, yes, but don't forget: they also use >intr=^? -- so do you wanna change this, too? (But then again, that's >the reason why they map the big grey key to ^H, since their users also >use it to erase text.) None of the above matters a bit to the issue of honest character code generation. Choose what you want. That's what .cshrc or .prolog and stty are for. Continuing to generate a code different from the name on the key only confuses people trying to set up stty and other code-function mappings.