From owner-freebsd-doc Wed Aug 21 12:35:40 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19049 for doc-outgoing; Wed, 21 Aug 1996 12:35:40 -0700 (PDT) Received: from mail.be.innet.net (mail.be.innet.net [194.7.1.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA18999 for ; Wed, 21 Aug 1996 12:35:24 -0700 (PDT) Received: from cv (pool03-31.innet.be [194.7.10.15]) by mail.be.innet.net (8.7.5/8.7.3) with SMTP id VAA02878; Wed, 21 Aug 1996 21:34:49 +0200 (MET DST) Date: Wed, 21 Aug 1996 21:34:49 +0200 (MET DST) Message-Id: <199608211934.VAA02878@mail.be.innet.net> X-Sender: year0229@pophost.innet.be X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Annelise Anderson From: Chris Vertonghen Subject: Re: vi tutorial Cc: doc@freebsd.org Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:21 18-08-96 -0700, Annelise Anderson wrote: >The arrow keys have always worked for me with FreeBSD (2.0.5 and >later). I think I'm using them in the circumstances where they >supposedly mess everything up. On the other hand if I telnet to a >computer at Stanford running Sun OS 4.1.4, and the arrow keys produce >capital letters. I believe this to be a key-binding problem but I'm not >sure. Just an idea: wouldn't it be much less confusing to talk about the keys as navigation keys (vi and all clones are based on these keys as navigation keys, just *because* not all terminals support the arrow keys). You could simply mention the usage of the arrow-keys in the manual when talking about the possible termemuls that support them... Cya, Chris. #include -- Chris Vertonghen Brilliant Solutions Lanier WorldWide Inc.