From owner-freebsd-current  Mon May 15 11:46:47 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA10713
          for current-outgoing; Mon, 15 May 1995 11:46:47 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA10703
          for <current@FreeBSD.org>; Mon, 15 May 1995 11:46:46 -0700
Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA17457; Mon, 15 May 1995 11:46:32 -0700
From: Poul-Henning Kamp <phk@ref.tfs.com>
Message-Id: <199505151846.LAA17457@ref.tfs.com>
Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H
To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman)
Date: Mon, 15 May 1995 11:46:32 -0700 (PDT)
Cc: terry@cs.weber.edu, current@FreeBSD.org
In-Reply-To: <9505151842.AA18796@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at May 15, 95 02:42:30 pm
Content-Type: text
Content-Length: 673       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> > Of course, this isn't recommended, since in principle, the key should
> > send the ASCII kvalue that its keycap label implies it sends.
> 
> Of course, not all keyboards are the same.  My LK-401 has a keycap
> labeled
>    ___
>   / X|
>   \__|
> 
> and I defy you to state definitively that this symbol implies any
> ASCII code at all.  DEC being typically obnoxious decided to make it
> send BS; I use this magic to make it send something sensible:

It should send an 'X' of course :-)

-- 
Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc.
'All relevant people are pertinent' && 'All rude people are impertinent'
=> 'no rude people are relevant'