Path: utzoo!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!convex!news
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.editors
Subject: Re: One user's editor wish list
Message-ID: <1991Mar11.192122.18883@convex.com>
Date: 11 Mar 91 19:21:22 GMT
References: <1991Mar11.163554.21156@scrumpy@.bnr.ca>
Sender: news@convex.com (news access account)
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
Lines: 25
Nntp-Posting-Host: pixel.convex.com

From the keyboard of bnrmtl!lewis@larry.mcrcim.mcgill.edu:
:I got quite a few replies to my original post.  Here are a few followup points.
:
:a) vi supports multiple files
:
:   A few wrote saying that vi does support multiple files.  Well, in a way,
:   it's true, but it's not quite what I mean.  I think I would say that vi
:   supports sequential editing of files (with a rewind possibility (:rew)).
:   At any one point, only one file is in memory.  Except for the possibility
:   of copying stuff from one file to the next, I see little difference
:   between
:      vi eins zwei drei
:   and
:      vi eins ; vi zwei ; vi drei

No, you lose buffer information in the 2nd method, so it's not the same.

:   What I mean for example is, as I edit say some.c, I go for a minute to
:   project.h to add some #define and then come back to some.c in the same
:   spot (the editor of course remembers where one was).

If you use switch between % and # with control-^, vi of course
remembers where you were.  

--tom