Path: utzoo!news-server.csri.toronto.edu!rutgers!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.editors Subject: Re: One user's editor wish list Message-ID: Date: 12 Mar 91 15:12:31 GMT References: <1991Mar11.163554.21156@scrumpy@.bnr.ca> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 20 In article <1991Mar11.163554.21156@scrumpy@.bnr.ca> bnrmtl!lewis@larry.mcrcim.mcgill.edu writes: > 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. ... It's not as nice as emacs, but it's really a useful ability. Of course, until you've used an editor that doesn't let you easily switch between files (say, for example, EDT on VMS) you really can't appreciate it. (I once freaked out a DEC user simply by doing a shell-escape in an "ed" clone I was writing on RSX-11. It's amazing the things you get used to in UNIX that just don't work elsewhere.) > 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). VI does this. I do this all the time. -- Peter da Silva. `-_-' peter@ferranti.com +1 713 274 5180. 'U` "Have you hugged your wolf today?"