Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!motcsd!mcdcup!mcdchg!tellab5!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.editors
Subject: Re: Xedit is better than vi and emacs
Message-ID: <1991Apr26.155233.7486@chinet.chi.il.us>
Date: 26 Apr 91 15:52:33 GMT
References: <1991Apr21.011316.13111@zorch.SF-Bay.ORG> <1991Apr23.024525.13795@cs.ucla.edu> <1991Apr24.155049.21710@njitgw.njit.edu>
Organization: Chinet - Chicago Public Access UNIX
Lines: 23

In article <1991Apr24.155049.21710@njitgw.njit.edu> ken@hertz.njit.edu (ken ng cccc) writes:

>Its me.  Let's see.  Let's say you have a pascal program with about a dozen
>or so functions/procedures.  You have already written the procedures, but
>need to refer back to them every so often to get the parameters straight.
>Instead of scrolling through the actual function source code each and every
>time, if you could hide or close off certain sections of code from being
>presently displayable, you could find the functions easier.  If you were
>not sure how function 'foo' works, you could open up/display the text that
>was hidden.

>For example, a hidden procedure:
>procedure foo( var a, b, c : integer);
>----------------------- 6 lines not displayed ---------------------------

If you just want to see something in vi without going there to edit
it, you can use :g/pattern/p or some variation (:g/pattern/-1,+1p).
to get the piece you want to see.  It isn't the same thing at all,
since you can't edit what you see, but it is sometimes handy.


Les Mikesell
  les@chinet.chi.il.us