From owner-freebsd-doc  Wed Aug 21 13:17:47 1996
Return-Path: owner-doc
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA22685
          for doc-outgoing; Wed, 21 Aug 1996 13:17:47 -0700 (PDT)
Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA22675
          for <doc@freebsd.org>; Wed, 21 Aug 1996 13:17:44 -0700 (PDT)
Received: from localhost (localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.7.5/8.6.12) with SMTP id NAA00315; Wed, 21 Aug 1996 13:17:25 -0700 (PDT)
Date: Wed, 21 Aug 1996 13:17:25 -0700 (PDT)
From: Annelise Anderson <andrsn@andrsn.stanford.edu>
To: Chris Vertonghen <chrisv@brilliant.net>
cc: doc@freebsd.org
Subject: Re: vi tutorial
In-Reply-To: <199608211934.VAA02878@mail.be.innet.net>
Message-ID: <Pine.BSI.3.94.960821131004.306A-100000@andrsn.stanford.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-doc@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Wed, 21 Aug 1996, Chris Vertonghen wrote:

> 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.

I discovered that the arrow keys work on Sun OS 4.1.4 provided one
calls nvi instead of vi.
> 
> Just an idea: wouldn't it be much less confusing to talk about the <hjkl>
> 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...

I think that's what Gary Kline is doing.  It turns out, I think, that
people use vi in many different ways, since it has so many options.  This
is part of what makes it difficult to write a tutorial.  
	
					Annelise 
> Cya,
> Chris.
> 
> 
> #include <disclaimer.h>
> --
> Chris Vertonghen <chrisv@brilliant.net>
> <a href="http://www.brilliant.net">Brilliant Solutions</a>
> <a href="http://www.lanier.com">Lanier WorldWide Inc.</a>
> 
> 
>