Date: Thu, 23 May 1996 14:39:31 -0400 (EDT) From: "Adrian T. Filipi-Martin" <atf3r@stretch.cs.virginia.edu> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Paul Richards <p.richards@elsevier.co.uk>, Michael Smith <msmith@atrad.adelaide.edu.au>, FreeBSD current mailing list <FreeBSD-current@freebsd.org> Subject: Re: editors Message-ID: <Pine.SUN.3.90.960523143547.9690A-100000@stretch.cs.Virginia.edu> In-Reply-To: <718.832860852@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 May 1996, Jordan K. Hubbard wrote: > As I've already said in another email, from my perspective I just want > things that are _self documenting_ in the installation path so that > you don't have to reach for a stack of books just to install the > system. If you had vi and some sort of "helper" app that actually > showed you the keymap and basic usage instructions in a side window > somehow, I'd happily use it here. > > Jordan Erm... Does ":help" count as "_self documenting_"? It spits out the following brief message: +=+=+=+=+=+=+=+ To see the list of vi commands, enter ":viusage<CR>" To see the list of ex commands, enter ":exusage<CR>" For an ex command usage statement enter ":exusage [cmd]<CR>" For a vi key usage statement enter ":viusage [key]<CR>" To exit, enter ":q!" Needless to say, ":viusage<CR>" lists more than you want to know. Adrian adrian@virginia.edu ---->>>>| Support your local programmer, System Administrator --->>>| STOP Software Patent Abuses NOW! NVL, NIIMS and Telemedicine Labs -->>| For an application and information Member: League for Programming Freedom ->| see: http://www.lpf.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.90.960523143547.9690A-100000>