Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!rutgers!uwvax!astroatc!nicmad!madnix!zaphod From: zaphod@madnix.UUCP (Ron Bean) Newsgroups: comp.editors Subject: Re: Yet another screen editor (Really: vi commands) Summary: vi's hidden secrets Keywords: vi commands Message-ID: <1710@madnix.UUCP> Date: 24 Jan 91 11:18:39 GMT References: <1991Jan16.230527.3200@cs.uiuc.edu> <3879@pta.oz.au> <1991Jan20.023645.12341@cs.ucla.edu> Organization: MADNIX, operated by: ARP Software Madison WI Lines: 29 In Article <1991Jan20.023645.12341@cs.ucla.edu>, gast@maui.cs.ucla.edu (David Gast) writes: >The trouble with your suggestion is that you have missed the concept of >. Thus, ) represents end of sentence, ( represents >beginning of sentence, } is end of paragraph. [...] >After you have learned how to use vi, you will understand that it is laid >out pretty well. I would guess that most editors seem that way after you've used them long enough. But why should this revelation be reserved until after you've crawled up the learning curve? It might really help people who are still at the bottom. Perhaps an explanation of this should be added to the vi reference sheet that is posted to the net periodically by maart@cs.vu.nl, since it's not in the FM [that is, the vi(1) man page, which is probably what most people turn to when they're told to RTFM]. >...And it works fine until you learn all the objects. Well, for some people it does. Much of the traffic in this newsgroup comes from people whose experiences with vi didn't work so well. ================== zaphod@madnix.UUCP (Ron Bean) {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!zaphod