From owner-freebsd-mobile Sun Aug 5 16:52:36 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 3288637B401 for ; Sun, 5 Aug 2001 16:52:35 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f75NqXm20023; Sun, 5 Aug 2001 16:52:33 -0700 (PDT) Message-Id: <200108052352.f75NqXm20023@ptavv.es.net> To: Michelle Brownsworth Cc: freebsd-mobile@freebsd.org, "Scott D. Yelich" Subject: Re: ThinkPad X20 keyboard mapping problems In-reply-to: Your message of "Sun, 05 Aug 2001 16:35:15 PDT." Date: Sun, 05 Aug 2001 16:52:33 -0700 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Date: Sun, 5 Aug 2001 16:35:15 -0700 > From: Michelle Brownsworth > > Makes sense. In that case, I guess I'm still confused about why you > wouldn't simply type a CTRL-O from the command line instead of > executing the script. Because most control characters are NOT echoed when typed. Many have special meaning to the shell (e.g. CTRL-C, CTRL-Z, CTRL-J, CTRL...). So the shell typically does not echo them as typed. That's why you need a program that does so. You could really type in the command directly, but the possibility of a typo when you can't read the echo make that impractical for all but the best typists. (The Perl script can easily be compacted into single line, but I see no reason to make it less easily understood.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message